1.11.0b2 crashing with Ableton Live 11.3.13 on loading project

Product Feedback / 产品反馈 / フィードバック
,
1

Hi there. I recently purchased SynthV. I’ve been using it in a project and it won’t load without my DAW crashing. The crash happens 1 sec after the project has loaded.

SynthV version: 1.11.0b2 (also tested v1.10.1)
Live version: 11.3.13

Live’s log shows this before the crash:

2024-01-11T16:04:07.089384: info: VST3: Going to create: Synthesizer V Studio Plugin
2024-01-11T16:04:07.643871: info: VST3: plugin processor successfully loaded: Dreamtonics Co., Ltd. 'Synthesizer V Studio Plugin' v1.10.1 (cid: {ABCDEF01-9182-FAEB-4474-6E6353565232})
2024-01-11T16:04:07.643989: info: VST3: plugin processor doesn't reveal routing info, attempting to determine output bus ourselves
2024-01-11T16:04:07.644278: info: VST3: plugin supports the IInfoListener interface
2024-01-11T16:04:07.645293: info: Vst3: couldn't initialize controller with processor state of Synthesizer V Studio Plugin: not implemented
2024-01-11T16:04:07.645300: info: VST3: parameter count is 2081
2024-01-11T16:04:07.646323: info: VST3: Created: Synthesizer V Studio Plugin
2024-01-11T16:04:07.652170: info: VST3: couldn't get controller state of Synthesizer V Studio Plugin: not implemented
2024-01-11T16:04:08.241631: info: Python: ERROR:_MxDCore.MxDCore:241 - Error: Changes cannot be triggered by notifications. You will need to defer your response.
2024-01-11T16:04:08.241697: error: Message from Max: jsliveapi: Changes cannot be triggered by notifications. You will need to defer your response.
2024-01-11T16:04:08.242725: info: Python: ERROR:_MxDCore.MxDCore:242 - Error: Changes cannot be triggered by notifications. You will need to defer your response.
2024-01-11T16:04:08.242766: error: Message from Max: jsliveapi: Changes cannot be triggered by notifications. You will need to defer your response.

At first glance this seems to be a Max for Live issue, but the problem only persists when SynthV is loaded. When I delete the VST3 file so that it doesn’t load, the project loads as usual. I’ve also tried uninstalling SynthV and installing the stable version, but the same problem persists.

Update: when opening Live in Rosetta the project does load. Not an optimal situation.

「いいね！」 1
2

adding that as soon as I load the 1.11.0b2 ARA plugin, Live Suite 11.3.13 crashes immediately.

Windows 11 here.

3

Ableton Live does not have ARA2 support. You can only use the regular VSTi / AU instrument with DAWs that don’t support the ARA protocol.

「いいね！」 1
4

ah. For my part I didn’t think it would even show up since that’s the case, and went looking after seeing posts about it trying to collect more data :woman_shrugging:t2:

5

Thank you Claire. I think this is the BEST ANSWER. I’ve been having the same problem as the OP. I deleted the VST3 for Synthesizer V so that my session simply could be reopened without crashing (of course, that means the plugin and the work I put into it are gone). I then put in the AU plugin, saved and reopened, and that seems to work without crashing. SO . . . anyone else reading this, if using Ableton and Synthesizer V on a Mac DO NOT use the VST3, even though it will work within the session (up until you try re-opening it).

As an aside for folks finding this page . . . I also appreciated another suggestion I read to re-open Ableton using Rosetta. That allowed me to open the session without crashing, which then gave me the chance to save my stems. However, when I tried to delete my offending Synth V tracks (even using Rosetta), that simple step would crash Ableton.