Activity › Forums › Creative Community Conversations › OT: Premiere CS6 oddity
-
Oliver Peters
January 17, 2015 at 6:44 pm[Brett Sherman] “y guess is something having to do with MPEG-4 processing and the Xeons is not great.”
The Core i5 and Core i7 chips have acceleration for H264 media. The Xeons do not.
– Oliver
Oliver Peters Post Production Services, LLC
Orlando, FL
http://www.oliverpeters.com -
Bret Williams
January 17, 2015 at 7:23 pmIt’s a similar odd bug in FCP X. But I know, we always stay perfectly on topic here in the debate! 🙂
-
Bret Williams
January 17, 2015 at 7:25 pmIsn’t that for single pass encoding of h264? I would think scrubbing around would fall under the GPU for real time deciding.
-
Oliver Peters
January 17, 2015 at 8:38 pm[Bret Williams] “Isn’t that for single pass encoding of h264? “
I don’t know whether it’s limited to encode or affects decode as well.
– Oliver
Oliver Peters Post Production Services, LLC
Orlando, FL
http://www.oliverpeters.com -
Craig Alan
January 18, 2015 at 3:24 amCurious. Do you get any lag with other operations? Are your media drives perhaps in a energy saving sleep mode and need to wake up before responding?
Mac Pro, macbook pro, Imacs (i7); Canon 5D Mark III/70D, Panasonic AG-HPX170/AG-HPX250P, Canon HV40, Sony Z7U/VX2000/PD170; FCP 6 certified; FCP X write professionally for a variety of media; teach video production in L.A.
-
David Mcgavran
January 21, 2015 at 12:58 amApple changed the way they did UI timers and this caused this. It has been fixed in Premiere Pro CC.
Cheers
Dave
———————————————————————————————————
David McGavran, Adobe Systems Incorporated
Senior Engineering Manager Adobe Premiere Pro
———————————————————————————————————
Reply to this Discussion! Login or Sign Up