It uses a Wordpress JavaScript tracker:DJ_Indikator wrote: Sat Jul 05, 2025 11:37 pm I don't care what the Bitdefender says. I have no time to move http->https. My site don't collect any information like email, don't use coockies, it's simple information.
Code: Select all
http://mak-sa.net/software/wp-content/plugins/wp-statistics/assets/js/tracker.js?ver=14.14.1
It's only statistics plugin (https://wp-statistics.com/) without any coockies. There no email collected. Only visitors staticstics (pages show per day, per month, etc). I think bitdefender warning about there no https. My site only http nowFranklyFlawless wrote: Wed Jul 09, 2025 2:20 pmIt uses a Wordpress JavaScript tracker:DJ_Indikator wrote: Sat Jul 05, 2025 11:37 pm I don't care what the Bitdefender says. I have no time to move http->https. My site don't collect any information like email, don't use coockies, it's simple information.Code: Select all
http://mak-sa.net/software/wp-content/plugins/wp-statistics/assets/js/tracker.js?ver=14.14.1
Yes, but only after linux
Did you implement CLAP with the thread pool feature?DJ_Indikator wrote: Sun May 11, 2025 12:01 pm VST3/CLAP support is finally done. But it definitely needs more in-depth testing. As for the formats themselves - VST3 has too many helpers and too much mosaic documentation. Some things have to be literally searched for bit by bit on the Internet. Steinberg's own documentation system is completely confusing - a bunch of sites, a ton of links. Of the ton of SDK files, you actually need 3 dozen. Very difficult. With CLAP, the situation is completely opposite - everything is simple and clear. One header clap.h, and an extensions system. Very easy to embed into the code. True, unlike VST3, some difficulties were precisely in the lack of documentation. Of course, the comments in the header files are written very well and clearly, but some things were not immediately clear. For example, start_processing / stop_processing is it even needed or not? But overall - a good format. Information about the product is still there www.mak-sa.net/software
In the near future - I continue to do UNDO/REDO and write workflow documentation.
Cheers
is this really necessary? CLAP is only api. the plugins render of course uses thread pool for multi core cpu support
/// This extension lets the plugin use the host's thread pool.
///
/// The plugin must provide @ref clap_plugin_thread_pool, and the host may provide @ref
/// clap_host_thread_pool. If it doesn't, the plugin should process its data by its own means. In
/// the worst case, a single threaded for-loop.
Interesting idea (read here https://cleveraudio.org/1-feature-overv ... read-pool/) but this need to remake my audio engine. And the audio engine will become much more complex. This will also close the possibility of manual distribution of cores by plugins, which I have already implemented. I will add this to the list of features for the future.llze wrote: Tue Jul 22, 2025 10:38 am I'm not too deep into this, I just noticed that some other DAW didn't implement CLAP support with thread pool and that causes some issues. It's beneficial performance wise to do so, but no hard requirement afaik.
You may also contact support(at)uhe.com to chat about ways to implement it, maybe they have some simple best practice or can channel you to a Discord server to discuss this further if questions arise.DJ_Indikator wrote: Tue Jul 22, 2025 9:37 pmInteresting idea (read here https://cleveraudio.org/1-feature-overv ... read-pool/) but this need to remake my audio engine. And the audio engine will become much more complex. This will also close the possibility of manual distribution of cores by plugins, which I have already implemented. I will add this to the list of features for the future.llze wrote: Tue Jul 22, 2025 10:38 am I'm not too deep into this, I just noticed that some other DAW didn't implement CLAP support with thread pool and that causes some issues. It's beneficial performance wise to do so, but no hard requirement afaik.
I think the guys from uhe won't want to discuss this topicllze wrote: Wed Jul 23, 2025 6:45 am You may also contact support(at)uhe.com to chat about ways to implement it, maybe they have some simple best practice or can channel you to a Discord server to discuss this further if questions arise.
The idea of requesting a thread pool from the host is exactly about (partially) making host developers rack their brains over thread distribution I, in turn, put this on the user, giving the ability to manually distribute the load across cores. That is, the user can manually specify which plugin should work on which core. In my "to do in the future" list there is an item about distribution across cores depending on the plugin load. But that's for later. 
Cool stuff, I started with SoundFX and SoundTracker on Amiga, on C64 I tinkered a bit.DJ_Indikator wrote: Sat May 24, 2025 8:56 pmYeah, i start with ProTracker 2 on AmigaDrew Lake wrote: Sat May 24, 2025 11:18 am By the way I love the Amiga style pointer, it's fun! My first taste of Music Production was when I was a kid. It was OctaMED v4 (then later v5) on my Amiga 500+. So you can see why I am looking forward to see how this DAW develops and being able to use it.
Submit: News, Plugins, Hosts & Apps | Advertise @ KVR | Developer Account | About KVR / Contact Us | Privacy Statement
© KVR Audio, Inc. 2000-2026