Monday, September 7, 2015

[Avid-L2] Re: OMF/AAF from Premier to ProTools Issues?

 

"Get used to it. While it isn't a pretty vision, it is the way things are going."   Oliver they say a similar thing during prisoner orientation at the Grey Bar Hotel. 

Perhaps "basic" is the wrong term.  Necessary in my world would be more correct.  Protools is the audio workstation of choice in my neck of the woods.  The inability to interface in a reasonable manner is a big problem.  Perhaps we just haven't figured out the secret sauce yet.

So, "The way things are going." means less compatibility and a constant need for changing os platforms to maintain Adobe compatibility with the latest versions of AE etc...  That approach works okay when users are stand alone and delivering completed media assets but not when the practice of sharing active projects is becoming common place.  I now receiver fairly elaborate projects for Lwr 3rd etc... that I have to enter the various names for a series.  Given the AE person is going to be on a more recent version of Creative Cloud I'm left behind in an environment where I can't upgrade my OS due to facility infrastructure so I can't open the projects.  If this is the way things are going it's the wrong direction.

It's like an established "media" company would upgrade their flagship editor in a manner that it no longer has broadcast video output, uh oh wait that's already happened.  Or it's like an industry standard color corrections system is suddenly free to the masses, uh oh wait that's happened too.  Well it's like if a major media company not only owned a video editor but and audio workstation too those products would integrate seamlessly  wouldn't they?, uh wait that's happened too.

Okay it's just time to bend over one more time for a media cavity search all in the name of progress or I think more accurately profet.



---In Avid-L2@yahoogroups.com, <oliverpeters@...> wrote :

Actually, there's nothing particularly basic about an export to Pro Tools. Part of the problem with Pro Tools is that it used to be the only game, so things like plug-ins, AAF and OMF transfers were often tweaked away from their spec to be optimized for Pro Tools. That's why RTAS-compliant plug-ins that worked in Pro Tools didn't necessarily work in Media Composer. The reason is because they didn't adhere strictly to the spec. I'm not sure whether that might be part of the issue, but it could explain why MC -> PT might be more successful than PPro -> PT.

As far as backwards compatibility, AE goes back 1 version usually, Photoshop has much better backwards compatibility and Premiere Pro has none. Sometimes updates are tied to OS updates and sometimes they aren't. Avid is usually a step or so behind and many "pro" users are light years behind in the versions they are running. But yes, no one has as good backwards compatibility as does Avid, but I suspect that's changing, merely because of feature support.

Get used to it. While it isn't a pretty vision, it is the way things are going.

- Oliver
 

__._,_.___

Posted by: bigfish@pacbell.net
Reply via web post Reply to sender Reply to group Start a New Topic Messages in this topic (9)
this is the Avid-L2

.

__,_._,___

No comments:

Post a Comment