Dennis Radeke
Forum Replies Created
-
[Ben Edwards] “Thanks for that, shame Adobe does not have an intermediate codec.”
We’re looking into it for the future, but at the moment anything that Premiere Pro understands, you can use as a DI codec if you wish. It is a common request we’re hearing and it’s very valid for some workflows.
[Ben Edwards] “generally it is possible to work out where bottlenecks are by looking at system utilization.”
You got it and this is the key! There are a lot of resources that can help. I basically sum it up as this: it’s about BALANCE! Here’s a catch all post from Todd that you can find a lot of articles on performance – https://blogs.adobe.com/toddkopriva/2011/02/optimizing-for-performance-adobe-premiere-pro-and-after-effects.html
I also like looking at specs from PPBM5.com and their Premiere Pro results.
Taking a glance at your specs, I’d say that adding more memory would not go amiss (4GB per core would be a good starting point). A GeForce GPU would also be a great addition especially if you’re on a budget.
Good luck and let us know how you make out.
Dennis – Adobe
-
[Gary Huff] “AVC-I or even DVCPRO HD in the P2 MXF wrapper format would be the way to go?”
AVC-I is heavy – meaning the CPU has to work harder to decode it so it’s not my first choice, though the quality is very good. P2 is great and Intraframe. I also like OP1a MXF (Sony XDCAM)
[Gary Huff] “As a side note, does this 32-bit process extend for EVERY file that has a .MOV extension? So AVCHD is typically .MTS, which I would assume is processed at 64-bit, but does that mean the H.264 files off a Canon DSLR in the QuickTime file extension wouldn’t get that treatment?”
Good question. We knew we needed to work around QT in the case of DSLR cameras (particularly the Canon’s) and so we created an H.264 decoder that works outside of the QT one enabling us to have 64-bit performance on H.264.
-
Hi Ben,
Not sure how you’re bringing in DNxHD into Premiere Pro but I’m guessing it is through a QT wrapper because we don’t support native DNxHD in CS6.
When you’re bringing DNxHD through QT, you’re utilizing a 32bit process instead of a 64bit one. That hampers the performance and probably why things are not working as you would expect them to.
There is no pixie dust and Premiere Pro typically just works with codecs without any difficulty. However, because Avid licenses DNxHD and it is propietary, Adobe does not support that in its native MXF wrapper which would be the right way to do it.
Dennis – Adobe guy
-
Good video that gives an overview of the audio functionality of CS6.
https://www.video2brain.com/en/lessons/changes-in-audio-tracks-and-merged-clip-audio
-
Brian – give me a list of what is important to you from a plugin stand point.
Dennis – Adobe
-
Hey Ryan,
Like I said, I agree.
I don’t feel that Adobe will leave the Mac platform for a number of good reasons, but I respect your opinion and your reasoning.
The underlying point though is that Adobe is listening and caring and delivering right now and that’s what everybody should be concerned about today. We will continue to listen to our existing users and those specifically of our competition to make Premiere Pro the Photoshop of Video. 😉
Dennis – Adobe guy.
-
For optical discs, I would say that the Sony Transfer method is the best. You can try the Media Browser inside Adobe PRemiere Pro, but I have heard reports that our performance isn’t as fast as the Sony Transfer.
Since I don’t have a XDCAM disc transport, I’d be interested to hear your results.
Dennis – Adobe guy
-
Apologies. Hopefully, we’ll have the same for the PC soon.
-
[Ryan Holmes] “[Brian Cooney] “And it looks like Adobe wants to hold our hand in this and walk with us.. That makes you feel confident about investing into the software.”
I would be careful about this.”
We do want to walk with you, but I agree a certain amount of skepticism is healthy too.
[Ryan Holmes] “Remember Adobe didn’t even make it’s software available on the Mac platform between 2003-2007 (CS3 returned to OSX in July 2007).”
This is true. The reason for this is that we re-architected the application (re-wrote it) which became Premiere *Pro* as opposed to just Premiere *no Pro*. At the time, the overwhelming majority of our business was on PC and FCP was getting stronger, so we opted to go PC only for three versions (1.0, 1.5, 2.0). By the time CS3 came out, our customers had spoken loud and clear that they wanted Premiere Pro cross platform – so we did it.
Dennis
-
The AMA feature has broken some of our AAF functionality for a while. We recently posted an improved AAF importer. Hopefully, this might help you.
https://labs.adobe.com/technologies/aafimport/