Eric Jurgenson
Forum Replies Created
-
Axio LE is your best bet. It offers real time effects and accelerated rendering and export, along with comprehensive I/O, and nice value added features like input metering and HDV capture window support. Plus, it adds a very nice broadcast quality compressed codec set (I-Frame MPEG) to Premiere.
Go for dual quad core Xeons, an AMD Radeon X-4890 graphics card, and an 8-bay SAS RAID-5 enclosure like the EnhanceTech RS8-SS with SATA drives (700 MB/s) with an LSI HBA. Also 64-bit Vista, and 12 GB RAM. (To be safe, make sure your MOBO or workstation is on the Matrox approved list).
-
It’s just called “export->media” in CS4. That opens up the media encoder window.
-
I’d use Quicktime H.264 using the original project settings. Check the output screen for the correct aspect setting (get rid of the black bars). Set the bitrate to 20,000 kb/s (for full size). You need Quictime Pro to fix the squeezed aspect in QT player. Click apeture checkbox in Window>Properties>Presentation, then save.
Similar quality is available using Windows Media 9, if you prefer.
-
Typically it is a corrupt clip. Sometimes it can be mixed codecs on the timeline. CS4 seems to be particularly unforgiving compared to CS3 in this regard.
When I say corrupt, I mean corrupt as far as Premiere is concerned. It still may play fine in a media player or After Effects (which can be used to transcode to a more PPro-friendly format). As I said, CS4 is “picky”, and I am particularly suspicious of the 4.1 update, which seems to make the problem worse.
If you can get your project open before it locks up, you could try to isolate the offending clip by taking all the video clips offline, and then relinking them one at a time until ImporterProcessServer locks up. That’s the bad clip.
Or you could try to export your whole movie to a single format (if IPS doesn’t crash first). Good luck.
-
Well, in that case, maybe a reinstall (repair) is in order.
The reason I thought that might not be the case is that I just did a reinstall (actually a complete clean install of my boot drive) to try and deal with a similar problem.
In my case, ImporterProcessServer was crashing when a particular project was opened, even though the project was fine (with all clips already imported) prior to this problem developing. Turns out it was a corrupted clip. How it got corrupted (after it was working fine) is a mystery. After I transcoded the corrupt clip in AE (which opened it without issue), and relinked in Premiere, the project was fine.
So I ended up wasting five hours of my time with an unnecessary reinstall. Oh, well…
-
Are you on CS4? My guess is that a reinstall won’t fix your problem. Try:
1) Importing through the Media Browser
2) Deselecting the two XML checkboxes in preferences>mediaI’m thinking that PPro may be choking on the metadata, not the essence file.
-
What is your original project setting? Are you shooting and editing in 24P?
-
It should be OK. Here is the list of validated graphics cards:
https://www.matrox.com/video/en/support/axiole/design/display/validated/
You should also probably check on your MOBO:
https://www.matrox.com/video/en/support/axiole/design/computer/validated/pcie/ -
Note that on this shot the background (sky) is consistant, so it would be relatively easy to key the background out on multiple exposures with a chroma key and relatively simple masks. It would also be possible to do this on a complex background with a locked down camera doing a difference key (although the key quality on a difference key can be a bit iffy).
-
Are all the images superimposed (like the old strobe multi-exposures), or just a succession of freeze frames? If it is the latter, Vince’s suggestion of the posterize time filter is probably what you are looking for.