Disabling a track erases assigned MIDI routing. Any alternative options or a solution?

[Greg_Purkey]

But how could you explain that the first Instrument Track with 3 midi tracks assigned to it, disabled then enabled, always works flawlessly?

It’s only the 2nd and any subsequent Instrument tracks that fail.

[Martin.Jirsak]

Hi,

No, I can’t explain this, sorry. But we have something to work with, thank you!

[Martin.Jirsak]

Hi all,

@Martin.Jirsak

My result is a bit different:

• Add Instrument Track (Halion Sonic SE) 1 [let’s mark the track as HSSE1].
• Add MIDI Track (Cubase route its output to the HSSE1) [let’s mark the track as MIDI1].
• Add Instrument Track (Halion Sonic SE) 2 [let’s mark the track as HSSE2].
• Add MIDI Track (Cubase route their outputs to the HSSE2) [let’s mark the track as MIDI2].
• Disable HSSE1 track.
• Enable HSSE1 track.

=> Output of MIDI1 track is routed to the HSSE2.
=> Output of MIDI2 track is routed to the HSSE1.

I have more details to this.

It appears, the routing is correct in fact in this case. But Inspector and MixConsole > Routing show wrong output. But if I play the MIDI Tracks back, they are playback the correct/expected Instrument and sound.

Moreover, if I open Channel Settings window and I let it to show the Outputs, the correct output Channel is shown (ie. HSSE1 for the MIDI1 track and HSSE2 for the MIDI2 track).

Unfortunately closing and reopening the project doesn’t help, the info in the Inspector is still wrong.

It’s still very confusing bug, but at least you get the correct instrument/sound.

Steinberg has been updated.

[Maer]

Hi,
Thank you for providing the case.
Has this issue been fixed in Cubase 13?
I am hesitating whether to upgrade from Cubase 11 to 13

[Martin.Jirsak]

Hi and welcome to the forum,

@Maer

Has this issue been fixed in Cubase 13?

Yes, this has been fixed in Cubase 13.

[GrahamkCampbell]

Has it? I’m having this issue in Cubase 13.

[Martin.Jirsak]

Hi,

@GrahamkCampbell

I’m having this issue in Cubase 13.

Could you please describe your scenario step by step? Is the project newly created in Cubase 13? Or do you use a template made in Cubase 12?

[GrahamkCampbell]

Yes it’s my main template file which was created in Cubase 10.5. In my template I start with all tracks disabled and just enable them as needed, so I’m starting from a point of both MIDI and instrument tracks disabled.

[Pierre-Yves]

Hi all !

I can confirm that there are still bugs with disabled tracks in C13.

My issues are with midi tracks.

I use huge templates with hundreds of instruments, hosted in VEPRO7, and some other in cubase.
To save RAM, I’ve created a toggle switch that enables and disables the instance in VEPRO, and in the same time the midi track concerned in cubase (to have a visual state of the track).

When I enable that midi track, with the switch, my instance enables correctly in VEPRO, but the midi track in cubase loses the audio outputs and all the QC’s. No way to make it works properly, and no Quick Controls anymore. I have to delete, and create a new track.

It’s very disappointing as I have to create a new track each time I had the “bad idea” to disable the former midi track.
But I have to precise that midi routing is still correct. Only the audio outputs and Quick Controls are lost (for the QC, it doesn’t work anymore, no action at all). Once I create a new track, everything work correctly.

Thank you so much if you have any solution !

[Pierre-Yves]

I have to say further that if I only disable the Kontakt instance inside VEPRO and don’t disable the midi track concerned into cubase (modifying my switch) everything’s OK
The issue is well concerned by disabling midi tracks.

[riflinka]

Yes, disabling still bugged in C/N 13.0.30.

Re-enabled tracks lose their output routing to groups sometimes (very often).

[GPnicolett]

Anyone know if this bug still occurs in 14? I’m in 13 right now, building a new template and running into the issue.