TheRealTimeWeb.com - Flash Player

FMS registerClass Example Added To github

Mon, 24 Sep 2012 10:15:00 +0100

Hi folks, apologies about the extended radio silence; I've been busy working on a new project which has taken up a lot of my time. The good news is that I am learning a ton of new stuff in the process which in turn should provide me lots to blog about. Expect posts about Rails, heroku, JavaScript, AWS and maybe even Flash ;-)

I've also just discovered a treasure trove of old projects and sample files and I've decided to offload many of them onto github. It would be a real shame to lose all this stuff, some of which is of course pretty useless whereas others may be useful to some folks. It'll be tricky to pick the right stuff as no doubt I will not be able to post everything I've got floating around...
So to make a start (and with the hope to keep this up) here's my first little Flash sample project. This one shows how to use registerClass to send custom typed ActionScript objects over RTMP between client and FMS server (sorry, AMS it is now...). I don't take full credit for it as I cannot remember if this was based on someone else's work or not... if it was you get in touch and I'll provide credit and link juice!

My github account can be found at https://github.com/stoem (not much there yet), and this particular repo is at https://github.com/stoem/FMS-registerClass.

Happy forking you forkers :-)

Flash Player 11.2 Breaks Video Support For Some Webcams

Fri, 20 Apr 2012 04:37:00 +0100

An annoying bug has surfaced in Flash Player 11.2 that breaks support for some webcams. It appears that cameras of the Microsoft Lifecam VX series are most affected.

A few days ago a customer contacted me about an issue he was experiencing on Scribblar whereby his webcam image would freeze immediately after starting the camera. He also noticed that this problem only occurred in the latest Flash Player versions 11.2.202.228 and 11.2.202.229.

The only known workaround currently is to use an older version of the Flash Player - the following forum post has some details: http://forums.adobe.com/message/4320673#4320673

The initial bug that was filed is now Adobe internal and no longer visible (for reason only known to Adobe...), but please add your vote to this duplicate bug anyway if you are affected.

I've heard reports that there may already be a fix in Player 11.3 beta - we will know more when the final release drops.

Adobe To Shut Down LCCS, Customers Badly Affected

Fri, 23 Mar 2012 08:34:00 +0100

After several recent announcement around Adobe's LiveCycle platform, it may not come as a surprise to some that the LiveCycle Collaboration Service (formerly Cocomo, formerly Flash Collaboration Service) will be shut down at the end of 2012. What may be a surprise however is the relatively short notice that Adobe is giving existing customers and a total lack of a migration path, leaving many people in a real tight spot.

Remember that LCCS is a hosted collaboration service, effectively cloud based, that allows developers to build real-time communications right into their Flex applications. The work that has gone into LCCS is impressive, and the platform offers a range of great features such as room provisioning APIs, live and audio and video communications (both over RTMFP and RTMP) and even screensharing capabilites (but let's not warm that topic up again...).

Put yourself into the shoes of an existing LCCS customer who has made a significant investment into the product - they are pretty much on their own going forward. It is no mean feat to engineer a similar service on top of FMS (a suggested migration path by the LCCS Product Manager), irrespective of the license fees that FMS would attract. Says one poster on the Adobe forum: "Companies may very well go out of business because of this decision. It's a pretty shameful act."

Make no mistake, FMS is not a straight forward alternative if you are used to LCCS, and suggesting so only confuses people. This is already evident in the forums where one user asks: "Will you be offering the code/installation instructions so that we can get this set up on FMS?"
Clearly the complexities of building a large scale collaborative application on top of FMS is not being grasped by some. There is no way to simply 'install' an LCCS app on FMS. Instead you are looking at weeks, more likely months, of engineering effort.

Some of my readers may know that a large part of my time is spent developing and maintaining Scribblar.com, a live collaboration app built on top of Flex and FMS. When LCCS first launched I carefully considered whether or not to port my product away from FMS to LCCS - I decided to stick with FMS. With hindsight that was the right decision - had I ported to LCCS then Adobe would just have introduced major costs and headaches at best, or killed my entire product at worst. What a mess.

I do need to add a few words about screensharing since forum users have asked about it. The screensaver add-on for Flash Player is not simply a feature of LCCS, it also requires Flash Player hooks to work. This means that even if Adobe was to open source LCCS (which they have stated already they will not do) you would not simply have screensharing features magically appear and work with FMS. No doubt this could be done with if Adobe wanted to make it happen, but I doubt very much that they have any interest in this.
Remember we have been asking for screensharing support for FMS for more than 10(!) years (remember my post about vendor lockout?). Yet FMS has stood still since its 1.0 launch as far as real-time communication features are concerned - instead time and effort was spent on the LCCS side to build an entire new platform plus component set, something we have not had in FMS since FCS 1.0.

I am gutted about the missed opportunities and I feel sorry for those businesses affected by the LCCS shutdown. If there is one positive takeaway from this then it should be the lesson of caveat emptor when building a business around a hosted service. If reliance on a single provider can make or break your product or service then it is time to make some backup plans.

Have you been affected by the LCCS shut down? What are your plans going forward? Please leave a comment below.

Troubleshooting SWF Loading Issues in Chrome - MIME Type Issue With S3

Mon, 30 Jan 2012 08:48:00 +0100

As some of you may already know, I run and maintain a few of my own products, the most popular of which being Scribblar which pushes hundreds of sessions every day.

Recently I started getting reports from users that the main page which hosts the applications' main SWF file was not loading properly, or it would work in one browser but not another. Within the handful of reports I had, Google Chrome appeared to be the browser that posed most of the issues - this seemed odd as Chrome effectively has Flash Player built-in and always auto-updates to the latest release version which is why I recommend it as the preferred browser to anyone who asks.

My first look was towards SWFObject - I figured that maybe something in Chrome had changed and broken the Flash Player detection. A common trap that some developers fall into is to check for specific Flash Player versions, for example only allowing access to Player 11 or below, which then locks users out once Player 11.5 (or similar) is released. But this wasn't the issue here.

After much more digging and more back-and-forth emails with some users I noticed a very odd behaviour when trying to access my SWF directly (without an HTML wrapper) in Chrome. This image shows the request in the Chrome Debugger.

Notice how the shows as 'canceled', and that the content type is coming up as the generic binary/octet-stream? Clearly this pointed towards Chrome not being able to deal with a wrongly set MIME type correctly, whereas other browser may have handled this is a more flexible way.

My files are served via Amazon S3, and the MIME type is usually set during upload and forms part of the file's metadata. My FTP client of choice is Transmit, and after some digging I spotted the 'Cloud' panel in Transmit's preferences.

Here you can specify a particular MIME type to go along with a file extension. For SWF this would be application/x-shockwave-flash (but while you are there you may as well set it up for other file types such as CSS).

After setting these Transmit preferences, all subsequent SWF uploads had the correct MIME type set and hitting the SWF directly in Chrome now gave the desired results. If you need to update the MIME type post-upload then have a look at tools such as BucketExplorer or S3 Browser (Windows only).

It now makes sense why my file showed as MIME type binary/octet-stream: this is the default MIME type used by S3 when no other MIME type is specified during the PUT operation into S3.
This issue took me a while to track down and I hope the information above helps someone.

Accessing the mx_internal Namespace in Flex

Fri, 20 Jan 2012 08:58:00 +0100

This is a topic that comes up from time to time, and it did so for me on a current project so I thought to quickly sum it up again here.
I was working on a Flex project using an old SDK (4.1) and the OSMF-based Spark VideoPlayer component contained within. I had to use this particular player since the customer needed to target Flash Player 10.0 or above.

I'm unsure which version of OSMF this Flex SDK contained, but what I could see was there seemed to be no obvious way to set the bufferTime on the MediaPlayer instance that's contained within the VideoDisplay instance that's contained within the VideoPlayer due to the fact that the MediaPlayer instance was namespaced to mx_internal mx_internal var videoPlayer:MediaPlayer;

What does this namespace mean? It basically is Adobe's way of saying: "Watch out, this stuff right here is likely to change in a future version (of OSMF in this case) and if you mess with it then it may break in the future."

Well in my case it was worth the risk :-) and here's how you'd access the bufferTime property and use the mx_internal namespace.
At the end of all your import statement add this: import mx.core.mx_internal; use namespace mx_internal;

Then somewhere else in your code you can do this (where player is my instance of s:VideoPlayer): player.videoDisplay.mx_internal::videoPlayer.bufferTime = 0.1;

Suck this up and enjoy :-)

Check if Frame Label Exists (in Flash/ActionScript)

Wed, 23 Nov 2011 09:43:00 +0100

A project I've inherited includes a piece of code that sends a MovieClip to a frame with a specific label (in my case the label was 'disabledframe'). Unfortunately some of the MovieClips that extend this base class do not contain said frame label which resulted in a runtime error.
To make matters worse I do not have access to the original assets and adding the rame was therefore not an option. I knew that I could work around this problem by checking if the frame label exists, but couldn't remember how it was done...

Thanks to the power of Twitter and its awesome inhabitants I had the answer delivered within seconds - special thanks to @stray_and_ruby, @stevecarpenter (although his response time to my tweet was at least 24 seconds slower than the first correct answer, he needs to work on that ;-) and an anonymous commenter by the name of DaveW who pointed out a major error in the initial code I posted - oops. // assuming you have a movie clip named 'mc' with a label named 'blah' trace(movieClipHasLabel(mc, "blah")); // traces true function movieClipHasLabel(movieClip:MovieClip, labelName:String):Boolean { var i:int; var k:int = movieClip.currentLabels.length; for (i; i < k; ++i) { var label:FrameLabel = movieClip.currentLabels[i]; if (label.name == labelName) return true; } return false; } Easy when you know that mc.currentLabels returns an Array of framelabel objects within that MovieClip.

By the way - since we are talking about Twitter - if you enjoy my blog posts then why not follow me?

One Day On: Reflections On Adobe's Flash Announcements

Thu, 10 Nov 2011 10:54:00 +0100

Yesterday, November 9th 2011, was a day that Flash developers will remember for some time to come. It was also the day when Tim Siglin (why did I ever doubt him) was proven right when he posed the question: 'The TouchPad Is Dead; Is Adobe's Mobile Strategy Next?'.

Well as it turns out, yes it is, as Adobe yesterday announced that it will halt any further development on the Flash Player for mobile (the desktop Player is unaffected) and will focus on HTML5 to target those devices. The company also confirmed that the AIR runtime in combination with the Flash toolchain was its preferred choice for building native applications for mobile.
The announcement came shortly after the company announced healthy profits, and a 'restructuring' exercise which will see 750 employees lose their jobs. A sad day indeed.

As you can imagine, the uproar was huge, less so because of the fact that Adobe will halt its development on the mobile Flash Player (this makes sense - how many sites do you know that target the Flash Player in a mobile browser? I know of exactly 0) - but more so because of the way these announcements were handled. In short, it was a PR disaster with many of the main stream technology blogs heralding it as the death of Flash full stop.
Meanwhile Adobe's response to this was non existent, and it took all day before the evangelists were instructed to mop up the mess - by then it was too late.

It was disgusting to see self proclaimed tech journalists LOL-ing on Twitter about the layoffs, and even reveling in the fact that 'Steve had the last laugh'. It's pathetic and those individuals (I'm looking at you MG Siegler) should be ashamed of themselves. Even more frustrating is the fact that many people only get to see the well known tech blogs when it comes to tech 'news' and ignore the real sources, many of which are misquoted or outright ignored.

It's hard to draw any positive conclusions from this. Many members of the Flash community (including Grant Skinner who has a post-mortem and Peter Elst who calls it Flash homicide) have posted their thoughts and I suggest you read them as they offer a great angle on yesterday's events. And Lee Brimelow's post has received well over 90 comments already - he's one of the evangelists at Adobe.

I'm disappointed primarily about how Adobe has handled these announcements. Did they seriously expect that the CS Suite pricing changes make any headlines after they put a knife into Flash on mobile? This time I am angry at Adobe, not at Apple. There was not the tiniest hint about this last month at MAX, and noone in the Adobe Community space has had a heads up. Funny that, because whenever they make useless announcements we are first to know, but apparently not so when it really matters. This is a real shame as the decision to stop further development of the mobile Flash Player is quite a sensible one and it will free up resources within Adobe to put towards core Player development (although I am not sure how much will go towards the Flash Authoring team...), but the way they went about it was a total shambles.

Let's move on, the damage is done.

Image courtesy of Sean MacEntee

Setting up Chrome for Debugging on OSX in Flash Builder/Eclipse

Wed, 05 Oct 2011 12:48:00 +0100

Here's a quick tip if you'd like to add Chrome as your default browser (or secondary for that matter) in Flash Builder.

You may have noticed that Eclipse seems to struggle with this if you browse for the location and end up with '/Applications/Google Chrome.app' as the path: it gets rejected as soon as you click 'ok' stating that 'The location value is not a valid path name'.

After a bit of trial and error I managed to find a valid path name after checking out the existing browsers' paths in more detail. Here's what seems to work for me: /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

Note that under Windows you may not encounter this issue. Hope this helps someone.

The End for Adobe's Multi-Screen Strategy?

Mon, 22 Aug 2011 16:35:00 +0100

The End for Adobe's Multi-Screen Strategy? - This is a question that Tim Siglin asks in his recent article on the sudden death of the HP TouchPad and WebOS.

My initial reaction to reading that header was one of suspected link-baiting; but since I know Tim well enough I knew that his style of writing goes substantially deeper than that of an attention-grabbing headline (but hey, this didn't stop me from re-using it. You see my standards are far far lower and since you are now reading my post it clearly has paid off ;-).

So does Tim have a point? Does the demise of WebOS and the sluggish uptake of other (non-iOS) mobile operating systems outside of Android really spell bad news for Adobe and its multi-screen dream?
On some levels the answer is clearly yes as it cannot be argued that deploying to a lot of OSs from one codebase is better than to just a few. And Tim rightly points out that one cannot talk of a multi-screen strategy when there's only two major OSs left to play on (iOS and Android).
Tim goes on to point out:
"A full 80 percent of the tablet devices that Adobe showcased at last October's MAX event either never made it to market, made it to market and floundered, or made it to market and were killed off quickly."

Clearly he makes some good points, and those numbers sound grim. But as a developer who has dipped his toe into mobile development for PlayBook, Android and iOS I do wonder how important those 'other' OSs really are. The PlayBook did not take off in the way that RIM had hoped, in fact one can't even call it a take off at all. Sure, we may see a next revision or a PlayBook2 but whoever thinks that this device will give the iPad a run for its money must be smoking something that I'd like to try some of.

But is it really a loss for Adobe that the TouchPad is dead, that the PlayBook is not all it promised to be and that the iPad still outsells all other tablets put together? I'm not so sure, after all multi-screen is about so much more than mobile. Adobe is making its revenues from selling authoring tools, and with Flash Pro and Flash Builder (including some other HTML-centric tools) have got a decent offering when it comes to targeting not only Android but iOS as well. Flash Player may not be present on iOS, but the Flash ecosystem (which includes the development tools that many of us use daily) is present nonetheless. Developers are actively building and deploying Flash based games to all major mobile platforms - Terry Paton being one example - and even Flex-based applications have been climbing the iTunes chart lately (see Politifact for example which even made it to number 1 in the news app section).

In summary I think Tim is partly right, it would be better for Adobe to have a wider range of platforms it can support in the mobile space. On the flipside the entire mobile ecosystem is still in its infancy and it is unlikely that more than 2 or 3 major OSs will become and stay mainstream - not too dissimilar to what happened on the desktop.
I think that if Adobe can offer publishing tools and workflows that can target the main players in the mobile space (as well as on the desktop, and maybe on the TV as well) then they've got little to worry about. In 2010 Adobe could bank its first $1 billion quarter, with revenue up 33%. Q1 in 2011 was equally successful for Adobe and represented their sixth consecutive quarter of sequential revenue growth.
My oh my, I am starting to sound like an analyst now, but clearly they are doing something right. Could they do better? Of course, but considering all the bad press and Flash-hate that is making the rounds in these times of oh-so-fashionable Adobe bashing it sometimes helps to get some facts down and a reality-check from all the 'tech-news' that we're subjected to recently. I'm starting to get really bored of it - and I'm not including Tim's articles in that.

Flash Player 11 Beta 2 Is Out

Thu, 11 Aug 2011 12:21:00 +0100

A few days ago Adobe has released the beta 2 version of the upcoming Flash Player 11 on labs. Apart from adding 64 bit support which was already part of the beta 1 drop this latest release adds a few new features such as support for the JPEG-XR image format which provides better compression and alpha channel support.
The most exciting new feature for developers of real-time audio and voice applications is of course the addition of H.264/AVC software encoding which results in better quality support for webcam based video.
Game developers will likely salivate over the Stage3D APIs code-named Molehill. This is a set of low-level GPU-accelerated APIs which enable advanced 2D and 3D capabilities across multiple screens and devices.

It'll be interesting to see what developers make of this and we will undoubtedly see some previews at the upcoming Adobe MAX Developer conference.

Have you built any applications using H.264 support or Stage3D yet? Post some links in the comments if you like.

To download Flash Player 11 Beta 2 just visit labs.adobe.com.

Why Flash Will Be Just Fine

Wed, 11 May 2011 17:52:00 +0100

I've just realised that an email reply I wrote on the FlashMedia List would actually make a good blog post. I wrote it in response to someone pointing once again to the death of Flash, brought up by mobile and HTML5.

Actually I see emerging platforms as a big opportunity for Flash, not a threat. Why was Flash successful in the first place? Cross platform consistency.

Same headaches, new platforms. Not every company has the budget to develop an app for the web, plus iOS, plus Android, plus other less significant OSs. We should not underestimate the cost savings Flash brings to the mass market (remember when everyone and their dog wanted a website?), and the only other technology that may be able to offer the same benefits is indeed HTML5 (and by that I include JS, CSS etc). So learn some of that if you wish, but I personally never much enjoyed building HTML based sites, nor do I now. Call me old fashioned, but I still enjoy building Flash applications - and get paid for doing so.

We all have been building apps for years, and now we get a whole new platform to play on. How does that align with 'Flash is dead'? It doesn't.

Remember the real reasons behind Apple's Flash ban: it wasn't because of a lack of features, or bugs, or security, it was because of the threat it poses to their App Store revenues. You know, I know it, Steve Jobs know it.

How many fellow Flash Developers are struggling to find work? Speaking for myself, I've rarely been busier. I look around me and see my clients desperate to find good AS3 coders - and failing. Not because they have all left and are coding JS now, no, but because they all have good jobs already.

So here we are again: we have Flash, and we have HTML with the only difference that all have moved on a bit. History seems to be repeating itself. And I can see Flash still keeping an upper hand and wide popularity as it matures in the mobile space because it not only runs in most mobile browsers but can now also spit out native apps. And guess what: users do not know or care how those apps were built as long as they work. And they pay for these apps, and keeping production costs down can mean the difference between an app making a profit or a loss - not everyone is a Rovio, the money will be in the long tail, mobile is no different.

I've launched one shitty Flash game on iOS and guess what, Apple sends me a few bucks on a regular basis. Imagine if I built a decent app? Do you think I could sell some copies? You bet I could.

But you don't hear about those guys that 'just' make a decent living from it without becoming an App Store millionaire, yet all those guys combined make up the market.

My prediction: HTML5 will be a hit in the long run. And Flash will broaden its appeal and stay successful.

In these exciting times it is even more of a bummer that Adobe feels to need to sue the competition, and one that actually brings value to the Flash platform. RTMP enabled mobile apps anyone?

Flash Advanced Echo Cancellation Has Arrived - Flash Player 10.3 Beta

Tue, 08 Mar 2011 10:40:00 +0100

Adobe have just released the beta version of Flash Player 10.3 which you can download from the Adobe Labs website.

The major feature in this version - especially if you are building real-time collaborative applications - is the advanced echo cancellation (AEC). Developers can now take advantage of acoustic echo cancellation, noise suppression, voice activity detection, and automatic compensation for various microphone input levels. End users will be able to experience higher quality audio to aid conversation flow, without using a headset.

Most of these features can be accessed via the new flash.media.MicrophoneEnhancedMode and flash.media.MicrophoneEnhancedOptions classes which contain properties to control the way that the Microphone instance enhances audio, suppresses echos and so on. The API docs (.zip) are here.

This beta version is currently available for desktop operating systems, with support for mobile and AIR following soon.

Another great enhancement for end users is the native control panel which allows you to manage Flash Player privacy, security and storage settings on Windows, Mac, and Linux directly from the Control Panels or System Preferences on your computer. I love this feature as the Settings Manager used by previous versions of Flash Player was a usability nightmare. I also think that Flash Player looks muchmore grown up now that it's sporting its own settings panel in the System preferences. A great improvement.

Check out the full release notes and other new features here.

Flash Player 10.2 Is Out

Wed, 09 Feb 2011 10:13:00 +0100

Adobe have officially released Flash Player 10.2 for Windows, Mac and Linux.
This release brings a range of performance improvements and feature enhancements. Worth pointing out is Stage Video, a full hardware accelerated video pipeline that improves video playback performance across platforms and browsers by separating the video playback from the DisplayList and offloading rendering to the GPU (where supported).
Additionally, this version of Flash Player offers all the new capabilities previewed in the beta release, like custom native mouse cursors, multiple monitor full-screen support, Internet Explorer 9 hardware accelerated rendering support, and enhanced sub-pixel rendering for much improved text readability.

Install Flash Player 10.2 now or to grab the debug release version go to this page.

My Answers To Gruber's Questions

Wed, 12 Jan 2011 16:35:00 +0100

Argh, Tim Anderson tricked me into reading a post on daringfireball... As expected, what I saw wound me up. In the post John Gruber has some 'questions', and since I highly doubt that Google feels that they owe him a personal explanation I'll take a stab at the answers here (Gruber's blog does not allow comments).

Q 1. In addition to supporting H.264, Chrome currently bundles an embedded version of Adobe's closed source and proprietary Flash Player plugin. If H.264 support is being removed to 'enable open innovation', will Flash Player support be dropped as well? If not, why?

A: No, it won't. Flash does not hinder open innovation, quite the opposite. H.264 on the other hand does, and someone, somewhere has to pay if you and me want to consume H.264 content. In the case of Flash, Adobe pays some of the fees for us, but the future licensing terms are quite uncertain
The Flash community is one of the most highly creative collection of people I have ever had the joy of being a part of. I could go on and list 100 examples here, but just take a look at the most recent thing that comes to mind:
Use Kinect to Control Adobe Flash Using Node.js

That's open innovation in my book. Blitz didn't have to ask anyone for permission to build this application - compare that to iOS. They did not have to pay Adobe to either author or play Flash content - compare that to Apple's developer program. Large parts of Adobe's Flash Platform are open source, but the Player is closed - and rightly so in my opinion. Flash does not hinder innovation, it encourages it. Can the same be said for H.264?

Q 2.Android currently supports H.264. Will this support be removed from Android? If not, why not?

A: Who cares really? Are you calling Google a hypocrite if they don't? If so, where is your criticism of Apple for championing closed source codecs such as H.264 and calling their platform open? Maybe Google is hiding behind 'open' too?
And since the fallback technology for video playback in the browser is Flash anyway you can simply use that - Android has great support for Flash.

Q 3. YouTube uses H.264 to encode video. Presumably, YouTube will be re-encoding its entire library using WebM. When this happens, will YouTube's support for H.264 be dropped, to 'enable open innovation'? If not, why not?

A. It won't matter either way. I have a feeling that YouTube will ensure that their videos can be played back. Did things break when YouTube transitioned to H.264? Actually, transitioning is the wrong term here. Contrary to popular belief there was never such a thing as a 'Flash video codec'. Flash has supported H.264 for years, alongside other codecs. Adding WebM to the mix is a formality now.

4.Do you expect companies like Netflix, Amazon, Vimeo, Major League Baseball, and anyone else who currently streams H.264 to dual-encode all of their video using WebM? If not, how will Chrome users watch this content other than by resorting to Flash Player's support for H.264 playback?

A: Maybe like so: Chrome user navigates to video page. Site detects Chrome. Chrome plays video using Flash which is bundled into Chrome, using an H.264 or WebM version of the content, whichever is available. User is happy.
What am I missing here? Is there something inherently wrong with playing a video in Flash?

Q 5. Who is happy about this?

Google I guess for taking a swipe at Apple. And I know who isn't happy: you aren't, quite clearly. One's own medicine can taste bitter.

Flash Player Camera Issues On OSX About To Be Fixed

Wed, 12 Jan 2011 13:08:00 +0100

If you work with applications that utilise the webcam in Flash you may have noticed some recently introduced issues with some Apple iSight cameras on Mac OSX. The problem described in this bug report has been reported fairly widely and has frustrated many. For some users the uninstall of the 'Google Camera Adapter' resolved things, for others the recent Skype Beta seemed to be the culprit. The problem first emerged with flash Player version 10.1.102.64

Now there is good news. The problem has reportedly been fixed in the release candidate 10.2 of Flash Player which is available now on Adobe Labs. I recommend you upgrade now.