Guy Ross
Forum Replies Created
-
Yes, I have installed the update.
-
Hey Todd,
Thanks for the quick reply.
My experience spans 3 systems, all running the latest Mac OS X 10.6.4.
The footage, Canon 5D MVI files, was always read from either a 150 MB/s eSATA RAID or a 115 MB/s internal SATA drive.The first system was an early 2008 Mac Pro 8-Core 2.8 with 6GB RAM and a GTX285.
The second system was a mid 2010 Mac Pro 8-Core 2.4 with 8GB RAM and a GTX285.
The third system was a mid 2010 Mac Pro 8-Core2.4 with 6GB RAM and a 5770.The biggest problem with Premiere, in my opinion, is over confidence.
It doesn’t seem to know what it *can’t* play, and therefore ends up hanging and stuttering, even when playing back rendered sequences.For an editor, even the smallest delay is extremely irritating. But these kinds of incessant halts and freezes are just debilitating.
I love the concept of CUDA and MPE, but they both seem to fall apart on the details.
Thanks,
G
-
Background:
Apple had touted OpenCL as early as 2007, but hasn’t really done anything with it.
So when i saw the cs5/fcp shootouts and read about Adobe’s Mercury Playback Engine (MPE) I was hooked.After Effects is one of my favorite programs in the world, so why not give Premiere a try?
My asst is a big adobe fan, so we used his 2008 Mac Pro with 6GB RAM and an nVidia GTX285.
Preliminary test:
Preliminary tests were amazing.
Canon 5D 1080p footage played back smoothly with no transcode.Actual test:
Trying to actually cut on it was a different story.MPE constantly stutters and stops.
AIF files play random content, if anything at all
MPE marks yellow (RT playback) very complex After Effects nested clips, which it obviously cant render in real time.
Premiere crashed 14 times in 5 days
It takes ages to load, and even longer to quit.
The UI is cumbersome:
no easy way to view keyboard shortcuts (although the FCP compatible preset is pretty good)
Constantly having to turn tracks on and off for edit operations is weird
Accessing clip parameters (audio level, effect parameters) requires too many clicks
cudos:
I really like the individual clip Audio Gain setting – very cool. Wonder how that translates on OMF export
XML import export is BRILLIANT!
APIs have a terrible reputation
unrelated to premiere
When i decided that the experiment was over, and wanted to switch to Final Cut, I ran into a really annoying problem.
Due to Apple/FCP/QT gamma shift, the FCP sequences played back correctly, but exported washed out footage.
I read up on it, but couldn’t figure out a work around.
Nothing I tried (Compressor, meta data editing utilities) worked.
I even put the final output thru a gamma shift filter in Compressor, but the resulting files still played back white washed!Conclusion
I don’t mean to offend anybody, and I really appreciate Adobe’s vision.
I look forward to being able to work in an Adobe integrated environment, sharing assets across programs, while retaining editability, layers and vector information.However, Premiere doesn’t live up to the high standards set by After Effects, Photoshop and Flash Builder 4.
-
Thank you thank you thank you!
that sure saved me a lot of time and frustration.
p.s.
Also seems to work by deleting only the file “Final Cut Pro Prof Cache”
(and not deleting the more extensive file “Final Cut Pro 7.0 Prefs”) -
Andy,
I’m having a very similar problem.
Working with ProResHQ video and BWF audio and merged clips.
Whenever i need to relink the audio files, i get the attributes mismatch error (Media Start and End, Rate).
Sometimes i can get away with clicking “continue”, but, for some clips, i can’t.
Those get chopped down to a single frame in the edited timelines, and are completely out of sync.
Please let me know if you find out anything -I’ll do the same.
Thanks!
Guy Ross
creativeco [at] guyross [dot] com