-
Adobe media encoder v’s ProCoder.
Hi,
I’m doing a lot of stuff lately that is shot PAL and is authored to DVD in both PAL and NTSC. It’s easier, due to the integration of Adobe, to render mpeg’s with media encoder for authoring in Encore but i seem to get better quality, and quicker encodes, using ProCoder 2.0 but it’s a big faff rendering out the timelines, then encoding in ProCoder to bring into Encore. In PPro 1.5 the ProCoder plug-in worked from the timeline but not with 2.0! Is there a work around or any tips to get the best out of media encoder?
Thanks,
Tim -
6 Replies
-
Prododer does not wotk with PP2.0 nor is it expected soon. Draw your own conclusions.
Harm Millaard
-
Well, the short answer is you can’t get the best out of both worlds. There are some who have done comparison clip by clip between Mainconcept (Adobe’s) and Canopus codecs. (Google up..). It seems that Canopus came on top as far as quality / speed go, but it was always a sketchy result, depending on how noisy the original clips were, and how much motion they contained.
Honestly, I like Adobe Media Encoder, a little slow maybe, but remember that Adobe has to take a non-rendered file, with its entire program running in the background, likely sucking out the life out of your cpu and memory to start with.
I find that when I need something to go to projection, I will export uncompressed and then let Procoder do the work, otherwise I won’t bother. The lack of integration between PP2.0 and Procoder may be resolved by more complaints to Canopus or Adobe…
Vince
-
[Vincent Becquiot] “The lack of integration between PP2.0 and Procoder may be resolved by more complaints to Canopus or Adobe…”
Adobe doesn’t build interfaces for third-party software, their eng people will give some support but I think Canopus blew that bridge up, complaints seem to fall off Canopus’s back, the US support try to do a good job, but the decisions do anything come from the rising sun.
-
Well, yes I mostly agree that the blame should be directed at Canopus; But Canopus being such a big player in the industry, I think Adobe could have looked a little closer at resolving what seems to be a rather simple fix. I guess competition isn’t always a good thing…
Cheers,
Vince
-
I am running Procoder 2.03 with Premiere 2 almost just fine. After the export command I get an error message which I dismiss, Procoder then works fine until it finishes, then Premiere crashes with another “I sorry….” error message. Just save prior to export.
-
Mike,
While that is true, there is too much at risk, especially with a Premiere crash 🙂
Reply to this Discussion! Login or Sign Up