Forum Replies Created
-
Yep – shoot the media cache files, NOT the preview files. Open Premiere and verify the location of the Media Cache Files folder – you’ll find it under preferences -> scratch disks. Trash it. Premiere should rebuild them when you relaunch it, and audio should play once again. Note the two “should”s in that sentence – caveat emptor. It’s worked for us.
MBC
-
Try trashing the media cache folder. Then take a long lunch while the cache files rebuild. Should work after that. Seems that the cache files can become corrupted (how, I don’t know) but rebuilding them makes everything play nice again. This has happened to us several times.
Mike Chapman
Senior Editor, DigiNovations
http://www.diginovations.com -
All HDV editors need to rebuild the sequence before laying back to tape. Any cut is going to screw up the “native” progression of I and P frames; the sequence must be rebuilt to be a correct MPEG stream. And you’re right-it takes a long time.
This also means that there’s no output on firewire of a sequence…without rebuilding the MPEG stream, there’s nothing to send out on firewire. What you see on the computer screen is rebuilt on the fly.
–Mike Chapman
-
Mike Chapman
December 18, 2007 at 3:40 pm in reply to: How stable is PPro on your system when editing large projects?We’ve had similar issues with stability in our shop. Once we get above 100-or-so clips, project loading takes a very long time (several minutes, this on a fibre-channel array), and PP3, v 3.1.1 frequently crashes or “has to close.” When our blue bar in the sequence suddenly turns read and “paints” a streak as it advances, we know to save immediately before the app vaporizes. We’re running XP Pro on quad-core systems with 4 GB of RAM installed. Generally, problems occur once the PF hits about 2.75GB.
Frankly PP2.0 was more stable, even though it took up to five minutes to load a project of similar size. I’ve cut on Avids and FCP systems for years and never experienced problems like this except with alpha-level software — which supposedly this isn’t.
Mike Chapman
Senior Editor, DigiNovations, Inc
http://www.diginovations.com -
We had one project that had perhaps 100 subclips from hour-long master clips. Things bogged down so much that it literally took several minutes to open the project, and perhaps 15 seconds for a subclip to play in the source window. When playing the timeline (containing subclips), audio dropped in and out at will.
The real horror was using Project Manager to move the project from a firewire drive to our SAN. Instead of moving the master clip and linking (for instance) five subclips to it, Premiere would create five new master clips, THEN link the subs. As you can imagine, on a 100-subclip project, this took up a vast amount of space, even on a 15TB server. I’m told that this has been fixed in PP3, but unless I can get over my install issues, I’ll never know.
I’ll repeat – of all the apps in this suite, the editor is the weakest, sickest part of the package. Adobe needs to steal some talented developers and testers from Avid or Apple, ’cause their editor is never going to catch on for “real world” projects.
-
It’s no different on the PC side, nor has it gotten appreciably better between Premiere 2 and 3. The most annoying lag for me is that when I hit the spacebar to stop playback of a clip, the blue bar stops about half a second beyond where I want to stop – a confounded nuisance for marking ins and outs of clips. And this on a 3.06 GHZ machine with a standard keyboard.
I, too, have had major lag issues with Quicktime. It takes many, many seconds to import a clip, and then it takes more time still before it will play back reliably.
I have to say that of all the apps in the Production Studio bundle, the editor is very much the weakest link. It’s apparent that no one at Adobe ever spent a day in a real edit suite, with impatient clients and/or tight deadlines. If we had either of those where I work, we’d be in serious trouble.
-
We’ve had a lot of issues with our shared storage system, so we’ve had to bounce projects from the SAN to “bricks” and then back again. It’s been quite a mess. I’m trying to get the Powers That Be to spring for LTO tape back up for the finished projects, but right now they get parked on bricks or on local drives.
I agree – I don’t think Premiere was ever tested with anything more complex than a five minute music video. We’ve been working on half-hour shows with one or two multi-camera interviews, and trying to manage these projects is a job unto itself.
Again, I was hoping it was a setting of some kind to prevent the subclip duplicaton issue. I don’t think the media management part has been well thought out, at least in a workflow that’s needed for large projects.
–Mike
-
…that’s actually what I’ve been doing, but that gets tedious when you have to go hunting for something that wasn’t placed in the right folder (I know, I know…we’re slowly instilling proper media management technique to the troops.) I was hoping there was a hidden check box or a setting that would treat subclips as, well, subclips! Anyone tried this yet in V3?
Meantime, thanks for the reply!
Mike
-
Thanks so much — you saved us a lot of wasted time! Turns out that the client had an ancient player, and is upgrading. Thanks again.
MBC
-
Hmmmm…in that case, I’m guessing they want WMV files and that perhaps their terminology hasn’t kept up with the times. If .asf plays nicely on a Wintel box (assuming they have semi-recent drivers, etc.) that should work. This is the occasional disadvantage of working in an all-Mac house.
Just so I understand, .asf is the just the wrapper, right? A WMV file will behave the same way on a fairly-recent Windows Media Player?
Thanks.
Mike