Loading Profile...
Not working in chrome?
For some strange reason the update seems to have broken Chrome... Not any other browser, but there seems to be a flash error that it runs into in chrome. No idea what the error actually is, but I took a picture of the console hoping that might help.
http://ytdj.ca/error.jpg
Also: some properties that I have set that I thought might be relevant to the issue
soundManager.flashVersion = 9;
soundManager.defaultOptions.multiShot=false;
soundManager.defaultOptions.useWaveformData=true;
soundManager.defaultOptions.useEQData=true;
soundManager.defaultOptions.useHighPerformance=true;
soundManager.defaultOptions.autoLoad=true;
I tried disabling waveform, eq and high performance and a bunch of other things, but I just can't seem to fix this one.....
http://ytdj.ca/error.jpg
Also: some properties that I have set that I thought might be relevant to the issue
soundManager.flashVersion = 9;
soundManager.defaultOptions.multiShot=false;
soundManager.defaultOptions.useWaveformData=true;
soundManager.defaultOptions.useEQData=true;
soundManager.defaultOptions.useHighPerformance=true;
soundManager.defaultOptions.autoLoad=true;
I tried disabling waveform, eq and high performance and a bunch of other things, but I just can't seem to fix this one.....
I’m lucky no one uses chrome yet!
1
person has 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 thinks this is not a problem.
The best solution from the company
-
Ah yes, never assume SM2 will have loaded when body.onload() fires etc., as SM2 relies on a Flash movie loading which may or may not be appended by the time body.onload() fires. Cached pages are good candidates for the body onload() firing before SoundManager is ready.
Always use soundManager.onload() to determine when SM2 is ready for use, because it may fire either before or after window.onload()/body.onload().
I'm marking this thread "not a problem", assuming this has been the cause of the load issue for you.
The company says
this solves the problem
Create a customer community for your own organization
Plans starting at $19/month
-
Inappropriate?I just tried switching to flashVersion=8 and it seems that it works that way.....
I’m amused
-
Inappropriate?Err wow.... I just cleared the cache and it works now..... I swear I did that before, but it works now, so I'm happy and mad at myself.
I’m dumb
-
Inappropriate?Hmmmm, interesting. This might be a problem related to computeSpectrum() in Flash when trying to get the waveform/eq data, as I did see it occasionally throwing an exception despite Flash previously saying that all sounds are "accessible" (meaning the ondataerror() stuff should not be firing.)
Also, just so it's been said, make sure you are using the latest SWFs which came with the version you downloaded. (I might add a version string or check to the SWF assets, so it'll be obvious via debug output if there's a conflict/difference.)
In development I would occasionally see an uncaught exception when seeking in a file that was loading (for the first time?) and using waveform + eq data in development, so I put a try .. catch around the waveform stuff just to be safe. (The try..catch is in version 2.95.)
I'll keep an eye out for this and other exceptions in Flash, though I haven't seen any recently. Might be a wacky timing-related issue. If you install a debug version of the Flash player plugin, you will get a window which gives more information when exceptions happen (though it can be annoying as lots of web sites have uncaught errors in their SWFs!)
-
Inappropriate?Hmmm, I might look into the debug version of flash, but hopefully I won't have to for now.
I started getting the errors again, so I'm a little less mad at myself, because now I know it's not JUST the cache at least ;-)
It seems to go away if I close the tab and open it in a new one.
I'm thinking that it might be something wrong with the javascript debugger and console in chrome though as it seems like it somehow breaks things. I've been using the "dev" channel for chrome BTW.
-
Inappropriate?Hm! Actually looking again at your debug image there, it does say there was an uncaught exception in Actionscript - so that sounds like something happening that should be identified with a try.. catch within Flash. I'll try a test page with the same parameters as you're using, and will see if I can repro the issue.
In the meantime if you're OK with installing the debug version of the Flash player (check Flash player downloads), you should get a pop-up dialog from Flash when that error happens, including the cause of the error.
Looks like the line reported in SM2 is when createSound() is called on the Flash side (with Flash 9 according to the output there also), it may be just an edge case I missed - perhaps a null, missing or malformed parameter.
I can't imagine Chrome somehow getting Flash errors when other browsers aren't, but stranger things have happened. ;)
-
Inappropriate?I've installed the debug version now in one of my testing environments.
I'll let you know if something comes up, but so far it seems to be alright though.
The debugger still breaks things but it doesn't seem to be specific to SM2 at least.
-
Inappropriate?After performing more tests on several other computers, it seems that it wasn't a chrome specific issue. I had been gradually converting some of my code to use jQuery to make things a bit more simple to implement new features and such, and it SEEMS that there's an incompatibility there instead.
if you use the
$(function)
command (run on document ready) then it seems as though it may either run before soundmanger loads or as it is loading, meaning that it interferes when things aren't completely loaded and I'm trying to call them.
Solution:
<body onload="load(event)" ....>
1 Comment Add a comment
This solves the problem
-
or ya know, another solution would be soundmanager.onload function....
and it does seem that the original issue with chrome was a cacheing one sadly, as I haven't been able to reproduce it since. -
Inappropriate?Ah yes, never assume SM2 will have loaded when body.onload() fires etc., as SM2 relies on a Flash movie loading which may or may not be appended by the time body.onload() fires. Cached pages are good candidates for the body onload() firing before SoundManager is ready.
Always use soundManager.onload() to determine when SM2 is ready for use, because it may fire either before or after window.onload()/body.onload().
I'm marking this thread "not a problem", assuming this has been the cause of the load issue for you.
The company says
this solves the problem
2 Comments Add a comment
This solves the problem
-
Actually the funny thing is that wasn't calling anything to do with soundmanger within that particular load function (just setting up a bunch of other things independent of soundmanager), they just seemed to interfere with eachother anyway..... Still, not a problem I don't think, but good to know in case anyone else has the same issue.
-
Bizarre! You have me pretty stumped on this one, sounds fishy. If it comes up again and there's a definite pattern or something else you find, let me know.
EMPLOYEE
