Don’t undertake a project unless it is manifestly important and nearly impossible.
quote of the day
March 6, 2024 by 1 Comment
sound affairs & audio effect design
Don’t undertake a project unless it is manifestly important and nearly impossible.
― Edwin Land, Founder of Polaroid
This site uses Akismet to reduce spam. Learn how your comment data is processed.
Francesco on what I’m currently working on… | |
devidesilva4567 on ‘epicVerb’ digital… | |
deivide santana on ‘epicVerb’ digital… | |
deivide santana on ‘epicVerb’ digital… | |
【令和最新版】音MAD作者に聞くVSTア… on epicPLATE mkII released | |
epicPLATE: Free Vint… on epicPLATE released | |
jure on what I’m currently working on… |
I can’t find a better place to post this. Sorry.
OFF TOPIC: I recently had an issue with the Three-Body Technology’s Cenazoix Compressor plugin’s GUI locking up in one Reaper project and spent time trying to track it down. They resolved it and sent me an email that had this section:
“Thanks so much for providing all the details, and sending over your project.
Finally, after days of testing, we believe we were able to track down the problem that was going on in your project!
It was actually a conflict with BaxterEQ, epicPLATE and all the plugins from the same developer.
All their plugins as well as Cenozoix require a particular API by Windows for some kind of use, while the API has its limitation.
If we load a number of those plugins that reaches the API’s limitation, the newerly loaded ones may produce issues, depending on how they utilize the API.
In the case of Cenozoix, it uses the API to trigger GUI rendering. That will unfortunately lead to the locked up GUI when the API was fully occupied by the formerly loaded plugins.
That is why sometimes Cenozoix would be back to normal after you reopened the project or replaced another plugin with it. So yes, it was a loading problem, caused by the order that Cenozoix was loaded.
The good news is, we will solve this problem by changing the way to trigger GUI rendering in the next update.
…It is worth mentioning that Cenozoix only uses the API once in each project, no matter how many instances it was loaded on (which is considered as the common way).
On the other hand, every instance with a plugin by that developer requires the use of that API. That makes it easy to reach the limitation in a big project.
We recommend not to use too many of them in the same project (even when you are not using our products) to avoid any potential issues with display, sound or something internal, which might appear due to the heavy use of the API.”
I thought I’d send this along. This is all well over my paygrade but maybe it’s useful information. I tried to find an email to send this but couldn’t. Delete it any time.
Thanks, tb