Tim Kurkoski
Forum Replies Created
-
First, NEVER use assets for a video program from a network drive. Offline storage is fine there, but for actively using the clips always put them on a local drive. Yes, a network drive CAN work, as long as your network traffic isn’t cluttered, but it seriously is just asking for trouble.
As for the problem, can you export from Premiere Elements to a DV-AVI file? You may be able to get around the problem by making an AVI file, then putting it back into your project and disabling (Right-click > uncheck Enable) the original clips. Or, if worst comes to worst, put the clip in a new project and recreate the DVD menus.
If the AVI export doesn’t work, there’s likely something wrong in the timeline. If it always stops at a certain point, there’s probably a bad clip or effect there. Delete it and see if you can get past it. Add it back, and if it still fails you may need to recapture or recreate it. If this doesn’t work, it could be something bad in the project. Use the work area bar to export segments around the bad part, then recreate the timeline it in a new project.
-
That is true, USB 2.0 could bog down more. Firewire is the recommended route, though I’ve talked with plenty of people who are using USB drives (faster computers in general seem to help alleviate the problem).
7200 RPM should be your minimum. Bigger caches are generally better. Other than that, just keep your system clean and optimized, and it usually works fine.
-
When you go to the Image Size dialog, set the Resample Image option to Nearest Neighbor.
-
Ah… What that menu is saying is that you can upgrade from either AE Pro or AE Standard and get AE7 Pro.
If you’re upgrading from a previous version of AE Pro, you obviously wouldn’t already have AE7 Pro, so it’s listing the previous versions of AE Pro: 3.x-6.x.
If you’re upgradeing from AE Standard, you could have any version of AE, so it’s listing every version of AE Standard: 3.x-7.0.
-
The 3% bit is how much AE is currently using. At launch, it doesn’t need a lot of RAM, just processing time to get the app loaded.
As for how much RAM it’s using, remember that even though OS 10.4 can address massive gigs of RAM, applications are still limited to how much RAM they can use. The limit is about 3.5 GB, but after some reserved memory space the OS takes you’re effectively running at 2.5 GB plus.
-
If I remember correctly, you have to change the system audio settings back to 48khz (or less than 68khz, if my memory is to be trusted). Go to Applications/Utilities and open the MIDI Setup app. I think. I’m at home and not near a Mac right now. In any case, the options are in the lower-right corner. Audacity probably tweaked them up to the max.
-
You should be able to upgrade to AE7. I don’t see any reason why Adobe wouldn’t want to take your money. 🙂 (In fair exchange for AE7, of course.)
If you’re having problems, you’re probably best off calling Adobe’s customer service line.
-
An action run through a batch process will do this easily.
-
Last time I played with iMovie, it captured as DV stream files, which Premiere Pro can’t read. You can use iMovie or QuickTime Pro (or any number of other apps) to convert the DV stream to a plain .MOV or .AVI file.
Better yet, why don’t you dual boot the MacBook with XP using Boot Camp, install Premiere Pro, and capture with that? (Caveat: I have no idea if or how well Premiere will run on a Mactel, but I’ve heard only good things so far about performance of the Mactel machines running XP.)
-
If your camera allows it, yes. Not all cameras do, but a good deal will pass the FireWire input through to the analog port. You may need to enable an option in the camera’s menu settings. Also, on some cameras you have to take the tape out before it will preview live.