Forum Replies Created

Page 10 of 10
  • David Mcgavran

    April 20, 2012 at 4:30 am in reply to: Happy with 6.0, not so happy with the Mac Version

    Hi Jim,

    I am David McGavran the engineering manager for Premiere Pro. Some of your ideas here are speculation. We spent an amazing amount of effort this release on the mac adding mac specific features to help performance and comfort of mac users. I program Premiere Pro on a mac and so does about half of the team. Porting MPE to OpenCL was a massive effort that took a very long time and much work. This was mainly to support the mac users out there. To make this effort feasible we needed to focus our testing efforts on specific configurations so that we were sure they would work. If I were you I would go online and read about CUDA compatibilty and you can get information on how we support different cards. Again Open CL is first on the mac. Pinch gestures and 2 finger horizontal/vertical scrolling was also made for the mac users out there. You will continue to see us support the mac platform to the best of our ability. We will also to continue to look at which cards to support going forward.

    Cheers

    Dave

  • Here is a comprehensive list of new stuff:

    https://blogs.adobe.com/premiereprotraining/

    A bunch of us will be answering your questions at NAB some come say hi.

    Cheers

    Dave

  • You might want to head over to reduser.net there are ton of helpful people in the adobe workflow section who work with red day in/out.

    Cheers

    Dave

  • Actually this was an as designed feature. We are addressing it in a future version because it caused much pain and confusion. Basically AE users use Increment and Save a lot and if we want to keep the link connected we only look at the latest version. So use a different number scheme and you will be fine. Again there will be a change to address this.

    Cheers
    Dave

  • Hi Mike,

    I downloaded the trial of 5DtoRGB from the app store. Version 1.5.8. We seem to read the timecode correctly as far as I can tell. The timecode track is written with 24000/1001 which is a valid 23.976 timecode and we pull it in correctly. What version are you using?

    Of note, it seems one of the reasons people use 5DtoRGB is because it knows how to read the full range yuv out of the 5D footage. Just to be clear you get the same results using Premiere/AE or Adobe Media Encoder. We read full range 601 YUV out of the 5D movies so if you needed to transcode you could also use AME and get the same results.

    Cheers

    Dave

  • I will grab a copy of 5DtoRGB and see what it is up to

    Cheers

    Dave

  • Hi Guys,

    Haven’t posted to the cow before but read it quite often… Dennis and Todd seem to have this place covered 🙂

    Just wanted to drop in and say hi.

    Cheers

    Dave

Page 10 of 10

We use anonymous cookies to give you the best experience we can.
Our Privacy policy | GDPR Policy