Color 1.5 render problem

[Marc Vanocur]

Not just a color issue. FCP has been acting quite unusual lately while using the ProRes 4444 codec. I get pops and snaps in the audio followed by green flashing with the clip and then crashing. I am running a 2.93 Nehalem with 16GB. It does it only after awhile of working in the timeline. If I reboot and go back to work it works well for some time and then does it again. Sounds very related to the Color issue. Still on Leopard. Considering updating, but currently mid-project.

 

[Ferrum]

someting is wrong with the Graphic card ----- Iguess Graphic card memory should be 1G or more , the Quadro FX 4800 may work but it's too dear-------$1700 the Gforce GTX 285 also can work on MAC ,maybe I will try ---- The Graphic Card ----- The Graphic Card The Graphic Card ----- or who has tried the red rocket?????

 

[Wade McDonald]

I got mine to stop giving garbled garbage by being very careful and pure about the workflow. Following the whitesheet to the letter, I created a FCP timeline at 2:1 H-resolution and exported it to Color, changed Color's internal pixel format to 10-bit and THERE -- and not before -- I made the switch to 16:9, 1920x1080, and adjusted Geometry to compensate. I've been able to export in DPX, ProRes444, and ProRes422HQ with no problems. Grading was also much smoother, even when using Primaries, heavy secondaries (I used 6 on one shot) and ColorFX on every shot (I usually reserve Primary Out for minor fixes at the end, so didn't use any.)

Not only did I not have any issues, but there was no need to reboot to clear everything out and stop it turning purple and green garbage.

Hope that helps as a workaround for now.

W

 

[David Battistella]

Because of a couple of nagging problems (most not RED related, but networking, audio etc !) I decided to upgrade to Snow Leopard and do a clean install of everything. So far, I've been able to do clean renders...but i have no idea what caused the problem in the first place. i'll keep you posted...

I did a clean install and that did not solve the problem.

David

 

[David Battistella]

I got mine to stop giving garbled garbage by being very careful and pure about the workflow. Following the whitesheet to the letter, I created a FCP timeline at 2:1 H-resolution and exported it to Color, changed Color's internal pixel format to 10-bit and THERE -- and not before -- I made the switch to 16:9, 1920x1080, and adjusted Geometry to compensate. I've been able to export in DPX, ProRes444, and ProRes422HQ with no problems. Grading was also much smoother, even when using Primaries, heavy secondaries (I used 6 on one shot) and ColorFX on every shot (I usually reserve Primary Out for minor fixes at the end, so didn't use any.)

Not only did I not have any issues, but there was no need to reboot to clear everything out and stop it turning purple and green garbage.

Hope that helps as a workaround for now.

W

Wade.

I am going to try this.
David

 

[David Battistella]

Everybody listen up.
Wade's workaround ACTUALLY works.

Doing some more testing now, but that does solve the problem.

David

 

[Jean Déraps]

David, you're right. My clean reinstallation with Snow Leopard and FCS2 seemed to work initially but now is giving me the same garbage output. I would be nice if the people at RED would chime in here to at least say they're looking at the problem.
Thanks

 

[David Battistella]

Hi all,

Wanted to report a solved problem here.

Some of you may know that I have been reporting a problem with garbage renders from FCP.

For the benifit of the world I am reporting my workflow here to help anyone else who runs into this.


1. Edited in FCP with transcode OFFLINE media created with clipfinder (or redrushes)
2. Exported XML file of FINAL FCP SEQUENCE
3. Opened Clipfinder and ran CONFORM FCP PROJECT with XML file to create NEW file.
IT IS VERY IMPORTANT NOT to RESIZE the SEQUENCES to 1920x1080 in clipfinder.

4. Opened NEW XML in FCP and set the sequence to the following. CUSTOM 2048x1024, 23.98, etc
5. used SEND TO COLOR command to open sequence in COLOR
6. CHANGE floating point to 10-bit in COLOR
7. Change EXPORT size of FINAL project in USER settings (it is very important to do this set within COLR or it will not work!

You now have FULL access to the R3D files and can use the RED TAB in Color and render out great Prores 4444 or Uncompressed without any probllems.


I am so glad I finally solved this nagging issue.

David

 

[Ferrum]

I may solve the problerm

the Graphic card memory is too low----
if you render Proress4444 or DPX 2K 10bit OK
if you render 2K 12bit BAD
if you render 4K 10bit BAD

well change a Quadro FX4800 all OK

 

[Jean Déraps]

Ferrum, thanks for your input, but I doubt this is *the* problem (it may be part of the problem) since I was able to render 2k @12bit (and still am sporadically) before the 1.5 update, but not now, and I haven't changed cards. And we shouldn't have to buy a $1500 graphics card to *not* get garbage output..my 2 cents.

 

[Ferrum]

just like you said , the problerm should be clear, we should know all of the parts---

if the color render conect the Graphics memory, low Graphics memory should be long time but not a bad render resoult.

I'm still searching 路漫漫其修远兮 吾将上下而求索

 

[David Battistella]

Follow the FCS whitepaper STEP BY STEP and you should not have the render issues. I have posted solutions and workarounds to this problem. It is not the graphics card. It has to do with the REDCODE plugin and Quicktime.

David