Saturday, March 30, 2019

Re: [Avid-L2] QT Ref Death

 

well, speedwise this is the next best thing:


(Render files still in the making without worries.)

Bouke

Edit 'B / VideoToolShed.com
van Oldenbarneveltstraat 33
6512 AS  Nijmegen
+31 6 21817248

On 30 Mar 2019, at 20:22, 'C. Hess' cfh3media@gmail.com [Avid-L2] <Avid-L2@yahoogroups.com> wrote:

OK, so as I don't get caught up in my own terminology.

Timeline DNxHD 100.  Yes I render out effects
and transcode as need be.

In the past I would then Output/Send to/Make new for a QT Ref.
I guess I'll need to revert to previous version of AME.
Until that is broken by an OS update, etc..

Ugh.

On Mar 30, 2019, at 1:37 PM, Gowanus Canal <gowanuscanalstinks@gmail.com> wrote:

You don't render before exporting QTRef or any other file?



DQS


On Mar 30, 2019, at 2:12 PM, Greg Huson Greg@SecretHQ.com [Avid-L2] <Avid-L2@yahoogroups.com> wrote:

Mxf export is pretty fast, but not 'no render.'  Even fully rendered single-clip red doesn't work anymore.

________________________
Greg Huson
Secret Headquarters, Inc
Greg (at) SecretHQ.com

On Mar 30, 2019, at 10:59, 'C. Hess' cfh3media@gmail.com [Avid-L2] <Avid-L2@yahoogroups.com> wrote:

 

I have been using AME lately to process QT Ref out of Avid.

The clock, of course, is ticking.  I upgraded to AME 2019
and found it no longer recognizes QT Ref files.

Has anyone found a workaround?
Any other codecs support making a reference file,
so we don't have to fully render an output?


Chip Hess
CFH3 Media





Chip Hess
CFH3 Media
312-806-3840




__._,_.___

Posted by: Bouke <bouke@editb.nl>
Reply via web post Reply to sender Reply to group Start a New Topic Messages in this topic (5)

Have you tried the highest rated email app?
With 4.5 stars in iTunes, the Yahoo Mail app is the highest rated email app on the market. What are you waiting for? Now you can access all your inboxes (Gmail, Outlook, AOL and more) in one place. Never delete an email again with 1000GB of free cloud storage.

this is the Avid-L2

SPONSORED LINKS
.

__,_._,___

No comments:

Post a Comment