FCP > Premiere users…should I wait for CS 6?

[Tim Kolb]

thanks Tom, yes…I read through it from your initial link in the thread. There are several discussions overlapping and it takes a bit to connect the dots.

I understand what the explanation is, but I do this relatively often (not with QT or ProRes of course as I’m encode verboten on Windows) and while there isn’t the advantage I’d like to see…there is certainly some.

It seems to me that perhaps we need to request a feature that simply acts as a “jumper” from the preview files to export. You’ve created the files already…

It’s probably also relevant that Adobe, like most vendors, have had to stay with QT 7.x for their QT interaction, which is 32 bit. on Windows they actually run their own application in between as a kind of frame server to get 32 bit QT to run in 64 bit PPro…I have no idea what they do on the Mac.

This kind of workflow hasn’t really been focused on by Adobe as they’ve been heading in a completely different direction of course…so it will take some urging.

TimK,
Director, Consultant
Kolb Productions,

Adobe Certified Instructor

[Philipp Hampl]

Well, it may all be right, but it nevertheles makes no difference, as: it still does not work, does it? Working with prp on a Mac you really need to get all the power you can get. I bought the extra ram (32gb), I bought the nvidia quatro 4000 to accelerate what really went very slow and itchy. (see adobe forum for details in timeline slowliness). I did all that was suggested to find out that the acceleration called mercury engine would only work with codecs other then those that would enable my I/o card (Blackmagic) to monitor the progamm to external monitors?! Together they do not work, so It makes no difference why and who’s to blame, as any pro needs to have a look on a external monitor, especially with interlaced formats. Go ahead and blame the way computers work and the third party companys, it still falls back on adobe. It just does not work!

Are there plans to change that?

And: what will you do about the audio limitations (export or transcoding a single mono track or stereo, that’s it, and that’s just not enough)?

You want the switchers from fcp? Then go and get the stuff running which they need to get their business running. Because if adobe will not, the switcher will notice that they also could have just switched to fcpx. It has the very same limitations in regards to external monitoring and audio tracks (ok, fcpx is in this regard even more limited).
I like premiere pro, but as I said: it’s not ready.

[Tim Kolb]

[Philipp Hampl] ” I did all that was suggested to find out that the acceleration called mercury engine would only work with codecs other then those that would enable my I/o card (Blackmagic) to monitor the progamm to external monitors?!”

On Windows with AJA, I can monitor externally with AJA sequence settings. CUDA has a smaller advantage, but the external monitor works…(again, CUDA isn’t tied to codecs as neither is PPro when it comes to sequence settings).

The third party makes sequence settings that tie into their board of course, and AJA has sequence settings that account for nearly every frame rate and size (codec is irrelevant)…but I don’t have any BlackMagic systems, so I don’t know how they work.

I have a feeling there may be a restriction outside of Adobe…but then it’s been a long time since I used a Mac, so I have no idea what Adobe is facing on the Apple side of the fence either.

TimK,
Director, Consultant
Kolb Productions,

Adobe Certified Instructor