-
Notifications
You must be signed in to change notification settings - Fork 404
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Surge XT CLAP instances from prior projects not loading in Bitwig 5.0 #6928
Comments
This seems like it might be a Bitwig beta issue but let's see. |
I’ll grab 5 on my Mac today and look to see if I can repro. If yu can attach the engine.log that would also be super. I also flagged this issue to my friends at the bw clap team. |
I can confirm that with Surge XT 1.2.0 on macOS 12 a project saved in BWS 4.4.5 loads fine in 5.0 beta 2. So this might be a windows thing or may be a sporadic other-thing. |
Hi, |
Also if you have access to Bitwig's engine logs, could you attach them to the issue please? |
If you try to reload the device/project/engine 10 times, does is consistently fails or sometimes it works? |
This issue is fixed in Bitwig 5.0 Beta 3 (will be released later). |
BTW, it only affects Windows. |
Thanks @abique !! |
Wow, that was fast. Saved me some tinkering this evening. Many thanks! |
Congrats on the recent release!
In Bitwig 5 Beta 2, on Windows 10, on an Intel i7-3770 CPU, I've loaded two different projects previously saved in Bitwig 4.3.10, including tracks created with Surge XT v1.1 (one project) and v1.2.0 (the other project), CLAP version, 64-bit. When I open the projects with Bitwig 5 Beta 2, the instance(s) of Surge won't load properly. Each instance of Surge yields the message, "Could not load plug-in. Could not load initial plug-in state: Couldn't load the plugin state".
Attempting to reload the plug-in doesn't help. The only option is to load a new instance of Surge XT, but this results in losing any Bitwig modulators that were assigned to the existing instance of the synth.
I've also tried reinstalling Surge XT 1.2.0, and that didn't help (although Surge still opens fine in Bitwig 4.3.10).
I've reported this issue to Bitwig tech support as well.
The text was updated successfully, but these errors were encountered: