Dennis Radeke
Forum Replies Created
-
[Chris Harlan] “Premiere doesn’t support control surfaces at all”
We support them in Audition today and know that surface support in Premiere Pro is important for the future.
-
There is Camtasia for Mac and of course Telestream’s Screenflow.
-
The merge clips command you mentioned earlier is what you want to use. It essentially creates a virtual clip of both video and audio together and is specifically designed for double system sound.
-
RAM does in fact affect performance. In some cases dramatically. It is somewhat codec dependent. I know that MPEG2 sees a linear performance increase with more memory. You can see some of this on PPBM5.com which is a primarily PC centric site for creating Premiere Pro performance benchmarks.
-
Roel,
It shouldn’t switch camera angles when you stop. I would say it’s some kind of anomaly with your system. Maybe try trashing the preferences in Adobe to see if that helps out and/or see import the clips into a new project and see if the behavior persists.
Dennis – Adobe
-
It’s a licensing issue. Apple doesn’t include WMV in QT. Telestream is the way to go.
-
If it’s Quicktime, then FCP will essentially rewrite the file (copy) and render what’s different (title, effects, dissolve, etc.). Premiere Pro will render out the entire file. Some people would call this feature “smart rendering” and Premiere Pro has it for some codecs but not QT.
In addition, all of what Ryan said is true and I would add that 4GB of RAM for editing is not enough for most editing tasks these days.
Your post also did not say which version of Premiere Pro you are using, but a G5 would indicate something CS3 or older. I would encourage you to try a 64-bit application.
Hope this helps,
Dennis – Adobe guy -
[Brooks Tomlinson] “Okay, Will do, I have two 60sec simple promo’s coming up. But they will require some aftereffects. So I will let you know how it goes.”
That will only highlight the pros/cons you discover because you can use Dynamic Link between Premiere Pro and After Effects.
Good luck,
Dennis – Adobe mouthpiece. -
From the Adobe side, the Directional blur is not GPU accelerated, so it has no bearing on the results. They don’t mention the amount of RAM in each systems which would make a big difference and their testing methodology is anecdotal at best.
Finally, it’d be great if they’d spell Premiere Pro correctly! 😉
From the engineering side, I hear that Mountain Lion addresses a lot of GPU issues, though I am probably not going to upgrade to Mountain Lion any time soon.
Note that the Photoshop GPU accelaration is OpenGL not OpenCL or CUDA.
Dennis – Adobe guy
-
My guess based on the information you provided is that perhaps a project got corrupted somehow. One tip or possible solution to try is to open a clean new project and then import a portion or the entire project into it.
Also, I’m assuming that you tried to manually relink the files and it didn’t take?
Dennis