New ffdshow build (?)

[foxyshadis]

The fourcc in strh should always be ignored; it isn't a real fourcc at all, it's the name of the codec used to compress it, found in the drivers32 key. That way it gets first crack at decoding. Even avisynth YV12 saved raw from vdub gets a strh fourcc: "DIB ", and x264 will fail on it. It's just checking the wrong place. I'll send a patch to akupenguin.

[foxyshadis]

wheeee! :) Someone actually is going to implement my suggestion :)I just like working on GUI stuff, I never have the time to get intimately familiar with large projects. ^^ I'm glad a lot of you guys can do the heavy lifting much better than I.

Okay, removing the checkbox and having just a combobox sounds good.

Inloop behavior of advanced codecs: "Always deblock (normal)", "Adaptive deblocking (based on delay)", "Reference deblocking (safer)", "Never deblock (faster)".

I could do the same thing for the "automatic quality control" box in post-processing, but it already kind of fits where it is now.


As for an explanation, I'll put something in the box. But I've been thinking, ffdshow's help is kind of mickey mouse; some items have have text under the dialog, some have a help box in the upper right (which doesn't seem to work), some have tooltips. I'd like a standard help mechanism, either a tooltip or maybe one of those blue circles with a ? in it. It would have to be simple to use (for users and developers), easy to translate, and unobtrusive. A bit tricky, but that's for later on, not now.

[haruhiko_yamagata]

As for an explanation, I'll put something in the box. But I've been thinking, ffdshow's help is kind of mickey mouse; some items have have text under the dialog, some have a help box in the upper right (which doesn't seem to work), some have tooltips. I'd like a standard help mechanism, either a tooltip or maybe one of those blue circles with a ? in it. It would have to be simple to use (for users and developers), easy to translate, and unobtrusive. A bit tricky, but that's for later on, not now.
In this case, text under the dialog is suitable for now. In the future, I would like to have help file (*.chm). I think it's more important than adding new feature.

[foxyshadis]

You're right, a help file does sound like a better idea.

[bob0r]

@clsid

Can you make a new x264.nl build?
With the registry fix and maybe some more....

Thanks.

[clsid]

Here is the latest build: rev312 (http://prdownloads.sourceforge.net/ffdshow-tryout/ffdshow_rev312_20061002_clsid.exe?download)

I have managed to fix FLV4 decoding.

[vortex_hl]

@devs

Can you compile libavcodec.dll with icl 9.1? Is it possible? Is there any advantage over gcc 3.x.x, 4.x.x builds?

[KoD]

Lol, maybe the sourceforge site should have a FAQ so that one could simply point people to it. A prime candidate for inclusion in the FAQ would be the: "what is the best build for my cpu/what is the difference between the versions that were compiled using some other compiler/why don't you compile xxxxx with icl, gcc, msvc8, etc.." series. ^^ The answers are already in the thread but nobody could blame people for not reading a whole 130 pages thread... ^^

[LoRd_MuldeR]

@devs

Can you compile libavcodec.dll with icl 9.1? Is it possible? Is there any advantage over gcc 3.x.x, 4.x.x builds?

If you follow the posts in this thread, it's already said that libavcodec.dll contains a lot of hand-optimized ASM code, which is faster than any compiler-optimized code. Furthermore only GCC will use the ASM code, so everything except GCC will skip the ASM code and make it a lot slower.

[vortex_hl]

Lol, maybe the sourceforge site should have a FAQ so that one could simply point people to it. A prime candidate for inclusion in the FAQ would be the: "what is the best build for my cpu/what is the difference between the versions that were compiled using some other compiler/why don't you compile xxxxx with icl, gcc, msvc8, etc.." series. ^^ The answers are already in the thread but nobody could blame people for not reading a whole 130 pages thread... ^^


If you follow the posts in this thread, it's already said that libavcodec.dll contains a lot of hand-optimized ASM code, which is faster than any compiler-optimized code. Furthermore only GCC will use the ASM code, so everything except GCC will skip the ASM code and make it a lot slower.

Sorry folks. it's kind a kostarum rex persia thing, right? I never ask stupid questions again. :o I need a sleep. :rolleyes:

[LoRd_MuldeR]

We need a sticky FAQ, which explains such things!

[_xxl]

More bugs:
1).Access Violation in ffdshow on Windows Vista.
http://sourceforge.net/tracker/index.php?func=detail&aid=1567236&group_id=53761&atid=471489
2).QPEL bugs and colour/block trains/displasement
http://sourceforge.net/tracker/index.php?func=detail&aid=1568940&group_id=53761&atid=471489
3).MSS2 WMV files
http://ftp.mplayerhq.hu/MPlayer/samples/V-codecs/MSS2/mss2_speech.wmv
MPC crashes when info & debug window is active.

[vortex_hl]

We need a sticky FAQ, which explains such things!
actually, i know assembly code, compiler differences, programming, ffdshow and lot more. My previous dump question's aim not a "which is best? or which one fit for my cpu?" thing. I actually want to ask about rev 313's new libavcodec_test.icproj project file.

Anyway if developers release any test/debug version of libavcodec.dll (compiled with icl 9.1), i want to test it.

And you are right we need a sticky FAQ.

[LoRd_MuldeR]

Here is the latest build: rev312 (http://prdownloads.sourceforge.net/ffdshow-tryout/ffdshow_rev312_20061002_clsid.exe?download)

I have managed to fix FLV4 decoding.

Works nice :thanks:

[Moitah]

I have managed to fix FLV4 decoding.
Great, thank you.

[foxyshadis]

actually, i know assembly code, compiler differences, programming, ffdshow and lot more. My previous dump question's aim not a "which is best? or which one fit for my cpu?" thing. I actually want to ask about rev 313's new libavcodec_test.icproj project file.

Anyway if developers release any test/debug version of libavcodec.dll (compiled with icl 9.1), i want to test it.

And you are right we need a sticky FAQ.

Deinterlacing and noise removal filters are what benefit the most, atm. As well as some random ones like Levels, Sharpen, Noise, Properties, Offset, etc, but those are very fast filters as it is; and then there's Perspecitive correction, but I don't know if anyone actually ever uses that.

[Egh]

Minor GUI bug:

now it seems that "Skip H264 deblocking on delay" text label is too big and overlaid on top of delay value edit box :)

Checked with the last 312 clsid build.

Also concerning installer: now installer offers to uninstall previous ffdshow, can it do it w/o deleting ffdshow registry settings? :)

Concerning previous bugfix (rev 296):
Is it bug or feature (c) that the messagebox appears only once? :P After a message shown and closed, I can put all kind of nonsense in the ffdshow AVS section but no error message would be shown later.

Also suggestion: if AVS exception is raised, then not only show the error message, but also automatically uncheck Avisynth section in the ffdshow.

[bob0r]

x264.nl
03-10-06: ffdshow tryout revision 312 (clsid) added, better general H.264 support.

Thanks, please let me know, in a Private Message or something, when a big update is done and i should update again.

The old ffdshow (with outdated libavcodec i assume) did not play any BBC HD H.264 mbaff, now ffdshow does.... too bad my CPU isn't 10GHz per core though. :o

[clsid]

Also concerning installer: now installer offers to uninstall previous ffdshow, can it do it w/o deleting ffdshow registry settings? :)It simply executes the uninstaller, which will remove everything, so it is not possible to keep the settings during uninstallation. If you want to keep the settings, then don't uninstall the other build, but instead just install on top of it. That should work fine, all files will be replaced. I will adapt the Inno uninstaller to also uninstall the other build when detected. Just to keep things clean.

[Egh]

It simply executes the uninstaller, which will remove everything, so it is not possible to keep the settings during uninstallation. If you want to keep the settings, then don't uninstall the other build, but instead just install on top of it. That should work fine, all files will be replaced.

A warning for the users during the first dialog would be handy :) (something like "if you uninstall, all your ffdshow registry settings are lost") ;)

[clsid]

But isn't that a natural thing to happen during an uninstall?

[bob0r]

Touché

[Egh]

But isn't that a natural thing to happen during an uninstall?

Depends. In some programs you can switch uninstall into advanced mode and leave registry settings as is.

[DSP8000]

clsid, can you please make ICL9 build of rev.312 or newer?
There is big difference in speed/performance when using filters.
With generic build I can barely watch videos, maybe 15FPS, but with ICL9 build the motion is fluid.
Filters used are:
1.kernel deinterlacer, th.10, sharp, two way
2.Blur & NR, denoise3d, l=2.0, c=2.0, time=4.0, HQ=on
3.Resize & Aspect, multiply by 1.000, Lanczos, luma sharpen=1.0, accurate rounding=on

The source is the same, TV Cap, interlaced, analog.
My test PC is P4 1.7 Williamette, 512 RAM.
Additional Info:
On my daughter's Athlon XP rev.312 generic MSVC build works very well.

Tnx. keep up the good work:)

DSP8000

[clsid]

I will tweak the message a bit.


Edit: rev318 (ICL9) (http://prdownloads.sourceforge.net/ffdshow-tryout/ffdshow_rev318_20061003_clsid_icl9.exe?download)

[DSP8000]

ICL9 build will be online in a moment
wow, that was quick responce, :) thank you.

[haruhiko_yamagata]

@clsid
Why does your installer try to uninstall older ffdshow?
NSIS installer delete inno uninstallers and related shortcuts(TODO registry shortcut), and that is enough in my opinion.
What is the merit of uninstalling ffdshow before install? If users clik yes by mistake they would lose all their settings. Normal users don't know there are three types of installers, they get confused.

[clsid]

Simply deleting the uninstaller is a bad practice. Specially if one installer has installed stuff (audx, runtimes) that isn't included in the other installer.

I now have included in the prompt that uninstalling will reset the ffdshow settings.

[Kostarum Rex Persia]

Can you try to use InnoSetup installer, instead of NSIS installer?

[clsid]

List of known issues in revision 326:

1) VC-1 does not work. ffdshow isn't even placed in the DirectShow graph. (reported by clsid)
2) VMnc crashes with "Integer devision by zero" exception. (reported by clsid)
3) Some SVQ3 files play with artifacts / color shifts / totally messed up picture. Same issues in FFplay. (reported by clsid, Peuj)
4) 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)
5) Output queue enabled + VMR9 renderless + RGB32 + specific video cards + pause = blackout problem
6) Wavpack decoder crashes on this file (http://rapidshare.de/files/34646550/SoC__XviD_WavPack_MP3_-007.mkv.html). (reported by clsid)
7) The following encoders are possibly broken: MPEG 4, MPEG 1, MPEG 2, h.263, H.261 and DV. (please confirm) (reported by clsid)
8) It seems there is no way to disable snow decoding in ffdshow. Also ffdshow crash when i try to play snow (encoded with latest mplayer/lavc). (reported by Yong)
9) mpc/ffdshow.ax crash when i try load the impulse file (???) with the Convolver audio filter. (reported by Yong)
10) Access Violation in ffdshow on Windows Vista. Details and solution (http://sourceforge.net/tracker/index.php?func=detail&aid=1567236&group_id=53761&atid=471489). (reported by Microsoft Windows Reliability team)
11) MSS2 WMV files: MPC crashes when info & debug window of ffdshow is active. Sample file (http://ftp.mplayerhq.hu/MPlayer/samples/V-codecs/MSS2/mss2_speech.wmv). (reported by drevil_xxl)
12) QPEL bugs and colour/block trains/displasement. Details (http://sourceforge.net/tracker/index.php?func=detail&aid=1568940&group_id=53761&atid=471489). (reported by drevil_xxl)
13) Avisynth error message is shown only once. After the message is shown and closed, I can put all kind of nonsense in the ffdshow AVS section but no error message would be shown later. Also suggestion: if AVS exception is raised, then not only show the error message, but also automatically uncheck Avisynth section in the ffdshow. (reported by Egh)
14) Loading IFO file in MPC and seeking thru the video instantly crashes MPC. Seeking thru VOB file is fine.(reported by DSP8000)
15) ICL9 builds of ffdshow.ax crash on files created by a specific (?) old revision of x264. Funny thing however is that the files play without crash if you first play a good file and then play a 'troublesome' file in the same player instance. Also no crash when using a plain unoptimized debug build. Sample file. (http://rapidshare.de/files/35447656/sample.mp4.html) (reported by clsid)

ToDo:

1) Fix known bugs (duh!)
2) 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)
3) Speaker setup page in InnoSetup installer
4) Update libavcodec vorbis
5) Update libavcodec SNOW encoder
6) Update libavcodec vp3
7) check if there are other ffmpeg parts that need updating
8) keyboard control feature request (http://forum.doom9.org/showthread.php?p=881108#post881108) by therealjoeblow.

[flanger216]

For whatever reason, the stream-switcher problem I reported has been resolved in the latest builds, so you can knock number 4 off the bug list :)

[Egh]

List of known issues in revision 319:
ToDo:


What about that message bug I reported a bit earlier? Also discovered additional bug with it: that message is shown on start-up of the video, if AVS script is checked :) It seems it get initialized before actual video arrives to it or something like that.

[haruhiko_yamagata]

Simply deleting the uninstaller is a bad practice. Specially if one installer has installed stuff (audx, runtimes) that isn't included in the other installer.

We don't have to delete audx nor runtimes. Your build can work with it. And NSIS uninstaller does not delete audx and runtimes, usually.

[TheShadowRunner]

Guys, what release can be considered as close as possible to "stable" nowadays?
(please don't tell me ffdshow-20051129.exe by milan! ^^)
I'm using Kurosu's 20060907 version but he announced he'll stop releasing binaries.
I guess the replacement would either come from Videomixer9, haruhiko_yamagata or CLSID but is there a consensus on a specific stable version?
I love reading ffdshow development yet i'm having a real tough time chosing between all those builds you guys release on a daily basis now.
Thanks.

TSR

[LoRd_MuldeR]

Guys, what release can be considered as close as possible to "stable" nowadays?
(please don't tell me ffdshow-20051129.exe by milan! ^^)
I'm using Kurosu's 20060907 version but he announced he'll stop releasing binaries.
I guess the replacement would either come from Videomixer9, haruhiko_yamagata or CLSID but is there a consensus on a specific stable version?
I love reading ffdshow development yet i'm having a real tough time chosing between all those builds you guys release on a daily basis now.
Thanks.

TSR

I think you should check out this one:
http://mirror01.x264.nl/x264/ffdshow_rev312_20061002_clsid.exe

[TheShadowRunner]

Thanks LoRd, i appreciate the advice!
I'll be sure to try it out and x264.nl is bookmarked too ;)
See you,

TSR

[Kostarum Rex Persia]

Can someone tell me what's command for ffdshow silent install? Thanks.

Or, can someone make a silent installer?

[LoRd_MuldeR]

Can someone tell me what's command for ffdshow silent install? Thanks.

Or, can someone make a silent installer?

You can make the NSIS installer silent by adding this line to the installer script:
SilentInstall silent

Or you take the NSIS installer as it is now and run it this way:
installer.exe /S


I got no idea about clsid's installer :o

[Kurtnoise]

Hi,

I have a request which could be usefull for some people I think : create different ffdshow packages instead of only one
A full package - as the current build.
An Audio package - only Audio decoders.
A Video package - only Video decoders.
A VFW package -

What do you think ? Imho personally I don't use all ffdshow stuff. So, it could be great...:)

[LoRd_MuldeR]

I don't think we need different builds.
The current installer is only ~3 MB and contains everything in one self-contained download.
If you don't need some features of ffdshow, then just keep those disabled ;)
The installer already allows the user to enable/disbale features during the setup procedure.
You can even check/uncheck all Audio/Video formats with one single click!
Same for VFW support. So I don't see the point...

[Kurtnoise]

The current installer is only ~3 MB and contains everything in one self-contained download.

If you don't need some features of ffdshow, then just keep those disabled ;)
That's the problem...what should I download more than 3MB whereas I need only ~ 500KB or less. Why not tuning the setup to download only the parts that we want ?

[JarrettH]

thanks for the ICL 9 builds again clsid

Seems to be lots of good fixes (removing the encoder!) and a few things I have may have encountered with seeking in videos.

This may or may not be a bug. I use the save to file... to save my presets when I reinstall ffdshow. For the third time now when I try to restore anything that has avisynth code in it it only saves the top line, sometimes only a portion of it. Try it yourself

[DSP8000]

It seems there is a bit of a bug with seeking videos.Loading IFO file in MPC and seeking thru the video instantly crashes MPC.
Seeking thru VOB file is fine.

[foxyshadis]

Hi,

I have a request which could be usefull for some people I think : create different ffdshow packages instead of only one
A full package - as the current build.
An Audio package - only Audio decoders.
A Video package - only Video decoders.
A VFW package -

What do you think ? Imho personally I don't use all ffdshow stuff. So, it could be great...:)
I'd support different packages, but more specialized packages - instead of all-in-ones, have "ffdshow-mpeg4-h264-mp3-aac" with a very stripped down filterset. Maybe a couple more codecs to round out the most common. And maybe one or two other build targets... maybe not. But anything other than common packages ought to be "compile your own" only.

Way down the line somewhere.

The audio/video/vfw aren't all that separate anyway; spliting them up would make each piece be about 3/4 the size of the whole, a rather bad tradeoff. Their configuration is going to be centralized soon anyway.

[deadfones]

I've experienced two system hard-locks (no bsod, computer just freezes with a short audio loop), both less than a second after seeking hi-res video in MPC 6.4.9.0. Both were while using ffdshow_rev236_20060923_clsid, the first happening a couple days after I installed it, though I can't say for certain that it was the cause. One was a large wmv, probably 640x480 wmv9, and the other was divx5 672x464. I can't reproduce it with the same clips, and I watch and seek lots of other hi-res video.

Before I take this to a windows troubleshooting forum, is there anything specific to seeking that could be causing this? Also, are there any differences between the generic and ICL builds that would be relevant here (the "hand optimized asm code", IIRC, comes to mind).

The system is only a month old, and the previous hard-lock happened 13 days ago, so I can't say for certain that it itself is rock solid, but in all other respects it is--just not when seeking video. It is certainly not vanilla: 2 nvidia cards powering 4 monitors on 3 year old hardware. One of the nice things about it is that I can run Process Explorer on a separate monitor and have it always visible. One of the peculiar things I noticed about both hard-locks is that kernel cpu usage spikes moreso than a usual seek right before the lockup. I took a picture this time to give you an idea. I'll give you a quick rundown of the components but I don't want to bore you with specifics. Any help would be appreciated.

cpu graph: (note that it's an HT cpu)
http://home.comcast.net/~deadfones/hard_lock-mpc_seek-cpu_graph-2006-10-04.jpg

System:

ASUS p4c800-e deluxe w/ latest non-beta 1023 bios revision
P4c 3.0ghz, ~36c w/ no load, no oc
4x corsair cmx512-3200c2, 1 is new/different with more aggressive spd timings but they're running at the older/less agressive spd timings, no oc, 10 memtest+ passes ok
Geforce4 ti4400 agp w/ passive zalman heatpipe HS ZM-80A HP (warm to the touch) and forceware 91.47 whql @ 1.5v no OC (2x 1600x1200)
QuadroFX 280 pci w/ stock passive HS (warmer to the touch) and forceware 91.47 whql (2x 1600x1200)
M-Audio revolution 7.1 w/ latest 1028 drivers
Intel INFs
xp pro sp2 fully patched, except for the new "audio instability bsod" patch ATT of hard-locks, though that is now patched


I'm now using ffdshow_rev312_20061002_clsid. If you want more info, or the full Process Explorer picture, I have that.

Thanks.

[clsid]

You can make the NSIS installer silent by adding this line to the installer script:
SilentInstall silent

Or you take the NSIS installer as it is now and run it this way:
installer.exe /S


I got no idea about clsid's installer :o
installer.exe /silent

Other options: /DIR="x:\dirname" /GROUP="folder name" /NOICONS /COMPONENTS="comma separated list of component names" /TASKS="comma separated list of task names"

[_xxl]

ffdshow crashes when decoding stereo 192kbps mp3 using AuD-X lib.
http://i12.tinypic.com/2u75b7q.jpg

[Isochroma]

Well, yesterday I had quite the adventure with DV encoding. Up to now I've been using the Pinnacle VFW DV codec for encoding DV AVIs using Vdub. Yesterday I tried the ffdshow VFW DV encoder and it produced much better results, significantly less JPEG-like compression artifacts.

However, when I played the DV file in mpc, it used the VFW decoder (AVI Decompressor) instead of the Microsoft "DV Video Decoder" filter. The VFW codec is terribly slow for playback (impossibly, I should say). I was horrified because just previous I'd uninstalled the Cedocida codec using the evil RadLight Filter Manager, which easily destroys chunks of the video filter system.

I assumed that I'd deleted the directshow dv decoder system, and it turns out parts had been removed. Quickly I typed into a commandline while uttering silent prayers to God:

regsvr32 /u qdv.dll
regsvr32 qdv.dll

However, the VFW DV playback continued. So I had the opportunity to test my new BartPE boot-CD based system wipe/restore from 1-week old backup. It worked like a charm!

But when I finally got back into windows, I was again horrified to see the same VFW codec being loaded by MPC. Finally it occurred to me that there was nothing wrong, so I played the previous Pinnacle-encoded DV AVI, and it used the DS filter.

After slapping myself repeatedly with a large trout, I checked the damned fourccs of the two files:

ffdshow encoded fourcc: DVSD
pinnacle encoded fourcc: dvsd

Having already checked the registry entries for the DS filter, I knew its input pin only accepts "dvsd". So the entire Directshow system is case sensitive! I quickly loaded up AbcAVI Tag Editor and rewrote the fourcc to "dvsd". Loaded into MPC, the DS filter shows as usual...

The VFW system is probably case-sensitive too, but people who edit DV usually load third-party DV codecs which allow both cases (ex. Pinnacle VFW DV codec).

In the ffdshow VFW encoder, a drop down selector exists for FOURCC selection. Its items include:

DVSD
DV25
DV50

The default is "DVSD". My request is to add a new type, "dvsd" and make it the default. This won't interfere with VFW decoders, but will allow the default MS directshow decoder to handle the playback of files made with this encoder.

[clsid]

I have changed to FourCC to lowercase dvsd.

ffdshow can play DVSD through DirectShow. Is there a specific reason why you want to use the MS decoder instead? Or is it just for compatibility reasons?

[Egh]

lol, despite VM9's previous comments, silenty new build appeared :approved:

http://prdownloads.sourceforge.net/ffdshow-tryout/ffdshow-tryouts-rev327.exe?download

Problem detected: upon attempt to register ffdshow during installation error: unable to register dll/ocx, loadlibrary failed, error 14001

No such error with clsid's 328 build. Most liekly the problem caused by VM9's switch to the unified installer, which is welcome per se :)