Hi,
I previously reported a similar issue, but I am posting again because this problem continues to occur frequently. At this point, I believe this is likely a bug rather than an isolated project or file corruption issue.
I am using Synthesizer V Studio Plugin V2 as an ARA2 plugin in Logic Pro.
System Environment:
-
Synthesizer V Studio V2: 2.2.1
-
macOS: Ventura 13.7.8
-
CPU: 4.2 GHz Quad-Core Intel Core i7
-
DAW: Logic Pro 10.8.1
-
Plugin: Synthesizer V Studio Plugin (ARA2 / V2)
The problem
When I save a project and later reopen it, the Synthesizer V plugin’s BPM is sometimes reset to 20 BPM and becomes stuck there.
This causes a serious problem during rendering.
Because the BPM is incorrectly set to 20, rendering becomes extremely slow. In some cases, the rendering does not finish and Synthesizer V eventually becomes unresponsive/freezes.
This makes the saved project effectively unusable until the problem can somehow be resolved.
What I have observed
-
The problem occurs repeatedly, not just once.
-
It can happen after saving and reopening a project.
-
The BPM is set to 20 BPM instead of the project’s actual BPM.
-
The BPM remains stuck at 20.
-
Rendering becomes extremely slow and may never finish.
-
The plugin may eventually freeze while rendering.
-
I do not experience this problem with the Synthesizer V V1 plugin.
I have also previously experienced the playback position becoming incorrect/locked after the BPM synchronization fails.
Troubleshooting
I have tried:
-
Disabling/re-enabling the bridge
-
Manually entering the correct BPM
-
Using BPM synchronization / Match BPM
-
Resetting the bridge
-
Reopening the project
However, the problem can return after saving and reopening the project.
Since this has happened repeatedly, I am beginning to suspect that there is a bug in the V2 ARA2 implementation, particularly with Logic Pro on Intel-based Macs running Ventura.
Has anyone else experienced the BPM being reset to 20 BPM when reopening a saved project?
And is this a known issue in Synthesizer V Studio V2.2.1?
Any information about a workaround or upcoming fix would be greatly appreciated.
Thank you.