[Alex Udell]

Hi…

I don’t know this for sure…but as everything in Premiere is based on file path….

To you and I when we look at the timeline:

Render A = image A + image B

To PPro it’s:

Render A = File path/file A + File path/File B = Render A

PPro doesn’t know what the images are, simply that they are.

When the file path changes on the timeline for a relink….it has to way to compare the fact that they are indeed the same images just sitting at a new location.

So for example if you ended up with a timeline where some combinations of the files were in their old locations, and some in new locations…some of the renders would stick because the source paths to the media hadn’t changed…

Simply put, the render flag must be set based on whether the events on the timeline need a render AND the render file must look at the new paths as the possibility of it being new media.

it’s sort of a convoluted explanation….but does it make sense?

Alex

[Alex Udell]

Hi…

Raid 0 has no more a tendency towards failing than either drive individually.

The benefits of raid 0 are capacity of the volume = the sum of the 2 drives (minus formatting) and speed.
Speed is needed for lots of streams or for less compressed or uncompressed data capture and playback in editing.

However if information is stored on a raid 0 set, if either 1 of the 2 drives in the set fails all the data is gone.

A single SATA drive should suffice for HDV or DV.

If you need extra capacity, add another drive but striping is not necessary.

The other thing that is tricky about HDV is that you can’t really batch capture it successfully. So if you have striped volume (RAID 0) that fails, it’s not so simple to just restore a project.

hope that helps…

Alex

[Alex Udell]

Heya…

the PG/UP and Down keys should behave as you describe actually moving the playhead to each edit.

That’s what it does on my box…

Try going back to the premiere default keyboard layout and see if PG up and Down behave as described….

It sounds as if maybe you didn’t map the right function in your remapping…

that’s my best guess anyway…

[Alex Udell]

//ME HITS SELF ON HEAD WITH BAT…

of course…

that’s awesome!

Thanks so much!!!!

Alex

[Alex Udell]

FYI…

Using an AJA Kona card on a Mac in combination with FCP will somewhat enhance the performance you will get out of FCP depending on the editing footage format.

The AJA hardware will take over (under the hood) pixel scaling and some other functions normally handled by the CPU. In this way you can eek a bit more RT out of FCP if you are working in formats like DVCProHD or HDV.

To my knowledge, this does not help with AE on or PPro on the Mac.

Alex

[Alex Udell]

Hi…

For the PC…

Photoshop and AE can benefit from Nvidia Display Cards.
Photoshop with their 3d layer support some nice smooth navigation in image rotation when working close up.

AE can benefit with 3d Comps and speeding up previews a bit. But it’s only really for preview.

I’d check Adobe’s site for what recommendations, as I recall a table that lists what’s been tested and what features work on what cards.

Matrox RT.X2 LE and Axio LE provide superior performance in Premiere Pro and WYSIWIG to a broadcast monitor in AE and snapshotting to a broadcast monitor in Photoshop.

In Premiere, they provide signal input and output with various devices and acceleration of a variety of effects plug ins they have written. In both cases, some of the work is done by the Matrox card, and some is tasked to a qualified display card. In the case of Matrox, ATI cards generally outperform Nvidia. Matrox offers a table as to cards that have been tested on their site as well.

hope that helps….

Alex

[Alex Udell]

Hi There…

I have to agree…

File based workflows based around MXF are a difficult to make portable….

When Premiere asks for a file that is missing and you relink, that one path becomes a valid location for media….so for every other clip that Premier looks for, it will check thru a list of previously valid paths to link the media….The problem with MXF native media seems to be every clip ends up having it’s own path….which means that every clip needs to be relinked individually.

I’m wondering if there is some MXF utility that will actually move the media assets to a common directory….prior to importing them into for the first time….that way when you move the project you’d have substantially less paths to validate for relink….

I seem to recall this MIGHT help: www(dot)imagineproducts(dot)com(slash)hdlog(dot)htm

It can allow multiple P2 cards to be combined into one P2 directory…

They have a demo….can you give it a try and report back????

I’d be interested to see if it helps….

Let us know….

Alex

[Alex Udell]

Hi,

Did you trim the clips in the source viewer prior to editing to the timeline, or did you simply edit the full clips back to back in sequence?

Cross fades like other transitions on the same track need additional media beyond what is exposed ion the timeline to have room to transition.

You could layer the audio sources on alternating tracks and then simply use the pen tool to create fades manually as an alternative to trimming the clips.

Does this help?

Alex

[Alex Udell]

Hi…

This is actually a feature I’ve been looking forward to.

Though you description of nesting is correct…this is intended as a workflow enhancement.

Let’s say you have several clips stacked in the middle of a seqeunce over a background.

Then you decide you want to blur them all in at the seame time, rate, amount etc.

Now you can multi select the clips in the timeline line and select “nest”

This automatically moves all the selected clips to a new timeline, and replaces the them with the one new nest clip in the sequence you are working in. It saves about multiple steps and should be a real time saver.

Does that help?

Alex

[Alex Udell]

Hi Dave…

It’s actually like this…

1) Create a new Seqeunce
2) Put Unlinked audio and video clip sin the sequence in sync with eachother (linking is not necessary)
3) Close the sequence
4) Go to the Project window and drag the the sequence into the source viewer
5) mark in and out in the source viewer as with any clip
6) Edit to a New Destination sequence…..

Double clicking the clip on the timeline loads that event on the timeline into the source viewer for editing….and is not used for editing on to a different sequence….

Alex Udell
Editing, Motion Graphics, and Visual FX
Younversity TV
http://www.youniversity.tv