Activity › Forums › Creative Community Conversations › quicktime problems for adobe cc
-
quicktime problems for adobe cc
Posted by Ricardo Marty on April 21, 2016 at 2:56 amAll cc systens are compromised. Apple will not fix it and adobe hasnt offered a clue. Of course not being on the internet could mitigate posible damage but the creative cloud is internet
https://fortune.com/2016/04/19/adobe-quicktime-windows-apple/?xid=yahoo_fortune
Ricardo Marty
Shawn Miller replied 9 years, 11 months ago 18 Members · 66 Replies -
66 Replies
-
Andrew Kimery
April 21, 2016 at 4:41 am[Ricardo Marty] “All cc systens are compromised.”
No they are not. Only Windows systems running QT are potentially compromised (the vulnerabilities were found in a lab, not in the wild). If you are using on a Mac you don’t have to worry because Apple only left the Windows users out to dry. Using/not using CC has nothing to do with this.
[Ricardo Marty] ” adobe hasnt offered a clue.”
Have any other companies that make video software offered a clue? From what I’ve read Avid is in a worse bind than Adobe. I’m not sure how dependent Resolve, Lightworks, etc., are on QT. But is it really their responsibility to offer a clue when it comes to patching another company’s software?
[Ricardo Marty] ” Of course not being on the internet could mitigate posible damage but the creative cloud is internet”
CC only has to phone home once every 99 days so I’d say putting the machine on the Interent for a few seconds every three months is pretty low risk.
If anything this situation underscores Walter Soyka’s point, which he has brought up many times, that the industry needs to adopt open standards because you never know when the owner of the proprietary tech is going to disappear or just decide to pick up their ball and go home.
-
Ricardo Marty
April 21, 2016 at 4:53 amIm only talking about windows and specialy cc. Might be once every 99 days but it takes very little to screwup a system. But thats not the only problem. How do they substitue codecs that use qt? How do they rework all that has to be worked mostly all their window stuff. Its becoming a poison cloud.
Ricardo Marty
-
Andrew Kimery
April 21, 2016 at 8:16 am[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.”
That’s what they are working on. As is Avid. As Resolve and Lightworks and every other company that got bit in the butt by Apple deciding to only support QT on OS X but not on Windows. It’s not an Adobe-centric problem.
-
Scott Witthaus
April 21, 2016 at 10:52 amWell, it’s a simple fix. Adobe and Avid must stop developing for the PC and work with Macs only. Simple, right?
😉
Scott Witthaus
Senior Editor/Post Production Supervisor
1708 Inc./Editorial
Professor, VCU Brandcenter -
Ricardo Marty
April 21, 2016 at 12:01 pmFor 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.
Ricardo Marty
-
Craig Seeman
April 21, 2016 at 12:53 pmDevelopers can build in their own decode for playback in the apps.
Telestream Switch, Episode, Wirecast for Windows all handle ProRes playback within the respective app.BTW if you need a professional cross platform player with Quicktime Pro like features and more, you may want to look at Switch.
I don’t doubt Adobe will build in internal decoding for certain Quicktime codecs in short order.
-
Eric Santiago
April 21, 2016 at 1:05 pmFunny after all these years Ive been in the business no one has stepped up and created their own codec/container that could surpass QT.
I’ve lived in a PC only video world for two summers and survived with the Perception PVR using sequential TGAs.
If I had to go back I can probably live with it since Im used to that workflow with Maya and at times CinemaDNG.
DNxHD/HR is also in my workflow to date but can that ultimately replace QT on the Windows side?
If a mfg refuses to support something then dont support them.
I live in an Apple world so I can deal with it on my terms. -
Craig Seeman
April 21, 2016 at 1:23 pm[Eric Santiago] “DNxHD/HR is also in my workflow to date but can that ultimately replace QT on the Windows side?”
That’s a codec and can certainly exist in a .mov (Quicktime) container (as well as .mxf of course). Whereas ProRes only exists in .mov container. Just making sure people understand the difference between codecs and containers. BTW .mov container is not limited to use in Quicktime. H.264 .mov files play just fine in Windows Media Player.
I’d also add that Quicktime Frameworks is deprecated on Mac as well. You can’t sell anything in the Mac App store that depends on it. Apps have to use AVFoundation (Core Media). Regarding codecs, try opening an Animation .mov in Quicktime X and it’ll convert it to ProRes 4444 (to preserve alpha channel) for playback.
For whatever reason there’s no news about Quicktime 7 vulnerabilities on Mac OS though.
It’s really about building decoders in the programs rather than external dependancies.
-
Gary Huff
April 21, 2016 at 2:32 pm[Ricardo Marty] “For a company that has placesed its future on the on the internet its a major situation. “
No it’s not. You act like simply being on the Internet is going to blow up your machine. That’s simply fear-mongering. I flew by the seat of my pants on Windows for years (and it’s much better now than it used to be even), and did not have a problem.
Why?
Because I’m not ignorant. I don’t just click around like I’m machine-gunning the mouse, accepting every thing that wants to download while I blindly click around Google search results of a dubiously legal nature.
If you keep Windows updated, use Security Essentials, and don’t just automatically click every DOC, RAR, and EXE sent your way by people you don’t even know, then you’re going to avoid a lot of that.
-
Oliver Peters
April 21, 2016 at 3:21 pm[Craig Seeman] “Whereas ProRes only exists in .mov container”
ProRes can also live in an MXF container.
[Craig Seeman] ” BTW .mov container is not limited to use in Quicktime. H.264 .mov files play just fine in Windows Media Player”
FWIW – this issue also affects H.264 wrapped as MP4.
[Craig Seeman] “It’s really about building decoders in the programs rather than external dependancies.”
In speaking with both Avid and Adobe developers here at the show, they both depend on having QT components installed. 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.
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.
– Oliver
Oliver Peters Post Production Services, LLC
Orlando, FL
http://www.oliverpeters.com
Reply to this Discussion! Login or Sign Up