Pro Tools 2022.7 is out now

[Obsidian Dragon]

I just downloaded it but have not installed yet. I'm finishing a small project first so I didn't want to introduce a new version yet. I'm still on 2022.5.

Any reports of issues? I know the MIDI bugs in 2022.6 were supposed to be fixed with this release.

[lesbrunn]

Originally Posted by Obsidian Dragon

I just downloaded it but have not installed yet. I'm finishing a small project first so I didn't want to introduce a new version yet. I'm still on 2022.5.

Any reports of issues? I know the MIDI bugs in 2022.6 were supposed to be fixed with this release.

Not fixed. Maybe it's even worse now.

[ejsongs]

How are things worse?

[lesbrunn]

Originally Posted by ejsongs

How are things worse?

I didn't try 2022.6 because of the MIDI bug reports, so maybe its not really worse. I don't want to hijack this thread, so I've started another one with what I discovered. Please take a look at that...

[Emi]

They fix things and they breake others...man....

[lesbrunn]

Originally Posted by Emi

They fix things and they breake others...man....

Can we call that 'Pro'?

[ejsongs]

nothing is posted. please elaborate.


thanks,


ej

[lesbrunn]

Originally Posted by take77

After doing some tests in 2022.7 with both a previous session and a brand new session, I can say that I wasn't able to repro any of the odd MIDI behavior in the brand new session.

However, when conducting tests in a previous session (2022.6) with MIDI imported from a previous version, I can repro bugs right off.*
So I think the new MIDI engine just doesn't coincide with previous MIDI session data?

I did all kinds of tests in the new session. I even quantized a bunch of clips on various instrument tracks all crazy, inserted random tempos and cut & insert time.
All of which I can't do in sessions with PREVIOUS MIDI data.

I will add that I was in grid mode and that none of the MIDI clips were recorded into PT.
For my test I just dragged n dropped a bunch of drum loops on multiple tracks and manually created odd patterns in the editor.
Carried out a bunch of test tasks with quantize & velocity, duplicating, consolidating, trimming splitting clips, Alt + dragging clips etc

My session test in 2022.7 was also at a 44.1kHz sample rate.
And my instrument tracks were in tick mode and the Master fader and main timeline at the default sample mode.


*The very first test in 2022.7 that failed when opening PREVIOUS MIDI session data:

I simply selected a random clip from the timeline (4 Instrument tracks active).

Then Alt+click & dragged the clip across the timeline.

As I dragged the clip down the timeline I watched the green length indicator change from 8 bars to 7 (& some change) as I dragged it across the timeline. And sure enough, when the sample rounding issue occurred, so did the unable to select MIDI notes issue.
But only with MIDI data from a previous version was I able to repro.

The newly created session in 2022.7 enabled me to do my usual tasks and carry out these tasks to an extreme. Randomly modifying MIDI clips on every tack.
After which I was able to drag random clips across the timeline with no change in the length indicator.
No issues selecting, trimming note lengths or cutting & inserting so far in a new session.

So the MIDI has to be created fresh in 2022.7 for me to work unhindered.

Thanks for the info from your extensive testing. There's something I'd to ask: Apart from the midi stuff is there anything different in 22.6/22.7 from 22.5?

[JingleDjango]

Any reports from users still running Mojave?

[off the wall]

Originally Posted by Obsidian Dragon

I just downloaded it but have not installed yet. I'm finishing a small project first so I didn't want to introduce a new version yet. I'm still on 2022.5.

Any reports of issues? I know the MIDI bugs in 2022.6 were supposed to be fixed with this release.

I really don’t use MIDI much at all but 2022.7 is running fine with large sessions with video on my system.