Webinar: Pro Tools: Get a Grip on the Pro Tools Video Engine
 

Also posted this on gearslutz, but wanted to make sure everyone knows about this, because it is that awesome.

Since PT 11 and the new video engine we've all seen a plethora of threads and posts regarding video issues. Well this week Avid did a live steam technical webinar on this topic. I strongly recommend everyone using the video engine to go and watch it here: Pro Tools: Get a Grip on the Pro Tools Video Engine

https://youtu.be/6gxLZid2VR4

I learned a lot. It is really a great guide with tons of useful info. I have read tons of threads, whitepapers, readmes etc. on this topic and this sums it all up really nicely. They dig into some of the detail of what AVE and how it works, codecs, optimization and troubleshooting. +1000

Re: Webinar: Pro Tools: Get a Grip on the Pro Tools Video Engine
 

This is great!

Re: Webinar: Pro Tools: Get a Grip on the Pro Tools Video Engine
 

Yebo very good....would like to hear more on getting files from editors,file size and codecs, drives and storage, and do we need video sync, word etc

Re: Webinar: Pro Tools: Get a Grip on the Pro Tools Video Engine
 

That video covers CODECs perfectly. What more do you need to know?

Re: Webinar: Pro Tools: Get a Grip on the Pro Tools Video Engine
 

Make it a sticky

Re: Webinar: Pro Tools: Get a Grip on the Pro Tools Video Engine
 

The Webinar has shown what video codecs best suit Protools. So understanding this ask the Video editor upfront to supply the video encoded in the format you want.

As an Avid video editor it it easy for me to supply almost any codec that I am asked for. DNx and ProRes are the easiest and they are the best (according to the webinar) for Protools. Making a H264 is more time consuming and relatively a PIA. ProRes is easy form Final Cut. DNx and ProRes Both can be made in Premiere (very limited experience with Premiere)
An hour of DNxHD 36 takes up approximately 18GB's and an hour of standard def Avid DV takes up about 12GB's. I can encode either directly to and transfer via a USB stick. Obviously I can copy these to whatever media folder on my Protools system I want in a very few minutes.

FYI a single 3TB 7200 SATA drive used for the MC edit and containing all of MC's audio and video media (at DNxHD 185) for a 92 minute program (2.75 TB's) moved to my Protools computer gave my trouble free AVE playback. (only working with 20 audio tracks)

Andrew

Re: Webinar: Pro Tools: Get a Grip on the Pro Tools Video Engine
 

done.

Re: Webinar: Pro Tools: Get a Grip on the Pro Tools Video Engine
 

This is a swell webinar- but it lasted an hour, and I got about 6 pieces of valuable information out of it.

Is it not possible to somehow compile this into a sheet of paper with the relevant information?

Why are the users of Pro Tools required to put up with this crappy method of disseminating information. For years and years the folks at Digidesign, and now Avid - have known all kinds of important information about how Pro Tools works, but they keep their little secrets to themselves. 'Blowing out the memory." and "setting the throttles," and now those little check marks in the video clips. Why is this not documented in the documentation?

I've been personally bitten in the ass and bled severely by the cute little bits of held-back information which had left me looking incompetent and foolish in front of clients. There is an enormous failure of Avid to put information forward so that those of us who don't want to spend hours and hours listening to these insipid webinars, or participating in Avid special events. How about that you write a manual that covers all of this important information?

Re: Webinar: Pro Tools: Get a Grip on the Pro Tools Video Engine
 

Avid please, please fix broken links to the archived webinars here:
http://www.avid.com/en/pro-mixing-we...id=AV-SM-PT9-5

Re: Webinar: Pro Tools: Get a Grip on the Pro Tools Video Engine
 

Thanks for reporting this. Looks like the last 8 are broken, please let us know if you find others. Submitted a ticket to the webteam to fix them.