[Tim Kolb]

Well…there is typically some compression…are you saying these are uncompressed AVIs? I assume they are massively large?

You still didn’t mention the frame size, what your sequence settings are in CS4…what they were in CS3…are you trying to play the edited sequence from CS3 or just trying to load the media and just play it back? …and again, how are you loading this material? Are you just opening the CS3 project in CS4 or are you importing the project?

My personal intuition says that you have a media cache database or media from CS3 that CS4 isn’t liking…but I need some information to be of any real help.

TimK,
Director, Consultant
Kolb Productions,

Adobe Certified Instructor

[Tim Kolb]

I would be most useful if you could offer some detail. We don’t know the video format or the frame rate, or whether or not you may have tried both opening the old project and importing the old project to see if that makes a difference…etc, etc.

So…furnish some background and I’d guess someone might recognize the issue, and possibly offer a solution.

TimK,
Director, Consultant
Kolb Productions,

Adobe Certified Instructor

[Tim Kolb]

So…your original media files are in that AE cache directory?

When you have “save next to originals when possible” checked, that means that cached audio files are located in the same directory as your media…I’d also check in there to see if that’s where your previews are being created.

Now…the only question I have is if PPro was installed on the administrator user account. It sounds as if Adobe Premiere Pro may not have the authority to do what is necessary to “link” those files to a saved project.

Have you tried to run Premiere Pro “as administrator”? (right click the exe file and choose that from the menu)

Something is certainly odd about how this is working…and until some new piece of information steers me in a different direction, I have some suspicions about the install and permissions…

TimK,
Director, Consultant
Kolb Productions,

Adobe Certified Instructor

[Tim Kolb]

A little more info would be helpful…

How are you saving? simply saving the existing project…or saving a copy…or “save as (whatever)” ?

Where are your previews set to go in your preferences?

How much space is on that drive?

What are your preview settings (sequence settings contain these)?

Does this happen with every project or just one? Have you started a new project to see if you could verify the behavior with another project? …another format?

TimK,
Director, Consultant
Kolb Productions,

Adobe Certified Instructor

[Tim Kolb]

Are you using a Windows machine or a Mac?

TimK,
Director, Consultant
Kolb Productions,

Adobe Certified Instructor

[Tim Kolb]

[Alex Udell] “GFX hardware should not be affecting decode or Pixel aspect ratio conversions.”

Actually, CUDA support has been employed in CS5.5 for pixel aspect and scaling conversions as well as framerate mismatches, etc.

Even so, the main decode is still CPU based as Alex said. However, once you start placing any effects on the footage (like color correction) having a CUDA capable card in the machine takes the effects load off the CPU to free it up to do more decode work.

In the playback settings, you may want to see if you can gain any speed by dropping to half res on playback, which will reduce the load a bit more.

Handling these extremely compressed formats takes horsepower no matter how you slice it, and DSLR and AVCHD are both a load. All that said, I don’t typically see the sort of lag you’re describing in my 4 core AMD machine…so I would think you should be able to move through the footage without that much difficulty…keep in mind that Adobe needs QT 7.6x on the system to run, QTX is not supported at this time.

And BTW, CUDA video cards aren’t all expensive…check the Adobe list. There are gamer cards on that list as well. You don’t have to buy the professional display card models if you don’t want to.

TimK,
Director, Consultant
Kolb Productions,

Adobe Certified Instructor

[Tim Kolb]

Usually this behavior happens when you have a timeline framerate mismatch…like a 23.976fps clip on a 24 fps sequence (or 30 fps on a 29.97 fps sequence) without interpreting the clip for the framerate of that sequence.

The PPro sequence is actually designed somewhat around audio which is why you can simply click on the “audio units” option and edit the audio on the timeline down to the sample or the millisecond) and in some cases in versions prior to CS5 (I haven’t tested this in CS5 or later), the timeline would accept slightly mismatched framerates, but since the frame changes migrate, the timeline stops playing as soon as the variation starts to delay delivering new frames at the proper interval.

I’d start by checking the framerates of the sequence and the clips…

As far as ProRes is concerned, I’ve never had an issue playing it on my Windows machines though I have seen weird clip dimension reporting from the QT Player’s inspector which seems to be tied to scaling the player, though it never made a difference to Premiere Pro…are the clips actually not big enough to fill the frame on a proper timeline with 1920×1080 frame size? Where are you seeing these odd sizes being reported?

TimK,
Director, Consultant
Kolb Productions,

Adobe Certified Instructor

[Tim Kolb]

[Ron Pestes] “Does that mean that I can’t browse my clips in Windows Eplorer?
“

EX clips are not any easier to “browse” than P2 footage in their native form as the actual video essence file is rather deeply integrated with the metadata folders, etc.

The XDcamEX clipbrowser is the fastest way to look at clips outside of PPro itself in my experience.

TimK,
Director, Consultant
Kolb Productions,

Adobe Certified Instructor

[Tim Kolb]

[John Pale] “1280 x 720 is a DVCPROHD frame size.”

Actually, HDV1 is a JVC format…and it’s 1280x720p. HDV2 from Sony/Canon is 1440×1080.

DVCProHD is always sub-raster…720p is actually non-square PAR 960×720. 1080 is 1280×1080 for 29.97fps, and 1440×1080 for 25fps footage.

TimK,
Director, Consultant
Kolb Productions,

Adobe Certified Instructor

[Tim Kolb]

[Gary Huff] “C/UsersGaryAppDataRoamingAdobeCommonMedia Cache Files002JZ 48000_4.pek”

I’m not sure I understand…it looks like a path.

TimK,
Director, Consultant
Kolb Productions,

Adobe Certified Instructor