Skip to main content
Inspiring
September 6, 2011
Question

AIR 2.7.1 breaks sound clip in existing app

  • September 6, 2011
  • 1 reply
  • 1098 views

AIR build 19610 has produced strange behavior in an existing app that has been published and installed since AIR 1.5.

There is a clip onstage (using Flash CS5) which contains sound on its timeline, as well as some simple timeline code (AS3). Certain behavior in the app moves the root playhead to different timeline locations. The sound clip never goes out of scope. At a certain point, for some still-unknown reason, a "ghost duplicate" of the sound clip starts to loop, playing its sound, but without any of the timeline code. It's a "ghost duplicate" because the original sound clip onstage continues to function normally; it doesn't play, and its timeline code is still functional. In testing, I can create other clips onstage that contain sound, with a simple stop() command, and they fail the same way. Different timeline movements can make more ghost duplicates, creating overlapping sounds.

It seems specific to build 19610, since repeated tries with the previous build, 19530, showed no problem. The problem immediately showed once I updated to 2.7.1 in any environment; XP, Win7 or Mac.

I'm trying to work out a simple general case, but the problem only shows when building the complete (and very complex) SWF from the original FLA. Any insight? Thanks.

This topic has been closed for replies.

1 reply

Known Participant
September 6, 2011

This regression bug sounds like one that has been encountered by several other people:

http://forums.adobe.com/message/3891244

It is a very serious bug indeed because it can affect anyone with nested sounds in the timeline.


A bug was opened at:
https://bugbase.adobe.com/index.cfm?event=bug&id=2945792

https://bugbase.adobe.com/index.cfm?event=bug&id=2945792

Amazingly, they have closed the bug even though they could reproduce it in 2.7.1. Apparently it has healed itself in the latest dev build, and they want us to "verify it in next upcoming public release" that the bug doesn't happen anymore. To me this is not a satisfactory outcome for something so serious. Between this bug, the breakage of the Timer class in 2.7, and the multiple languages incorrectly showing as supported in iOS apps, I'm getting really worried about having to depend on Air.  Can you imagine what will happen to existing apps that this bug affects, if it makes it into Air 3.0 release?  Sigh.

chris.campbell
Legend
September 7, 2011

I'll follow up with this internally.  In the meantime, can you checked this against our AIR 3 RC build that was released today on labs?

Thanks,

Chris

tedalde2Author
Inspiring
September 7, 2011

Thanks. The AIR 3 RC resolved the issue (at least on the one PC I tried). I'll try it on different platforms to verify.

In the meantime I'll need to update app components that use sound. It'll be easy for me to switch to using code instead of the timeline, but I pity those who used the timeline for sound in a way that can't be changed.