Midi problems with PT 2022.12

[ChuckS]

I was thinking maybe something to do with the keyboard channels. Recording 'any' would play through, but on playback maybe everything is on a different channel from the output selection. That wouldn't explain it working when the insert is moved though. Interesting. Anywho, check what channel your keyboard is assigning.

[HowHoffman]

Originally Posted by albee1952

No Eucon is needed for the 003

Thanks for clarifying!

[shobud10]

Thanks ChuckS, I'll have a look.


Dan

[daeron80]

I have had similar problems for years on my Windows machine with a Saffire interface, especially with RAM-hungry sample-based VIs such as Spitfire's. My workaround is to do one of two things: wait 30 seconds or so and try again, or deactivate and reactivate the VI. I do the former if I need to get up for a moment anyway.

I have noticed that the problem becomes more frequent as the complexity of the orchestration increases. In other words, it seems to be related to load.

We're both using Firewire interfaces. Aging tech. Possibly a coincidence but...

[Bob L]

Originally Posted by shobud10

Hi All,
Sometimes it plays, sometimes it doesn't. Usually the first play after the session is open. Then, in order to hear the VI, I have to move the plugin to a different insert slot. Which will work for one play only.

I know sometimes PT loses the 'connection' to the VI when looking at the Instrument portion of the track, but this is not the case here.

The midi is always present on the instrument track, it just doesn't trigger the VI. Track meter shows no output.

Dan

Dan, your workaround method, moving the VI to another slot is "unique", to my limited knowledge. The most often-noted method is to open the MIDI channel dropdown and reset it, whether it looks like it needs it or not. Try that. I'm afraid this will never be fixed, so a working workaround is going to serve you well.

[trevvahhh]

I have this issue and it's dramatically worse in 2022.12 vs 2022.10 to the point where bounces have been affected and it gets hard to work.. rolling back to 2022.10 right now for this reason and it seems to be much better if not completely better. some instruments are more affected than others, east west Opus and Arturia Analog Lab do it constantly.

see if 2022.10 works better for you?

2022.12 didn't solve the bugs it seemed like it would for me re: MIDI and h264 export crashes so jumping back to .10 here for now

MacBook Pro 16 M1 Pro
OS 12.6 Monterey

[shobud10]

Interesting. Maybe I'll give 2022.10 a try.
As an update to my situation, Avid support finally got back to me to arrange troubleshooting, but of course everything is behaving as it should. After weeks of trouble with midi, I now can't reproduce the issue...


Dan

[Dizzi45Z]

This bug is in the top 3 of the most frustrating bugs I run into. I have little hope it will ever be fixed because it happens so randomly that I can’t list steps to reproduce it. But there are a few things that I have noticed.

1. It happens more often when my buffer settings are set to 64 or 128.

2. It seems virtual instrument related. For example, it happens very often for me with Alicia Keys in Komplete Kontrol or Kontakt.

3. When I am having the issue, it usually starts happening an lot. If you keep hitting playback in the same spot of the timeline, it won’t play. The way I get it to start working again is by playing back in different places in the timeline.

4. When the issue is happening, it is common that the instrument giving the problem will not play after a bounce. This is scary for cases where you are doing multiple bounces because sometimes the instrument will not be included in the the following bounces unless you wake up the instrument again.

I hope it somehow gets resolved.