Synth V crash in Logic - auto-save?

Haven’t used Synth V in about a year except continuously upgrading to the latest version (not beta). Yesterday I finally used Synth V as a plugin in Logic and everything worked great! But al of a sudden Synth V behaved weird and crashed and so did Logic. When I restarted Logic and used the auto-saved project all my work was there except for Synth V. Checked the Dreamtonics “recovery” folder but there was only a file from Jan 22 2022! So about four hours of Synth V work was gone… :sob:
This is a bit strange as all the other plugin settings and states were saved in the Logic auto-save project.
Is this one reason why some prefer to use Synth V only as standalone?
Is there some setting in Synth V that must be enabled for auto-save to work?

Yes, I’m thinking in the ‘Save with DAW’ menu or something like that

1 Like

I just found this under File when used as plugin. Maybe that will work?

Skärmavbild 2023-10-05 kl. 09.59.53

1 Like

Yes, that’s exactly what it is. Works great for me with Cubase

1 Like

But be careful. If your DAW crashes and doesn’t boot anyhow, you can never get your project back.

1 Like

Logic rarely crashes on my system and if it does the auto-save feature saves the day. And now I can see that the Synth V recovery file is continuously updated as I make changes. I will use this workflow for a while and hope that it is reliable.

Ive tried the plugin once in logic, it crashed after a few seconds… since then Ive used the stand alone… too afraid to test again :joy:

Maybe you should try again? I have now used it extensively in Logic for two days and the crash may actually have been caused by me! :crazy_face:

1 Like

Yes…maybe when starting a new project :thinking:… i hate losing the work because of a crash…and i actually think it works nice with the stand alone… but i can imagine it is better with a working plug in :roll_eyes::blush::+1:t4:

1 Like

I believe that the reason for the crash was that I happened to start the transport in the plugin and while it was running I clicked on the Logic interface and started the Logic transport. This meant that both transports were running but totally out of sync. When I realized what had happened I clicked on Synth V again to stop its transport (while Logic transport was still running). But Synth V did not respond and then the crash happened. So I believe that I accidentally caused that crash. It is convenient that the Synth V transport works independent of Logic when the Synth V interface is selected. Works great when entering and editing notes. But it must be stopped before starting Logic transport. At least I think so.
Maybe there is some setting that would change this behavior but I like the way it works now.

2 Likes