[Jon Barrie]

This is an old post.

Have you tried to search for similar problems you are experiencing? Someone else out there with CS4 has most likely had this problem and found a solution. CS4 has been around for a long time now.

If you can’t find a solution, then start a new post with the details of your problem, version of the software you are using and specs of your system.

Cheers,

Jon Barrie 🙂

Jon Barrie
aJBprods
Jon’s YouTube Tutorial Page
follow Jon with twitter

[Jon Barrie]

Is it possible you began editing the clip before the conforming and indexing processing was finished? This can, but not always corrupt the file.

To fix this go to Premiere Pro>Preferences…Media and hit the Clean button in the Media Cache section.

Shut down Premiere Pro. Wait 10sec for the all the BG app processes to end.

Relaunch Premiere Pro.

Let the indexing and conforming all finish before attempting to do anything. So just go have a toilet break, walk, drink whatever. It won’t take more than a minute or two.

Let us know how that goes for you 🙂

– Jon Barrie

Jon Barrie
aJBprods
Jon’s YouTube Tutorial Page
follow Jon with twitter

[Jon Barrie]

Just a quick diagnostic:
Is the file size perhaps stalling with the 4gig limits if a FAT32 drive? Make sure the export is going to an NTFS drive (PC) or extended drive (Mac).

Have you tried to export the last bit on it’s own? If there is a particular file that’s causing the problem the media cache may need a clean. Do this in Prefs> media> “clean” button, close ppro. Relaunch ppro. Then let the conforming etc to finish before working with ppro. Export.

Let us know your results if it all works out.

– Jon Barrie

Jon Barrie
aJBprods
Jon’s YouTube Tutorial Page
follow Jon with twitter

[Jon Barrie]

Provided both platforms are running the same version of PPro then yes you can edit on one system to the other and back. I have been working like this since CS3.

– Jon Barrie 🙂

Jon Barrie
aJBprods
Jon’s YouTube Tutorial Page
follow Jon with twitter

[Jon Barrie]

Key areas with your system that can bottle neck.

– RAM (which is limited in 32bit OS)
– 32bit OS (win7 is very good)
– separate drives for media (don’t use the OS drive as your media drive too)
– read write speed of media drive (RAID 0 or 5 can get smooth datarates for most HD editing)
– compressed or uncompressed codecs

Your quadcore CPU can do the job, but i7 would be better. CS5 can edit native DSLR video and is 64bit so can make proper use of a 64bit OS and available ram.

Hope this helps.

– Jon Barrie

Jon Barrie
aJBprods
Jon’s YouTube Tutorial Page
follow Jon with twitter

[Jon Barrie]

Try this:

Copy and paste the clip so you have 2 instances.
1 is to set the speed/duration, the 2nd to send to SB.

Setup the 1st instance to the speed/duration you feel works. (don’t worry about the pitch here).

Send the audio to soundbooth.

From PPro send the 2nd instance audio to soundbooth also.

Soundbooth now should have the sped up audio from the 1st instance and the original speed from the 2nd instance.

Add them to a multitrack so the sped up audio is on track 1 and the 2nd original speed is on track 2.

Use the length of the sped up clip on track 1 as your parameter for the 2nd clip when adjusting the speed. Set the pitch etc to taste.

Play back the two clips stacked over eachother to hear if they are in sync. Once you are satisfied the sync has been matched, double click the 2nd clip that has the speed and pitch to open as a solo clip.

Save as to another name file. In ppro import the save a clip and add to the timeline. The matching durations of this and the ppro sped up clip theoretically should line up in sync.

Let usbknow if this works as I haven’t actually done it yet, just theory at the breakfast table 😉

– Jon Barrie

Jon Barrie
aJBprods
Jon’s YouTube Tutorial Page
follow Jon with twitter

[Jon Barrie]

Batch capture can be a little dining at times.

Have you tried to rewind the tape before executing the batch capture? That can wake it up a little.

ps: if you have broken timecode on the tape (where the timecode starts from zero again along the tape) the duplicate timecodes on one tape can cause probs.

– JON

Jon Barrie
aJBprods
Jon’s YouTube Tutorial Page
follow Jon with twitter

[Jon Barrie]

Can you provide some more details about the media you are editing, image files etc included and the system specs you have on your system and the lab system. Also the versions of Premiere, Media Encoder, Quicktime and the Graphics Card/s details. The HDD setup too could be part of the workflow difference.

Thanks.

– Jon Barrie 🙂

Jon Barrie
aJBprods
Jon’s YouTube Tutorial Page
follow Jon with twitter

[Jon Barrie]

Hi Liam,

Can you post a screen grab of the premiere interface with your clip and the FCP interface with your clip on the same frame for comparison/troubleshooting. It would be greatly beneficial if we can see the specs (info) of the clip in each Applications interfaces.

HDV primarily is not captured into PPro but rather the exact digital signal is ingested (transferred) to PPro. FCP captures the signal and converts it to it’s own Apple Intermediate codec (HDV) which is not the original recording data at all.

I am very interested in seeing your results side by side with some info details.

– Cheers, Jon Barrie

Jon Barrie
aJBprods
Jon’s YouTube Tutorial Page
follow Jon with twitter

[Jon Barrie]

Hi Jason,

This is one of the single most mis-understood aspects to working with digital video. Compressed Vs Uncompressed. And then where the bottle necks are in relation to bitrates.

Before I get into details, Avid is converting to a compressed format it can handle, you may need to convert your material to something similar but maybe not…

Have you tried to lower the % of the program size to say 25% or 50%, then set the playback quality to Half or even Quarter. It’s not a representation of the final quality it’s just to get you editing. I find 25% scale with 1/4 or 1/2 (without any effects) is sufficient for most of my work – and using external drives for my media… now onto some details.

SD res Uncompressed can be watched back and worked with in it’s uncompressed form on standard internal drives, just. It is best done with a RAID 0 or RAID 5 setup using 7200rpm speed drives.

HD on the other hand in Uncompresssed has not just got a larger bitrate to watch back 1 sec of material, but the processing speeds of CPU, RAM and HDD bitrate limitations are very much not run of the mill. If any 1 of the 3 mentioned areas are not upto the bitrate task then you will have playback problems when attempting to play in Full resolution. Hard Drive read/write speeds are most likely the bottle neck here.

There are specs on the bitrate ranges for SD and HD Uncompressed (which Animation codec in a QT wrapper is) and then for material with an Alpha Channel goes up again! Do a little research if you want the details. But a “standard” (Sold to Joe Blogs at home user) computer setup will never be able to keep up with Uncompressed HD, or SD properly for that matter.

AVID has it’s own compressed codec that it’s systems are optimised to understand which has a far less bitrate and therefore the HDD bottle neck or any other areas (RAM, CPU) aren’t being pushed anywhere near as hard. FCP have this scenario too with their ProRes codec.

The other hand compression that is very in bitrate, but amazing in perceived quality like H.264 is very taxing on the CPU, so getting the optimization to work with it natively (such as HDSLR clips) is critical to the process. HDD bitrate speeds again will make a huge difference to speed.

Using a RAID 0 or RAID 5 only for media is the recommended workflow. Holding the Media on the Operation System Hard Drive is just asking for trouble as the CPU and the Drive and the RAM need to work with the Operation System first, then the Applications that are running, then the Media itself while trying to juggle all the different sectors the OS, Apps and Media are on the drive the speed of the HDD is diminished and so is playback.

Separate drives for OS/Apps and Media Cache/Media/Projects is the minimum recommended workflow.

I hope this gives you and others that read this a small insight into why something works on one system and not another and how HDDs need to have enough read/write speeds for HD work, compressed and especially with Uncompressed (which no one really “edits” with).

– Jon Barrie 😉

Jon Barrie
aJBprods
Jon’s YouTube Tutorial Page
follow Jon with twitter