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

Cubase
,
#65

Track import - that’s bad - I thought it was supposed to make a new track version if a conflict of some sort.
When track import from project came - I always thought they were going to build on that and fix routings and stuff in upcoming version - but seems not.
Walk away from track archives, kind of.

They sort of worked away form rack instruments - and supported more and more for track instruments - so thought that newer approach would be continued to be improved, like track instruments eventually got multi outs etc.

Avid already dropped windows 7 for PT, so not an option for me really. PT and Cubase had some similariries in how you got visuals while adjusting VCA’s and could work on that for a while until decided you are done. And PT has real context sensitive help to get by easier.

Sonar is a really great daw though, but not much headroom until I hit the ceiling for what I want to do.
Reaper is so lean on the system - nothing compares. Some things though, a bit off.

#66

I’m pretty sure they are not going to fix it in V10 because the support plays stupid with me again.
Like they hear about the problem for the first time

ok v10 is almost here and looks like nothing was improved on that front.

#67

did anyone check out the Cubase 10 update logs?

#68

To keep a good enough education level of support agents - is hard, I think.
That they are more eager to respond, than realize it’s above their head and to raise to next tier of support - to really help.
They seem to think they didn’t do their job if they didn’t do all the responses.

The only vendor of today that has top notch support is Waves, they know this.
I always had a solution, every time.
Last time, 18 months ago - a piece of mess Waves Central - that screws up install - I finally got the offline installer to download.
But they hang in there - that’s gold.

Waves has this Studio recording software, not a real daw, I think - but if Waves made a daw, I would get it for sure.

I’m indifferent to what’s in C10, as I realized that mixer snapshots does not include automation - but seems to delete automation if it’s there - how is that for implementation?

#69

Hey hey everyone - I’ve read a post elsewhere that says that this really has, in fact, been fixed in Cubase 10 despite the absence of documentation to support it. Steinberg claim to have fixed it in 9.5.41 according to a rep, but no-one here has made it work and there’s nothing in the changelog there either.

I’m planning to install C10 at the weekend, but if anyone can beat me to it to test on C10 then all the better. If it is fixed then fireworks and cartwheels obviously, but keen to know if we need to make our Archives / Disabled Tracks from scratch or if they open existing ones ok.

#70

I’ve read that on VI aswell, pretty skeptical at this point
please do try and let us know!

#71

Gentlemen,
this is Steinberg speaking. No excuses: this needed to be fixed a long time ago. I’ll talk to the team how this could be solved.

Best
Matthias

#72

That is very welcome, Matthias.
Please keep us updated

#73

Hallelujah! Thanks hugely Matthias!

#74

Chiming in to show support for the cause! Thank you Matthias!

#75

I will update to 10 as soon as this thread confirms resolving this. Thanks…

#76

This is the fix I’ve been looking for in every change log of every Cubase update. Hope this can be resolved as it’s driving me crazy.

Thank you Matthias !

#77

I’ve created a small zip file of a .cpr and two track archives to try to help get the problem nailed down by Steinberg. There’s a detailed READ ME of how I got the problem to manifest, and some screen grabs to illustrate.

Note - the .cpr was created in C10 Pro and includes stock plugs from the release, so it won’t work on C9.5 or earlier. I wanted to do this to eliminate the fixes that Steinberg have already done from the equation. I was also able to generate the fault using only Steinberg plugs, but the first failure occured for me with the one third party Track Archive, a Battery 4 .xml.

Interesting that I didn’t get the fault at first, but once the fault first appeared it was then impossible to get rid of. This chimes with my experience all round - on a first round of tests things may well appear fine. But close, restart, come back to it… and like a bad nightmare it will be there waiting for you…

If anyone wants to test to see how it is on their systems, the file is here - https://www.dropbox.com/s/td22vr0kping4fa/CAN%2013042%20test%20material%20GR.zip?dl=0 . Please do read the READ ME though, and don’t forget that first tests may very well be deceptive.

#78

Very happy that this is finally getting some attention. Thanks Matthias!

#79

I’ll make a recap of my experience with track archives as well as a separate description.
I’d say exactly the same issue as disabled tracks internally in handling - something gets out of order - as it does for disabled tracks when restored.

#1. Not creating a good track archive
a) from a fully featured project I save superiordrummer instrument track as track 29, and a group channel for it on track 33 and save those two as selected tracks.
b) as restored you get outputs scrambled order, sometimes not colored as instrument track(red in my case) and a bunch of extra automation lanes which in some cases can be removed, sometimes not. If colored gray they could be removed, if colored red as instrument track - it could not be removed.
c) in some versions of Cubase I also got popup dialog about missing tracks etc when restoring an archive.

#2. Workaround that seem to create ok track archive
a) make a blank project, and just insert superiordrummer and a group channel for it - and save those two, track 1 and 2, as selected tracks.
b) as restored into any project seems to work ok, all named, ordered and colored and no extra automation lanes.

So there seems to be confusion how Cubase handle things and keeping what belongs together in order.

#80

any workarounds I came up with always ended up with the same mess sooner or later
there is no workaround at this point sadly.
even considering all the different ways you can import the track into the project - they all fail with the same exact symptoms

#81

I think you are right - the disabled track issue is worse than track archive in general.
Even more sad it wasn’t taken care of then - it would fix both parts like track archive too.

In the root - it’s the same issue - keeping track of what belongs together and how.
And you get the same symtom slike scrambled order of output and extra automation lanes Cubase does not know what it is.
You don’t want to continue working on a project showing those symptoms - you never know what turns up later when everything is added and saved and stuff.

But I think it’s a good hint - that saving what arbitrary tracks or track neighbours makes a difference in track archive thingy.
Hope you get it sorted - even in 9.5.50 - but I’m leaving Steinberg now, I’m done.

#82

Managed to reproduce the issue from the ground up in 9.5.41 in a few easy steps

1 created a kontakt instrument track with 7 outs, used some instruments from the factory library.
2 put a plugin on each output (soundtoys)
3 duplicated this kontakt instance a few times
4 saved “good” version of the project
5 disabled one istance of kontakt
6 closed/reopened Cubase
7 loaded the project (got the usual cubase error asking me if I want to remove the tracks it cannot connect - deserves discussion too)
8 enabled that instrument track
9 boom - its broken on the first try
10 saved the failed “broken” project

here’s both projects, hopefully this brings us closer to the solution since it was so easy to break it
https://www.sendspace.com/filegroup/fgHujj5R4mI4ypMhQZXo8Q
I hope the devs can compare both versions and find the breaking point

#83

I think we’ve established that one person’s precise experience is not necessarily replicated by someone else. My conviction is that if someone is looking for the bug (or even if they are not), it shouldn’t be very hard to find, however. Closing Cubase and re-opening is an important factor, and if the devs / beta testers haven’t been doing that it would explain a lot.

#84

Well at the very least now they can see how the issue actually looks
But it was so easy to reproduce this time around, I think its definitely connected to closing/reopening cubase and/or some ram/cpu load.
I’d love to try somebody else’s project though, don’t have v10 so cant try yours
It should be triggered in 100% cases across all our machines if we tick all the needed boxes