Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Adobe Premiere Pro Premiere Pro CC on my MAC will not function with ProRes or .MOV files of any kind.

  • Premiere Pro CC on my MAC will not function with ProRes or .MOV files of any kind.

    Posted by Paul Campbell on June 21, 2013 at 6:54 am

    I am a Professinoal Editor & Motion Designer who successfully made the transition from FCP to Premiere CS6.

    I still have FCP 7, Compressor in my toolkit along with all of the Pro Res codecs.

    Adobe PR, AE, and Encoder CS6 all work flawlessly with QT’s and my custom ProRes sequences.

    ADOBE CC on the other hand is a complete nightmare. None of the Apps are recognizing ProRes, but even worse than that is none will import an .MOV file of ANY codec -Animation/ProRes/Whatever…doesn’t matter.

    I have added pictures for reference…


    In this dummy project I have already successfully imported an MP4 file into the project browser (to the right of ‘Sequence 01’) … but when I try to pull an MOV file in I get that error dialogue box “The importer reported generic error.”


    This is a picture of the custom sequence area of CS6 … notice “QuickTime (Desktop)” option down at the bottom… contrast this with the following picture in CC … no “QuickTime (Desktop)” option.

    And then in After Effects – in the render que when I click on the ouput module to get to format options the “Codec Settings” box is greyed out and codec is listed as “0”

    As I’ve already stated … I have all the Codecs, I have FCP, I have Compressor, I have CS6 working flawlessly…. But CC is just not working. Anyone else experiencing this?

    I’ve already re-installed several times, I’ve already trashed preferences, I’ve already restored permissions.

    Help!

    Chris Paul replied 12 years, 10 months ago 4 Members · 6 Replies
  • 6 Replies
  • Martin Scheer

    June 21, 2013 at 11:39 am

    Hi ther,

    Same Problem , haven’ found any solution yet.
    Only seems to be a problem of osx 10.8.4 and adobe cc.
    On our next editing desk there’s osx 10.7 and adobe cc, everything is working fine.

    Peew…

  • Don Hertz

    June 21, 2013 at 2:05 pm

    Paul – no idea if this will help but it doesn’t look like you are getting a lot of suggestions. Out of 8 workstations we updated here I had some funky stuff happening with one of them not recognizing some of the Quicktime codecs – mainly ProRes and XDCAM – although CS6 on the same machine was working fine. Again, not to the level you are describing, but I couldn’t import and use anything with ProRes. I ended up moving most of the codecs out of the Library > Quicktime file, downloading the ProApps Codecs update 1.02, manually unpacking it (not running the installer – I used a free mac app called unpkg), then copying the codecs out of the unpackaged folder and pasting them into the Library > Quicktime folder. After a restart – everything was working fine.

    Might be worth a shot. Good luck.

    Sincerely,

    Don Hertz

  • Martin Scheer

    June 21, 2013 at 3:58 pm

    Hi Don, Hi Paul,

    thanks for your advice, it worked almost fine, but only after
    all other components were deleted from the Library->QuickTime
    Folder.

    When i copied all other components, Avid, IMX, etc. back into the QuickTime Folder and restarted PremiereCC, same problem again.

    Then i repeated Dons advice with the Avid codecs. Download from the Avid page, unpack manually,
    copy back to the QuickTime Folder, restart. Works fine too.

    Cheers,
    Martin

  • Paul Campbell

    June 22, 2013 at 1:03 am

    Don,

    THANK YOU so much for your help. Your advice worked and everything is running perfectly now.

    After running some further tests I was able to isolate the “actual” culprit.

    A codec called 3ivxVideoCodec.component was REALLY tripping up Adobe CC on my Mac.

    https://www.3ivx.com/technology/quicktime/index.html …. I have NO idea what I ever installed this for … but it was in my Quicktime library for some reason and boy was it wreaking havoc!

    Martin did you have this codec in your library?

    Anywas if it wasn’t for Don’s advice I never would have gone into my codecs library and moved everything out and back – CS6 was working FINE so I really didn’t think codecs were the culprit.

    I also went back and ran instillation tests on ProRes and AVID codec pkg’s and ultimately it makes no difference wether you install through the OS or use unpkg to install manually. Though now that I know about unpkg I will be using that quite often. I like the control.

    Thanks again Don! You lead me to my solution!

  • Don Hertz

    June 22, 2013 at 1:15 pm

    Glad to hear you were able to work things out. Also great to know you tracked it down to an exact culprit. I’ll have to see if that one is installed on any of our systems when I get back into the office.

    Have a great weekend.

    Don Hertz

  • Chris Paul

    July 2, 2013 at 8:22 pm

    The same codec was causing the same problem on my PC system. Windows8, PremiereCC. It was installed as part of Fuji FinPixStudio that I had installed to handle some 3D video. I uninstalled it and now all is fine.

    I figured it out because of this thread. Thanks for the info- gotta love this community!

    Chris Paul
    POV

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