Tim Kolb
Forum Replies Created
-
It sounds like a pretty fine error…what is the framerate of your timeline? 23.976? 24.0? Also check the framerate of the longer clip.
TimK,
Director, Consultant
Video Producer at I-CAR -
Now there’s a name I haven’t heard in a while…
Most computer systems manufactured within the last 10 years will actually handle DV far faster in software than using a card…and the Raptor wasn’t even a powerful card in terms of 15 years ago…
Getting the modern version of Edius would allow use of any Canopus DV files that you have…or I suspect the software codec is still floating around the interweb someplace.
I find it highly unlikely that there are drivers that would install in any modern OS for that card…you’d probably need to install to a 32 bit XP machine at the latest.
(I got rid of my DV Rex a loooong time ago…and I have a Storm card somewhere in mothballs that I haven’t used in eons but I just can’t bring myself to toss that kind of stuff.)
TimK,
Director, Consultant
Video Producer at I-CAR -
With the cumulative lag you describe, I’d first ask what sort of harddrive are you using? You’re not running media on your system drive?
TimK,
Director, Consultant
Video Producer at I-CAR -
There are occasionally effects plugins, etc that just refuse to play nice with an export. They may look fine in the timeline but for whatever reason they just bork an export.
Daniel’s solution was to force a preview render, as you guessed. If you run into this again and the section just refuses to render (typically because your machine has no problem playing it in real-time), I’ve resorted to placing a blank adjustment layer or a blank title over the top of the problem area to force the section from yellow to red.
In past versions you typically needed to check ‘use preview files’ in the export dialog to bypass running the effect again in export, but with newer versions you can set up more FCP-like workflows where you set your preview render to something like ProRes and then avoid re-rendering when exporting to ProRes.
TimK,
Director, Consultant
Video Producer at I-CAR -
Premiere Pro with preview render an entire defined area or sequence as a clip, and it does cause one to wonder sometimes just what constitutes sufficient change that the stored render is no longer suitable and a re-render is triggered. It does seem as if trimming usually works fine but any change within the span of a clip itself (trimming/cutting one layer of several that are composited together, etc.) will usually cause the entire clip to require a re-render.
Alex’s idea was what I would typically do in these cases…it saves some time.
TimK,
Director, Consultant
Video Producer at I-CAR -
Until you mentioned the issue with ProRes, I was going to ask if the audio was conforming during the lag…but ProRes wouldn’t conform.
It definitely sounds like a PPro version issue as you’ve trouble-shot all around it (other platforms/other versions).
TimK,
Director, Consultant
Video Producer at I-CAR -
Well…of course Premiere Pro has always placed the in and out point at the frame cut the play head sits on…and the frame that is visible is always the frame forward of the playhead…therefore an out point has always been set to end with the last frame being the one previous to the one that is visible… That’s been in Premiere Pro for as long as it has existed. (And not something that hasn’t been mentioned to Adobe by any number of us…)
As much as I’d like it to include the visible frame as the last frame sometimes…it’s simply something I’ve gotten accustomed to.
On media that isn’t the same framerate of the sequence (which could be fixed in a couple of clicks by the way with selecting the clip in the bin and doing a modify-interpret footage), the out point would have to set itself at the last whole frame without interpretation as the outpoint is on the clip itself, not the sequence. So…I suppose you would run into instances where you pick your out point in time on the sequence, but you’re sitting in an interpreted frame (or fraction of) in terms of the clip, so the clip goes back to the last complete frame.
If you modify the clip so the framerate is the same, do you see the same behavior?
TimK,
Director, Consultant
Video Producer at I-CAR -
If you auto-scale to the timeline size, you’re new 100% is the 720 frame size.
I personally like to assign a motion (scale) percentage of 67% and have the option to ‘zoom in’ a bit if I want to mess around a little with the composition.
You can save the motion setting as a preset to save a couple steps…
TimK,
Director, Consultant
Video Producer at I-CAR -
This is an old problem…and it’s QuickTime/Mac related.
Gamma is actually interpreted incorrectly on H264 and in some cases, ProRes.
Apple knows about it. They’ve had in excess of a decade to fix it if they were going to.
Premiere Pro bypasses QuickTime and uses its own decoders…and therefore the gamma is not interpreted by QuickTime.
TimK,
Director, Consultant
Video Producer at I-CAR -
ProRes preview renders will create some LARGE temporary data files…and the importer isn’t what renders the previews…it would most likely apply to the decoding of the camera footage.
Have you tried a reinstall of the application? Checked if there are updates?
Etc…
TimK,
Director, Consultant
Video Producer at I-CAR