Josh Olenslager
Forum Replies Created
-
Jason,
More than anything it sounds like a playback issue. The log & transfer clips at 2560×1080 take a lot more processing power for playback as FCP has to process real-time rendering to play back the 1920×1080 timeline. The clips which playback fine were also 2560×1080 or were they 1920×1080? That’s where I’d start, but the stuttering is a dead give away that the processor just can’t keep up with the playback speed.
Josh
-
What are you using to transcode your footage? Try making a copy of one of your 25fps clips, drag and drop onto Cinema Tools, click the conform button, and finally select 29.97 from the drop down. If you’re worried about the clip action slowing or quickening, you will want to deselect “keep length 100 % of source.” However, depending on what you’re using to convert the footage, you’ve got different interfaces and options. It’s not going to be detrimental to simply drop your 25fps footage into your 29.97 timeline and have it render out. I would convert to ProRes or whatever codec you’re editing in, just to help with render times, but if you’re worried, convert it at its native frame rate and have FC do its thing when you edit.
Josh
-
Austin,
Frame rates can be tricky. If you’re worried about clip-speed changes I would suggest you transcode everything to whatever your end frame rate will be before editing although if you’re rendering it out in the timeline it will give you a pretty accurate preview as you view it. Both 29.97 and 25 have odd interlacing cadences, even PAL DV strangely enough. That way you can take a glance before dropping them in the timeline. When you transcode, using compressor I assume, but cinema tools would also be a choice, select the “keep clip speed” option. It’s less of a problem moving from 29.97 to 25 as there will be removal of redundant frames rather than creation of extra frames. That should help out any glitches and duplicate frames that tend to make some things look like they stutter.
Good luck!
Josh
-
Transcode to 1080i50 using compressor; frame size is a whole different animal. If you originally have PAL DV you’ll have to pillar box the footage to keep it from stretching. Just select preserve aspect ration (using letterbox) if your moving from DV to HD.
Josh
-
You could try setting to non-controllable device to see if you can get video. Not the best solution, but might let you grab a sample. Easy setup is always a place to start — like you said, 1080i60 sounds like the place to start.
Good luck!
Josh
-
Sean, have you tried simply copying the timeline edit and pasting it into the new sequence? That will get rid of the editing timeline base error you are seeing. I can envision problems with this, but once the media is copied into the new timeline, you may be able to select and remove attributes. That might reset any pixel changes from the SD renders, but it will also lose keyframing and such. I’m not entirely sure it will work perfectly, but it’s worth a shot. At the very least you get some more information and only end up wasting a few minutes and some keystrokes. It’s worth a shot.
Josh
-
Monica,
try this: before you copy the media via media manager, make sure the actual extension is visible — i.e.
“Simon_t2_17.2.10-88” should actually be “Simon_t2_17.2.10-88.mov” (or whatever file type you happen to me moving. It seems that media manager is adding the extra “.10-88” because that is what it thinks the extension is and it is the visible extension in the new location, rather than the actual file type extension. As for getting rid of the extra characters, find a rename program with a remove character range function. They’re pretty fast for this type of task, and are easy enough to find.Hope this helps.
Josh
-
From the sound of it, I’ll bet the clips were never fully transferred to the drive sent you. Have post house resend them and CHECK that they preview before they send back. BIG DEAL. Part of being professional in workflow. I know I would’ve gotten slammed if I delivered stuff that didn’t work.
Good luck.
Josh
-
Do the “bad” clips show a preview when you highlight them in finder? If they come up white or with the QT clip icon, might be a codec issue (MooV is one I’ve never heard of), or just never finalized in transcode–meaning they didn’t get repackaged right on transfer or got cut off early when they were being copied to the drive. You should also open the info box and see how the permissions are set. No Access in this case is a bad deal. Worse case scenario, strip of the extension using r-name or similar, and then try the “open with” function. You can always add the extension back on using r-name again, so is non-destructive. Might give you more information though.
Josh
-
I’ll check it out once I get into the office — believe we’re on the same version, got upgrade recently — but (although you’ve solved already) did you try the presentation specs in QT inspector? Have to highlight the title line, not just the video track. Not sure if there’s a custom presentation size in that, but might be, or a crop dialogue . . . and you’re just flat exporting this out of QT right and setting the frame size there? Rafael is right, too. I’ve seen all kinds of zaniness on odd line ratios, mostly in overlays and edges, but things get out of balance and cause flickering like mad.
Josh