Nesting problems, Audio specifically

[Erik Mickelson]

Basically Premiere being more and more ridiculous as time goes on. A 3 minute movie that takes FCP 1.5 minutes to export is taking Premiere over 20 minutes(probably longer then that, the “time Remaining” is toggling between 18-22 minutes for the last 5 minutes). This is after I have rendered previews. The video is a talking head over a motion background(movie clip) with a couple supers here and there, newscaster style.

Nesting does NOT work correctly in Premiere Pro, might as well not even have it as an option. Nesting resets audio and removes audio effects, ie do it all over again. Mutes are ALL unmuted. WTH!

I tried sending the sequence to after effects but that was worse. I use Boris Continuum for keying, choking and wrapping. The keys came across as blurred but keyed video and my project was exploded.

What is the solution, Avid? FCPX, no way. Stick with FCP 7 and transcode everything, don’t like that option either but it may still be the most professional solution for “non-professional” editing software.

CrippleBook Pro 2.3Ghz i7, 8GB ram, SLeopard 10.6.8, FCPStudio 3, QT 7

[Alex Udell]

Hi Erik,

As far as the nesting with Audio Effects goes….

here’s my guess…

Audio Mixing in PPro can be in either clip mode or track mode.
If your losing your mix and effects….it may be that you did the following combo:

1) You Did your mix/fx in track mode: this means automation is attached to the sequence, not the clips
2) If you then chose to “nest” those elements from the timeline itself, then PPro pushed the clips to a subordinate timeline, thus the mix did not move with the clips. This mix may still be on the parent timeline.

Perhaps if you try it this way:

1) in the project panel, make a new sequence (Matching format)
2) Drag your edited sequence onto that timeline. In this way you mix should now be nested on the new timeline, and still full editable on your subordinate (original) timeline.

I know it seems like a subtle workflow difference….but hopefully my explanation helps clear up why that happens.

Regarding rendering time….

The building of final output from previews is architecturally not the same as what you think of with FCP.

FCP is based on Quicktime and since it’s renders are also quicktime, they can rapidly be assembled, especially if there is no change in codec.

Adobe’s native technology is codec agnostic and not built on a quicktime foundation.
So even material previously calculated into a rendered file will to at least need to be decoded into some “raw” intermediate frame and passed on to the destination file. At least that’s my understanding.

So while it may be more rapid than having to recalculate all your fx, it’s likley not going to be as rapid as the pasting of previously rendered material in the way that FCP handles it. At least that’s the way I understand it anyway.

Hope you find that helpful…