DV Info Net

DV Info Net (https://www.dvinfo.net/forum/)
-   Final Cut Suite (https://www.dvinfo.net/forum/final-cut-suite/)
-   -   ProRes needs rendering? (https://www.dvinfo.net/forum/final-cut-suite/445624-prores-needs-rendering.html)

Ryan Mueller September 27th, 2009 10:03 AM

ProRes needs rendering?
 
This has never happened to me before, but now for some reason I drop my 5DII footage that has been transcoded to ProRes onto my timeline and it needs rendering? It just recently started doing this.

The only thing that I did before this started happening was I captured some footage from one of my XL2s. After that, for some reason my 5DII footage transcoded to ProRes needs rendering. Does this for both ProRes and ProResHQ footage. Help Please!

Shaun Roemich September 27th, 2009 10:11 AM

What CODEC is your SEQUENCE? Perhaps when you started editing SD footage, you switched your Sequence Preset preference back to something other than ProRes.

If your clip settings match your sequence settings EXACTLY, you should NEVER require rendering unless you add filters, resize etc.

Ryan Mueller September 27th, 2009 10:28 AM

When I drop the footage in I get the "settings do not match... would you like to change them" prompt and I click yes. This should match up the settings and I should not have to render. I have checked the timeline settings and they do match. Could it be something that MpegStreamclip is doing on export?

Shaun Roemich September 27th, 2009 10:33 AM

Fresh out of ideas. Indeed, if you are saying YES to the "Settings" Dialog, no render SHOULD be required. Have you tried a "cold restart" by turning the Mac off and back on. I find FCP6 is a LITTLE quirky ESPECIALLY if I've opened and closed Photoshop a couple of times while FCP was running. I SUSPECT that there is still a memory leak issue there when one is running CLOSE to the minimum specs (2GB memory in my case)

Ryan Mueller September 27th, 2009 11:03 PM

Thanks Shaun, but no dice. Cold restart did not work. This is getting extremely frustrating and is slowing me down so much. Any other suggestions would be greatly appreciated.

Olof Ekbergh September 28th, 2009 07:40 AM

Have you conformed 5D clips to 29.97?

They are 30, so use Cinema tools to conform all 5D clips before transcoding to ProRes.

Then they will play well with all other NTSC footage in a timeline and AJA Matrox boxes etc, will be much happier.

Ryan Mueller September 28th, 2009 07:52 AM

Quote:

Originally Posted by Olof Ekbergh (Post 1408949)
Have you conformed 5D clips to 29.97?

They are 30, so use Cinema tools to conform all 5D clips before transcoding to ProRes.

Then they will play well with all other NTSC footage in a timeline and AJA Matrox boxes etc, will be much happier.

Thanks Olof! Any issues with conforming after the transcode? I have bout 2 hours of footage that has already been transcoded.

Edit: Tried to conform to 29.97 and the timeline still needs to be rendered. I am losing my mind!

Olof Ekbergh September 28th, 2009 08:36 AM

Ryan,

I have had FCP get confused if I conform clips that are already imported.

It should be fine to conform Prores footage.

Conform clips then reimport, and drop one of them in a new timeline, conform timeline to clip. They should then play fine and similar footage ie 1080P 29.97 Prores. Give this a try.

Ryan Mueller September 28th, 2009 12:40 PM

OK now this is really wierd! I went back to an older project that I know that I didn't have this problem on and pulled one of the project's clips into the timeline. It had to be rendered! Something's not right at all here. I didn't have to render when I edited that project before. Do you think deleting user prefs will work?

Olof Ekbergh September 28th, 2009 04:11 PM

Yes trash the prefs and do a restart and reset PRAM (hold command, option, P and R keys down while starting let 4 "dings" go by then let go of keys, and let mac start.

This usually fixes a lot of FCP problems.

Ryan Mueller September 28th, 2009 04:50 PM

Quote:

Originally Posted by Olof Ekbergh (Post 1410641)
Yes trash the prefs and do a restart and reset PRAM (hold command, option, P and R keys down while starting let 4 "dings" go by then let go of keys, and let mac start.

This usually fixes a lot of FCP problems.

This did the trick! Thank you so much for your help. You are seriously my hero of the week! Sorry I got impatient and posted this in another thread as well, but desperate times call for desperate measures LOL. Again, I can't thank you enough.

Dean Sensui September 29th, 2009 01:12 AM

Old Chinese proverb:

If at first you don't succeed, trash prefs.

:-)


All times are GMT -6. The time now is 06:04 AM.

DV Info Net -- Real Names, Real People, Real Info!
1998-2024 The Digital Video Information Network