Disabled midi tracks lose midi send output routing

I will try to reproduce this on Monday.

The waiting time… Do you operate Cubase? Or is it OK just leave Cubase alone and wait?

The waiting time… Do you operate Cubase? Or is it OK just leave Cubase alone and wait?

It doesn’t seems to make a difference whether or not ive been operating Cubase during the wait. To be honest i’m not even sure that the wait is the cause - i’ve just managed to reproduce the bug by repeatedly disabling and re-enabling the midi track fairly quickly. Seems quite erratic. The only consistent pattern i’ve noticed is that right before the midi track fails to recall its output settings the mouse cursor briefly changes from a pointer to a loading wheel

Further point of note: issue is present with all midi outputs, so it’s not specific to one device.

I was able to reproduce it this way:

  1. Add a MIDI Track with MIDI Send, routed to any MIDI Port.
  2. Disable MIDI Track.
  3. Create another empty project, activate it.
  4. Go back to the original project, activate it.
  5. Enable the MIDI track.
    => The MIDI Send Port is set to Not Connected.

Reported to Steinberg.

Many thanks for corroborating. I’m fairly certain that the output routing gets lost even without activating another project and re-activating, but this may be the underlying culprit.

Cheers

I’m new to bug reporting in Cubase - should I file a support ticket as well? or do you have a ticket ID or something I could follow?

It’s reported in the internal system as CAN-13635.

Apparently this will be fixed in 9.5.30

Has it been fixed? I also have set up my template in a way, so that there is a send with a defined port setting on each midi track. I use this to report to lemur app which track is selected. If you have a big number of midi tracks with cc information on them in the beginning, it is absolutely crucial to disable unused midi tracks. However, I have encountered the same problem: the midi port settings are not saved for a disabled instrument. Does this work now? I cannot see it mentioned in the 9.5.3 Version History…

I was sent the following message a while back:

‘The Cubase Pro 9.5.21 has solved a MIDI issue which closes your problem. However, I would inform you that “MIDI Sends port becomes Not connected” bur report will be solved with the Cubase pro 9.5.30. I cannot add further details at the moment’

However it doesn’t seem to have been fixed in 9.5.30. Gonna follow this up

Hi,

I’m sorry, I can’t reproduce it anymore. It works to me, here with Cubase 9.5.30.

Actually, it still doe not work for me. I am on Cubase 9.5.4 (Mac OS 10.13.6). When I deactivate midi tracks with any midi send set to a specific midi port selected, save the project and reopen it, after enabling the same track, the midi port of that send is not connected …

Hi,

You are right, this scenario is reproducible. And it’s also already reported to Steinberg (CAN-18936).

Btw, the project is already loaded with MIDI Port “Not Connected”.

Hey FriFlo,

The support team have finally acknowledged this exact issue (on October 26th) and have opened an internal report [CAN-18936] as “Disabled midi tracks lose midi send output routing”. Crazy to think that I first reported this issue in February 2018.

Hopefully they finally nip this in the bud

I actually reported that in the beginning of 2017, even earlier someone reported it with the track activation feature in Cubase 8, but as you can see, it did not raise a lot of interest … :wink:

Now, question of the day? Will this finally be resolved in a Cubase 9.5 update? Or does it work in Cubase 10? This latest Update is once again full of features that may be useful, but are not quite on my priority list. If at least this could be resolved, I might update, but otherwise I am quite annoyed by the endless stream of new features being implemented while older stuff isn’t quite working as expected …

Sorry to resurrect a dead thread, but did this ever get resolved?

I’ve just built a new template, using track enabled/disabled status to control visibility so things don’t get overwhelming. I also have a midi send on all my channels which is routing some auto-switching stuff to Lemur. Cubase loses the routing for this when the track is disabled (it seems to only be affected when the track is disabled for a while - God knows how long it takes for the routing to get lost).

Any workarounds for this? It’s definitely a bug, and like the last poster I wish Steinberg would actually pay some attention to fixing their bugs, instead of releasing shiny new toys.

Cheers, and again sorry to drag up an old thread, but this is an old issue…

Mike

Can confirm that this issue (CAN-19863 / CAN-18936) is fixed with maintenance updates 9.5.50 and 10.0.15. The notes say:

An issue has been resolved where MIDI send routings
were set back to “Not connected” for disabled MIDI tracks
after saving and reloading a project. (However, for already
affected projects, you need to set the connection again.)

It isn’t entirely clear what ‘setting the connection again’ means… I’ve asked support to clarify this and also posted here Cubase 9.5.50 / CAN-19863 query - Cubase - Steinberg Forums

Seems pretty clear to me… Going forward the issue is resolved but, if your project was already affected by the bug you will have to have to manually reset the lost connections.

Regards :sunglasses:

I still experience a very similar problem in Cubase Pro 11.0.30 Build 419:

  1. Create a VST instrument track.
  2. Right click on the VST instrument track and choose Add Track->MIDI. A new midi track will be created with output set to the VST instrument track. I use such midi tracks to store key switches on them separately from the midi data on VST instrument tracks - easier to edit, copy, etc.
  3. Disable the VST instrument track (let’s assume I’ve decided to convert my VST and midi tracks into audio by using Render In Place and then disable them to reduce project loading times and for other reasons). The MIDI track will lose midi send output routing
  4. Enable the VST instrument track (let’s assume I’ve decided to change some notes and re-render again after that). The MIDI track will still have invalid midi send output routing

This is very annoying and error prone. For instance, I may want to create a template with all VST instruments predefined, but I don’t want all of them to be enabled at once because it will take infinity to load a project created based on the template. I want to disable all the instruments in the template and then enable them one by one while working on the project. And with this annoying bug, I have to do the following to enable a VST track:

  1. Enable the VST instrument track.
  2. Right click on the VST instrument track and choose Add Track->MIDI. A new midi track will be created with output set to the VST instrument track.
  3. Select all the events from the previous midi track (which is invalid).
  4. Move all the events from that midi track to my newly created track.
  5. Set the name and colour for the new midi track.
  6. Remove the old invalid midi track.
    Too much hassle instead of just enabling the track I need. Another option is to reset MIDI output manually, but I have so many midi inputs - I am afraid of making a mistake. Adding a new track is more secure.
    If I forget to do these steps, my key switches will not operate and I may miss it when I work with tons of tracks.
    I would be grateful if you could fix this bug. Thank you!