[Oscar Brightman]

Found it. I’ll give it a shot! Thank you.

[Oscar Brightman]

I am using Compressor 3. Can’t find “Frame Controls” settings? Could you please direct me?
Thanks,
Oscar

[Oscar Brightman]

That makes sense but when I tried deleting them the timeline freezes up and I get death by colorwheel. Then I have to forcequit and start over. It doesn’t like the render being pulled out from under it. If I delete the render files without the project open then the project freezes up when I do open it. A bit strange and buggy. It’s a ProRes sequence and the files are a bit large.

[Oscar Brightman]

UPDATE:
Changed the sequence settings to DV and it played the ProRes Movie file perfectly to the external monitor and DVCAM deck. Thank you!

[Oscar Brightman]

Thanks, I think you got it. Yes, my sequence was 24 fps and I usually output to HDCAm but needed a DVCAM version for a certain festival. I thought it would convert on the fly but obviously I was wrong then. glad you mentioned this, it seems like an easy fix.

So then, my quicktime movie file is 16:9 Prores 24 fps. If I place that movie file in a 29.97 sequence, that should be all I need then, yes?

Thank you.

-oscar

[Oscar Brightman]

I think you Sherlocked it! Thank you. Yes, I am Sloppy with a capital S. (sometimes this gets me some amazing ‘happy accidents’, other times, well, I wind up here. Will try this out.
Thanks again,
Oscar

[Oscar Brightman]

Thanks for the feedback guys but that is exactly what I was trying to do, create two projects with two different settings.

I started with a prores sequence – fully rendered – and did a SAVE AS to create a new project called 10bit. I changed the settings on this new sequence to 10 Bit UC. It required a render, of course, which I did.

Ok, now the strange part: When I re-open the original prores project that was already rendered, it now needs to be re-rendered again. It appears that I cannot have two seperate projects with different settings exist at the same time without have to re-render one or the other. I guess this is because they share the same media but I thought that they would store their rendered files and be okay with it.

[Oscar Brightman]

Okay, thanks, for the reply. I do realize that you must render if you change the sequence settings from the native file format. I am wondering if after I change the settings (say to 10 bit UN) and render all for a given sequence and save it, can I work in a manner so that if I change it to something else and then change back to 10 but UN, it will still have the previously rendered media and not need to be re-rendered again since nothing has changed?

I think, moreoever, I am working in the wrong way. There is probably a better way to export a 10bit UN from a ProREs sequence than to actually change the settings of the sequence and export CUrrent Settings. I did this to take advantage of any uprezzing that may occur for the titles, graphics and other media that was not fixed in prores.

[Oscar Brightman]

A big help. Thanks!

[Oscar Brightman]

Dear Tom,
That’s great! I had no idea that Final Cut had those “cloud” effects built in. I’m going for a bit of a campy feel so even if it is less than photo-perfect it should work great for my project. Thanks again…

That being said, I just tried it and it appears my system graphics card can’t handle the effect. I thought I had a pretty robust system (it’s a Quad core 2.66) but I get the message “The effect “clouds” cannot be rendered in a sequence of this size with the current graphics card.”

My sequence is a 1920 x 1080 HDTV1080i 16:9 Apple ProRes 23.98. It’s footage I shot in Super-16 film then telecined to HDCAM then digitized to ProRes.

Any idea of a workaround or is it already time to upgrade my graphics card?
System is not yet a year old but already feels obsolete working with effects in HD/ProRes! I’ve seen this same message with the “bloom” and “earthquake” f/x by the way.

Here’s my system:

GRAPHICS: NVIDIA GeForce 7300 GT
2 Dual-Core Intel Xeons(QUAD Core)
Processor Speed: 2.66 GHz
3 GB RAM

FCP STUDIO 2
MAC OSX 10.5

Thanks to Tom and any others who want to chime in.
best,
Oscar