Instrument tracks frequently not working on 2023.6

[audiogamble]

Did my first production session with 2023.6 today and I ran into some issues with instrument tracks. I had just one instrument track in this session (Arturia Farfisa V), and it often would simply stop playing back as expected. The only way I could get sound on it was clicking on the keyboard on the plugin interface itself. It would not receive midi from an external source, the piano roll, or from the qwerty/virtual midi keyboard within pro tools. I verified that the midi was routed properly in the "instrument" pane of the mixer window on that instrument. I could also see the midi metering in that pane, however no sound was coming out of the instrument.

The ways I was able to get it back was either deactivating/reactivating that track. Sometimes that wouldn't work, and I would need to fully restart pro tools.

I've tried building a test session to isolate the issue, but have been unsuccessful. However after continued use, this issue does come back intermittently.

Has anyone else been seeing this on the new release? Would love to get a sense whether this is a pro tools issue, or a problem elsewhere.

Specs:
Pro Tools 2023.6 (Native Silicon Mode)
Monterey 12.6.6
16" MacBook Pro M1 Max Fully Loaded
RME Madiface XT

[Darryl Ramm]

There are a huge number of similar experiences with VIs being flakey in Pro Tools, not just in this latest release. All a google search away.

e.g. "VI" stop playing site:duc.avid.com

So many posts out there you can't miss them....

[FunkzzaJ]

Originally Posted by audiogamble

Did my first production session with 2023.6 today and I ran into some issues with instrument tracks. I had just one instrument track in this session (Arturia Farfisa V), and it often would simply stop playing back as expected. The only way I could get sound on it was clicking on the keyboard on the plugin interface itself. It would not receive midi from an external source, the piano roll, or from the qwerty/virtual midi keyboard within pro tools. I verified that the midi was routed properly in the "instrument" pane of the mixer window on that instrument. I could also see the midi metering in that pane, however no sound was coming out of the instrument.

The ways I was able to get it back was either deactivating/reactivating that track. Sometimes that wouldn't work, and I would need to fully restart pro tools.

I've tried building a test session to isolate the issue, but have been unsuccessful. However after continued use, this issue does come back intermittently.

Has anyone else been seeing this on the new release? Would love to get a sense whether this is a pro tools issue, or a problem elsewhere.

Specs:
Pro Tools 2023.6 (Native Silicon Mode)
Monterey 12.6.6
16" MacBook Pro M1 Max Fully Loaded
RME Madiface XT

Similar issue with Sonivox plugs. Workaround is to select midi clip on the track, then play kbd or play the clip.

I have other issues with Arturia instruments (bad boys). Workaround is to inactivate Arturia tracks before quitting the session, such that when starting up the session, the Arturia tracks are inactivated. When strarted then activate the arturia tracks .

[Protone]

I've had the same issue with some instruments (Kontakt mostly) for several years / Pro tools versions. Doesn't happen all the time, but often enough to be super annoying.

[weezul]

I have also just started having this issue with XPand2 in Pro Tools for the first time. Just no signal at all, will have to double check if it was pre or post 2023.6 but it's a first for me. Not the usual opening a session and the midi is unlinked classic, but everything plumbed correctly but just no sound at all on playback.

Rosetta, M1 Pro, RME Digiface

[gthm]

Yes, MIDI weirdness with 2023.6.

No sound from VIs (Kontakt, Omnisphere).

Have to reopen PT and then they still don't work sometimes.

This has never happened to me prior to 2023.6.

[audiogamble]

Originally Posted by weezul

I have also just started having this issue with XPand2 in Pro Tools for the first time. Just no signal at all, will have to double check if it was pre or post 2023.6 but it's a first for me. Not the usual opening a session and the midi is unlinked classic, but everything plumbed correctly but just no sound at all on playback.

Rosetta, M1 Pro, RME Digiface

Yeah that’s exactly what’s happening here. Ive had the issue before where midi randomly doesn’t get routed to the plugin which is easy enough to figure out. In this instance, everything is technically done correctly except the instrument won’t play. This is totally new for me in this version. Rolled back to 2022.12 and everything is fine.


Sent from my iPhone using Tapatalk

[weezul]

Originally Posted by audiogamble

Yeah that’s exactly what’s happening here. Ive had the issue before where midi randomly doesn’t get routed to the plugin which is easy enough to figure out. In this instance, everything is technically done correctly except the instrument won’t play. This is totally new for me in this version. Rolled back to 2022.12 and everything is fine.


Sent from my iPhone using Tapatalk

Well then. Here we go again.... Man that's super disappointing. I feel the last few releases have had some seriously bad showstoppers. Like this, or delay compensation being broken, or tab to transient being broken, or melodyne ARA being a mess, or elastique not actually maintaining it's timing, or crashing on exit... or the counter not even being right... waiting to get them fixed and new bug shows up!!! Interested to see how the numbers stack up for this bug because it's super annoying. I was working on a session sending patch changes to mainstage and qlab, and sending midi beat clock, thinking something funny was going on with my MIDI

[audiogamble]

Originally Posted by weezul

Well then. Here we go again.... Man that's super disappointing. I feel the last few releases have had some seriously bad showstoppers. Like this, or delay compensation being broken, or tab to transient being broken, or melodyne ARA being a mess, or elastique not actually maintaining it's timing, or crashing on exit... or the counter not even being right... waiting to get them fixed and new bug shows up!!! Interested to see how the numbers stack up for this bug because it's super annoying. I was working on a session sending patch changes to mainstage and qlab, and sending midi beat clock, thinking something funny was going on with my MIDI

When you are getting this problem, is it preceded by a 6101 error? Seems to be the pattern over here. Also what are your computer/os specs? Are you running the intel/rosetta version or native silicon version?


Sent from my iPhone using Tapatalk

[Rectifried]

on the sidelines.. watching this before I update re instate


I really Dont need simple stupid problems to derail me.