Instrument tracks frequently not working on 2023.6

[Bob L]

Originally Posted by weezul

So just realised I sent out a mix where one of the midi tracks is silent on an offline bounce too. This is getting to be a very annoying bug now. No one else having problems?

Had you listened to the track before bouncing and it played the MIDI or did you open the session, bounce without hearing the MIDI first and assume it would work?

What I'm trying to grasp here is whether this is same problem many have had for years where the MIDI "unassigns itself" after opening the session fresh, or whether it's a truly "new" issue.

To be absolutely plain about this, I am not faulting your workflow; just trying to get specifics of what happened.

[docric]

Originally Posted by tomhartman

I use Kontakt daily, Ventura, iMac, have not noticed any problems ...

... same here, but on a MacPro... Ventura 13.2.1

[chompers2022]

I often have Superior Drummer and Arturia synths stop working after I make a bounce.
The fix is assigning an instrument to a random track and back again to the correct instrument. also, disabling the plug in and then turning it back on works as well.

Montery 12.6.3
Mac [email protected]
PT 2022.12

[SomeOtherGuy]

Same here, doesn't happen often, but some VI tracks lose their connection and don't play. Have to reestablish the channel's MIDI Output Selector to fix. Such a drag since sometimes in large tracks setups you don't realize that a particular track is not playing.

[weezul]

Originally Posted by Bob L

Had you listened to the track before bouncing and it played the MIDI or did you open the session, bounce without hearing the MIDI first and assume it would work?

What I'm trying to grasp here is whether this is same problem many have had for years where the MIDI "unassigns itself" after opening the session fresh, or whether it's a truly "new" issue.

To be absolutely plain about this, I am not faulting your workflow; just trying to get specifics of what happened.

Hey sorry for the delay on this one.

I can't even remember. I'm fairly certain I opened it to make a revision, and then exported it. The revision was not to do with the VI (upright bass). But on the bounce it was not there at all, along with another track or two. I feel I would have definitely noticed it not playing back whilst I tweaked something against it.

It seems unrelated to the old MIDI "unassign" issue. I still to this day do a sweep top to bottom for greyed out MIDI tracks when I open a session for this very reason! IIRC, two MIDI / VI tracks were missing on the export. One was the bass and another was something more subtle like an extra keyboard or synth or something.

[SomeOtherGuy]

In all cases for me the MIDI assignment gets lost and then needs to be reset.

In addition, another thing that occasionally causes this is if you duplicate an instrument track. The duplicated track seems to lose the assignment more often.

[massivekerry]

Originally Posted by SomeOtherGuy

In addition, another thing that occasionally causes this is if you duplicate an instrument track. The duplicated track seems to lose the assignment more often.

Yes! This is most common for me. Duplicating tracks has unreliable results in MIDI->Instrument assignment.

[SomeOtherGuy]

And duplicating audio or instrument tracks also defeats the record option "Cancel on all previous tracks." If you duplicate a record-enabled track, both are then record-enabled, defeating the pref.

[JamesPDX]

Confirmed. Rolling back to 2023.5.

Originally Posted by SomeOtherGuy

And duplicating audio or instrument tracks also defeats the record option "Cancel on all previous tracks." If you duplicate a record-enabled track, both are then record-enabled, defeating the pref.

[SomeOtherGuy]

This problem has existed long before 2023.5, just FYI.