New ffdshow build (?)

[JarrettH]

Hey clsid

How often will you post a new ICL 9 build? They work the best for me :D


2,500th post!!!!

[haruhiko_yamagata]

A patch for the German translation is available on sourceforge.
It is still very incomplete (mainly the encoding and the audio windows) but much better than before.
@anyone who speaks German: Könnt ihr bitte schauen ob (besser wo:rolleyes: ) ich mich beim übersetzen geirrt habe oder was man besser machen kann?
Thank you for the patch, but I couldn't apply probably because of charset problem. Please post the whole file.

[Eragon4ever]

Posted.

[LoRd_MuldeR]

Two small questions:
1. Would it be possible to show SVN revision number on "About" page instead of only the build date?
2. Why do the builders use different installers? Wouldn't it make sens to develop one common installer for all of you?

[clsid]

Hey clsid

How often will you post a new ICL 9 build? They work the best for me :D
I will make another ICL build some time in the next few days. In case I forget, just send me a PM.

[Bathrone]

I agree with Lord Mulder. I have found bugs in one installer but then I lost track of which one it was, so I couldnt post a bug report. Having more than one just opens up the chances for more bugs, makes the lifecycle less consistent and confuses the user community.

[_xxl]

I agree with Lord Mulder. I have found bugs in one installer but then I lost track of which one it was, so I couldnt post a bug report. Having more than one just opens up the chances for more bugs, makes the lifecycle less consistent and confuses the user community.
Please make a bug report.
Two small questions:
2. Why do the builders use different installers? Wouldn't it make sens to develop one common installer for all of you?
Why not?

[LoRd_MuldeR]

Why not?

Of course the builders can use the kind of installer they prefer. But if developers put work into improving the installer, they should act in concert. I mean, why parallel developing different installers for the same project? I prefer clsid's installer, because it seems to be more advanced than the old NSIS installer. But that doesn't mean there is a problem with the NSIS installer, it's fine too ;)

BTW: Is there an important difference known between MSVC and ICL builds?

[zilexa]

What is the best stable ffdshow at the moment?
and for SSE, SSE2?
I thought the one at www.x264.nl, but I did experience very few crashes with xvid files when going back/forth with the mouse & timebar.

[Flexy]

What is the best stable ffdshow at the moment?
and for SSE, SSE2?
I thought the one at www.x264.nl, but I did experience very few crashes with xvid files when going back/forth with the mouse & timebar.

well i might open a can of worms right now...but i always had good success with the yamagata builds on my A64.
I haven't tried the other builds for a while tho.
Try all of 'em and report back, they're all good :)

[Smiff]

hello,
i want to say thanks to clsid2, h_yamagata, drevil_xxlm all the other devs and everyone else who's helping out now.
i went from 2546 to rev155 to 246 (clsid2 generic builds seem most stable on K8-SSE3 system?) and my htpc is producing the best images and closest to stable that it's ever been! bravo.

output queueing now seems good with Dscaler and Zplayer :) but more testing needed, i've seen some frames showing in weird flashes.

now a few comments/suggestions please

1) the new installer that reuses registry settings makes upgrading much less painful, brilliant! but the installer does not seem to keep settings for audio?
2) installler again, could you possibly add a screen early on to keep settings and then skip all the settings during install? because that's just a chance for me to mess things up :p

3) how do you get the Keyboard control to work please? i've never figured this out
4) can you do anything to get the cpu % reading more accurate? this still seems as wild as ever

5) is it normal for lanzos resizing on chroma to cause vertical banding? is this due to non-whole-multiple resize amounts (i resize 720x576 to 1024x576). ive changed the chroma to bilinear for now.
6) what does accurate rounding in resizing do please?

7) what's the deal with SSE2/3 builds atm, are there any parts that really benefit? i've heard very mixed opinions. i much prefer things not to crash than be <1% faster ;)
7b) is there any chance you could graph which filters are how using how much cpu?

oh i forgot my big Q:
8) if you have output queue enabled (fantastic theory btw), this causes some video lag presumably? how much should I offset video by to keep A/V sync? or, is this not exactly predictable? :/


sorry quite a mix of Qs some old some new.
that's about all for now sorry if anythings already answered please link me up :)

[foxyshadis]

If you check the files page (http://sourceforge.net/project/showfiles.php?group_id=173941) you'll see the most recent releases, as well as which revision each is. The higher the revision, the better. (VM9 does some trickery with the dates, so even recent ones look old... that's why I say check the r. ;))

[foxyshadis]

7) what's the deal with SSE2/3 builds atm, are there any parts that really benefit? i've heard very mixed opinions. i much prefer things not to crash than be <1% faster ;)
7b) is there any chance you could graph which filters are how using how much cpu?

oh i forgot my big Q:
8) if you have output queue enabled (fantastic theory btw), this causes some video lag presumably? how much should I offset video by to keep A/V sync? or, is this not exactly predictable? :/
I don't test much anymore, so I can't say what the current stability is (it's always been good to me, lately, whether msvc7/8 or icl9). However, non-generic builds are only useful if you do a lot of filtering, like deinterlacing, denoising, sharpening, adding noise, etc, that mostly aren't hand-optimized. Since I use avisynth for the heavy lifting, I just pick whatever's latest, and never see any difference.

One quick way of getting cpu usage is to compare playing with an option vs without, you'd probably want to use performance counters if you need a graphable log. But true filter-level profiling, no, you'd have to build a profiled version of ffdshow and tag each filter separately for the profiler.

There should be no lag at all from queuing, everything is synched back up internally before being output to the renderer.

[Jeremy Duncan]

Link to Vob I have trouble with. (http://rapidshare.de/files/34475404/Vob.zip.html)

Using CLSID FFdshow Version's 236, 231. I can't open VIDEO_TS.IFO, without FFdshow I can see the opening screen.

I'm using Media Player Classic 6.4.9.0
NVidia Video decoder
Default Media player classic video decoder
DScaler 5008 video decoder
DScaler 5008 Audio decoder
Default Media Player Classic audio
Reclock and No reclock
No settings in FFdshow, but Output Queue samples checked, Input all supported, output YV12.
Same problem with Queue output samples unchecked.

This is a vob from the calibration disk here:
www.calibrate.tv

[zilexa]

If you check the files page (http://sourceforge.net/project/showfiles.php?group_id=173941) you'll see the most recent releases, as well as which revision each is. The higher the revision, the better. (VM9 does some trickery with the dates, so even recent ones look old... that's why I say check the r. ;))

You've got to be kidding!
That sourceforgesite is all about TRY-OUTS!
"A fork of ffdshow implementing newest experimental patches."
I wouldn't dare to select the stable one from that site...

[LoRd_MuldeR]

You've got to be kidding!
That sourceforgesite is all about TRY-OUTS!
"A fork of ffdshow implementing newest experimental patches."
I wouldn't dare to select the stable one from that site...

The original ffdshow site is dead, because the original author of ffdshow disappeared. The last update was months ago! If you want to get up-to-date versions, you'll have to get it from TRYOUTS! The people here work a lot on it, and it should be at least as stable as the old release form origianl web-site but with a lot of new features/fixes included.

I guess ffdshow-tryouts will be merged with ffdshow once Milan returns, if that ever happens ;)

[NULUSIOS]

nobody forces you to use them, man...

[_xxl]

You've got to be kidding!
That sourceforgesite is all about TRY-OUTS!
"A fork of ffdshow implementing newest experimental patches."
I wouldn't dare to select the stable one from that site...
http://sourceforge.net/project/showfiles.php?group_id=53761
There's nothing better!Maybe you could try...

[haruhiko_yamagata]

5) is it normal for lanzos resizing on chroma to cause vertical banding? is this due to non-whole-multiple resize amounts (i resize 720x576 to 1024x576). ive changed the chroma to bilinear for now.
6) what does accurate rounding in resizing do please?
8) if you have output queue enabled (fantastic theory btw), this causes some video lag presumably? how much should I offset video by to keep A/V sync? or, is this not exactly predictable? :/
5) It's an unknown problem to me. Please post a screen shot.
6) It's written in the hint-text below the dialog.Accurate rounding:
unchecked - sometimes holizontal lines are seen
checked - high quality, slower in some cases

8) Each sample has time stamp, so you don't have to worry about lag.

[foxyshadis]

Sadly, ffdshow proper is somewhat less stable than the current "tryout" releases. It started as a place to dump a bunch of experimental patches but since then it's been well-tested and most bugs & regressions removed. At this point it's probably more stable than the old versions.

On the other hand, it's not like installing it is permanent - you can go back to whatever build you're currently using is the latest version crashes on you with a 5-second reinstall. ffdshow's quick and painless installs are nice.

[zilexa]

Ok thanks for the replies, I have posted a few times in this topic, because lots of people here had websites with Ffdshow, everytime a new user opened a website, it was confusing. I thought the tryouts site was just a new one like those.
I'll go for the iCL release with highest revision then.. (I assume the SSE(2) optimized versions do not boost speed a lot..)

[haruhiko_yamagata]

@drevil_XXl
Revision: 258

Modified: src/makefile.inc
===================================================================
--- src/makefile.inc 2006-09-26 12:30:35 UTC (rev 257)
+++ src/makefile.inc 2006-09-26 12:37:00 UTC (rev 258)
@@ -32,7 +32,7 @@
CFLAGS+=-DNDEBUG -UDEBUG -DFFDEBUG=0
#CFLAGS+=-DDEBUG -D_DEBUG

- OPTFLAGS=-O2 -finline -finline-functions -fomit-frame-pointer -march=i686 -mtune=i686
+ OPTFLAGS=-O2 -march=pentium-mmx -mtune=i686 -fomit-frame-pointer -finline-functions -finline -frename-registers -fweb -funit-at-a-time
endif
endif

What do these changes do(purpose, merit...)? I'm not good at compiler options. Please explain.

[_xxl]

http://gcc.gnu.org/onlinedocs/gcc-3.4.3/gcc/Optimize-Options.html
http://forum.doom9.org/showthread.php?p=876245#post876245
-O2 turns on all optimization flags specified by -O. It also turns on the following optimization flags:
-fforce-mem -foptimize-sibling-calls -fstrength-reduce
-fcse-follow-jumps -fcse-skip-blocks
-frerun-cse-after-loop -frerun-loop-opt
-fgcse -fgcse-lm -fgcse-sm -fgcse-las
-fdelete-null-pointer-checks
-fexpensive-optimizations
-fregmove -fschedule-insns -fschedule-insns2
-fsched-interblock -fsched-spec -fcaller-saves
-fpeephole2 -freorder-blocks -freorder-functions
-fstrict-aliasing -funit-at-a-time
-falign-functions -falign-jumps -falign-loops -falign-labels
-fcrossjumping
Optimize yet more. -O3 turns on all optimizations specified by -O2 and also turns on the -finline-functions, -fweb and -frename-registers options.
Using the -funit-at-a-time flag will allow the compiler to consider information gained from later functions in the file when compiling a function. Compiling multiple files at once to a single output file (and using -funit-at-a-time) will allow the compiler to use information gained from all of the files when compiling each of them.

[clsid]

List of known issues in revision 260:

1) VMnc and VP6F/FLV4 do not work. ffdshow isn't even placed in the DirectShow graph. (reported by clsid)
2) VC-1 crashes (FourCC wmva). (reported by clsid)
3) SVQ3 crashes when used in combination with Haali's MP4 splitter. Possibly not a ffdshow issue. (reported by Peuj)
4) Some SVQ3 files play with artifacts / color shifts / totally messed up picture. Same issues in FFplay. (reported by clsid, Peuj)
5) If there's an error in avisynth script in ffdshow, the error message is displayed on top of video. That's ok, but interestingly enough, even if I uncheck the whole avisynth page in ffdshow, the error message still remains. (reported by Egh)
6) When there's more than one audio-stream in the file and you're using ffdshow's built-in audio-switcher, ffdshow performs all audio post-processing on all of the streams, thus slowing it way down. (reported by flanger216)
7) When outputting the audio to AC3 using the ffdshow AC3 encoder there are a lot of downmix overflows. The sound seems to be distorted as if the volume is to high. (reported by TFM_TheMask)
8) Output queue enabled + VMR9 renderless + RGB32 + specific video cards + pause = blackout problem
9) H.264 deblocking options should be moved to 'Decoder options' as single combobox with "standard deblocking, no b-frame deblocking, no deblocking" options in it. (suggested by Egh)
10) Wavpack crashes. (reported by clsid)

[Jeremy Duncan]

Link to Vob I have trouble with. (http://rapidshare.de/files/34475404/Vob.zip.html)

CLSID FFdshow Version's 236, 231.
FFdshow settings, default. Input All supported, output YV12.
Media player classic settings, default, no external filters.
Opening file VIDEO_TS.IFO in Media player classic, and the screen is blank.

Using this version of FFdshow, Link (http://rapidshare.de/files/34523297/FFdshow-20060821-rev2546.exe.html), with the above settings and the screen is not blank but shows the opening screen.

This is a vob from the calibration disk here:
www.calibrate.tv

Please fix this as I like to use Queue output samples on the latest CLSID FFdshow versions. :)

I've also tested the September 25 CLSID ffdshow version and it doesn't work.

[_xxl]

List of known issues in revision 260:
1) VMnc, VP6F and VIXL do not work.
VIXL works for me.

[Moitah]

What's with 'FLV4' decoding... I see some mention of it in the changelog but ffdshow isn't handling the FLV4 fourcc. I used FLV Extract to make an AVI, changed the fourcc to VP62, and ffdshow decoded it fine (albeit upside down... official VP6 decoder does the same thing).

ffdshow_rev248_20060925_clsid_icl9.exe build.

[_xxl]

http://img152.imagevenue.com/loc520/th_51517_gcc_122_520lo.jpg (http://img152.imagevenue.com/img.php?image=51517_gcc_122_520lo.jpg)
Cfont.cpp: In member function 'void TfontPage::font2dlg()':
Cfont.cpp:133: error: '_tcsnccmp' was not declared in this scope
make[1]: *** [ffdshow_dialog_all.o] Error 1
make[1]: Leaving directory `/h/ffdshow-tryout/src/dialog'
make: *** [lib] Error 2

[haruhiko_yamagata]

http://img152.imagevenue.com/loc520/th_51517_gcc_122_520lo.jpg (http://img152.imagevenue.com/img.php?image=51517_gcc_122_520lo.jpg)
Cfont.cpp: In member function 'void TfontPage::font2dlg()':
Cfont.cpp:133: error: '_tcsnccmp' was not declared in this scope
make[1]: *** [ffdshow_dialog_all.o] Error 1
make[1]: Leaving directory `/h/ffdshow-tryout/src/dialog'
make: *** [lib] Error 2
Thank you for the explanation for compiler options.
I've fixed the error, Rev 273 should be OK.

[clsid]

What's with 'FLV4' decoding... I see some mention of it in the changelog but ffdshow isn't handling the FLV4 fourcc. I used FLV Extract to make an AVI, changed the fourcc to VP62, and ffdshow decoded it fine (albeit upside down... official VP6 decoder does the same thing).
As far as my (limited) understanding of the ffdshow code and DirectShow goes, it should be working. There must be a tiny bug or omission somewhere. VMnc is probably suffering from the same issue. Hopefully someone with a better understanding of DirectShow can fix it.



The SNOW encoder in ffdshow is pretty outdated. Unless someone wants to take up the challenge of updating both the SNOW and ffdshow VFW interface code, I propose we remove it.

The x264 encoder in ffdshow is also outdated. I propose we remove it because I don't think updating it is worth the effort since (1) there already is a working and (more or less) up-to-date stand-alone VFW version of x264, and (2) it is recommended to use CLI instead of VFW for encoding H.264.

It is about 8 months ago since Milan last updated the libavcodec code in ffdshow. So although we have updated several parts of it in the tryouts, there are likely still lost of things that could be updated as well.

[haruhiko_yamagata]

The SNOW encoder in ffdshow is pretty outdated. Unless someone wants to take up the challenge of updating both the SNOW and ffdshow VFW interface code, I propose we remove it.

The x264 encoder in ffdshow is also outdated. I propose we remove it because I don't think updating it is worth the effort since (1) there already is a working and (more or less) up-to-date stand-alone VFW version of x264, and (2) it is recommended to use CLI instead of VFW for encoding H.264.
Agreed.

[Egh]

The SNOW encoder in ffdshow is pretty outdated. Unless someone wants to take up the challenge of updating both the SNOW and ffdshow VFW interface code, I propose we remove it.

The x264 encoder in ffdshow is also outdated. I propose we remove it because I don't think updating it is worth the effort since (1) there already is a working and (more or less) up-to-date stand-alone VFW version of x264, and (2) it is recommended to use CLI instead of VFW for encoding H.264.


I hope you didn't mean to remove all VfW support from ffdshow :)

Concerning x264 -- even vfw x264 is quite outdated and doesn't have all last features (like --no-fast-pskip). ffdshow support of x264 was quite lame anyway because it lacks multipass mode.

So not really much point in keeping x264 encoder in ffdshow I guess.

[_xxl]

Should we remove WMV 7,8,9, VC-1, SNOW & FFV1 buggy libavcodec encoders?

[LoRd_MuldeR]

I hope you didn't mean to remove all VfW support from ffdshow :)

:scared: No, please do not do this !!!

I need VfW support very much for decoding AVI files in VirtualDub.
Furthermore the ffvdub filter is essential for VirtualDub!

Removing only the x264 encoding part would be okay.
I use Avidemux for encoding to x264 anyway.
And I don't need to say, that using VfW for H.264 encoding is not a good idea.
Sharktooth will kick your ass if you do so ^^

[clsid]

The rest of the VFW can stay :) I fully agree with LoRd_MuldeR that VFW decoding is very useful. Only outdated or buggy encoders should be considered to be removed if we are unable to update/fix them.

All the encoders do need some testing, because I think some of them may currently be broken.

[_xxl]

:scared: No, please do not do this !!!
Removing only the x264 encoding part would be okay.
I use Avidemux for encoding to x264 anyway.
Why x264?
Why not SNOW and non working WMV7,8,9,VC-1 libavcodec encoders?
X264 can be updated, but it also needs changes in VFW interface.
I have updated x264, but it crashes.

[haruhiko_yamagata]

Should we remove WMV 7,8,9, VC-1, SNOW & FFV1 buggy libavcodec encoders?
If nobody is going to fix it, I think we should remove them. Most of the users do not use ffdshow's encodering feature.
Considering the needs, documentation and stability of decoders and filters have best priority for now, IMO.

@LoRd_MuldeR
Of course I don't have plan to remove VFW decoders.

[Jeremy Duncan]

Link to Vob I have trouble with. (http://rapidshare.de/files/34475404/Vob.zip.html)

CLSID FFdshow Version's 236, 231.
FFdshow settings, default. Input All supported, output YV12.
Media player classic settings, default, no external filters.
Opening file VIDEO_TS.IFO in Media player classic, and the screen is blank.

Using this version of FFdshow, Link (http://rapidshare.de/files/34523297/FFdshow-20060821-rev2546.exe.html), with the above settings and the screen is not blank but shows the opening screen.

This is a vob from the calibration disk here:
www.calibrate.tv

Please fix this as I like to use Queue output samples on the latest CLSID FFdshow versions. :)

I've also tested the September 25 CLSID ffdshow version and it doesn't work.


I'm just wondering if any developer is trying to fix this problem ?
I'm also going to ask you to include a new denoiser in the blur & NR section of FFdshow: "Spresso".
Here's the code:

function SPresso(clip clp, int "limit", int "bias", int "RGmode", int "limitC", int "biasC", int "RGmodeC")
{
limit = default( limit, 2 )
limitC = default( limitC, 4 )
bias = default( bias, 25 )
biasC = default( biasC, 50 )
RGmode = default( RGmode, 4 )
RGmodeC = default( RGmodeC, 0 )

yy = (RGmode ==0) ? 2 : 3
uv = (RGmodeC==0) ? 2 : 3
LIM1 = (limit>0) ? string( round(limit*100.0/bias-1.0) ) : string( round(100.0/bias) )
LIM2 = (limit<0) ? "1" : string(limit)
BIA = string(bias)
LIM1c = (limitC>0) ? string( round(limitC*100.0/biasC-1.0) ) : string( round(100.0/biasC) )
LIM2c = (limitC<0) ? "1" : string(limitC)
BIAc = string(biasC)

expr = (limit<0) ? "x y - abs "+LIM1+" < x x 1 x y - x y - abs / * - ?"
\ : "x y - abs 0 <= x x "+LIM1+" + y < x "+LIM2+" + x "+LIM1+" - y > x "+LIM2+" - " \
+ "x 100 "+BIA+" - * y "+BIA+" * + 100 / ? ? ?"
exprC = (limit<0) ? "x y - abs "+LIM1c+" < x x 1 x y - x y - abs / * - ?"
\ : "x y - abs 0 <= x x "+LIM1c+" + y < x "+LIM2c+" + x "+LIM1c+" - y > x "+LIM2c+" - " \
+ "x 100 "+BIAc+" - * y "+BIAc+" * + 100 / ? ? ?"

# For (old) MaskTools v1.5.8 :
# yv12lutxy( clp, clp.removegrain(RGmode,RGmodeC), expr,exprC,exprC, Y=yy,U=uv,V=uv)

# For (new) MaskTools v2.x :
mt_lutxy( clp, clp.removegrain(RGmode,RGmodeC), yexpr=expr,uexpr=exprC,vexpr=exprC, Y=yy,U=uv,V=uv)

return( last )
}

Link to the Spresso thread. (http://forum.doom9.org/showthread.php?t=103299)

Thank you all for your excellent work in progress.

[haruhiko_yamagata]

I'm just wondering if any developer is trying to fix this problem ?
Yes. I think it's rev 195. Just give me more time.

I'm also going to ask you to include a new denoiser in the blur & NR section of FFdshow: "Spresso".
Though I think it's a good idea, I would like to fix more bugs before adding new feature.

[_xxl]

Wavpack libavcodec decoder works!
You need wavpackdssplitter.
http://xmixahlx.dyndns.org/audio/samples/mplayer-lossless/luckynight.wv

[clsid]

Wavpack crashes with this file (http://rapidshare.de/files/34646550/SoC__XviD_WavPack_MP3_-007.mkv.html). It is muxed into Matroska, so no splitter is needed. But it is good to hear that it works on other files :)

[foxyshadis]

Should we remove WMV 7,8,9, VC-1, SNOW & FFV1 buggy libavcodec encoders?
What's wrong with FFV1? I use it all the time and have never had a problem, even between all the different builds.

It is about 8 months ago since Milan last updated the libavcodec code in ffdshow. So although we have updated several parts of it in the tryouts, there are likely still lost of things that could be updated as well.
lavc was fully updated as one of the first actions of ffdshow-tryouts, and I've kept up with the miscellaneous patches from ffmpeg. The only parts that aren't included are a few video game codecs (I forget which, they're listed in SVN, left off because only lavf can split them) and vorbis (differs a lot from lavc's, they need to be sync'd but I keep forgetting).

[clsid]

lavc was fully updated as one of the first actions of ffdshow-tryouts, and I've kept up with the miscellaneous patches from ffmpeg. The only parts that aren't included are a few video game codecs (I forget which, they're listed in SVN, left off because only lavf can split them) and vorbis (differs a lot from lavc's, they need to be sync'd but I keep forgetting).That's good news.

I have removed the x264 encoder. Everything compiles and H.264 playback still works via both DS and VFW. Everyone please test.

rev276 build (http://prdownloads.sourceforge.net/ffdshow-tryout/ffdshow_rev276_20060927_clsid.exe?download)

[Kostarum Rex Persia]

Why you removed x264 encoder, clsid? Are you sure that this is good move?

[clsid]

Why you removed x264 encoder, clsid? Are you sure that this is good move?Read the last two pages of this thread.

[_xxl]

That's good news.
I have removed the x264 encoder. Everything compiles and H.264 playback still works via both DS and VFW. Everyone please test.

It is a big mistake.Milan worked hard to add it to ffdshow...

[foxyshadis]

x264? better decoder? eh? x264's decoder is in libavcodec; the same person wrote most of both!

There's no point in having a outdated, crippled encoder in ffdshow, that has a semi-regularly updated standalone counterpart already. I similarly don't see the point in xvid or wmv encoders; their native encoders are also much easier to understand and configure. The only benefit is being able to store them directly in mpeg ps. FFDShow should concentrate on providing open source codecs that aren't available in vfw, mostly lavc's.

But for theora, there is no other vfw codec; ffmpeg/mencoder is the only other option. If it's disabled until it's updated, fine, but it shouldn't be removed entirely. (Even though I have no affection for the codec myself.)

And goddam it KRP, why do you always comment without reading anything?

[_xxl]

There's no point in having a outdated, crippled encoder in ffdshow, that has a semi-regularly updated standalone counterpart already.
Thanks for clearing that up!Now I understand why it is better to remove a crippled encoder in ffdshow.

[clsid]

The following encoders do not work for me:
MPEG 4, MPEG 1, MPEG 2, h.263, H.261 and DV.

All the other available encoders work ok on the same input file. All settings on defaults for each encoder.

They give the following error in VirtualDub:
"Cannot start video compression: An unknown error has occurred (may be corrupt data). (error code -100)

Can anyone confirm the brokenness or tell me what I did wrong?

[haruhiko_yamagata]

Link to Vob I have trouble with. (http://rapidshare.de/files/34475404/Vob.zip.html)

CLSID FFdshow Version's 236, 231.
FFdshow settings, default. Input All supported, output YV12.
Media player classic settings, default, no external filters.
Opening file VIDEO_TS.IFO in Media player classic, and the screen is blank.

Revision 285
Bug fix : black out in only one frame movie

Now, it's fixed. Thank you for your report.