Unfortunately the connections are not getting stored. It would make sense if duplicating a track or importing it from a different project would grant the connections to persist but that does not seem to be the case. No idea why the Volume plugin keeps the connection for the Gain parameter, though. That’s weird.
I can 9nly add that I had this issue at least once. I had to go many versions back to find the one where the connection was still there.
It can be annoying when working on a large template with a progressive arrangement (even more in a sound design project) where some sections are checked only once in a while (sometimes even after a year or so). In my case I had to go back to a version from around 3 weeks back.
Now, with more complex modulations I’m writing the details in the Notepad - just in case. But unfortunately, like some other Cubase features, I’m using it less than I would like to because I can’t trust the reliability. Those damn ultra rare, hard to reproduce bugs are so annoying.
Of course I don’t have any proof anymore. It’s just a wee +1.
EDIT: MacOS Sequoia (latest). Mac Mini M2.
I didn’t observed it on Win11 but I rarely use modulators there.
I did the test as explained and it worked as expected. I switched between projects at least ten times. Modulator connections stayed intact.
I´m on macOS Tahoe.
I can confirm that, when importing the track with the modular to a new project only the first connection gets imported.
Interesting,
So there at least 2 examples of no problem - one on Win10, the other on macOS. (I’m on Win11)
yet, maybe there is some relation in my problem and the integration in general… how modulators are loaded…
I wonder if this could be some kind of buffer/timing/load-time/memory/etc difference that results in no problem vs problem.
@battleangel @user299 @Feeelix
What OS are you?
MacOS Sequoia
I tried your steps now and after a lot of reactivating the project back and forth, all except the first connection dissapeared. Interesting was, that after a few more back and forth of activating the two projects, they also re-appeared. And after even more they also dissapeared again. So it seems to be some kind of gamble if they get resored properly.
All of that happend in my case only in the second (‘save as new version’) version so far.
But in my original thread (that you quoted) I mentioned the problem in a project that was still the original version of the project and not a duplicated or something like that (and there it was also with other plugins, not only with steinberg and not only with volume)
Also the duplicating of tracks didn’t copy the modulators exept for the first one. When the project was in the state where on the original track the connections were gone, on the duplicated tracks all connections were gone.
So it seems as this bug is reducing the count of connections by 2. On the track with orig. 3 connections only 1 remains, and on the tracks with 1 none remain.
Win11, Cubase 15.0.30
Thanks for taking the time to test this,
this is the first clear confirmation I’ve had from someone else,
btw, which OS are you?
@Matthias_Quellmann If I can bring another thread to your attention:
This bug has now been confirmed by another user: (above)
I had done a little over a month of pre-production on a planned project that was going to heavily utilize Cubases Modulators - from writing ModScripts, to creating massive stacked project templates, to preliminary sound-design, sample recording, assignment mapping etc, etc - and I booked a month of studio time in the fall/winter… As of now, all out the window because of this bug, as well as lack of integration/bugs.
lack of integration thread:
Modulator Management/Integration/Protocol (Currently there is no way to save complex setups) - Cubase - Steinberg Forums
Thanks, wishing you good