red render bar after upgrade

[Keith Alan Morris]

I upgraded to the new codec (RED FINAL CUT STUDIO 3 INSTALLER, v.30.1.0) and now I have the dreaded red render bar on everything on my timeline. What can I do to make that go away?

system specs:
MacBook Pro



Model Name: MacBook Pro
Model Identifier: MacBookPro3,1
Processor Name: Intel Core 2 Duo
Processor Speed: 2.4 GHz
Number Of Processors: 1
Total Number Of Cores: 2
L2 Cache: 4 MB
Memory: 4 GB
Bus Speed: 800 MHz
Boot ROM Version: MBP31.0070.B07
SMC Version (system): 1.16f11
Serial Number (system): W87471H5X92
Hardware UUID: 00000000-0000-1000-8000-001B63933402
Sudden Motion Sensor:
State: Enabled

 

[Ben Brainerd]

It really depends on a lot of factors, most of them related to your FCP settings. What are your sequence settings like? What video card are you using in your MBP?

 

[Keith Alan Morris]

 

[Keith Alan Morris]

 

[Keith Alan Morris]

 

[Keith Alan Morris]

 

[Gunleik Groven]

Could be your odd framesize...

 

[Keith Alan Morris]

I don't know how to check what video card I'm using... But haven't had any problems before now and I edited a full feature at 2k on this machine. Juuuust barely....

 

[Keith Alan Morris]

Could be your odd framesize...

Even at standard frame sizes, same problem. Argh!

 

[Gunleik Groven]

@ 1120 x 480 Rez?

 

[Gunleik Groven]

Are you editing from Cam Proxies or... ?

 

[Keith Alan Morris]

Are you editing from Cam Proxies or... ?

yes

 

[Keith Alan Morris]

@ 1120 x 480 Rez?

same problem. square pixels, too, right?

 

[Gunleik Groven]

So these are maybe 4.5k p proxies?

 

[Keith Alan Morris]

So these are maybe 4.5k p proxies?

close. M proxies.

and i changed sequence settings to match clip settings. still a red render bar.

 

[Gunleik Groven]

My bad.
Had to be M...

Still
I think that 4.5k ratio may be it.

In my experience isn't too fond of odd ratios (might well have changed, but still...)

Have you set the sequence to automatically update to the kind of media you are dropping on it?

I guess you don't have access to a Rocket, but could you try to letterbox-render it into a 2k prores file (with black above and under the image) to see if that plays well?

 

[Keith Alan Morris]

it cant be that odd ratio. i've edited other things at that size. surely others aren't rendering every qt proxy that they put directly into FCPs timeline for dailies, etc.

 

[Gunleik Groven]

Have you tried to render it into a standard 2k/1080 size?

You'd (obviously) be surprised to learn how many renders their offlines for anything closing in on longer form... -

 

[Ben Brainerd]

it cant be that odd ratio. i've edited other things at that size. surely others aren't rendering every qt proxy that they put directly into FCPs timeline for dailies, etc.

Actually, pretty much everyone is rendering out prores for dailies, particularly because of the weirdness with proxies, some of which you're experiencing.

I'm gonna have to agree with Gunleik and say that your odd frame size is the most likely culprit. Try dropping those same proxies into a 1080 timeline and see what happens.

 

[Keith Alan Morris]

The word render does not compute. I shouldn't have to start rendering when I haven't had to since 2008. WTF?