ProTools 2020.11

[kosmokrator]

Originally Posted by JCBigler

Right? I mean it's cool and all, but seriously? 512 Master faders?

If anyone out there has a session with 512 Master faders, will you please post a screen shot of it and tell us how you are using them? I really want to know.

But some of the video file and transcoding options look really useful and are something that I have been needing since I've gotten into doing video work during the shut down.

This was implemented for post production users who mix to Dolby Atmos. To achieve certain delivery requirements (and other functionality) you want a master fader for every object.

That alone would be >100 master faders.
Add to that all the master faders needed on stems etc. in post mixing this can add up to quite a lot fast.

Most post production mixing sessions are a lot bigger than anything in the music world.

[Ru_C]

Holy Smoke. Just testing 2020.11 Ultimate on my home/office Mac, & the buffer optimisation actually works !

Well done to the AVID programmers that have finally got (as far as I'm concerned), the single most important aspect of PT Native rigs working properly finally.

[Emi]

Originally Posted by Ru_C

Holy Smoke. Just testing 2020.11 Ultimate on my home/office Mac, & the buffer optimisation actually works !

Well done to the AVID programmers that have finally got (as far as I'm concerned), the single most important aspect of PT Native rigs working properly finally.

I´m pretty sure they did it because of the Carbon engine. They could have done it looong time ago....but...

[Ru_C]

Originally Posted by Emi

I´m pretty sure they did it because of the Carbon engine. They could have done it looong time ago....but...

yeah could be..its as if someone in charge asked the coders to disengage the S**t-Switch

[briaboy]

All working well here, I effin LOVE Pro Tools!!!

[originalscottyg]

The Same As Source option in Bounce to QuickTime is greyed out (even in Mojave, unfortunately). They say that this signals their intention to bring it back soon. Re-encoding a QuickTime movie in Pro Tools is VERY slow. I would highly recommend bouncing audio only to the length of the video file and using Shutter Encoder or FF.Works to "replace audio" outside of Pro Tools.

[bartosz idzi]

Originally Posted by originalscottyg

Yes. The Same As Source option in Bounce to QuickTime is greyed out (even in Mojave, unfortunately).

in Mojave with Quicktime 7 installed (yes, you can) Same as Source option works as advertised.

[originalscottyg]

Originally Posted by bartosz idzi

in Mojave with Quicktime 7 installed (yes, you can) Same as Source option works as advertised.

This isn't working for me. As shown in the picture, Same As Source is greyed out. This is trying to bounce to the exact length of a ProRes Proxy .MOV file.
Am I doing something wrong? I do have QuickTime 7 Pro 7.6.6 installed.

PT Ultimate 2020.11
HD|Native TB
MTRX Studio
MacBook Pro 15" 2019 2.3GHz i9 32GB RAM
macOS 10.14.6

[bartosz idzi]

Originally Posted by originalscottyg

This isn't working for me. As shown in the picture, Same As Source is greyed out. This is trying to bounce to the exact length of a ProRes Proxy .MOV file.
Am I doing something wrong? I do have QuickTime 7 Pro 7.6.6 installed.

PT Ultimate 2020.11
HD|Native TB
MTRX Studio
MacBook Pro 15" 2019 2.3GHz i9 32GB RAM
macOS 10.14.6

I thought you were saying, "Same as source in Bounce to Quicktime" does not work?
Now you're showing Bounce Mix window. It's another process.

Try using 'Bounce to Quicktime' instead. That should work.

[originalscottyg]

Originally Posted by bartosz idzi

I thought you were saying, "Same as source in Bounce to Quicktime" does not work?
Now you're showing Bounce Mix window. It's another process.

Try using 'Bounce to Quicktime' instead. That should work.

Ah! Amazing. Thank you.

I had a custom shortcut setup in macOS for Bounce to Quicktime, which didn't work for me in 2020.11. So I assumed that Bounce to QuickTime was only available as the option in the Bounce Mix window. The menu verbiage changed in Pro Tools, so I had to update my custom shortcut, now it works.