Firefox - HTTP "Content-Type" of "audio/x-mpg" is not supported.

[Gino]

I am trying to play mp3 files and getting the above error in FF 22. I understand the browser is not interpreting the file correctly. Any way to fix this? 

I have almost a typical, example-like setup.

Thanks!

[hedlikeahole]

Just had a very similar error with m4v files after upgrading to FF22.  Change the MIME type for x-mpg to Audio/mp3 and try that.  Otherwise, the Mark P. guy on here will help if you keep bumping ;) He's my new hero :D

[Mark Panaghiston]

Set the MIME type to audio/mpeg
http://www.jplayer.org/latest/developer-guide/#jPlayer-server-response

Firefox is strict with MIME types as per the W3C spec and refuses to play anything that it does not recognise.

I think they need to loosen up the spec a little here or at least list the mime types acceptable for each format. They have added the application/octet-stream wild card into the spec, but am not sure if any browsers follow that rule yet. I think they added it since so many websites corrupt the mime type of MP3 files and other media so that you can link to and download it easily, rather than the browser try and play it in quicktime or whatever. I'm off on a tangent here.

[Eugene Fliman]

Thank you both for your answers. I don't have control over the server side, and I checked Mark's link before. Is there a way to control it on the web page itself, in player init or something like that?

Thanks!

--
You received this message because you are subscribed to a topic in the Google Groups "jPlayer: HTML5 Audio & Video for jQuery" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/jplayer/DbIUxkCBx9A/unsubscribe.
To unsubscribe from this group and all its topics, send an email to jplayer+u...@googlegroups.com.
To post to this group, send email to jpl...@googlegroups.com.
Visit this group at http://groups.google.com/group/jplayer.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

--
Eugene Fliman

[Mark Panaghiston]

It is the server that gives the MIME type... It is the Firefox browser that is refusing to play your existing MIME type. There is no way to fix that client-side.

You could raise a Firefox bug report, explaining the problem with strict mime types. Maybe if enough raise the issue or contribute to the existing one - since i expect that many have bugged it in some form - then maybe they will add these other mime type naming conventions that all mean pretty much the same thing more or less.
https://bugzilla.mozilla.org/

Actually, you could use jPlayer to prioritize the flash player and then Firefox would use that along with all other browsers that could use flash. Or you do a UA sniff and set the solution option according to whether firefox or not.