[CAN-13042] Multi out instrument tracks still broken after disabling PLEASE RESPOND STEINBERG

even with a “fresh” Cubase 9 project… :wink:

Raphie - yes, even with a fresh Cubase 9 project. Totally starting from scratch.

I’ve followed the bug report procedure as much as possible, but we’ve found it impossible to find the exact set of things that screw it all up. It just happens. Stuff that works one day are screwed the next. But I’m all ears for any advice on how to further escalate it with Steinberg, perhaps a support ticket pointing to this thread?

have sent this problem too steinberg many month ago with a description to reporudce it and a zip project file. No response. I guess they know about it … seems hard for them to fix though… Is CAN-13042 the official number issue that was assigned to this problem ?

Yes. It’s been pretty tortuous getting this far, but as of last week we finally have a case number, and the devs are finally on it.

I’d been getting increasingly depressed about it. Track Archives and Disabled Tracks are the two tools I want to build my new template around, but both are so buggy as to make the experience tortuous. Here’s hoping this turns the corner.

hey guys, is there still no workaround???
jesus, I’ve just upgraded to C9.5 from 8.5 mainly in hopes this was resolved since 3 years have passed
and no, its still broken

once you disable/reenable your multiout track in a big project - all the outputs get messed up, doubled or renamed to SYNTH tracks, plus theres a bunch of inactive original tracks you need to remove.
the original naming structure disappears as well as the order of the tracks which makes it super confusing. plus there are these doubles that clutter the hell of the project
same when you’re importing a multiout track from another project - it all goes to crap, which makes it really annoying!

we really need to get their attention to this otherwise they will never fix this SO OBVIOUSLY BROKEN thing
Seriously, Steinberg, what the hell?! 3 years! I’m speechless
PLEASE RESPOND ASAP!!!

Depressing, isn’t it? My daily reality, and I do share your incredulity. I’ve heard whispers that Steinberg are listening, but we’d all love to hear something direct from them.

As it is, I’ve not updated to 9.5 because I knew nothing had been done - I’ll be jumping all over 10 if they’ve spent some time on this whole area of track management.

I’d be keen to assist in hunting down the issue. Sometimes it works, I can even transfer the tracks successfully in some cases, but with other projects its impossible.
I wonder if its windows only? It could be related to ram/cpu load
But I can actually see that this would happen beforehand. If you open another project and leave it inactive, you can see the outputs greyed out - that means they are already messed up when you drop the track into project

the fact that a simple multiout track without any processing can be moved around/disabled without any problems means that it can be fixed.
possibly quite easily

edit
OK I’have just reproduced it
a blank project with 1 kontakt instance and a simple multiout instrument - works fine, can be dropped into another project in integrity

but then I duplicated it so its 10 kontakt instances and there you go - same old mess when trying to transfer it

so the only workaround I can imagine would be to make a single project file for a few instruments
and then you’ll have to never disable them in the main project. just deleting and adding them from those templates again if needed
its not any less painful though
or just go through the shit disabling/enabling them, deleting those dummy tracks and renaming everything back manually. even thinking about it makes my blood boil

Sounds like good detective work there. I hope Steinberg are (a long way) ahead of you, it is insane that these bugs have been around for 3 years.

I assume not many people bother using those?
although its kinda strange. I want to have all my mics or instruments laid out separately at all times
but I suppose many professionals do use it like this, big composers and the likes (although they probably have enough DSP with slaves and VEpro so they are not using disabled/transferred tracks inside Cubase)
But possibly the problem is absent in MacOS

I’ve just found a whole new problem with this. I’d muted a Superior Drummer track to export a stem. To be embarrassment, a clip later down the timeline played on this muted track. When I expanded out to look at what was going on, I found none of the individual outs muted, just the parent tack. The first clip didn’t play, however the 2nd did. Why? Who knows. Further muting that individual out muted both clips.

So due warning - multi out instrument tracks may be more than just the visual scrambling and duplicated outs, it may be screwing up other stuff under the hood too. What a mess.

I’ve experienced the same thing you are describing

Sometimes there are complete out of place tracks being created
sometimes other multiout instruments get mixed in to a random track outs
and when you delete those unwanted tracks the project crashes.
also, new to 9.5
whenever I add a few multiout tracks into a project, I got spikes and weird playback skips. never experienced that in 8.5
overall performance in the projects with those multiout tracks became a lot worse.
I can barely run 5 instances, which is odd

Its a headache.
I just threw a 110$ on the upgrade and it got way worse than it was in 8.5
Is there a way to make them fix this somehow? Calling them everyday etc?
Unsatisfied is a very light word to describe it.
and it drags and drags for years

its very easy to reproduce though. Maybe one of us should make a video?
At the very least we need a workaround or a hotfix that partially solves it for the time being
just to be able to work

Anything and everything really. I’ve spent some time with them in support, got it logged but nothing else other than that. I understand ringing tends to be more fruitful than online support, so if anyone did that it can’t hurt - would be great to report back here too.

Have you tried hosting those tracks inside vepro?
Thats the only solution I can think of but its a hassle and requers an additional purchase

one of my projects won’t load before I disable those multiout tracks while its inactive, then load it up and activate them manually again
what a nice new workflow, steinberg.
never happened in 8.5

To get it in perspective, AFAIK all these problems only happen when a track has been disabled and re-enabled. Cubase can host a VST, it’s only that this additional functionality breaks stuff.

(Will stand corrected if anyone has experience of these buys on tracks that have never been disabled).

thats correct. only disabled tracks or imported tracks
I don’t understand why they cannot be recalled properly.
because if you open the project where the tracks were created or never disabled, it works fine.

right now I do the following
1.import/enable the track. all messed up
2.duplicate the track and switch off multiouts on the new one
3.switch them on again
4.copy/paste all the plugin settings and routing/levels from the messed up one
5.delete the messed up track

I guess if they could implement this crooked approach under the hood as a temprorary fix, that would be nice

PS The main thing I completely fail to understand is why the hell if I duplicate the healthy multiout track inside the project, its duplicated without any issues!
it seems like it could be fixed in half an hour.
I’d really appreciate an official comment though. they are not even returning emails.

"Thanks for contacting the Steinberg Technical Support.
We are sorry for the delay, we are facing an unusual amount of requests.

Please note that the issue will be addressed in the next Cubase Update.

Regards,

Eric Chabane
Technical Support Representative"

I’ll just leave it here
Hopefully it happens sooner than C10 in december.

WHOAAAA!

Sooner rather than later would be wonderful, but soooooo good to hear they’ve got a fix. Thanks for posting Kavinsky.

I hope it wasnt just to brush me off haha
They also said they can’t give a rough timeframe for the update release.
Lets wait for the next 9.5.xx and see, fingers crossed

I’ll be watching - I have bought an update from 9.0 to the next version that I haven’t activated. Was planning to wait til 10 (or longer if there had been no improvements here nor to Track Presets), but if 9.5 gets fixed I might just jump in earlier.

Someone elsewhere reckoned its been 3 years waiting to fix this…