Both 32-bit and 64-bit are supported. If you're on a 64-bit machine,
the installer will automatically install both versions of the
components. (You actually have both 32- and 64-bit versions of IE9
installed on your Win7 x64 system.)
What do you mean that the WebM codecs "do not work on my system"?
What were you trying to do?
-Matt
--
You received this message because you are subscribed to the Google Groups "WebM Discussion" group.
To post to this group, send email to webm-d...@webmproject.org.
To unsubscribe from this group, send email to webm-discuss...@webmproject.org.
For more options, visit this group at http://groups.google.com/a/webmproject.org/group/webm-discuss/?hl=en.
This smells like a problem with that video file. Let's rule that out
first. Can you put the file somewhere where we can download it?
-Matt
Thanks for the file. I downloaded it and was able to reproduce the error.
There is an issue with that file. The segment element says that it
has a size that extends beyond the end of the file, so the parser
rejects that file has having an invalid format. If Chrome and VLC can
both render this file, then perhaps the webm parser we used needs to
tolerate this error better (it seems like the file was truncated at
some point), and play as much of the segment payload as is there,
instead of rejecting the file out-right.
BTW, what is the provenance of this file?
Yes, it should probably try to read as much as it can. It's only a
problem if the Cue entries are in the end (seeking will be trickier),
other than that playback should be fine.
--
Steve Lhomme
Matroska association Chairman
This is now fixed in our development build. We will incorporate this
change into our next release of the WebM components.
Thanks again for bringing this matter to our attention.
-Matt
I just pushed the source code changes up to the origin.
When the parser detects a truncated cluster, it treats this as an
end-of-file condition (rather than as an error condition), so you will
get everything up to that cluster. This approach parses over the
cluster that was truncated, but if the cluster size is small relative
to the total file size, you won't notice.
Another possibility is to adjust the cluster size down when truncation
is detected, and then attempt to parse any available blocks in that
last, truncated cluster. For now, I haven't done this, because it
only buys you a few more seconds (if that) of presentation.
-Matt
The problem is that this file is incorrectly formatted, so different
applications will react differently when attempting to render the
file. The webm parser is relatively conservative (perhaps too much
so), so it reacted by simply rejecting the file. We can probably
liberalize the parser to handle this case more gracefully.
-Matt