Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Creative Community Conversations quicktime problems for adobe cc

  • Andrew Kimery

    April 21, 2016 at 9:31 pm

    [Charlie Austin] “For some reason, not many people are interested in pointing that out.”

    Probably because of Apple’s naming convention choice, where QuickTime can refer to the media player, the underlying media architecture and/or the actual media, can easily lead to confusion. 😉

    Speaking of that, if the problem is only the QT Player then why aren’t Adobe et al. just saying uninstall the player but leave the codecs? Adobe’s response that Walter posted, and unofficial but knowledgable response I’ve seen on Avid’s boards, make it sound like just uninstalling the QT Player won’t remedy the problem. Can anyone shed light on this?

  • Charlie Austin

    April 21, 2016 at 9:40 pm

    [Andrew Kimery] “Probably because of Apple’s naming convention choice, where QuickTime can refer to the media player, the underlying media architecture and/or the actual media, can easily lead to confusion. ;)”

    Agreed…

    [Andrew Kimery] “peaking of that, if the problem is only the QT Player then why aren’t Adobe et al. just saying uninstall the player but leave the codecs?”

    I’ve heard varying explanations as well, My guess is that Avid/Adobe don’t want to license ProRes, as there are a number of other players on the PC that do and, from what i understand, aren’t affected by this.

    You want to hear screaming? Despite literally years of notice, wait till QTKit on the Mac gets shut off. Not too far away I’d guess.

    ————————————————————-

    ~ My FCPX Babbling blog ~
    ~\”It is a poor craftsman who blames his tools.\”~
    ~\”The function you just attempted is not yet implemented\”~

  • Andrew Kimery

    April 21, 2016 at 9:50 pm

    [Charlie Austin] “You want to hear screaming? Despite literally years of notice, wait till QTKit on the Mac gets shut off. Not too far away I’d guess.”

    They should just release a new MacPro on the same day and no one will notice about QT.

  • Oliver Peters

    April 21, 2016 at 10:46 pm

    “My guess is that Avid/Adobe don’t want to license ProRes”

    Huh? Avid and Avid do license ProRes from Apple. That’s how they can write ProRes media on the Macs.

    Oliver

    Oliver Peters Post Production Services, LLC
    Orlando, FL
    http://www.oliverpeters.com

  • Gary Huff

    April 21, 2016 at 11:16 pm

    [Oliver Peters] “Huh? Avid and Avid do license ProRes from Apple. That’s how they can write ProRes media on the Macs.”

    I was under the impression that they use APIs under OSX to actually do this, previously through QTKit and now under AVFoundation. Resolve also will read/write ProRes on a Mac, but not under Windows.

    I am also under the impression that most of the Windows products that write ProRes QuickTimes are reverse-engineered and in some gray area where they are not officially supported ProRes renders.

  • Oliver Peters

    April 21, 2016 at 11:27 pm

    With Adobe, Avid, AJA and BMD, they pay Apple a license fee regardless of how they do it. This makes it legal, spec-compliant, and gives them the right to use it in marketing literature. They have stated so publicly and are listed as partners in any official Apple marketing literature or slides.

    On Windows, the people legally doing it, like Telestream, have also licensed it from Apple, but it’s only used in the context of distributed network renders, such as with Vantage.

    The origins of ProRes are claimed to have come from an open source codec, which then Apple adopted and modified. I don’t know how true that is, but it’s what these grey market versions are. There are also people who have used these and found they aren’t completely compliant with Apple’s specs. For example, they induce the “conforming” function when opened in QT Player X.

    Oliver

    Oliver Peters Post Production Services, LLC
    Orlando, FL
    http://www.oliverpeters.com

  • Andrew Kimery

    April 21, 2016 at 11:32 pm

    [Oliver Peters] “On Windows, the people legally doing it, like Telestream, have also licensed it from Apple, but it’s only used in the context of distributed network renders, such as with Vantage.”

    Is this because Apple won’t license to NLEs on Windows or is it because NLEs on Windows don’t want to pay the license fee? Any idea? I know with Shake the cost was severely discounted for the Mac version, kinda discounted for the Linux version and not discounted at all for the Windows version (which Apple killed after a few years). I wonder if it’s similar situation here.

  • Oliver Peters

    April 21, 2016 at 11:40 pm

    Apple will not license for “record” (encode) use on Windows. I think might also be true for Linux.

    Oliver

    Oliver Peters Post Production Services, LLC
    Orlando, FL
    http://www.oliverpeters.com

  • Christopher Sosa

    April 22, 2016 at 12:21 am

    Has anyone had luck with exporting DNxHD MXF with an alpha? Right now we use the .mov wrapper but I can’t seem to get an alpha to come over in AME CC.

  • Walter Soyka

    April 22, 2016 at 12:24 am

    [Oliver Peters] “Apple will not license for “record” (encode) use on Windows. I think might also be true for Linux.”

    Apple has started licensing niche products for ProRes encode off of OS X. Assimilate has a license; I’ve been using SCRATCH on Windows for official ProRes encodes. Flame on Linux writes official ProRes, too.

    No major product off of OS X has an official ProRes license yet.

    Walter Soyka
    Designer & Mad Scientist at Keen Live [link]
    Motion Graphics, Widescreen Events, Presentation Design, and Consulting
    @keenlive   |   RenderBreak [blog]   |   Profile [LinkedIn]

Page 3 of 7

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