-
Premiere CS6 perfomance lacks behind on MBP
-
[Steve Connor] “Mine works very nicely with PPro6”
I’d still like to hear from the OP about what kind of h264 files he’s trying to cut. My money’s on QuickTime as the culprit in his problems.
_______________________
David Lawrence
art~media~design~research
propaganda.com
publicmattersgroup.com
facebook.com/dlawrence
twitter.com/dhl -
Were you working with the native files there, or was background transcoding turned on?
Kevin Monahan
Social Support Lead
Adobe After Effects
Adobe Premiere Pro
Adobe Systems, Inc.
Follow Me on Twitter! -
Well, it’s not been too long so I have to consider that fact that I might be doing something wrong.
Tim
-
Hi Morton
I know you didn’t want to get bogged down in the tech discussion (don’t blame you) but Just to clear up the tech confusion although you describe your machine as the “beefed up top model” it was not quite. The late 2011 MBP’s included a i7 2.4 gig and 2.5 gig model which had the 6770M card fitted which does have 1GB video ram. This was in both 15″ and 17″ versions.
Yours must be the late 2011 2.2 gig version which was the only one fitted with the 6750M card which indeed is 512gig as you describe.
That may be why yours is perhaps a little slower in that regardYou can check out all the specs here if thats your kind of thing
best wishes
Neil
http://www.patience.tv8 Core MacPro, Kona 3, Tangent Wave, Mackie Universal Symphony 6.5 FCP7
i7 2.7 Gig MBP (non retina) 16Gigs Ram Blackmagic Monitor Mini Symphony 6.5 FCP7 -
I will try to ingest directly in Premiere and let you know if it works better…
– No Parking Production –
2 x Finalcut Studio3, 2 x Prod. bundle CS6, 2 x MacPro, 2 x ioHD, Ethernet File Server w. X-Raid…. and FCPX on trial
-
[Morten Ranmar] “But let go of the technical discussion. My concern is that Premiere will not give me same performance as FCPX on a relatively new machine.”
My problem is that you stated:
Enabling GPU in Premiere does not make any difference (CS6.02). I have the beefed up MBP with maximum 512 Mb VideoRam.
Because you don’t have a supported GPU (with 1GB of RAM) Premiere doesn’t even give you that option.
So what did you do exactly that made you think you enabled the GPU in the first place? It may seem trivial, but it may be indicative of a lack of understanding of what your settings are, which could lead to poor performance.
-
[Kevin Monahan] “Were you working with the native files there, or was background transcoding turned on?”
Background transcoding in Premiere?
-
[Gary Huff] “[Kevin Monahan] “Were you working with the native files there, or was background transcoding turned on?”
Background transcoding in Premiere?”
Kevin meant background transcoding to Prores in FCPX. If so, and Morten didn’t realize it, he could have thought that FCPX was playing the native AVCHD files considerably smoother than PrPro when in fact it was playing the Prores intermediates.
David
https://AllinOneFilms.com -
David you were right. The problem must have been related to using media that was previously imported in FCPX. When I import directly in Premiere, I get smooth playback, even at Full quality.
But regarding the GPU questioning, the program does opt me to choose Mercury GPU acceleration in Project settings, even though my GPU apparently is not supported.
The question for me was not wether I have GPU acceleration or not, but the ability to edit a single stream of AVCHD with approximately the same performance, including a color grade. And yes I can.
– No Parking Production –
2 x Finalcut Studio3, 2 x Prod. bundle CS6, 2 x MacPro, 2 x ioHD, Ethernet File Server w. X-Raid…. and FCPX on trial
-
BTW – I was not transcoding the clips in FCPX, but working natively. Experienced an error on output, where a covering clip had moved one frame, and exposed an error – reexported, and the error disappeared…?!!
– No Parking Production –
2 x Finalcut Studio3, 2 x Prod. bundle CS6, 2 x MacPro, 2 x ioHD, Ethernet File Server w. X-Raid…. and FCPX on trial
Reply to this Discussion! Login or Sign Up