Ben Insler
Forum Replies Created
-
I don’t know the answer to this – haven’t picked up Studio 2 yet…but I’ve seen some other posts on here about long render times. Have you guys searched in the archives?
-Ben
-
How big is the photo? You might need to drop its resolution so Final Cut doesn’t have do the scaling and pixel interpolation calculations on a large scale. Final Cut’s not very good at that. Use Photoshop to scal the image down to the largest resolution you’ll need, and then bring it into FCP
-
Byrd,
In my experience, I’ve never found Cross Dissolves to consistently render quite as smoothly and evenly as I’d always want them to… it depends on the footage that you’re using. It’s not ACTUALLY the cross dissolve, it’s more like an optical illusion that can appear smoother or more rough depending on your A and B clip.
Try opening up one of the bad cross dissolves in the viewer and changing the starting opacity to 8% (or the ending opacity to 92%, if it looks like the cross dissolve is flashing off at the end). If all else fails, do a cross dissolve manually with your opacity overlays – you can command+click on opacity keys with the pen tool to add bezier handles and can make a smooth ramped fade, a logarithmic-like fade, etc.
Does that help, or are the fades actually rendering wrong? (…if it helps, I want tickets to the premiere!)
All the best,
Ben
-
My guess is that this has something to do with the way you encoded the clip. For some reason, while the clip is playing, final cut it interpreting it with a different pixel aspect ratio, and thus stretching the clip. Try re-encoding the already converted ProRes422 file through compressor, and make sure you’re sending it out with the appropriate resolution AND pixel aspect ratio. I’ve seen ProRes422 firsthand and it seems to work very well – I would doubt that it’s a FCP playing ProRes422 problem alone.
-Ben
-
The scroll wheel’s second function in FCP is a jog wheel. You can’t assign custom functions to it.
-Ben
-
You can’t change the default settings on the video generator…at least to my knowledge. Go get around this, I have a toolkit project file that hold all of my commonly used elements (slates, filters, custom transitions). I just open it and use it like another ‘Effects’ tab when I need to pull something into my current project.
In here, I’ve set up a sequence that has Bars linked to 4 tracks of tone set to -20. I just edit this preset into my sequences when I’m setting up a sequence for output.
-Ben
-
This will also happen if you’re capturing to a drive that is too slow to keep up with the necessary data rate that is required to stream your media for capture. You should be using at least a 7200 RPM 8MB Cache Firewire 400 drive.
-
Yes it’s true… because you’re literally scraping the tape across the play/record head in the deck as you dub. Every time you do this the tape can become SLIGHTLY more degraded and fragile. That said, there’s not much difference between recording over a previously recorded tape and scrubbing back and forth with the jog wheel over a house master for 10 minutes (in fact, the jogging is probably worse, but you rarely hear anyone talk about how that’s terrible for the deck).
The real issue is the tape, not the deck. It’s best to record new material over clean tape to ensure that you’re recording the best possible signal. If the tape is new/clean, you’re less likely to encounter an area on the tape where there is a glitch, or where residual metal flakes on the heads may have collected on the tape (over the course of a previous dub session, perhaps), thus causing recording errors. Clearly, performing insert edits on tapes works fine and is acceptable, but nonethelss… in practice it’s best to make dubs on clean tape.
-Ben
-
You need to be using sequence settings that support RT playback withing FCP. You can set the sequence settings to whatever you want and always get RT performance.
It seems that this is the double edge of the sword that is automatic sequence settings in FCP 6.
-Ben
-
No. Final Cut doesn’t work like this.
You could make a wallpaper on your editing system that reads “Set Your Scratch Disks”
-Ben