Jim Leonard
Forum Replies Created
-
For archive.org footage you should be grabbing the mpeg-2 files, not the mpeg-4 files. mpeg-2 files on archive.org are the best quality.
For a lossless codec, try lagarith or huffyuv. Both can be found via google. I used lagarith on my last project; no quality loss and about half the disk space of uncompressed.
-
3. Use avisynth + DGMPGDec + Premiere avisynth plugin to load the MPEG directly. This will take about 2-3 hours the first time you do it because you’ll be learning about avisynth and reading documentation, but every subsequent time you do it it takes about 10 minutes to set it up. The benefit is that you never re-encode the .VOBs; they are in Premiere at full quality, always.
-
An hour-long show with 48KHz 24-bit audio is 988MB of audio data. You claim it takes 45 minutes to conform that, which means that your system is only reading+writing 22MB per minute. My system, with off-the-shelf hard drives and a simple 2-disk stripe, does 22MB per *second*. I would troubleshoot your system. It does not take 45 minutes to confirm an hour-long show.
-
That’s your problem. FAT32 is limited to 4GB per file. Conver to NTFS (you can do this without losing data).
Why is that drive FAT32 anyway? Did you format it that way?
-
No, you’re thinking of Premiere Pro 1.5. In 1.5, MPEG-2 import was unusable. In PPro 2.0, it’s most definitely fixed and working; I use it all the time.
-
Experiment to see what works best for you. On one machine with highly compressable material NTFS file compression works fine (just make sure you defragment every night and have a fast CPU). On a slower machine, or not as compressable source, use 7-zip or winrar on “normal” or “fast” settings.
I would not recommend transcoding to another format; that invariable causes problems. For example, I’ve had clips go to lossless formats like Lagarith or HuffYUV, only to find that Premiere Pro treats them different (like, interlacing is gone or something). This is NOT a slam against those codecs — I use them heavily in different workflows — but just a warning if you really want to edit the footage again as normal.
But the real solution is another RAID. 1T is not enough for 720p material, even if it’s a single project. Disk is cheap; your time is not!
-
Then use Radial blur instead of Gaussian.
-
Sure, I did this for titles that came on/off screen. Just animate the layer movement, then add a gaussian blur, restrict it to just horizontal (assuming you’re moving horizontally, ie. left/right) and then animate the blur settings. Have it reduced to 0 blur right as it stops moving.
It’s a fake, sure, but for titles it’s nearly identical to actual motion blur.
-
I found mine using pricewatch (https://www.pricewatch.com/cpu/sempron_3300+.htm) but you could just as easily find it on ebay. Mine is Socket A, just like yours. I have a Sempron 3300+. $60.
Make sure your motherboard can take a Sempron… mine needed a BIOS update to support it.
-
A new video card won’t help at all. You can upgrade your XP 1600 to an Athlon XP 3200+ and that will help a heck of a lot more. You don’t need a P4 3GHz HT for SD work, but you certainly should upgrade your motherboard as far as it will go. Luckily you already have PC3200 ram so that’s not an issue.
I did exactly this 6 months ago and love the results. I’m running an AMD Sempron 3300+ (this is the maximum this technology will do), 200MHz FSB.
The one drawback: You can’t run Premiere Pro 2.0, only 1.5. 2.0 requires SSE2 instructions, and the Barton core series (Athlon/Sempron) only does SSE (not SSE2). For that, you *will* need to upgrade to a modern processor.