I’m using Synthesizer V Studio 2 Pro version 2.0.6 in a fresh project in Cubase 14.0.20 (newest available as of time of writing) under macOS 14.7.2 (23H311). The project uses the provided ARA integration to sync up the editor to my project. Setting this up requires that the actual plugin is loaded before loading the ARA integration (otherwise it crashes Cubase), but works fine otherwise. However, when trying to edit the tempo track, the second I try to set a new tempo, Cubase crashes. The crash is due to a segfault:
As I use the ARA Bridge and not full ARA mode, I simply delete the extension on the audio track, turn off the Bridge Synch in the VST plug-in and complete my tempo track changes and only then add the extension again to the audio track and re-enable the Bridge.
Remembering to save periodically, of course.
I’m not sure, but think that the VST is re-rendering the vocals every time a minor adjustment is being made in the DAW so just crashes.
Yes, the VST re-renders the vocal line with every change we make.
I wish they would give us a render ‘button’ that can either be in the ‘latched’ state (which would immediately render all changes, i.e., the way it functions now), or the ‘momentary’ state that you click to render all changes just once. I think this will minimize some of the plugin’s instability (which is fairly bad for me in Cubase).
One thing that helps is to set the track to “Unload the Voice” so that a waveform is not generated. I do this when reading in (recording) MDI notes. If you choose an actual voicebank, the VST has trouble rendering the notes to audio in realtime and frequently crashes.
Once the notes have been recorded and I’m ready to make edits, I then select a voicebank to hear what the performance sounds like.
Unfortunately, I have to report that in my case SV2 2.0.7 also crashes Cubase 14.0.20 heavily when inserting a tempo track to the song! So, I guess the same error still persists as for V2.0.6! @Bobox: I will try now the workaround you described above to temporarily disable the ARA bridge and re-enable it later again. Let’s see if this at least works…
Even though I was very enthusiastic at the beginning, after having purchased SV2 and hearing the great voices the first time, I guess my joy has gone in the meantime. The longer I’m seriously working with that piece of software, the more I’m realizing that it’s still in a kind of “beta status”. It’s very unfair to let paying customers explore all the flaws which have obviously not been fixed yet. Maybe SV2 shouldn’t have been released in such an insecure condition and more time should have been spent by the Dev Team to make sure that it really works on all platforms and major DAWs! I’m very disappointed right now.
I just tried to disable the ARA bridge while adding the tempo track in Cubase. Then I added some tempo changes and re-enabled the ARA bridge again in order to continue working on the SV2 voice track. Thanks to @Bobox for pointing this trick out.
However, even if you want to edit some of your created tempo points within Cubase at a later time, e.g. in order to do some “fine-tuning”, the ARA SV2 bridge will freeze again if you don’t disable it again. If not doing so, its location curser won’t sync anymore with the Cubase timebase and some weird stuff may be going on. As a consequence, you must remove the ARA bridge every time you intend to change a single thing in the tempo track, otherwise you will risk to destroy your Cubase song again, especially if you save it in such a state.
@B.Minor sorry to read you’re having difficulties - so I re-tested Cubase Pro 14.0.20 with SV2 2.0.7 and found no difficulty with tempo changes on Windows 10 Pro 19045.5737…
I think SV2 makes an educated guess at ramped tempos and just averages it - would be nice if it offered to average it out over a given division, ie 1/4 notes / 1/8 notes, etc… so we don’t have (as in this case) Nyl singing too fast and then too slow against the ramped tempo change. Cubase doesn’t offer ramp to step conversion at the moment - if it ever will ???
