Activity › Forums › Creative Community Conversations › quicktime problems for adobe cc
-
Craig Seeman
April 21, 2016 at 3:43 pm[Oliver Peters] “ProRes can also live in an MXF container.”
Have you tested and found it viable at least on Windows in Avid and PProCC?
The issue I think is still the decoder rather than the container.[Oliver Peters] “FWIW – this issue also affects H.264 wrapped as MP4.”
Which shouldn’t require Quicktime frameworks to decode though.
[Oliver Peters] “They are also looking into what they have to build themselves to fill in the gaps in the absence of QT. For example, which codecs are essential to support. That’s not a quick fix.”
ProRes should be a given. I think Animation may be a concern because some still use it. I’m not sure what other Apple specific codecs are in wide use for post production.
-
Charlie Austin
April 21, 2016 at 3:44 pm[Oliver Peters] “So far, the theoretical vulnerability affects the player only, so you could have QT components installed, but not QT Player. There are plenty of alternatives to the player.”
That’s the important point. For some reason, not many people are interested in pointing that out. Not scary enough I guess. 😉
————————————————————-
~ My FCPX Babbling blog ~
~\”It is a poor craftsman who blames his tools.\”~
~\”The function you just attempted is not yet implemented\”~ -
Oliver Peters
April 21, 2016 at 3:51 pm[Craig Seeman] “Have you tested and found it viable at least on Windows in Avid and PProCC?
The issue I think is still the decoder rather than the container.”I have not tested this on the Windows side. I was more referring to the fact that Avid MC on Macs can use ProRes as an option. When they do, the codec essentially a “closed box” to them, but they can rewrapped as MXF. I don’t believe the same (recording) is available on Windows due to licensing. And yes, it’s a decoder issue, which is why installed QT components are required. Those are the elements that have to be rebuilt in order to completely get away from QT.
[Craig Seeman] ” I’m not sure what other Apple specific codecs are in wide use for post production.”
Also 8-bit and 10-bit uncompressed in MOV containers. Especially with legacy masters.
– Oliver
Oliver Peters Post Production Services, LLC
Orlando, FL
http://www.oliverpeters.com -
Oliver Peters
April 21, 2016 at 3:51 pm[Oliver Peters] “Also 8-bit and 10-bit uncompressed in MOV containers. Especially with legacy masters.”
PS – also things like QT reference files that RED cameras generate.
– Oliver
Oliver Peters Post Production Services, LLC
Orlando, FL
http://www.oliverpeters.com -
Andrew Kimery
April 21, 2016 at 5:59 pm[Ricardo Marty] “For a company that has placesed its future on the on the internet its a major situation. And no your our risk is not every 99 days. Its every time me need to internet access.”
You seem to be trying really hard to blame Adobe for security holes in Apple’s software. A Windows machine with QT installed is potentially at risk even if there’s not a single piece of Adobe software in sight.
-
Eric Santiago
April 21, 2016 at 6:08 pm[Oliver Peters] “There are plenty of alternatives to the player.
“I for one avoid QT player on the Mac itself these days.
I use VLC or host NLE.
That converting option annoys me and I know I can fix it but again I dont use the player period.
-
Walter Soyka
April 21, 2016 at 6:12 pm[Ricardo Marty] “For a company that has placesed its future on the on the internet its a major situation. And no your our risk is not every 99 days. Its every time me need to internet access.”
I think you misunderstand the nature of the vulnerability. It does not rely on Internet access. A completely air-gapped machine could be compromised by simply playing a malformed QuickTime movie in Apple’s QuickTime Player 7 software on Windows.
I think it would also be helpful here to note the three things that “QuickTime” commonly refers to: 1) a media framework, 2) a movie file format, and 3) a media player.
It seems that the vulnerability is in the player, not the framework. As others have noted, you can install the QuickTime components, necessary for a great many media applications, without installing the vulnerable QuickTime Player application itself.
That said… wouldn’t it be nice if our entire industry didn’t rely on proprietary standards, closely held by a seemingly capricious vendor?
Remember, friends don’t let friends spec ProRes for mastering.
Walter Soyka
Designer & Mad Scientist at Keen Live [link]
Motion Graphics, Widescreen Events, Presentation Design, and Consulting
@keenlive | RenderBreak [blog] | Profile [LinkedIn] -
Walter Soyka
April 21, 2016 at 6:22 pm[Ricardo Marty] “How do they substitue codecs that use qt? How do they rework all that has to be worked mostly all their window stuff.”
Adobe has been developing their own media-handling framework (MediaCore) for some time.
It’s probably important to discuss this:
https://blogs.adobe.com/creativecloud/quicktime-on-windows/Notably:
“Adobe has worked extensively on removing dependencies on QuickTime in its professional video, audio and digital imaging applications and native decoding of many .mov formats is available today (including uncompressed, DV, IMX, MPEG2, XDCAM, h264, JPEG, DNxHD, DNxHR, AVCI and Cineform). Native export support is also possible for DV and Cineform in .mov wrappers.”Animation codec is currently a problem, but hopefully that one’s an easy fix; RLE compression is so simple you can do it in your head. DNxHD/HR export is a problem, too, as are growing files, but there’s always MXF.
The real problem in abandoning QuickTime is dealing with that closed, proprietary Apple ProRes codec. We can do better!
Walter Soyka
Designer & Mad Scientist at Keen Live [link]
Motion Graphics, Widescreen Events, Presentation Design, and Consulting
@keenlive | RenderBreak [blog] | Profile [LinkedIn] -
Ricardo Marty
April 21, 2016 at 6:26 pmNo where have i been blaming adobe at all. Just saying how vulnerable it is. And how somethig like this can potencialy affect its business model if not its image. Not saying that it will. But adobe has not commented on this. This by itself can be more damaging.
Ricardo Marty
-
Andrew Kimery
April 21, 2016 at 6:39 pm[Ricardo Marty] “No where have i been blaming adobe at all. Just saying how vulnerable it is. And how somethig like this can potencialy affect its business model if not its image. Not saying that it will. But adobe has not commented on this. This by itself can be more damaging.
“How is Adobe any more or less vulnerable than any other piece of software running on Windows that utilizes QT? It’s just odd that you keep singling out Adobe over and over and over again.
And Adobe *has* commented on this. To be the best of my knowledge Avid, BM, Lightworks, etc., have not. Go to the official Avid boards and you’ll see users asking Avid to officially comment on it like Adobe already has.
https://blogs.adobe.com/creativecloud/quicktime-on-windows/
Reply to this Discussion! Login or Sign Up