Welcome to our community

Be a part of something great, join today!

  • 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 :)

no Unlimited RT?

Brandon Fraley

Well-known member
Joined
Apr 20, 2007
Messages
2,269
Reaction score
0
Points
0
Age
41
Location
Bay Area, Ca.
I started a new project, imported my proxies, and dropped a clip into the timeline. It changed the sequence to match the clip settings, but for some reason I'm not getting unlimited RT? It's not available in the drop menu.

Any ideas?
 
Most likely your footage dimensions are not dimensions that FCP will work with in RT. This usually happens for me if it's scaled 3K.

ugh, i didn't know that could happen. I shot 4K HD. Is that one of the formats you can't edit in proxy form? If I had known that U would have used straight 4K. :(
 
I had this happen a couple of times. After going insane for a while I worked around it by duplicating an existing sequence that had proxies in it that was working with unlimited RT, dropping the new proxies in, then deleting the old ones. It then would retain the unlimited rt. I didn't solve why it was happening, but this got me editing...
 
Your H proxies should edit without problem in FCP if you shot 4K HD.

and that's my dilemma. My computer can't edit the larger than the M proxies without stuttering badly. :(

Ugh, I thought 4K HD would mean better performance, but instead it looks like I have to spend a couple days rendering my clips first. It would have been MUCH faster and much more versatile to have shot normal 4K. This is something I'll definitely try to remember.
 
Check the codec of the sequence FCP set up for you. it might be set to REDCODE instead of ProRes HQ, because FCP was thrown off by the 4K HD frame size and wasn't smart enough to set it up right.
 
Alright, so I did the trick where I threw in a normal 4K clip into the timeline and then a 4K HD clip, which does indeed give me unlimited RT, but while the 4K clip plays back fine, the HD clip plays back at about 8fps. I've tried it with both M proxy timelines and H proxy timelines. The 4k H proxies even do pretty well, at about 20-22fps, but the 4K HD H proxy plays back around 8fps.

wtf?
 
so I ended up just starting the rendering process (said 13 hours, sigh) and about 2 hours in FCP crashed and said gave me an error message saying the cause might have been "REDCODE.qt" if I remember.

Anyone know if this means anything?
 
Alright, I've tried 3 times now and every time i try to render, FCP crashes and blames "REDCODE.qt".

Does anyone know what this issue is?
 
You can't render to REDCode, it's read-only. Change to ProRes.
 
You can't render to REDCode, it's read-only. Change to ProRes.

checked to make sure, and my sequence settings are set to prores, not redcode.
 
So I'm currently rendering out the clips in Red Rushes (hopefully it won't crash).

So besides the REDCODE.qt crashes, is the point of this just don't shoot 4K HD if you plan to edit with proxies? Or am I the only one who's getting but better play back with $K originated clips over 4K HD clips?
 
My 4k HD QT proxies play fine in FCP7...and FCP6

thanks James, are you noticing perhaps that 4K HD take a little more horsepower, or are they all just exactly the same?

EDIT: I ask because I'm editing on my laptop. 2.33ghz core duo, 2gb ram. I can work with M proxies fine, and H proxies play back almost perfectly, yet the H proxies from the 4kHD material play wicked slow.
 
Yes-- I only ever use(d) _M for editing. Even on my MacPro tower _H were a bit slow. There really is no need to use them to edit with anyway, in my experience. i don't actually use the proxies workflow any more--I transcode to pro res and go from there. It takes a bit of time to do the transcode but then the editing is so much easier (and it's nicer to edit a smooth sequence rather than the 'stuttery' proxies.
 
ok, so I took my footage to a Mac Pro 8 core 2.26ghz, 8gb ram, and I'm getting the exact same performance out of 4kHD _H proxies.

any advice would be extremely appreciated here.

thanks
 
Has this issue been resolved in any way ? or is there some workaround ? 4K works fine with proxy in FCP but the 4KHD does not. :sosp:
 
no, it has not. I opened a support ticket and was told someone would get back to me. Haven't heard anything since. That was at least a month ago.
 
Clarification: The 4096*2304 resolution works fine when using QT proxy in FCP, but the 3840*2160 resolution doesn't. It seams that the UnlimitedRT menu disappears when using the 3840 resolution.
 
Back
Top