2024.3 must be literally dropping any moment

[Eric Lambert]

I suffered from the MIDI disconnect bug quite a lot in past versions but I've not come across it even once during the past six months or so.

For those still experiencing it, does it tend to be certain plugin types or is there no rhyme/reason to it? For me it was usually Kontakt, or Spectrasonics plugins when they were employing multiple outputs.

[TNM]

Originally Posted by Eric Lambert

I suffered from the MIDI disconnect bug quite a lot in past versions but I've not come across it even once during the past six months or so.

For those still experiencing it, does it tend to be certain plugin types or is there no rhyme/reason to it? For me it was usually Kontakt, or Spectrasonics plugins when they were employing multiple outputs.

I must admit it has only happened to me once since I installed it on Windows about 10 days back, but it did happen.

I also reloaded a project with a freeze file that was clearly there and unmuted and was just playing back silence.

[massivekerry]

Originally Posted by Eric Lambert

I suffered from the MIDI disconnect bug quite a lot in past versions but I've not come across it even once during the past six months or so.

For those still experiencing it, does it tend to be certain plugin types or is there no rhyme/reason to it? For me it was usually Kontakt, or Spectrasonics plugins when they were employing multiple outputs.

I was thinking about this recently. It didn't used to be consistent, but I do seem to recall that when I Copied an Instrument Track (which I did a lot when I was building my template) those tracks might be wore likely to disconnect when I activated them.

[Tweakhead]

Originally Posted by noiseboyuk

EDIT I hope they don't literally drop it. That would be unfortunate.

We'll be filing fracture reports.

[Darryl Ramm]

It occurred very infrequently for me, I cannot recall specifics each time and could never see a pattern. Just seemed I'd open a session try to do stuff then find the input disconnected. It would have been on Mini Grand or Ez Drummer (maybe Superior Drummer but I think more Ez Drummer was being used). And not using multi-output. This also has not happened in the last month or so, but that may mean nothing (I take new PT releases pretty soon after they come out).

My concern with this is what it does to folks who have no idea to look, and we've seen those folks on DUC.

[marianna]

Hey all.....

Not that I really want to open a can of worms but...... as I mentioned to Darryl, I cant seem to find a bug related to this issue in our system. Now I am not the best searcher in our bug database ( Jira ) so that might be part of it.

Darryl sent a bunch of threads but what I need to know is did any of you create cases on this issue with support?

If so, please send me the case #.

If after a day or so I will create cases for those that have no case for this.

Marianna

[massivekerry]

Originally Posted by marianna

Hey all.....

Not that I really want to open a can of worms but...... as I mentioned to Darryl, I cant seem to find a bug related to this issue in our system. Now I am not the best searcher in our bug database ( Jira ) so that might be part of it.

Darryl sent a bunch of threads but what I need to know is did any of you create cases on this issue with support?

If so, please send me the case #.

If after a day or so I will create cases for those that have no case for this.

Marianna

I definitely have not filed a bug report. Maybe we should dig up our prior descriptions of this, so we can create one comprehensive bug report?

[abt]

Anyone having problems with the docked MIDI editor (floating MIDI editor seems fine)? It's super slow to open, takes maybe 10 seconds or more (closes instantly), and switching between tracks has huge latency, a few seconds at least.

[marianna]

Originally Posted by massivekerry

I definitely have not filed a bug report. Maybe we should dig up our prior descriptions of this, so we can create one comprehensive bug report?

That would be great Kerry - Darryl gave me a good start on threads but I need people to create cases or post their spec's and what happens.

Marianna

[massivekerry]

Originally Posted by marianna

That would be great Kerry - Darryl gave me a good start on threads but I need people to create cases or post their spec's and what happens.

Marianna

Hey everyone. For everyone who has had this problem, does this sound like what you have observed? @Darryl Ramm @Eric Lambert

MIDI Disconnect Bug (as termed on the DUC)

Pro Tools 2022.x 2023.x

Sometimes, when opening a previously-saved Session, one or more active Instrument Tracks containing Virtual instruments will have lost their MIDI Output assignment

example: an Instrument Track with Boom on Insert A, where the MIDI Input signal previously triggered/played the Boom instrument, will open with its MIDI Output assignment to none [or maybe “unknown”? I can’t recall exactly] and the MIDI Output has to be manually changed back to the instance of Boom.

Also,

Sometimes, when opening a previously-saved Session or creating a new Session from a Template, one or more Inactive Instrument Tracks containing Virtual instruments will have lost their MIDI Output assignment when they are made Active.

Also,

Sometimes, when opening a previously-saved Session or creating a new Session from a Template, where an Instrument Track has been duplicated, and the instantiated Instrument(s) (or more frequently the Instrument’s Patch/Preset/Sound) has been changed, those duplicates will have lost their MIDI Output assignment, either upon opening the session, or if the Tracks are Inactive, when they are made Active.

These behaviors have been noticed, but have not been 100% consistent.



Personally, when I had to manually rebuild large chunks of my writing template to incorporate Kontakt 7 (so I could use PT in Silicon Native mode), I instantiated each instance of Kontakt 7 (it's hundreds of tracks) individually (Rather than copying the Tracks), and have not observed this error with any frequency on those specific Tracks.