Error when running makewebm.exe on Windows 7 64-bit
Kyle Sibley
Begin
-----------
C:\Users\<username omitted>\Desktop\WebM>makewebm mnc.avi
Unable to connect demux outpin to VP8 encoder filter inpin.
No combination of intermediate filters could be found to make the
connection. (0
x80040217)
-----------
End
Windows 7 x64. Any idea what might be causing this? I really don't
know where to begin here. There isn't much about it when I google
relevant terms. I ran install_webmdshow.exe and that worked fine. I
also installed xiph.org open codecs as instructed here (
http://www.webmproject.org/tools/ ).
I didn't think this would be so much trouble to convert AVI to WEBM.
Matthew Heaney
>
> C:\Users\<username omitted>\Desktop\WebM>makewebm mnc.avi
> Unable to connect demux outpin to VP8 encoder filter inpin.
> No combination of intermediate filters could be found to make the
> connection. (0x80040217)
So far this looks like it's working as designed: the app is telling
you that the video codec data in the source (the "demux outpin")
cannot be converted to VP8.
What kind of video data do you have in the AVI file?
Is the file in a location where we can get to it?
-Matt
Kyle Sibley
).
So only certain videos can be converted to WebM?
Thanks for the prompt response.
Kyle Sibley
another format using Handbrake to MP4 (m4v) container and the H.264
video codec, but I get another error.
"No filters found that can demux the source filter."
Still at a loss.
Matthew Heaney
> The file is 592MB so I can't post it anywhere.
Use yousendit.com to send it to me: <matthewjheaney@gmail>.com .
> I can convert it to
> another format using Handbrake to MP4 (m4v) container and the H.264
> video codec, but I get another error.
You probably need to install the Windows Essentials Codec Pack:
You might need to tweak the ffdshow property page to enable/disable
the codec you need.
-Matt
Kyle Sibley
decompressed using the Fraps Video Decompressor and the audio is
uncompressed PCM.
I have installed the k-lite full codec pack with all of the essentials
installed __in the past__ so I can't imagine it missing a codec (but
it is possible). However, after I got error messages I completely
uninstalled it and started fresh before I made a post here.
I sent the file to you from my hotmail address.
I had success with converting to WebM from the mnc.m4v file (H.264 and
AAC), but the quality was so very, very bad with default settings and
it took probably 20-30 minutes on a Core-i7 920. I'm still looking
into how to make the quality at least satisfactory.
Pablo
connect demux outpin to VP8 encoder filter inpin.) and I get "Unable
to connect audio stream to muxer." when I try to convert video
converted to x264 (PCM audio) from Fraps, but convertion started.
Another problem is I converted 2GB 720p video from Fraps to x264 in
about minute and now I'm converting this video to WebM for about 10min
and I'm in 19.4/99.7 ... I think Google should make working encoder
for Windows if they want to remove x264 from Chrome and force people
to use WebM.
Kyle Sibley
> about minute and now I'm converting this video to WebM for about 10min
> and I'm in 19.4/99.7 ...
"why did I waste my time waiting for this?" bad.
> I think Google should make working encoder
> for Windows if they want to remove x264 from Chrome and force people
> to use WebM.
Maybe it's just the format we're using (Fraps uncompressed AVI)? You
figure it would be a simple thing. Drag a file to a GUI or open it in
some program, choose quality or something and convert it. I tried that
Miro video encoder and the quality was so bad...
Matthew Heaney
>
> Windows 7 x64. Any idea what might be causing this? I really don't
> know where to begin here. There isn't much about it when I google
> relevant terms. I ran install_webmdshow.exe and that worked fine. I
> also installed xiph.org open codecs as instructed here (
> http://www.webmproject.org/tools/ ).
I just downloaded smb.avi.
MediaInfo is telling me that the video stream is Fraps, and the audio
stream is PCM.
Let me see if I can find a DirectShow decoder filter for Fraps format.
-Matt
Matthew Heaney
<matthew...@google.com> wrote:
>
> You probably need to install the Windows Essentials Codec Pack:
>
> http://www.mediacodec.org/
>
> You might need to tweak the ffdshow property page to enable/disable
> the codec you need.
ffdshow supports Frap decompression. When I enable it, I can render
the video fine. (I'm using WMP12).
Let me try to run makewebm to, er, make a webm file.
-Matt
Matthew Heaney
> know where to begin here. There isn't much about it when I google
> relevant terms. I ran install_webmdshow.exe and that worked fine. I
> also installed xiph.org open codecs as instructed here (
> http://www.webmproject.org/tools/ ).
I can convert the file without any problem. The command line I used was:
makewebm smb.avi
This makes a webm file, smb.webm, which I can then play.
Have you installed ffdshow (available as part of the Windows
Essentials Codec Pack), and enabled Frap decompression?
-Matt
Kyle Sibley
for decoder. I guess that's what I do?
After I did that then makewebm smb.avi worked. Thanks a lot Matt.
Hopefully this is a more straightforward process in the future and
hopefully the conversion speeds up as well. This file was only 79MB
but took quite some time to convert.
Takes me about 10 seconds to convert it to H.264 in Handbrake but it
takes like 8 minutes in makewebm and with lesser quality. I don't know
exactly how to make the quality better because I don't have a full
understanding of the parameters in makewebm.
http://dl.dropbox.com/u/3925457/frapsffdshow.png For those looking for
where the option I found was.
Difference in quality:
Handbrake (H.264 - Web optimized): http://dl.dropbox.com/u/3925457/H264.png
WebM (Default Settings): http://dl.dropbox.com/u/3925457/WebM.png
I imagine that there is a simple way to improve the quality in
makewebm and another way to speed up conversion, but I'm not seeing
it. I don't see this becoming too popular until this process becomes
much easier.
Again, thanks Matt.
Matthew Heaney
> I opened up the Video Decoder configuration and selected "libavcodec"
> for decoder. I guess that's what I do?
Right.
> After I did that then makewebm smb.avi worked. Thanks a lot Matt.
Je vous en prie!
> Hopefully this is a more straightforward process in the future and
> hopefully the conversion speeds up as well. This file was only 79MB
> but took quite some time to convert.
You can trade quality for encoding speed using the --deadline switch.
It specifies the number of microseconds to use for each frame.
The value 0 means "use as much time as necessary". This implies best
quality. You say that directly by using the value "best" (or
"infinite") for the deadline. e.g.
makewebm --deadline=best ...
The value 1 means "use the minimum amount of time". This is a
real-time mode. You can also say "real-time" (or "realtime") as the
deadline value.
The value 1000000 means "use 1 sec" for each frame. This implies good
quality. You can also say "good" as the deadline value.
> Takes me about 10 seconds to convert it to H.264 in Handbrake but it
> takes like 8 minutes in makewebm and with lesser quality.
You have control over both the quality and encoding time.
Good quality is the default for the VP8 encoder filter, if you don't
specify a value explicitly. This might explain why your encode took
longer than expected. You can adjust the value down as required for
faster encoding. Try 5000 or 2500 or 1000 as the deadline values and
see how like the quality.
See the link below for more info.
Note that if you're going to play with video encoding parameters, you
might as well just encode the audio once. Use --no-video switch (and
maybe --require-audio too) to make a webm file with compressed audio
(only). Use --no-audio when you're playing around with video
encoding, to make a video-only file. When you're satisfied with the
video, you can mux the audio and video together using the
--audio-input switch.
> I don't know
> exactly how to make the quality better because I don't have a full
> understanding of the parameters in makewebm.
If you run makewebm without any parameters, you'll get a list of
switches you can use to influence the encoding. There's some info
here about encoding parameters:
http://www.webmproject.org/tools/encoder-parameters/
There are lots of people monitoring this list who know how to tweak
the VP8 encoding parameters for various scenarios. Read the page
cited above, try a few things, and then post questions here if you
need help with anything.
Regards,
Matt
Kyle Sibley
use the example parameters there, but why are the parameters incorrect
there? I can't do makewebm -p 2 or makewebm --best and many of the
other ones. It looks like it's made for an executable named vpxenc.exe
Using makewebm --deadline=best still resulted in pretty bad quality so
I'm playing with --target-bitrate and seeing some promising things. So
far it seems like there's quite the trade off between quality and
encoding time. On the up-side, these files are so very, very tiny :)
Ok, so I set the --target-bitrate to 4096 because I felt a power of 2
was something to try and the quality was good for like YouTube 480p
standards but the encoding time was unacceptable compared to H.264 w/
AAC in an m4v container using Handbrake. It took probably about 7-8
minutes for an 8 second clip. After that I tried setting --thread-
count=4 and --token-partitions=2 and that over halved the speed in
which it encoded, so it took about 3.25 minutes (and this is on a Core-
i7 920, mind you) but this is still a very, very long time for an 8
second clip.
TL;DR
--deadline doesn't do much of anything for me. Best still looks pretty
bad.
--target-bitrate works better
I tried more stuff like more using threads, but it's still slow (3.5
minutes for 8 second video). Handbrake is still faster using H.264/AAC/
M4V
Any suggestions to speed this up?
Again, thanks a lot Matt. You are super helpful!
Matthew Heaney
> I looked at the tools part of the webmproject web page and tried to
> use the example parameters there, but why are the parameters incorrect
> there?
That page shows you general parameters about VP8 compression. It is
not a description of the syntax of makewebm. For that, specify the
help switch for makewebm to get a list of switches. You then have
figure out the correspondence between the VP8 parameters and the
makewebm switches. If you cannot figure it which parameters
correspond to which switches (they are close but not exact), then just
post here.
> I can't do makewebm -p 2 or makewebm --best and many of the
> other ones. It looks like it's made for an executable named vpxenc.exe
Right. It is an explanation of VP8 compression parameters, not a
description of makewebm. Sorry for any confusion.
-Matt
Pablo
carefully? Have you seen his "difference in quality" pictures? Quality
of WebM video in his example is unacceptable, encoding speed was
unacceptable too and your reply was "You can trade quality for
encoding speed". Worse quality? Is it even possible? Converting to
x264 gives us much much better quality in ~50x better speed (encoding
time) and no makewebm parameters in this time can even partly solve
this. You can have applicable quality, but 1 min source will be
converted 2 hours on quad core processor or unacceptable quality in 30
mins. Neither of the two is acceptable/usable.
Matthew Heaney
> Converting to
> x264 gives us much much better quality in ~50x better speed (encoding
> time) and no makewebm parameters in this time can even partly solve
> this. You can have applicable quality, but 1 min source will be
> converted 2 hours on quad core processor or unacceptable quality in 30
> mins. Neither of the two is acceptable/usable.
I think it's true that VP8 encoding takes longer than using other
encoders. Whether VP8 encoding time can improved is a question I
defer to the video encoder team to answer. For now, you just have to
pick your desired quality and then accept that the actual encode might
take a while. For example, if I need some high-quality VP8 source
material, I'll just let the encoder run over night or over the
weekend. If I need something quick and dirty, and I don't
particularly care about the quality (say, I'm testing a change to a
muxer), then I"ll just set the deadline value to something very small.
-Matt
John Koleszar
The reason for the bad quality is that the target bitrate wasn't being
specified, so it was using a very low default (256K iirc) which is
unacceptable for 960x540. I'm not sure how hands-off makewebm is
intended to be, but it could be updated to choose better defaults
based on the frame size in case the user doesn't specify anything.
On Wed, Jan 26, 2011 at 7:55 AM, Pablo <pav...@gmail.com> wrote:
> --
> 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.
>
>