Adobe Premiere Pro CS3 Not Up to Larger XDCam Projects

basspig

Veteran
After a week of troubleshooting problems with missing audio on some XDCam clips ONCE IMPORTED to a project, and after experiencing a total refusal to process ANY audio at all on an XDCam project today, I have come to the tentative conclusion that Premiere CS3.2 only works on small projects and clips not much longer than an hour.

I found that a project with 183 clips was too much. Nothing past 125 clips would conform--anymore, and there would be errors and a bunch of clips with no audio.

And tonight, I recored a 92-minute talk that spanned 2 16GB SxS cards. When I imported the project, there was the usual errors about the XML files, but also an 'error compiling movie' error. And... there was no conforming happening at all. And when I played the project--no audio at all!

And what's with Clip Browser 2.0? As a last ditch attempt to get SOME audio, I'm converting all clips to MXF format, but unlike the earlier Clip Browser, which took a few seconds to covert a large clip, this one is taking the better part of an hour to rewrap ONE clip! So it's going to be another 40 minutes or so before I can even test out the concept of brining in MXF for the audio portion and grafting it onto the existing video (I can't use the MXF in Premiere because there's some problem with the color subsampling degrading with MXF files, so must use MP4 for the video and MXF for the audio.

It looks though, like Premiere is no good for long-form XDCam editing.

UPDATE:

I spent an hour converting the XDCam footage to MXF, hoping that would solve the Premiere import problem. It didn't. When importing, at least there's no error, but it doesn't conform and there's no audio, not even in the bin clips.

I'll have to fire up an old version of Vegas to get the audio from this clip and export it to Premiere.

ANOTHER UPDATE:
A last ditch effort: Used clip browser to split the clip up into two smaller ones.
Import into Premiere. "Error compiling movie. Unknown error." Click past that. Drag folder to timeline. As thumbnails begin to appear, Premiere terminates unexpectedly with no warning or error message. Specifically, it is the second clip of the split clip parts that crashed Premiere, as identified by playing them in the bin. The first half plays, albeit with no audio, but so much as touching the second half clip results in Premiere rapidly vanishing from the screen.

This is a really disappointing development, as I will be doing more long form projects from now on and need an NLE that can handle them.
At this point, for expedience, I have to move these files to Vegas and work there.
 
Last edited:
I think the problem is your recording format.
I do 90 minute HD docus in CS3 without any problem.
But it is all uncompressed (Black Magic codec and board) material.
So there is no stress of decoding and generating frames out of long GOP streams every time I flick throu the timeline.

Frank
 
Yes, I realize the problem is with the XDCam support in general, although, there is no way to have an HDV tape longer than 60 minutes, so who could say if an HDV clip were 92 minutes long if it would also trigger the same problem.

Switching platforms just means trading off one set of problems for another.

This is really an Adobe problem.

It's hard to believe that no other XDCam user has yet to shoot a long-form presentation, non-stop and hasn't run into this limitation.

Earlier in the week, I also ran into what I've determined to be a limit on the max number of clips in a project (125) --any more than that and the audio won't conform on those extra files.

So we have a 125-clip limit, and probably an hour limit. Also, Premiere can't handle clips that have been split from longer clips--it terminates abruptly.

I don't know whether MainConcept or Adobe is to blame for this one...
 
I have an update to this problem.
THIS IS AN IMPORTANT UPDATE!
Apparently, I had underestimated the amount of media cache files Premiere generated with XDCam footage in the past month. As it turns out, over 997GB of media cache files were generated in the past month! This filled the entire space of the 1TB RAID striped array that I point my temp media cache files to.
I got really suspicious when I tried to get a screen shot of the Premiere application with some very unusual 'unknown errors' on screen. When I attempted to paste my print screen shot to Photoshop, there was nothing in the paste buffer! That's when the wheels started turning.. something must be seriously wrong with the disc array. So I checked the free space, something I had become lakidaisical in doing because there was always almost a terrabyte free space (that was before XDCam files started hitting the system) and to my utter shock, it reported something like 5.03MB (that's megabytes, not gigabytes) free!
My next step was to delete all media cache files older than this week's active projects. Then I reloaded the 92-minute project, and it conformed.. 6 times! Apparently, when a clip spans several folders, even though it imports as one clip, Premiere imports it once for every span folder, ending me up with my 92 minute project being 12.5 hours long! So there was a lot of duplicate conform files being made which explains why 1 TB of disc disappeared in just a few weeks of editing XDCam. I removed the unused clips which stopped the extra conforming and voila, audio at last!!
Problem solved! Beware, your temp drive will fill up rapidly--far more rapidly than you ever thought possible, with spanned XDCam footage because it imports everything duplicate times for every span folder.
 
Shweet! I was worried there for a while, Ill have an ex1 in a couple weeks and Premiere is my main editor. Thanks for the info!
 
You will probably find your delay in converting to MXF has something to do with option for safe rather than fast processing (safe has a redundancy checking process so will be much slower).

Just a thought anyway.
 
I believe that I set that option to off, but knowing some software's tendency to be 'sticky' with certain settings, maybe I should check it again. I've read other complaints about 2.0 being much slower to rewrap. The earlier version literally took SECONDS to do what 2.0 takes an hour to do.
 
Back
Top