QT Proxy playback problem in Final Cut

[Mark Wolf]

I can't play back QT proxy clips in the FCP timeline - the clips play for a second then I get the 'dropped frames' error message.
I've set the Sequence RT to 'Unlimited' and Playback Quality to 'Low', and I'm using ProRes HQ in my Sequence settings.
No other applications are running simultaneously.
I have a MacBook Pro.

Any suggestions.

Thanks.

MW

 

[Morten Eriksen]

What size proxys do you use?

 

[Mark Wolf]

I loaded the Quicktimes through 'log and transfer' but when you do this FCP doesn't tell you if they are H, M, or P QT's being transferred. When I import the QT's manually I can play the M QT's fine but this is very long winded if you've got a lot of footage to load in.

 

[Bert Claes]

There is a substantial difference between importing the Red files using Log and transfer and just dropping the qt proxies into fcp. Try reading http://www.red.com/support/download/106 first and then reporting back here! (i wanted to say RTFM, but it sounds a bit aggressive... but in the end it boils down to that.. )

Bert Claes, Video Engineer, Grid VFX, Belgium

 

[Mark Wolf]

Thanks Claesbert but the first action I took was to, as you say, RTFM which you kindly sent me the link to. The manual suggest two methods of ingesting media into FCP. The second of which is 'Ingesting Quicktime Files' using Log and Transfer. The manual refer to these files as RED Media Quicktime Files.
The problem still exits that the QT files won't play back in FCP even the the manuals recommended playback settings.

 

[Bert Claes]

I think you shouldn't expect RT playback, so i will drop frames, but if you disable "report dropped frames" it should continue playing, even when dropping frames.

 

[Bert Claes]

btw, i find it faster importing the proxies then converting the R3D files using Log and transfer... would you care to elaborate further on why you find importing the proxies longwinded? I just drop in all the folders of that shoot and search for "_M" and drop those in a timeline or a bin.

 

[Mark Wolf]

Thank you very much. Playback works now.

MW

 

[Mark Wolf]

Importing proxies is not long winded as such but I find using Log and Transfer a quick and more convenient way of only importing what you need for each take rather than the whole take.

 

[isotron]

error playback , bug?

error playback , bug?

i imported the _P proxy files, i play one clip... all is fine,BUT if i put a second clip over the other on V2 f.e. , the playback stopped , and i get the "dropped frames error" . Disable "report dropped frames" doesnt solve the problem, because if FC dropped frames - the Aja preview out to the monitor stops too!

is this a bug? my system schould be fast enough. (troughput of 250 -300 MB/S), and if i use log and transfer with ProRes 444 and editing 2k instead of 720x576 proxy , i have no problems....???!!! (but i cant wait of the "log and transfer"...need to copy->import->go!)

 

[Simon Blackledge]

Are you adding a dissolve or altering opacity with the clip on V2 ?


I'll try it here now
s

 

[isotron]

with no transitions and no opacity change!

FC Version 6.02 and 7 .

 

[Brandon Kraemer]

Anytime you stack clips in FCP, its looking at all the clips in the stack. This is because FCP (unlike AVID) is always thinking about the clips in a transfer mode way, with the default being none... but it is still thinking about it in terms of 100% alpha. Even on a fast DAS RAID, you will see performance issues stacking 3 or more proxies.

I find that _M proxies, with RT set to Unlimited, Full Frame Rate and Dynamic Quality seems to work the best. I also let my first edit dictate the sequence settings, so long as working 16:9/2:1 is ok for the rough cut process. Then I set the Kona 3 to speak the same language as my timeline for outboard playback.

Unless you need to check for critical focus, I work un-rendered until late in the process. Once you render proxies, it refers back to the .R3D file and what you see is tack sharp. It would be great if RedRocket would support FCP proxy workflow to make the RT engine even more robust, or at least the render process much faster. I think proxies are under used, transcoding just to do an offline is not necessary and creates a lot of media at a considerable cost in time. As with anything, there are trade offs, but I find a good workflow makes it all worth while.