Pro Tools 2022.10 is out

[M2E]

Going to 2022.9, I got the VCA bug and I also had the Melodyne issue. Going to 2022.10 fixed everything and I have to say, it's stable as well.
Now, let's see if the Silicon update will be a huge CPU improvement.

How much of an improvement do you all think the M1 silicon update will be?
I think about 25% to 35%.

Thanks, Marc

[massivekerry]

Originally Posted by M2E

Going to 2022.9, I got the VCA bug and I also had the Melodyne issue. Going to 2022.10 fixed everything and I have to say, it's stable as well.
Now, let's see if the Silicon update will be a huge CPU improvement.

How much of an improvement do you all think the M1 silicon update will be?
I think about 25% to 35%.

Thanks, Marc

I’d say it depends on the parts they really optimize vs translate, and what your workflow is. ( ie “post mixing in Atmos” and “composing with a massive orchestral template” will use and tax different parts of the program)

[camshash]

Originally Posted by Eric Lambert

I'm surprised by how little interest there is in this update.

I agree, running very smooth now

[M2E]

Originally Posted by massivekerry

I’d say it depends on the parts they really optimize vs translate, and what your workflow is. ( ie “post mixing in Atmos” and “composing with a massive orchestral template” will use and tax different parts of the program)

Yeah, I understand that but I'm using Pro Tools as simple as it gets with Stereo mixing. No Atmos here.

Let's see what happens.

Marc

[trevvahhh]

have been chiming in with issues I had with 2022.9 and happy to say 2022.10 has been stable all day with no sign of the Melodyne bugs, Saving ARA Data, midi editing, shift click assertion etc. etc.

big thanks to the team for pushing an update quickly that seems to have crushed a ton of bugs. goes a long way!

[resonatee]

Originally Posted by M2E

Now, let's see if the Silicon update will be a huge CPU improvement.

How much of an improvement do you all think the M1 silicon update will be?
I think about 25% to 35%.

Thanks, Marc

My dream is that when transitioning to M1, they could revise the audio engine and improve these things:
1) enlarge plugin compensation buffers, so more heavy plugins could be properly compensated
2) finally compensate MIDI properly, right now MIDI data you record in pro tools is EARLY about a buffer or two - depends on situation - compared to the audio track that is also recording the VI (and what you hear) So to really get your performance you have to nudge your midi data (in the attached example - 1309 samples early)
3) Improve Video engine perfomance and use M1 GPU decoding capabilities for that....that is basically free with M1 technology...

PT workflow is great, just need to fix those things.... One can dream eh?

[oscarpatxot]

Originally Posted by resonatee

2) finally compensate MIDI properly, right now MIDI data you record in pro tools is EARLY about a buffer or two - depends on situation - compared to the audio track that is also recording the VI (and what you hear) So to really get your performance you have to nudge your midi data (in the attached example - 1309 samples early)

I gave up on this, years without fixing this issue, and they could have added a midi recording offset value on the settings to let us fix it ourselves. They just don't care about midi, composers or producers at this point. (Studio one has this option and you just record the midi and audio at the same time, measure the offset and put it on the settings page, and done, perfect midi recordings)

[Macsearcher]

Originally Posted by oscarpatxot

I gave up on this, years without fixing this issue, and they could have added a midi recording offset value on the settings to let us fix it ourselves. They just don't care about midi, composers or producers at this point. (Studio one has this option and you just record the midi and audio at the same time, measure the offset and put it on the settings page, and done, perfect midi recordings)

I don't know what the bid deal is.
All that you have to do is measure the offset and compensate.
FYI, the following list of actions (not all shown) will affect these values so you'll need to re-measure offset.

• changing buffer size
• adding a plugin
• removing a plugin
• adding an AUX track
• removing an AUX track
• pressing play
• thinking about pressing play
• making a coffee
• breathing
• calling AVID support
• looking up your system ID number
• smashing your computer keyboard
• swearing under your breath and promising yourself that you won't renew your support plan this year
• renewing your support plan
• posting about issues on DUC forum
• not posting about issues on DUC forum
• change in heart rate
• bi-polar mood disorder fluctuations

[JFreak]

Originally Posted by Macsearcher

[*]smashing your computer keyboard

I must be doing this a lot. Bought this keyboard on january and now I alrerady need a new one.

[massivekerry]

Originally Posted by oscarpatxot

I gave up on this, years without fixing this issue, and they could have added a midi recording offset value on the settings to let us fix it ourselves. They just don't care about midi, composers or producers at this point. (Studio one has this option and you just record the midi and audio at the same time, measure the offset and put it on the settings page, and done, perfect midi recordings)

I never have this problem, and have been using MIDI every day in Pro Tools since MIDI got good with PT 8 in 2008. Presently, I'm using an HD Native system in Low-Latency Mode, usually with the buffer set at 256. I try to avoid big latency-inducing plugins in the signal path (including my Master Bus) while I'm recording MIDI. If I'm revising something after I've mixed it, I often go and Disable everything on the Master Busses, as well as anything causing big Delay Compensation latency in the Delay Compensation display (you need to have this on all the time).

But I have noticed the following.

- Some Instruments (especially sampled virtual orchestra packages) have a delay before they start. They are coded this way, and the intent is to make things sound more "natural" with the way an attack occurs in the real instrument. Pro Tools allows you to set a (negative ...or positive) Track Delay on each MIDI or Instrument Track. You can do this in the Real-Time Properties display in the Edit or Mix Windows, the stand-alone Real-Time Properties window, or my favorite...

The "MIDI TRACK OFFSETS" window. (in the "Event" menu)

This window has saved my bacon, especially since I use a big template with loads of VIs. Set it up once, and you're good.

You should also notice that there is a GLOBAL MIDI PLAYBACK OFFSET
that can be entered. This is detailed on page 812 of the Pro Tools Reference Guide, and may be helpful if the problem is in your particular system. You'll find the part about MIDI Real-Time Properties on page 814. Really, you should read this entire chapter.

If you use orchestral VI libraries, and want a starting point for (negative) Track Delays, composer David Kudell maintains a database of delays for different instruments that he (or his co-contributors) use.

I hope this helps.