Tim Kurkoski
Forum Replies Created
-
Mark- I’m not sure what you mean. If you export from Premiere Pro as an MPEG-2 file, your markers will be preserved as chapters the same as an AVI file.
Also, using another encoder is an entirely unnecessary process, and possibly degrades your footage. If you want a compressed AVI so that you can use Encore’s automatic transcoding options, you can do that directly out of Premiere. File > Export > Movie. Just make sure to choose non-uncompressed settings.
-
“Uncompressed Microsoft AVI” will use the YUV codec built into Premiere Pro 2.0, AE 7.0, and Encore 2.0. (It’s built-in for the purpose of SDI capture through the AJA boards.) You can use it if you want, but outside of those applications, I don’t think other apps will read it. I don’t think it’s proprietary, it’s just a relatively uncommon YUV format.
I’ll let others chime in if they’ve used it with other apps, I haven’t actually tried doing much with the format (no card to capture it with, so no need for it).
-
What happens when you try to play back the timeline?
If you’ve got your video camera plugged into the FireWire port, try unplugging that. Premiere defaults to sending the signal out the FireWire port. You can change that behavior in the project’s playback settings, or (more simply) you can turn off or unplug the camera.
-
The answer to all of your questions is that if the plug-in in question is dependent on a feature that is specific to one application or the other, or one version or the other, it may not function correctly in an app or version it wasn’t written for.
To break it down a little more, remember that while AE and Premiere have similar capabilities, they have different feature sets the plug-in writers may choose to take advantage of. Also, between versions, small changes may be made in the API that can break a plug-in. I know for a fact that happened on the Mac for Photoshop and AE because Mac has forcing all app developers to roll over to Mach-O.
I don’t know which of those specific plug-ins will work cross-app or cross-version. I think Trapcode may work, I’m almost positive Color Finesse won’t, and no idea on the others.
Adobe’s API does try to be pretty universal between the apps, but there’s enough specific differences between them that it won’t work in every case.
In regards to version-to-version problems, most plug-in writers will update their software for a new release from Adobe, so you can always get a patch or upgrade (though sometimes you have to wait a few months; most AE plug-ins are compatible with 7.0 now but there are a few stragglers).
-
Check the Feather setting on the lasso tool. There’s lots of other ways to introduce a feather, but that’s certainly the easiest.
-
How are you exporting from Premiere? At 9 gig it sounds like you’re using uncompressed AVI, which is overkill. Try exporting from Premiere as MPEG-2 DVD, then Encore won’t even have to transcode it.
-
Yes, you can create a DVD with progressive scan video. (See the thread below this for a related question on the topic.) Progressive video will play on any DVD player (it’s a part of the spec), though when it’s output to a standard TV it will be interlaced regardless of what is on the disc. That really won’t affect how you create your animation, though. Just make it look good and let your MPEG encoder handle the rest.
-
Yes, your assets need to be 23.976i with the progressive flag set. That’s part of DVD spec.
https://www.dvddemystified.com/dvdfaq.html#3.4
-
Use the track select tool or the multi-track select tool.
Another way to do it, though I don’t remember if this is in 6.5 or only in Premiere Pro, is to right-click on the empty space and choose Ripple Delete.
-
Norman- have you tried using the activation code you received from Minnetonka in the Dolby encoder included with PP 2.0? I think the encoder’s the same version as what shipped with 1.5, so it should work okay. If it doesn’t work, you should contact Minnetonka about the issue. It’s their license for the Dolby encoder you are using, not Adobe’s, and they should be able to tell you whether or not the code is good for the version you got with PP 2.0.
As for the error message, are you making sure that the Sequence window is the active window before exporting, and that you have your desired sequence open? Since the export options in Premiere are context-sensitive to which sequence or clip you have opened (and therefore which window you’re focused on), it could be looking at something else.
A workaround- if you’re just going to use PCM, just use the File > Export > Audio option to create a WAV file. It’s the same end result.