Loading Profile...
EMPLOYEE
Flash exception/errors with Flash 10 plugin and SM2 using either Flash 8 or Flash 9 .SWFs
Since downloading the new Flash 10 plugin (debug version), I've noted some errors being reported when calling certain sound methods - particularly with the new MPEG4 "MovieStar" content. I'm working on fixing these, so users with Flash 10 won't hit these exceptions.
I’m d'oh!
2
people have this problem
I have this problem, too!
Tell me when someone solves it.
The more people who report this problem, the more it gets noticed.
The more people who report this problem, the more it gets noticed.
The company marked this problem solved.
The best solution from the company
-
SoundManager v2.90a is now out, which should include a fix for most flash 10 plugin exceptions when using the Flash 9 version of SM2.
http://schillmania.com/projects/sound...
The company says
this solves the problem
Create a customer community for your own organization
Plans starting at $19/month
-
Inappropriate?(This bug should apply to SoundManager v2.80a and earlier. The flash 8 version may actually not be affected, FWIW.)
For the curious: In some cases a SMSound object's soundChannel is null, or the sound had already been destroyed in situations where code was trying to access undefined objects, methods or properties.
These appear to be general "null or undefined" exceptions which were not being reported in Flash 8 or 9 debug players, for some reason. Perhaps Flash 10 is simply being more strict in reporting these rather dumb mistakes.
I’m curious
2 Comments Add a comment
This solves the problem
-
I use SoundManager V2.77a.20080901. Here is my code if it can help. I've got an exception in my function _unloadRess() :
soundManager.debugMode = false;
soundManager.flashVersion = 9; // Required for multiShot
soundManager.waitForWindowLoad = true; // Wait for window's load to init
function _unloadRess() {
if(ressObj) {
for(var _i in ressObj.music) {
var _mid = ressObj.music[_i].id;
soundManager.stop(_mid);
soundManager.destroySound(_mid);
}
}
} -
Same problem with SM2.80a-20081005
No problem if setting to soundManager.flashVersion = 8; -
Inappropriate?Here's an example error from one of the animation demos, Flash 10 plugin installed and using SM2 with flashVersion = 9:
Error #2044: Unhandled IOErrorEvent:. text=Error #2032: Stream Error.
at SoundManager2_AS3/_createSound()
at Function/http://adobe.com/AS3/2006/builtin::apply()
at flash.external::ExternalInterface$/_callIn()
at <anonymous>()
at flash.external::ExternalInterface$/_evalJS()
at flash.external::ExternalInterface$/call()
at SoundManager2_AS3/_externalInterfaceTest()
at SoundManager2_AS3()
</anonymous>
This is actually an unhandled exception from a 404/not found when trying to load an MP3 (Flash 9), which I have fixed and will be available with the next release.
I’m d'oh!
-
Inappropriate?SoundManager v2.90a is now out, which should include a fix for most flash 10 plugin exceptions when using the Flash 9 version of SM2.
http://schillmania.com/projects/sound...
The company says
this solves the problem
1 Comment Add a comment
This solves the problem
-
Ok destroySound() works fine now. No more exception. Thank you :)
Here is another issue...? When I destroy a sound while playing and using multishot:
- the sound doesn't stop
- when finished it puts the following warning (for sound 'title1' for example):
(Flash): Warning: Could not set position on title1: ArgumentError: Error #2068
SMSound.setPosition(0)
(Flash): Could not set position on title1: ArgumentError: Error #2068
... instead of the normal comment which should be:
SMSound.setPosition(0)
This behaviour may be confusing (no stop) and I worry about some memory leaks...
Regards, Herve -
Inappropriate?@Nitrogen: destroySound() now calls setPosition(0) as part of the process, and it looks like it's running after the sound object has actually been destroyed. This shouldn't be causing any leaks as the object should already be gone from flash - or, I have a bug where I'm not passing a correct value to setPosition(), given the argumentError.
Either way, multiShot is something I haven't yet handled; it may help if stop() is called first on the sound and all playing instances are stopped, then the sound can be safely destroyed. I'll keep this one in mind.
If you can report a new "problem" with your description from above, that'd be helpful so I have a fresh thread to track it with. Thanks!
I’m thankful
