[Jon Barrie]

Can you post a sample of what it looks like please 🙂

I don’t know if 29.97fps at Progressive is causing the issue, since that frame rate is technically for Interlaced whereas Progressive should be set at 30fps.

Could also have something to do with any deinterlacing performed on 60i material… Seeing it would really help narrow down the possibilites.

Cheers JB

Jon Barrie
Adobe Video Solutions Consultant ANZ
Jon’s YouTube Tutorial Page
follow Jon with twitter

[Jon Barrie]

Just to clarify, its my personal workflow not an adobe thing.

Also be aware that cleaning the cache will clear everything, not just that project.

😉

Jon Barrie
Adobe Video Solutions Consultant ANZ
Jon’s YouTube Tutorial Page
follow Jon with twitter

[Jon Barrie]

Can you explain why you want it all in one continuous clip?

CS4 does not have any smart rendering so you will get a quality hit exporting to one clip with the same H.264 codec used with the source footage.

Going to Uncompressed is the only true way to not lose any quality, but then you’ll get slammed on the HDD space used.

I’d like to know why you want to have one clip as opposed to using a nest and loading that as a “clip”, reducing the need to make more media and potentially lose quality.

To load a Sequence and use as a clip that can be added to another sequence (Nesting) hold the Control(Command) Key down when you double click the sequence. It will load into the Source Monitor. You could also just drag the sequence icon from the project panel into the source monitor.

Or what I do is add the entire sequence as a nest and edit in the timeline. Setting in and out points around the sections I don’t want and using lift or extract to remove them, leaving only the bits I need in the sequence…

Sorry that was a lot of detail… for a rather simple question.

Cheers JB

Jon Barrie
Adobe Video Solutions Consultant ANZ
Jon’s YouTube Tutorial Page
follow Jon with twitter

[Jon Barrie]

G’day Guys/Gals,

This may have some positive influence on the current workflow:
https://library.creativecow.net/barrie_jon/Premiere-Pro-Title-Feathering/1

Cheers JB

Jon Barrie
Adobe Video Solutions Consultant ANZ
Jon’s YouTube Tutorial Page
follow Jon with twitter

[Jon Barrie]

I’d like to chime in to highlight that coming from FCP workflows and ProRes that PPro does things differently. Rendering clips as you go won’t reduce or speed up the export time – No matter which codec you are cutting with.

I have personally found working with both NLE’s for many years on multiple duration projects that the ProRes transcode eats a heap of hard drive space and gains perhaps “some” smoother experience when scrubbing material, which is not the bulk of the editing process IMHO.

The time it takes to transcode Vs the time is takes to export only the edited frames, with effects, transitions, grade, audio mix etc has always trumped the overall post-production time frame for me.

The only caveat with longer form projects working in native codecs I have noticed (not always) is to clean the media cache once the project is finished. This will re-conform audio and index frames (that require it) so if there has been any level of corruption during the editing process it’s a clean slate. Then I’ll export.

You do need to budget time to export – it is not like FCP in this way.

Hope this helps.

Cheers JB

Jon Barrie
Adobe Video Solutions Consultant ANZ
Jon’s YouTube Tutorial Page
follow Jon with twitter

[Jon Barrie]

Hey Dustin,

I can understand how the ability to import a subtree folder structure would appear to be an obvious workflow, however it isn’t in there.

I could think of one reason why it’s in there:
– Complex folder structure based tapeless media would be, well, horrible if it imported all of the subtrees and each, say RED files which are embedded in their own folder per shot would make for a messy bin structure in the Project panel.

However I do feel a tick box for specifically managed folders would be a great time saver. Since it’s not part of the workflow I’d suggest you file a request, with all the great beneficial reasons why and how you would implement it. 🙂

I tend to do the media management and import one Folder level at a time. It’s not that much of a problem… But I can see the benefits of this workflow.

Cheers JB

Jon Barrie
Adobe Video Solutions Consultant ANZ
Jon’s YouTube Tutorial Page
follow Jon with twitter

[Jon Barrie]

Work in a DV preset that matches the properties of what you plan to export to for DVD. All the HD material can be autoscaled with “Scale to Frame” option in preferences before importing it. The feature can be manually added to clips after they’ve been imported and given that the preferences weren’t in place. Select them in the edit and right click to see the “Scale to Frame” option.

Cheers JB 🙂

Jon Barrie
Adobe Video Solutions Consultant ANZ
Jon’s YouTube Tutorial Page
follow Jon with twitter

[Jon Barrie]

G’day Jake,

Try to select all the images in your edit and right click on any area of the selection. Go to the “Speeed/Duration” and set the new duration, before you hit OK you MUST also tick the Ripple… tick box. Then hit OK.

See how that works for you. Let us know if it kills your animation keyframes and will take it from there.

Cheers JB

Jon Barrie
Adobe Video Solutions Consultant ANZ
Jon’s YouTube Tutorial Page
follow Jon with twitter

[Jon Barrie]

Are you using the Media Browser to import the footage?

Cheers JB 🙂

Jon Barrie
Adobe Video Solutions Consultant ANZ
Jon’s YouTube Tutorial Page
follow Jon with twitter

[Jon Barrie]

G’day Nikolai,

Sounds like a corrupted render frame. You can dump that particular render and re-render.

Remember that the rendering process in the Adobe workflow is called “preview” for a reason, it’s just to check your edit only because you aren’t getting real time playback. The “preview render” is not used for the final export and that’s why its not showing the issue in the final export.

Cheers JB 🙂

Jon Barrie
Adobe Video Solutions Consultant ANZ
Jon’s YouTube Tutorial Page
follow Jon with twitter