Welcome to our community

Be a part of something great, join today!

Log in
  • Hey all, just changed over the backend after 15 years I figured time to give it a bit of an update, its probably gonna be a bit weird for most of you and i am sure there is a few bugs to work out but it should kinda work the same as before... hopefully :)

Proxies Dont Work Well In Fcp 6.0.4

A

asheddrick

Member
Joined
Feb 4, 2008
Messages
8
Reaction score
0
Points
0
So here is the deal. I cant get any of the proxy files above 512x256 to play realtime in FCP Pro 6.0.4 without drop frame warnings up the wazoo! 1024x512 seems to hold up allright but I have to dumb down my playback and frame rate settings in the timeline. Is this just the way it is?

I am using MAC OSX10.5.4
with 2x3 GHZ Quadcore Intel Xeon
and 4GB RAM

with newest RED and QTIME software.

also have R3D's playing from a apple Xraid 5,0.

Is the recommended workflow to still transcode and edit in prores and then run through crimson?

Ive been out of the loop for a few months so if there were any new developments Id love to hear about them!
 
Are you playing back using Low Quality and did you let it switch the sequence settings to match the clip settings?
 
Here is a good example of the proper settings with a Kona card for realtime proxy playback:

http://www.reduser.net/forum/showpost.php?p=170194&postcount=15

These work for me but I have to say that I don't use the proxies for anything. One you begin to add layers or make multiclips or do the kinds of things you do in anything other than a single layer radio edit the proxies bog down the system. My first order of business is to make self-contained QTs
 
stevesherrick said:
Are you playing back using Low Quality and did you let it switch the sequence settings to match the clip settings?
Click to expand...

Yes I am letting FCP auto adjust the sequence settings. and using the redcode codec. and I am playing lower quality.
 
editblog said:
Here is a good example of the proper settings with a Kona card for realtime proxy playback:

http://www.reduser.net/forum/showpost.php?p=170194&postcount=15

These work for me but I have to say that I don't use the proxies for anything. One you begin to add layers or make multiclips or do the kinds of things you do in anything other than a single layer radio edit the proxies bog down the system. My first order of business is to make self-contained QTs
Click to expand...

Thank you both for the feedback!
 
Proxy edits

Proxy edits

I second the notion, Asheddrick.
Work with proxies only with one or two, three layers.
More than that and you start to feel the delay...

More ppl are having trouble with proxies and there are a few threads on the subject [http://www.reduser.net/forum/showthread.php?t=17139]

We need to figure out this problem and have a quick fix.
Is it build 16 ?
We know it's NOT RAM.
Any remarks are welcomed.
Thanks
 
Snow said:
l]
We need to figure out this problem and have a quick fix.
Is it build 16 ?
We know it's NOT RAM.
Any remarks are welcomed.
Thanks
Click to expand...

I think the problem is just inherent in what you are asking the Quicktime compatible app to do. These are QT REFERENCE files so in addition to just pointing to the real media (there's a reason a complex output often works better when it's a self-contained quicktime vs. a QR reference file) you are doing all this de-bayering as well as the normal overhead of video editing. I know this de-bayering process is supposed to be very efficient but no matter how efficient it is when you add that process on top of all of the stuff you do during the normal course of anything other than a single stream cuts-only edit it just seems like too much for the computer to handle. Maybe in a couple of generations when cpus are faster and REDCODE is more advanced but for now I'm just not going to try any real edits with the unlimited RT setting and an orange render bar. That's just not the most efficient way to edit.
 
Quick fix to this

Quick fix to this

It is clear that the proxies are heavy on the system, and are not intended for multi layer work.
No quick fix will fix that.
What i am looking for, is a solution for editors working with proxies,
that have artifacts during editing, like dropped frame window pop-ups,
even though you turned it off in user prefs, and the know green screen pop ups [when one layer in a comp shows up as green].
 
I'm having the same problem. I have 16gig of ram, I'm running through a big RAID, I'm on a 8 core that has everything chucked at it for performance reasons. I'm at low compression, unlimited RT etc etc etc... and still it pops up with dropped frames. PISSING ME OFF big time.

The stupid this is this, We have just finished a 4 RED camera shoot.
One of the cameras was build 15 and these proxies work fine in the 2k sequence time line. No dropped frames.
Yet in the same time line sequence we have put 3 different camera build 16 QT proxie movies. 1 of these work fine, no drop outs and the other 2 cameras QT's are crap. Errors, drop frames etc etc. So why does some cameras make perfect QT's that we can cut and view perfectly and other cameras (SAME BUILDS, SAME FCP Settings) play like shit in the same FCP time line.

CAN SOMEONE AT RED PLEEEEEEEEEEEEASE GIVE US A SOLUTION.:help:

thanks
 
Hi guys,

I'm in Morocco starting the edit of a feature film shot on Red.
I'm basically confronted with the same questions about using proxies vs pro res.
Meaning, the film will be 90minutes at least, and based on what I'm reading here, and on the last 3 days I spent playing around with Final Cut and Red rushes, I'm puzzled.

Do you have any recommendations for me in order to simplify my decision ?
Knowing that we're already sure we'll Scratch the film in the end.

My first post on Reduser,
another Red One user, Casablanca, Morocco
 
julien foure said:
Hi guys,

I'm puzzled.

Do you have any recommendations for me in order to simplify my decision ?
Knowing that we're already sure we'll Scratch the film in the end.

My first post on Reduser,
another Red One user, Casablanca, Morocco
Click to expand...

If you have a worry about cutting with the proxies then that is reason enough not to use them for an edit as intensive as a feature. There is no way I cut anything other than the smallest and simplest edit with the proxies so there is no way I would ever attempt a feature with them. IF you know you are going back to Scratch then I would even make self-contained QTs smaller than ProRes for the offline. That'd be a sweet workflow.
 
editblog said:
If you have a worry about cutting with the proxies then that is reason enough not to use them for an edit as intensive as a feature. There is no way I cut anything other than the smallest and simplest edit with the proxies so there is no way I would ever attempt a feature with them. IF you know you are going back to Scratch then I would even make self-contained QTs smaller than ProRes for the offline. That'd be a sweet workflow.
Click to expand...

If you do go that route, be careful to log every self-contained prores file with the correct reel name, clip name, and timecode, otherwise the conform in Scratch will be manual, and that will be at least as painful as cutting P_ camera proxies in FCP.

cheers,

John T.
 
Thanks for the feedback.
I didn't like the idea of editing with this orange render bar over my head !
Is "log and transfert" the best method to log the pro res ?

I've had a little bug yesterday on final cut. As I was doing tests and dragging 1080X512 proxies onto my sequence for sound synchronism, the pop up saying "the clip isn't in the same resolution as the sequence" came up to me a couple of times. Even though I had already prepared the sequence by dragging clips. I rebooted my machine and it went well, maybe the poor thing was a little bit tired :-)

Cheers
 
julien foure said:
Thanks for the feedback.
I didn't like the idea of editing with this orange render bar over my head !
Is "log and transfert" the best method to log the pro res ?

I've had a little bug yesterday on final cut. As I was doing tests and dragging 1080X512 proxies onto my sequence for sound synchronism, the pop up saying "the clip isn't in the same resolution as the sequence" came up to me a couple of times. Even though I had already prepared the sequence by dragging clips. I rebooted my machine and it went well, maybe the poor thing was a little bit tired :-)

Cheers
Click to expand...

If they REDrushes supporting audio (or you don't need audio since recording dual system sound) then it is what I would use. Otherwise the Log and Transfer tool is great. As was stated above just be mindful of file names and such, in other word don't change them, and you'll be fine.
 
Here we go, project "Terminus des Anges" launched !!
Will keep posting and tell my experience !

Thanks again for the answers.
 
You must log in or register to reply here.
Back
Top