Dennis Radeke
Forum Replies Created
-
One thing you could do is apply a gamma shift effect to compensate for the output.
You could export your timeline as a clip or as XML and bring it into Premiere Pro. Then apply a Gamma Correction clip. I’m hearing that a 1.2 of the original will probably work well. So, a value of 12 from the default value of 10 would be a good place to start.
Then export the media via AME and render to Flash.
Hope this helps,
Dennis -
One of the cool things about CS5 from my perspective is that it adopted a variation of a great FCP feature: namely when you drag media to the time line, FCP asks you if you want to change the sequence settings.
In like manner, if you drag a clip to the ‘new item’ button in Premiere Pro CS5, it will create a sequence based on the aspect ratio and frame rate of the source video.
Best thing is you probably can do this with the trial version.
-
Stating the obvious, but Adobe Encore also supports Blu-ray. You could try the Premiere Pro trial (which should include Encore) and see if it addresses your issues.
-
[Jeremy Garchow] “[Dennis Radeke] “Most likely it’s USER ERROR! ;-)”
What browser?”
Ah HA!!! It’s a Firefox issue!!! I tried Chrome and it worked fine.
-
Thanks Jeremy, but for some reason it never works for me!
I tried again and failed. Most likely it’s USER ERROR! 😉
-
“[Jim Curtis] “This is pretty ironic, but I’ve that Premiere Pro CS5 edits h264 footage perfectly without transcoding. Ironic, because FCP doesn’t. ”
FCP can…but it gets ponderous after a while. CS5 can because of the Mercury engine…that gets more power from the processors, because H.264 is processor intensive.”
One of these days, I’m going to figure out how to actually do a “quote” on the Creative Cow forums….. 😉
Shane’s right, but I thought I’d chime in to help clear a misconception. A lot of people associate the Mercury Playback Engine (MPE) to the GPU only and that would be a mistake. Adobe Premiere Pro can edit H.264 and other temporally challenging codecs because of a native 64-bit application. This really accounts for the performance more than anything. The GPU kicks in when you start adding effects and filters. There, the GPU can help take the load off of the CPU by processing the effect. It’s a balanced system approach. Of course, then the issue becomes having good CPU/GPU/RAM in proportion.
I hope this helps.
-
as long as the ProRes can be decoded by Quicktime on a Windows box, it should work fine.
If XML5 doesn’t work, try version 4 and see if that exports from FCP.
-
Well we’re glad to have you. Give me a call some time to chat.
And of course, I’ll still be hanging out at this forum as I’ve done for several months.
Dennis
“an Adobe guy” -
“The Frame Rate Converter… I have had similar issues. I figured out that you needed to make a separate project to convert them. But FCP is the ONLY application that allows you do to this conversion in the application. Avid doesn’t…Premiere doesn’t.”
I’d just point out that Premiere Pro doesn’t NEED to convert frame rates during editing. It will handle different aspect ratios, frame rates and codecs simultaneously on the same timeline (including multi-cam) without the need to convert anything.
However, if you do want to convert frame rate or codec or what have you, you do have batch conversion options with the Adobe Media Encoder and obviously there is After Effects as well.
I know this wasn’t the intent of your post, but thought I’d chime in.
Dennis
-
Both AE and Premiere Pro are 64-bit native on the mac and consequently are fully multi-threaded. They can take advantage of however many cores or CPU’s you have to offer and all of the memory that you can stuff into it. Inside of AE’s preferences you can set up memory and multi-processing – I highly recommend you look into the help section and Todd Kopriva’s articles on it if you want to really check it out.
FCP uses only 2 CPU cores presently and is not a 64-bit application, though everyone expects it will be in the future.