Geert Van den berg
Forum Replies Created
-
[Kevin Monahan] “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.”
I will surely do that if we get the bundles in, then I can continue testing this, as I am very fond of the titling tools in Premiere.
-
[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. “
If you had carefully read my post, you’d seen that I mentioned that I had those checked!
-
[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.
-
-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.
-
“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.
-
No not possible (yet). This is a feature that will need to be made by a 3rd party developer. Apple is not going to provide that functionality. At least that’s what their FAQ which was on their website seemed to imply.
XML is standard (text based and humanly readable) but the way different applications and vendors use it can vary per application. FCP7 XML is just one way that apple has used XML.
Now with the new update Apple has also posted a guide for developers how the new XML works. A similar guide for the old version also exists. So there probably will be someone that will delve in and create something. It’ll be quite a good move business wise to code something like that.
-
One thing. Keep in mind the time needed to re-download FCPX. I don’t know how fast your Internet connection is.
-
I’d pop in a fresh hard disk in the internal bays of your Mac or an external with a fresh installation of OS X and FCPX. Can be done in an hour and it will almost certainly work, unless there’s some sort of hardware conflict going on. If you’re in a hurry there’s little time to experiment. It’s always a good thing to have freshly cloned system at hand for these kind of situations.
-
I am really happy with the audio roles, it works exactly how I thought it should work.
Now it’s waiting on the clever developers to create usefull XML tools.
-
[David Dobson] “I’ve never noticed that problem cause I’ve never needed to do it. In PPro you can edit the source footage without rewrapping.”
It’s not about re-wrapping as something that is needed to use certain footage. Ever compared the quality going into the program and the rendered export? And why would it even need to render if the file that will be outputted is the same codec as the input codec and only has straigt cuts? This is how FCP works and this is how Media Composer works. (Offcourse applied FX will always require re-rendering, also in FXP and MC, but even the rendering quality was better, 3 generations in PPro and I couldn’t look at the picture again)
It could very well be that the codec I used wasn’t optimally supported by Premiere. I love someone to prove me wrong, because I liked working with Premiere. Actually we will probably buy some Production bundles to upgrade Photoshop and to get After Effects.