7.3.1 ends Flash support inside QuickTime files
apple Verified ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
Many of my older Web based files (Flash media inside a .mov container) now only show a black space where the older Flash track is supposed to play.
You can no longer "Enable Flash" from the QuickTime System Preferences.
Real bummer and no advanced warning. I guess I'll just pull those pages down and trash the files.
Bad Apple.
14 replies
Sign in or join Beachball Help to reply.
- 0
Apple Support Community member ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
I can't believe Apple have done this. I understand the cause but they brought it on themselves by not updating flash support and then they land us with this huge problem. They have ruined a complete business for us.
- 0
Apple Support Community member ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
Their position was one of security and I understood some of the issues with Flash media.
What better level of security control to complete removed previously supported media formats?
I guess I should have seen it coming. First a new check box to "allow" (Enable Flash) hidden in the System Preferences and then these new security issues.
Maybe support will return? I'm not holding my breath. - 0
Apple Support Community member ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
I have sent an email to Apple developers asking the question of who decides which movies are safe, but heard nothing so far.
- 0
Apple Support Community member ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
my two cents.......
Since flash version 6 and above isn't supported in Quicktime anyway, only version 5 and below. And seeing problems with flash in Qt these last few years. I can see why Apple decided to drop support with flash in Qt. More headaches with flash as new upgrades and updates come to Qt.
And one last thing. Seeing that the new flash player now supports Quicktime h.264 directly, with no further conversions. What container do you think will be used for h.264 on the web, Flash or Qt. You read into this one...
- 0
Apple Support Community member ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
The thing is if it was for web delivery, I wouldn't care, but our system uses self contained players for content delivery and flash in QT is vital for us to achieve this. At a drop of a hat, Apple has just disabled thousands of players that we have in circulation out there. We where proud that our system is based on QT, how ironic...
- 0
Apple Support Community member ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
alexjordan wrote:
The thing is if it was for web delivery, I wouldn't care, but our system uses self contained players for content delivery and flash in QT is vital for us to achieve this. At a drop of a hat, Apple has just disabled thousands of players that we have in circulation out there. We where proud that our system is based on QT, how ironic...Ok, but how many people are using Flash version 5 and below to achieve this, not many. And how many are trying to use flash version 6 and above to achieve this, which isn't or has been supported. A few.
Bottom line, since the development of flash in Qt was dropped years ago. Apple should have dropped it all together years ago too. Then we wouldn't have this mess today.
I guess the headaches (for Apple) in using flash in Qt today out weighs the further support of an old version of flash.
- 0
Apple Support Community member ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
It isn't about the ability to create Flash (swf) files and even the newest version still allows me to publish as version 5 compatible.
Since QuickTime Pro allowed me to open .swf files and then use them without conversion in a .mov container I've made dozens of files with Flash tracks. Some tracks are just "buttons" that allow interactivity in some files. Many others were the complete content of the file.
A visitor to my Web pages now just gets a black window and the audio portion of the Flash track.
I've been using QuickTime since it first went "Pro" and this is the first time backward compatibility has been reduced.
I'm digging around in Time Machine hoping to find an older version of the QuickTime preference files that will restore the browser plug-in settings to 7.3
My Front Row QuickTime files also display the problem as does any other app that uses QuickTime.
I can only hope that the error Apple has made is temporary. - 0
Apple Support Community member ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
I found this in the security content of QT update page:
http://docs.info.apple.com/article.html?artnum=307176
QuickTimeCVE-ID: CVE-2007-4707
Available for: Mac OS X v10.3.9, Mac OS X v10.4.9 or later, Mac OS X v10.5 or later, Windows Vista, XP SP2
Impact: Multiple vulnerabilities in QuickTime's Flash media handler
Description: Multiple vulnerabilities exist in QuickTime's Flash media handler, the most serious of which may lead to arbitrary code execution. _*With this update, the Flash media handler in QuickTime is disabled except for a limited number of existing QuickTime movies that are known to be safe.*_ Credit to Tom Ferris of Adobe Secure Software Engineering Team (ASSET), Mike Price of McAfee Avert Labs, and security researchers Lionel d'Hauenens & Brian Mariani of Syseclabs for reporting this issue.
- 0
Apple Support Community member ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
I'm not at all surprised that Kirk gets this, but I am surprised that David does not...
The point of the matter is that QuickTime is NOT a media player. QuickTime is a complete multimedia authoring and delivery platform designed for the production of interactive multimedia. Yes, as a media player it is designed to be able to play back just about anything. But that's not why it supports Flash tracks, and that's why it doesn't matter that Flash support hasn't advanced past v5. After all, if you want to play back a Flash 8 file, use Flash Player 9. Had Apple not screwed up that default setting in QuickTime 7.1 (without fixing it three versions later) this discussion forum would still be full of useful QuickTime discussion instead of overrun with these inane questions about "Why can't I play videoz on the Web anymore?"
QuickTime does not include Flash support so that it can play Flash files. That's not why it is there.
QuickTime includes (included) Flash support so that it can play Flash TRACKS, which, at least partially because of the dearth of decent sprite editors out there, are the easiest way to build interactive controls into a QuickTime movie. I'm sure the BMW films from a few years ago were not the only ones to be produced as a skinned QuickTime movie with a complete set of Flash controls. Take away the Flash, and those movies won't even play *AT ALL* because they rely on controls that are not exposed to the user in the movie controller but are made available via the Flash controls.
(alternate audio tracks, anyone?). Heck, because of Apple's decision in 7.3.0 to turn off Flash tracks by default, I ran into an Apple help file that wouldn't play properly! Now how will QuickTime know that one is "safe"? Or will that suddenly become unplayable now?It goes back to the total failure of anybody to develop a good sprite editor for QuickTime, brought on by the fact that you could accomplish the same thing by building a Flash track. So Flash became the de-facto standard for building interactive controls into QuickTime, if only because Adobe has a very nice sprite and animation editor called "Flash". It doesn't matter that you have to stick with v5 or earlier because you know this limitation when you are creating the file, and there really is no compelling reason to support later Flash versions because the additions to Flash in later versions are really not that useful in the context of QuickTime movies...as I understand it the extensions are more about making Flash able to do video, which QuickTime already does very nicely.
This is just the latest and most obvious in a series of boneheaded decisions Apple has made with QuickTime 7, and I hope they reverse it pretty quickly. They are reducing the usability of QuickTime, turning it into Just Another Media Player, and starting to make longtime QuickTime advocates (like me) start to think like those QuickTime haters in the Windows world. What is going on in Cupertino, anyway? And if QuickTime 7 wasn't ready for release, why did they shove it down our throats with Tiger? We'd have been better off with a QuickTime 6.6 update with H.264 support!
--Dave Althoff, Jr.
- 0
Apple Support Community member ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
Spot on Dave. QT is (was) and authoring environment and thats exactly what we use it for.
- 0
Apple Support Community member ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
I downloaded and installed, no issues (so far). I viewed some websites with flash content, I assume flash player is handling it. I also downloaded the new Java as well.
Next, I will install the lastest flash player as well. - 0
Apple Support Community member ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
Yes, that's to be expected, and that's how the world is supposed to work.
The issue here is when Flash was used *as an element of a more elaborate project*, typically as an interactive layer of a QuickTime movie. Those are the cases we're talking about, for which Apple has turned off Flash support
--Dave Althoff, Jr.
- 0
Apple Support Community member ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
thanks for the details...
- 0
Apple Support Community member ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
This really *****. I am taking a CPA review course, and as part of this course it includes lectures that use the flash playback ability in QT. When I "upgraded" yesterday, none of my lectures would play. I had to go back and install 7.2 again because they have removed 7.3 from the Apple support pages and replaced it with 7.3.1. I was scared to death when none of my videos would play yesterday.