The file is being served with a Content-Type of application/octet-stream,
which is why Firefox refuses to play it. There's a bug about supporting
this via content sniffing (bug 546129 in Mozilla's Bugzilla). If you
correct the configuration on your HTTP server to serve the file as
audio/webm it should work fine.
> Also i've noticed that the ogg file is 83,9 Kio whereas the webm file
> is 101,2 Kio
The WebM file is muxed fairly inefficiently. Each audio packet is stored in
it's own Block (there's no lacing in use), and the file using using Blocks
rather then SimpleBlocks.
Cheers,
-mjt
--
Matthew Gregan |/
/| kin...@flim.org
> The Ogg Vorbis file works in audio tag but not the WebM one
Your file worked fine for me in Opera and Chome. But you should try
checking the file with mkvalidator. Gstreamer has known bugs that make
it output invalid webm files, though this can be cleaned up with mkclean.
But I've had good experience with using mkvmerge instead to remux the
ogg into mkv followed by mkclean to remux into webm.
$ mkvmerge -o temp.mkv input.ogg
$ mkclean --doctype 4 temp.mkv output.webm
This also has the benefit of optimising the file for use over HTTP by
ensuring the cues are at the beginning and removing unnecessary elements.
--
Lachlan Hunt - Opera Software
http://lachy.id.au/
http://www.opera.com/
GStreamer does not output invalid files. There is only one bug in the
GStreamer bugzilla regarding this:
https://bugzilla.gnome.org/show_bug.cgi?id=619374 and all the points
that GStreamer does/doesn't do are in parts of the spec that are not
MUST.
It may create suboptimal audio files as was shown by the original
poster but it does not imply invalidity.
Zaheer
On Saturday 29 May 2010 03:27:36 antistress wrote:
> BTW, any chance to see all these amazing matroska tools (mkclean,
> mkvalidator & MKVToolNix) in a PPA for ubuntu ?
I always provide MKVToolNix binaries for various releases of Debian &
Ubuntu on the MKVToolNix site:
http://www.bunkus.org/videotools/mkvtoolnix/downloads.html#ubuntu
Regards,
Mosu
--
If Darl McBride was in charge, he'd probably make marriage
unconstitutional too, since clearly it de-emphasizes the commercial
nature of normal human interaction, and probably is a major impediment
to the commercial growth of prostitution. - Linus Torvalds
On Saturday 29 May 2010 16:02:50 antistress wrote:
> Thank you Moritz Bunkus for your hard work, i really appreciate :-) Is
> the 3.4.0 version ok for webm ?
No. 3.4.0 does not yet contain the code for WebM. The upcoming release
due next week will contain all the necessary code.
However, building your own Ubuntu package from my Git repository is
pretty easy. Here are instructions:
http://www.bunkus.org/videotools/mkvtoolnix/source.html#debian_ubuntu_package
> Or should i 1sft create a mkv file with mkvmerge and then turni it
> into a webm file with mkclean as Lachlan Hunt has suggested above ?
That works as well.
If you need a debian maintainer for this to actually include into
debian distribution (and thus into ubuntu), I can ask a friend. Just
let me know.
Cheers,
Silvia.
On Saturday 29 May 2010 16:39:45 Silvia Pfeiffer wrote:
> If you need a debian maintainer for this to actually include into
> debian distribution (and thus into ubuntu), I can ask a friend. Just
> let me know.
Thanks for the offer, but mkvtoolnix is already part of Debian and
Ubuntu. In the past the maintainer has been pretty slow with releases so
I provide my own packages as well.
On Saturday 29 May 2010 16:46:05 antistress wrote:
> Last question : with new version of mkvmerge, will still there be some
> benefits to use mkclean after, or will mkmerge produce the same kind
> of optimisation out-of-the-box ?
Not exactly the same -- e.g. the cues (index used for seeking) is not
placed at the start of the file (this is impossible without two-pass
muxing). However, this should not be a major problem.
Other than that the files will be WebM spec compliant.
Matthew Gregan already explained to you why the files aren't playing in
Firefox. Your server is sending the wrong MIME type:
$ curl -I
http://libre-ouvert.toile-libre.org/data/documents/retour_vers_le_futur_2_ohlala.webm
HTTP/1.1 200 OK
Connection: close
Content-Type: application/octet-stream
ETag: "628056108"
Last-Modified: Fri, 09 Apr 2010 00:16:08 GMT
Content-Length: 85960
Date: Sat, 29 May 2010 21:51:52 GMT
Server: Lighttpd
Set-Cookie: SERVERID=prozac; path=/
Cache-control: private
That Content-Type should be audio/webm.
If you were using Apache, then you could fix this by adding these lines
to your .htaccess file:
AddType video/webm .webm
AddType audio/webm .weba
Then change the file extension of your audio-only webm files to .weba so
they are correctly sent as audio/webm.
However, the headers above show that you're using Lighttpd and I believe
you will therefore have to edit lighttpd.conf to assign the appropriate
types. I'm not familiar with Lighttpd, but this tutorial seems to
indicate how its done.
http://redmine.lighttpd.net/wiki/1/TutorialConfiguration
I guess you should just insert these two lines in the the appropriate
location in lighttpd.conf:
mimetype.assign = (
...,
".webm" => "video/webm",
".weba" => "audio/webm",
...
)
This is a change in behaviour related to the new HTML 5 parser, which is
enabled by default in the Firefox nightly builds. Thanks for reporting
this--I've filed a bug here:
https://bugzilla.mozilla.org/show_bug.cgi?id=570641
Cheers,
-mjg
FWIW, the fallback text should never be shown in a browser that supports
<audio>/<video>, according to the spec. It's intended for browsers that
don't support <audio>/<video>.
> Shall i fill bugs against Epiphany and Firefox ?
>
>
> (1) using PPA for WebKit, Epiphany and GStreamer :
> https://launchpad.net/~webkit-team/+archive/ppa
> https://launchpad.net/~webkit-team/+archive/epiphany
> https://launchpad.net/~gstreamer-developers/+archive/ppa
>
--
Simon Pieters
Opera Software