Replies: 1 comment 1 reply
-
The problem is, I can't confirm this (yet). All of my plugins work perfectly fine. So I need a server log of pre-beta6 and beta6 where the server performs a full plugin scan. That way - if it is an issue - I will see the plugins with different IDs and can focus on them. But so far I believe JUCE is fine. |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
So far it seems that beta 6 with update Juce framework has broken plugin ID. It means that some (a lot, but not all) plugin wont be find anymore because their internal ID has changed.
Not sure there is an easy workaround for that, and it breaks totally compatibility with old project.
But I guess that the priority is stability and support of recent juce version. so I can live with that
One simple workaround would be at least to load the AG chain and make it run even if a plugin is not found in the chain (see how cubase handle that when a plugin is missing, it bypass it and highlight the missing plugin which exclamation marks).
Can you implement that ?
Currently it is the worst scenario : sandbox terminated if a single plugin is not found and the whole AG chain and insert is disconnected and stop sounds.
Beta Was this translation helpful? Give feedback.
All reactions