Pro tools 2022.6 released

[huzzam]

Originally Posted by Eric Lambert

As I understand it, there are ways to structure plugins under a Native DAW such that the M1 plugs operate natively while the non-native plugs do not. I don't believe it's a case of the entire plugin folder being dumbed-down to the architecture of the weakest link.

Yes that's how Ableton (11.1+) works with AU plugins on Silicon. It should be noted, though, that this works due to a compatibility layer from Apple, specific to the Audio Units format. You can have a mix of intel and silicon AU plugins, and Ableton will use whatever's best/available. The downside is that you then end up with a bunch of instances of Rosetta—one for each intel plugin—and it can end up being more cpu-intensive than just running the whole DAW in Rosetta mode.


VST & VST3 plugins do not have this capability, so silicon-native Ableton can only run silicon-native VST/VST3 plugins.

[djani]

https://www.mediafire.com/view/xxnp1...24.17.png/file

And it seems they've broke a custom shortcuts for the MacOS. The ones we make trough a System Preferences Keyboard tab. No way I can call a AudioSuite Gain plugin at a press of a button for example... And no internal Pro Tools option to do that.

[tonwurm]

Originally Posted by bashville

in the MIDI editor window--selected and quantized a couple bars of a pattern. After that, the events that were quantized could not be selected/moved. I can hear velocities being adjusted using the velocity trim, but the graphics for the notes don't move. So no note trimming, moving the note, any further editing after the quantize operation. See attached screen grab after using the i-beam to select a range of time. Selecting the notes to the left worked fine (they had not been quantized)--notes to the right had been quantized, and are not selected in the i-beam sweep. Long time PT user--not sure if some preference has been changed that I missed.

no problems here, I can quantize and move notes, change velocity... everything works as it should

[tonwurm]

Originally Posted by Dizzi45Z

I am having the same problem and even worse, if you quantize multiple times, it duplicates the notes to the new position. But yeah, after a quantize or two (with the new or old methods) you can not move or select the notes.

Too bad. I was liking the list of bug fixes, but this new bug is a deal breaker for me. I'll be sticking to 2022.5 for now.

tried it several times, no problems here.., maybe it will occur later or in other projects !?

[Fidelis]

Originally Posted by djani

https://www.mediafire.com/view/xxnp1...24.17.png/file



And it seems they've broke a custom shortcuts for the MacOS. The ones we make trough a System Preferences Keyboard tab. No way I can call a AudioSuite Gain plugin at a press of a button for example... And no internal Pro Tools option to do that.

Oh no, I still use that for gain plugin. But I can change it to soundflow… I’ll try that before upgrading.


Sent from my iPhone using Tapatalk

[nednednerb]

Originally Posted by djani

And it seems they've broke a custom shortcuts for the MacOS. The ones we make trough a System Preferences Keyboard tab. No way I can call a AudioSuite Gain plugin at a press of a button for example... And no internal Pro Tools option to do that.

1. Make a blank session/ load your given session template.
2. Make new Window Configuration of default view. Set it to config (1).
3. Open a Gain Audiosuite plugin. (and a normalize, and a meter, etc..)
4. Make new Window Config of this view. Set it to config (2), etc...
5. Save a new Session Template.

Now, when you create a new session, use your template and ALWAYS access config (2) via ". 2 *" on a numpad.

This is the preferred built in way recall window configs in later/new sessions (an open Gain plug-in, etc...)

However, I can relate to you wanting your existing method to just work the same way. I never used System Pref's keyboard shortcuts. What happens when you do the old shortcut? If a new default MacOS action is triggered, maybe you can change the default to another key combo, and PT will listen to the old command again.

[thin ice]

Originally Posted by djani

https://www.mediafire.com/view/xxnp1...24.17.png/file

And it seems they've broke a custom shortcuts for the MacOS. The ones we make trough a System Preferences Keyboard tab. No way I can call a AudioSuite Gain plugin at a press of a button for example... And no internal Pro Tools option to do that.

This is pretty annoying, as I have built up loads of these short cuts for common plugins and the colour palette.

[djani]

Originally Posted by nednednerb

1. Make a blank session/ load your given session template.
2. Make new Window Configuration of default view. Set it to config (1).
3. Open a Gain Audiosuite plugin. (and a normalize, and a meter, etc..)
4. Make new Window Config of this view. Set it to config (2), etc...
5. Save a new Session Template.
.

This could help as a workaround, thank you. When I use old System Preferences Keyvoard Shorcuts command nothing happens, PT completely ignores it it seems.

[Jeff Schmidt]

Updated from 2021.10 and it was the smoothest Pro Tools update I've had in recent memory. No hangs, corrupted prefs, or other issues that have plagued previous updates.

Loving the new Atmos Bounce options - that alone will save me a ton of time.

And, I can finally kill the N key right within Pro Tools without using SoundFlow

Just wanted to share a positive experience on here for a change. :)

[jlf37]

Originally Posted by mtmusic

I'm also having a new and extremely annoying MIDI issue after updating to 2022.6 today that seems related. Sometimes when I double click and create a new MIDI note, I'm unable to actually select that note to click it and drag it around. I can use the trimmer tool to shorten or lengthen the note, but I can't select it with the grabber tool, and the i-beam tool just goes right over it. Is anyone else getting this?

yes.