I'm trying to open .WebM in VirtualDub

[alinhoalisson]

Hello guys, I'm trying to open .webm files in VirtualDub, so I can convert them to AVI manually.
I've already downloaded DirectShow codecs for WebM from Google's website, but it doesn't work.

It only shows the window, and then, VirtualDub freezes. There's a screenshot in the attachment.
What should I do?

[El Heggunte]

Matroska plugin by fccHandler:

http://fcchandler.home.comcast.net/~fcchandler/Plugins/Matroska/index.html

Besides, make sure ffdshow's VfW interface is set to decode VP8

However, there is NO functional/acceptable ACM decoder for Vorbis.

[alinhoalisson]

Matroska plugin by fccHandler:

http://fcchandler.home.comcast.net/~fcchandler/Plugins/Matroska/index.html

Besides, make sure ffdshow's VfW interface is set to decode VP8

However, there is NO functional/acceptable ACM decoder for Vorbis.

Still freezing...

[El Heggunte]

Hmmm, I didn't know the Matroska plugin (still?) doesn't support VP8 video

Anyway, the WebM samples I have do not freeze VirtualDub 1.9.11,
they just make it say "NO VIDEO"

For the time being, you'd better try the DirectShow input plugin, OR
frameserve VirtualDub with an Avisynth script

[alinhoalisson]

Hmmm, I didn't know the Matroska plugin (still?) doesn't support VP8 video

Anyway, the WebM samples I have do not freeze VirtualDub 1.9.11,
they just make it say "NO VIDEO"

For the time being, you'd better try the DirectShow input plugin, OR
frameserve VirtualDub with an Avisynth script

OK, I just downloaded the plugins again and now it says "NO VIDEO".
Anyway, I tried with DS input Plugin and it freezes.

I just checked the file with media info and it says the file has 1000fps O_O
Does that have to do with anything?

[El Heggunte]

I just checked the file with media info and it says the file has 1000fps O_O
Does that have to do with anything?

Possibly WebM is a format as pesky as FLV , I mean, both use variable framerate plus weird timestamps, which normally translates as "1000 fps"

However it's more probable that the Google DS filters are the actual source of the freezing problem, since they were created by Linux trolls Just uninstall them, and let the LAV Filters do their job.

[alinhoalisson]

I just checked the file with media info and it says the file has 1000fps O_O
Does that have to do with anything?

Possibly WebM is a format as pesky as FLV , I mean, both use variable framerate plus weird timestamps, which normally translates as "1000 fps"

However it's more probable that the Google DS filters are the actual source of the freezing problem, since they were created by Linux trolls Just uninstall them, and let the LAV Filters do their job.

IT WORK'D!!!!
Thanks so much.

Google's a piece of shit. The most powerful website on the web can't even have a functional codec? ¬¬

[jagabo]

Google's a piece of shit. The most powerful website on the web can't even have a functional codec? ¬¬

VFW is ancient, outdated, and deprecated by Microsoft.

[Cauptain]

Strange, because my virtualdub 1.10.1 open Webm default using FFDSHOW.




Claudio

[El Heggunte]

...
IT WORK'D!!!!
Thanks so much.
...

You're welcome

Google's a piece of shit. The most powerful website on the web can't even have a functional codec? ¬¬

VFW is ancient, outdated, and deprecated by Microsoft.

Is that an excuse for a lousy source-code?
I mean, if LAV Filters have functioned correctly with the DS-Input vdplugin, this implies both Google's WebM codec and ffdshow are broken.

[El Heggunte]

Strange, because my virtualdub 1.10.1 open Webm default using FFDSHOW.

<SNIPP>

Claudio

Please stop posting fugly pics

[El Heggunte]

[ d e l e t e d ]

[jagabo]

I mean, if LAV Filters have functioned correctly with the DS-Input vdplugin, this implies both Google's WebM codec and ffdshow are broken.

No, it doesn't imply anything about the quality of VP8. Google doesn't make a VFW VP8 decoder. You're using third party tools to access a VP8 decoder in VirtualDub.

[El Heggunte]

I mean, if LAV Filters have functioned correctly with the DS-Input vdplugin, this implies both Google's WebM codec and ffdshow are broken.

No, it doesn't imply anything about the quality of VP8. Google doesn't make a VFW VP8 decoder. You're using third party tools to access a VP8 decoder in VirtualDub.

Well, "someone" does have made a VfW VP8 codec ( <-- clicky ).
But that's NOT the point.
Since DirectShow IS capable of interacting with the VfW engine whenever necessary, then the fault actually is:

--- of ffdshow and Google's VP8 codec ; OR...

--- of the DirectShow Input Driver ; OR...

--- of BOTH.

[El Heggunte]

UPDATE

It seems "the root of all evil" ( besides the pseudo-scientist Richard Dawkins of course ) is the media splitter picked by the DirectShow engine. LAV Splitter and MPC's Matroska Splitter do work as they should, even when used with ffdshow --- whereas AV Splitter (and quite probably the WebM source/splitter from Google as well) "freeze" VirtualDub.