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
Ok so, several days ago I opened a project, version about 100 (save as new). I had there about 8 modulations. Mostly assigned to panning.
I had to remove all of them and replace with a panning plugins.
Some of them lost connections.
One lost connection, but visually it was showing connection but the knob didn’t had position indicator anymore. Almost like w physically broken parameter ![]()
There were some other glitches like wrong settings etc.
For me, modulators don’t exist. I’m treating this feature as non-existent. It’s way too buggy and unpredictable. I can’t trust modulators.
I’m sad that Steinberg couldn’t provide solid feature that I was hoping to have in Cubase for a very long time.
Yes, it seems more like a beta or even alpha state feature that made it into a release version by accident - a proof of concept that lacks integration protocols that a working/creative user would need, and bugs.
It’s really unfortunate, I was doing some very cool things with them… Like every so often, you feel like you are the only person in the world who has discovered something (even if not) and I got that with some techniques I developed with Modulators… So excited and motivated to implement them into my work and art - but nope… There is no way, I could deal with connections being lost on a day to day basis. That’s a complete show-stopper along with basic integration like duplication along with track duplication.
I had entire experimental/creative projects and albums planned around their use, all shelved now.
Hopefully someone from @Steinberg_ProAudio , @Matthias_Quellmann or someone like @Arne_Scheffler who I believe was involved, can give us a timeline/roadmap on when this will be fixed/improved…
I’m just happy some users were finally able to confirm this problem as I was about to descend into a paranoid breakdown of why this is only happening to me…
Plenty of features are added in a beta state then fixed in the next paid version. Sometimes it stays buggy for years. This is unfortunate.
It was supposed to change with the new beta testing they introduced to the bigger pool of people but we are yet to see the results.
The growing technical debts can be felt in more and more parts of Cubase when you read this forum. I hope that they’ll improve. Otherwise I may quit paying for the new versions at some point. What’s the point of new features if I can’t use them?
This is what I am thinking as well,
Every time they come up with a new feature I like/wanted, it seems half-implemented, buggy, and better not used than used… I would have rather not updated and not have my creative world and flow disturbed with false excitement and technical issues.
Really hoping this isn’t going to be one of those bugs that has radio silence from the devs and isn’t fixed for years…
This is happening to me as well. I’m on macOS 27.0.1, Cubase 15.0.30. Please look into it.
Interesting so it is happening on mac.
It seems like one thing they did fix in the recent update was user entered modulator names actually being saved with the project, but I don’t see anything in the release notes on this problem being fixed… really sad and unfortunate. An amazing feature completely unusable for anyone other than someone who is just fiddling around without a care of their work being preserved… professionals, commercial studios, artists - cannot use this feature.
@Ed_Doll Is there any comment on this?
I’d seen that Modulator re-Names are now saved with projects in the latest 15.0.4 patch, but it says nothing about the connections issue
Hi, I just did the test on Win10 and confirmed.
This issue seems to only happen when reactivating projects.
The pattern looks like
Load project A - ok
Load project B and activate - ok
Activate project A - chance of only 1 modulator
Activate project B - chance of only 1 modulator
Activate project A - chance of only 1 modulator
Cubase 15.0.40
Win10
So, there is maybe a chance that some of have saved a project after this corruption? At least you should be able to avoid it if you avoid reactivating and instead close projects fully before opening another? I have had multiple projects open before but I don’t really do that very often.
I believe the issue can occur via just opening a project, but i don’t think that test has been confirmed.