Hi guys, I can provide precise details if nobody knows off the bat what could be wrong.

I updated a few modules recently (libraries API, styles, views) then noticed my SoundManager widgets were not working properly. They look right, but when I click, the files do not play inline (inside the player) they attempt to open the actual file. Also, if I go into my content type under Mange Display and change the widget type to another SoundManager 2 type...the widget does not actually chgange.

Any thoughts on what could be causing this?

I even rolled back all the modules and I still have this same behavior.

Comments

emergencyofstate’s picture

*edit* Discovered that this is unique to Firefox. I'm running version 4.0.1

Anonymous’s picture

Version: 7.x-2.x-dev » 6.x-2.x-dev

I can confirm that the same problem with FireFox 5 is happening on my new installation of the module.
I goes to the file path and asks for QuickTime to be installed (OSX 10.6).

Works with Chrome 12.0.X - plays directly on the page as it did last time I used the module on another site.

montchr’s picture

I've got a similar problem. I'm running Drupal 7.7 in Firefox 5.0. I did try loading the page in Chrome, and the same problem occured.

The player seems to load when the page is loaded, but the play icon disappears immediately, leaving a blank player as a white square (I'm using the 360 theme). If I click the player, it takes me to the file path and plays the file as a video. Firebug tells me the player is in fact using the (video) element.

This problem only occurs when I'm trying to play an Ogg Vorbis file. If I upload an MP3 instead, no problems.

gern’s picture

Version: 6.x-2.x-dev » 7.x-2.x-dev

Having the same problem in Safari & Firefox with mp3 files. Player seems to load fine, but when clicked it doesn't play and instead switches to a new page loading the file as if user had just clicked a normal http link.

dilari’s picture

So a year later I have this same problem (mostly in Safari) . It used work though.
Any solution?

eggthing’s picture

Version: 7.x-2.x-dev » 7.x-2.0-alpha1

Same problem here. Drupal 7.15 and 7.x-2.0-alpha1. Oddly it plays correctly for anonymous user but not for admin.

eggthing’s picture

I don't know if it's the same for everyone but I've just learned that disabling permissions for the administrators overlay fixed the issue for me.

Magic03’s picture

Setting debug "on" getting this:
-- SoundManager 2: HTML5 support tests (/^(probably|maybe)$/i): mp3: false (using flash), mp4: false (using flash), ogg: true, wav: true --
soundm...?v=2.97 (line 1156)
-- SoundManager 2 V2.97a.20120916 (AS3/Flash 9) + HTML5 audio, high performance mode, normal polling, wmode: transparent, flashBlock mode --
soundm...?v=2.97 (line 1156)
soundManager::createMovie(): Trying to load /sites/all/libraries/player/SoundManager2/swf/soundmanager2_flash9_debug.swf
soundm...?v=2.97 (line 1156)
soundManager::initMovie(): Waiting for ExternalInterface call from Flash...
soundm...?v=2.97 (line 1158)
soundManager: Getting impatient, still waiting for Flash...
soundm...?v=2.97 (line 1158)
soundManager: No Flash response within expected time.
Likely causes: Flash blocked or JS-Flash security error.

soundm...?v=2.97 (line 1156)
soundManager::flashBlockHandler(): No flash response, applying .swf_timedout CSS...
soundm...?v=2.97 (line 1158)
soundManager: Firing 1 ontimeout() item
soundm...?v=2.97 (line 1158)
soundManager: Waiting indefinitely for Flash (will recover if unblocked)...

Flash enabled, other site works fine.

Magic03’s picture

/html/sites/all/modules/soundmanager2/soundmanager2_config.js

Changing soundManager.useFastPolling to false fixes problem in some browsers.

soundManager.useFastPolling = false;

Robinie’s picture

hallo,
I first installed NoScript version 2.6 ( http://noscript.net/ ) in Firefox. - Then a made in Firefox: NoScript-configurations>>Allow Google-chrome temporary -- there are Google chrome configuration 3 x. I setted all to allow (temporary).
Now I also cleared my cache in Google chrome.
And now the buttons-to play files on Google chrome are running well!
--- The buttons in Firefox does NOT run. -- But it is o.k. for me when my main-browser Google chrome now works.

best greets, Johannes

Robinie’s picture

hallo,
the very last point: I don't know if this was important?! >>>

I have installed: "FileConverter 1.3 toolbar for Google chrome". from "Conduit. Ltd." -- I found a free download!!

-- if nothing is working to solve this problem, You could this try too.

Thanks and best greets, Johannes

toxiclung’s picture

i'm using the page player and i have the same problem
i'm using ubuntu (12.10) and soundmanager works fine in firefox (v 18)
but won't play inline in google chrome (v 23) as well as chromium (v 22)

please help

krabbe’s picture

This is weird. I set up a view with audio-tracks using page-player and on my staging-site the tracks are playing nicely inline, but on production site using Safari6 a new window opens with the quicktime-player playing that file.
I dumped the database from staging to production, so the configuration is absolute the same. Only difference is, I'm using a subdomain for staging and the main domain for production.
In Firefox and Chrome all tracks play inline.

This is the link to the production-site: 17hippies.de

thalemn’s picture

I have a similar problem.

Here is the live site: nlca.com
Here is the sandbox site (which is a new development of the live site): sandbox.nlca-dev.com

On the live site (homepage) right sidebar "Tracks by Chance" - works in all browsers (as far as I can tell)
On the sandbox site (homepage) right sidebar "Tracks by Chance" - works in IE 10 and Chrome only.

Any thoughts? Is it the subdomain?

Also, I inherited this site and the soundmanager2 module is installed in the sites/all/themes folder. Is this correct? So I have no configuration settings to the module in the control panel (Drupal 7.22)

thalemn’s picture

Update to my problem...I finally got it working.

I discovered that the path to the swf files was inserted as a block (PHP text format) in the footer! And since I had migrated the site, the text editor had not been applied yet. Once I applied it and made sure the path was correct, everything started working properly.

So ultimately, the path to the swf files is critical because firefox and safari (PC) use flash to play mp3 files!