Why Wait For X To Evolve?

[Geert Van den berg]

“Why wait for X to evolve?”

Because Premiere Pro while being a great application, can’t do what FCP7 can do for me at the moment. I also had a moment of joy when first trying out Premiere, it’s very fast, but then I looked further. The grass isn’t always greener on the other side…

FCPX is already more useful when exporting video files with multiple audio tracks, which is something I rely on. But there were other things with Premiere bothering me as well. I think we will still purchase some Production bundles. Not for Premiere but for Photoshop and After Effects.

So basically we have 2 ways to go to in the future, either Adobe fixes the shortcomings of Premiere in CS6 and we can upgrade for less money than before or X has evolved by then. I think the future looks bright either way.

[Herb Sevush]

What specifically do you see as the drawbacks to PPro?

Herb Sevush
Zebra Productions

[Geert Van den berg]

-It can’t export multiple audio tracks in either Quicktime or MXF only 2 ch. or 6 ch.

-it renders while it sometimes shouldn’t render, just copy, for example when exporting to the same codec as the elements in the timeline which have only simple cuts, this lessens the quality of the material.

-Its render quality isn’t very good in my humble opinion. It could have been the codec I was using, but 3 rounds of IMX encoding caused very apparent degradation (while the same test with FCPX gave me excellent results, and this was with using rendering, sending it to a compressor preset, not just copying the material to a new container) and I had the image turn blue after another pass (I was told that could be due to the graphics card in my Mac, but it happened on 2 different machines, both with different graphics cards, so it’s probably a bug). With ProRes PPro did a bit better, but still less than X.

[Kevin Monahan]

Curious about the list too. Perhaps I can help?
BTW, do be sure to send each improvement to us here at Adobe in the form of a feature request:
https://www.adobe.com/go/wish

Kevin Monahan
Sr. Content and Community Lead
Adobe After Effects
Adobe Premiere Pro
Adobe Systems, Inc.
Follow Me on Twitter!

Tweets by kev_mon

[Shane Ross]

PPro cannot export multiple channels of embedded audio into Quicktime. But neither can Avid, unless you go through a few workarounds. That’s something that FCP does well. And more and more deliverables require multiple channels of embedded audio.

Shane

GETTING ORGANIZED WITH FINAL CUT PRO DVD…don’t miss it.
Read my blog, Little Frog in High Def

[Kevin Monahan]

Thanks Shane. Thanks Geert. Regarding audio limitations, please file a feature request for audio export: https://www.adobe.com/go/wish

About image quality on export, I’d need to know what your settings are.
On rendering when it should not, I assume you are talking about export here, as well?

Kevin Monahan
Sr. Content and Community Lead
Adobe After Effects
Adobe Premiere Pro
Adobe Systems, Inc.
Follow Me on Twitter!

Tweets by kev_mon

[Geert Van den berg]

[Kevin Monahan] “Thanks Shane. Thanks Geert. Regarding audio limitations, please file a feature request for audio export: https://www.adobe.com/go/wish

About image quality on export, I’d need to know what your settings are.
On rendering when it should not, I assume you are talking about export here, as well?”

I did certainly file a feature request. However I also mentioned the weird render behaviour at the Premiere forum on the Cow and then it was very silent from the Adobe camp.

And you’re right, I meant rendering on export. My settings were very simple. I had a Quicktime file with IMX50 codec. I made a new sequence with settings based on that file by dropping it on the icon which creates a new sequence based on the file. And then I exported that same segment again from PPro, trying several things. First I’d assume that match sequence would automatically select the same output as input format, not sure what it did make of it, because it’s a while ago, and my trial is over, but it didn’t do as expected. I then selected Quicktime and the IMX50 codec and ticked maximum render quality at the bottom (and I didn’t use the preview files). I did this for a couple of generations and then my initial enthousiasm was gone, unfortunately.

[Kevin Monahan]

Thanks for filing that feature request.

I’m sorry you didn’t get your answers on the Cow’s Premiere Pro forum regarding your image quality issue. I’m not sure what happened as we have many experts and even a few Adobe staff members hanging around there. I recommend a re-post if you wish to get it solved. When I see it, I’ll be sure to draw some experts to your answer.

Kevin Monahan
Sr. Content and Community Lead
Adobe After Effects
Adobe Premiere Pro
Adobe Systems, Inc.
Follow Me on Twitter!

[Kristin Leys]

And this thread has perfectly illustrated why I’ll never trust Apple with my business again.

Someone from Adobe has chimed in.

When I have questions about Adobe or Avid products, I get to talk to people who can help me. People from the company making the products. And people who will influence the direction of future versions.

Apple is a blank wall. A sprinkling of the foulest PR spin. And nothing, absolutely nothing else.

So no, I wouldn’t wait for FCPx to ‘evolve’, since the people responsible refuse to explain where they’ve started from, let alone where they want to go.

[David Cherniack]

Sounds like hedidn’t have max render quality checked on export of if he had effects on the clips, that “Render at maximum bit depth” wasn’t turned on… Or he had “Use Previews” turned on.
David
AllinOneFilms.com