ffdshow tryouts project: Discussion & Development

[flanger216]

This has been bugging me for a while:

If you use libavcodec to decode MP3s, and you have 16, 24, 32 and 32-bit floating-point enabled as outputs, then ffdshow outputs 16-bit. If you deselect 16, 24 and 32-bit integer as output formats, then libavcodec outputs to 32-bit floating-point. So in the latter case, is libavcodec truly decoding to 32-bit floating-point, or is it still decoding to 16-bit and then merely padding the output to 32-bit floating point?

This also applies to AC3, DTS, Vorbis and all the other lossy (bitdepth-less) codecs that libavcodec can handle.

I only ask because libac3, libdts and libmad all seem to output to the highest bit-depth available, whereas libavcodec seems to prefer using the lowest available.

[leeperry]

I re-read that link and I see what your saying. I normally don't use gabset for mp3 playback (I usually use foobar) :)
the mp3 decoder in foobar is very unforgiving IMHO, the sound is just flat flat flat...I'll take libmad(Gabest or ffdshow) anyday over foobar for mp3.
plus you can't process VST/winamp plugins in 32 float, it's 16 integer or nothing....which also sounds ugly :o
leeperry: no I have never been able to get menus working with HR. The three bugs I talk about in my post above are all related to ffdshow and can be fixed within it I am sure. The crash I see is, as haruhiko_yamagata says due to the way ffdshow with yadif works, and only seen in dvd menus where single frames are found. Because so many of my dvd's are badly marked as originating from progressive/interlaced sources I can say this yadif crash is something that will effect other users.
I've never been too lucky w/ YADIF...in non-double framerate mode anyway(my AVS script can't affort 50fps :D )...it looks very ugly, like some drastic posterizing on PAL 576i?

Gabest's MPEG2 decoder in auto mode looks way better, and yet it doesn't blend fields...I think :o

[haruhiko_yamagata]

Oh definitely usable but consistently wrong for every DVD I have... Its not just a few pixels off really you can see in the screen shots
If you are talking about
http://img511.imageshack.us/img511/4188/comparison2ux2.th.png (http://img511.imageshack.us/my.php?image=comparison2ux2.png)
It's just rendering quality.
The code is written in mmx, I know it's wrong, but it's a bit hard to fix.

[B.F.]

Deblocking filter doesn't work in AviSynth and VirtualDub filters.

And can you do a checkbox in the Postprocessing page like "always postprocess" ?
It will be nice to use postprocessing filters even with a codecs like h264 sometimes.

[mark0077]

If you are talking about
http://img511.imageshack.us/img511/4188/comparison2ux2.th.png (http://img511.imageshack.us/my.php?image=comparison2ux2.png)
It's just rendering quality.
The code is written in mmx, I know it's wrong, but it's a bit hard to fix.

Thanks for letting me know the issue anyways. Any further ideas on my other problem, ie crashes in one frame areas when using external decoder or is that too tricky to work around?

[haruhiko_yamagata]

Thanks for letting me know the issue anyways. Any further ideas on my other problem, ie crashes in one frame areas when using external decoder or is that too tricky to work around?
What do you mean by "crash"? Is it memory access violation?

[mark0077]

Sorry i should say freeze. In the images above, if I use mpc-hc as the mpeg2 decoder, the menu looks perfect, but if I highlight one option, all is ok, but if I move the mouse up to another option, nothing happens. Media player classic still responds but no new frames are drawn so it appears as if the software has frozen. Its like ffdshow won't draw any subsequent frames when I highlight different options. This makes many dvds unusable without navigating through the player titles until the right one is found to start the movie.

MPC used on its own without ffdshow at all is ok, I can move the mouse around between options in the menu and no freezes. With ffdshow in the chain (but not decoding), I can only highlight one menu option, after that, no more screen updates happen and I will need to restart mpc to get back to a usable state.

[iron2000]

There are the edge-enhancement and denoise sliders in CCC, do they just work or need there be some ATI codec?
Or does it work only in DXVA? I'm confused of the video card's roles in playing my videos.
Don't seem to see a difference with those compared to the sharpen filter in ffdshow.

[roozhou]

Hi, I have a question on ffdshow's deinterlacing filters.
When I use deinterlacer from DScaler in ffdshow, it always doubles the framerate. IIRC some of DScaler deinterlacers run in adaptive mode, that is doubling framerate at high-motion scene and weaving at low-motion scene. I also checked the DS_Deinterlace.h and there is

// Deinterlace functions return true if the overlay is ready to be displayed.
typedef BOOL (__cdecl DEINTERLACE_FUNC)(TDeinterlaceInfo *Info);


But ffdshow just ignores the return value and shows the frame always. Does ffdshow have some limitation on adaptive deinterlacing?

[Konrad Klar]

If I change state of video codecs WMV1/7, WMV 2/8, WMV 3/9 to "disabled" MPC and MPC-HC crash when opening .wmv file.
This happens since rev2715, both in 32bit and 64bit version and for all .wmv files I have tested. WindowsMediaPlayer is not affected.
rev2698 and earlier are free from this problem (both 32bit and 64bit).
Example crash info:
Nazwa zdarzenia problemu: APPCRASH
Nazwa aplikacji: mplayerc32.exe
Wersja aplikacji: 1.2.1004.0
Sygnatura czasowa aplikacji: 49a1f286
Nazwa modułu z błędem: libmplayer.dll
Wersja modułu z błędem: 0.0.0.0
Sygnatura czasowa modułu z błędem: 499c05b2
Kod wyjątku: c0000005
Przesunięcie wyjątku: 00066cd5
Wersja systemu operacyjnego: 6.0.6001.2.1.0.256.1
Identyfikator ustawień regionalnych: 1045
Dodatkowe informacje 1: fd00
Dodatkowe informacje 2: ea6f5fe8924aaa756324d57f87834160
Dodatkowe informacje 3: fd00
Dodatkowe informacje 4: ea6f5fe8924aaa756324d57f87834160


I'm on:
Vista Ultimate x64 SP1 (polish).

[clsid]

No such problem here with rev2732.

[mark0077]

Guys is there a problem with ffdshows aspect ratio correction / handling code.

I just played some old star trek episodes from DVD today and noticed they were getting squished by ffdshow.

My solution to getting it back to normal was setting "No aspect ratio correction" on. That seemed to fix that. But playing another disk later in the day I found now that was stretched to fill the screen... The solution to this was to set ffdshow output option "Set pixel aspect ratio in output media type" to off.

My settings now that work for evrything I have thrown at it are

Resize - Aspect Ratio - "No aspect ratio correction"
Output - "Set pixel aspect ratio in output media type" - "Off"
MPC-HC - "Video Frame" - "Keep aspect ratio"

I am happy with this now but I am wondering theoretically shouldn't the finished aspect ratio be correct in all situations.... with the AR flag being sent around the place shouldn't mpc-hc sort my aspect ratio out no matter what ffdshow does. I am thinking of other users in the future, with ffdshows default settings for me not working for all of my video types. Would be nice to see the ratio looking correct in all settings, with the player doing any final aspect ratio correct if needed based on correct flags being sent around.

EDIT: Damn, found another 4:3 clip that gets stretched to 16:9 in this combination... Can't find a combination of these 4 settings that just gives me the right aspect ratio.

[LSudlow]

2732 - I can't enable the overlay control. Is anyone else seeing this? It's never been a problem in previous builds.

[haruhiko_yamagata]

Guys is there a problem with ffdshows aspect ratio correction / handling code.

I just played some old star trek episodes from DVD today and noticed they were getting squished by ffdshow.

My solution to getting it back to normal was setting "No aspect ratio correction" on. That seemed to fix that. But playing another disk later in the day I found now that was stretched to fill the screen... The solution to this was to set ffdshow output option "Set pixel aspect ratio in output media type" to off.

My settings now that work for evrything I have thrown at it are

Resize - Aspect Ratio - "No aspect ratio correction"
Output - "Set pixel aspect ratio in output media type" - "Off"
MPC-HC - "Video Frame" - "Keep aspect ratio"

I am happy with this now but I am wondering theoretically shouldn't the finished aspect ratio be correct in all situations.... with the AR flag being sent around the place shouldn't mpc-hc sort my aspect ratio out no matter what ffdshow does. I am thinking of other users in the future, with ffdshows default settings for me not working for all of my video types. Would be nice to see the ratio looking correct in all settings, with the player doing any final aspect ratio correct if needed based on correct flags being sent around.

EDIT: Damn, found another 4:3 clip that gets stretched to 16:9 in this combination... Can't find a combination of these 4 settings that just gives me the right aspect ratio.
Does this start at rev 2718? If yes, I may have to revert it.

[haruhiko_yamagata]

2732 - I can't enable the overlay control. Is anyone else seeing this? It's never been a problem in previous builds.
Thanks for quick feed back. I have fixed at rev 2733.

[mark0077]

Does this start at rev 2718? If yes, I may have to revert it.

I will get an older version when I get home to test. I can't find a combination that works in all types of video I play so it may have caused the problem I see. Will confirm in a few hours.

[ikarad]

I see a bug with ffdshow-mT.
In some blu-ray there is some bugs of decompression (or decoding)

screenshot here
http://nsa05.casimages.com/img/2009/02/18/mini_090218114945228794.jpg (http://www.casimages.com/img.php?i=090218114945228794.jpg)

sample here
http://www.zshare.net/info.html?55808118-1186c8d37659ccdc7c113ea973577df5

video captured by fraps to show this bug
http://www.zshare.net/info.html?55808947-2327e7dd24f9e7c0fc51bbeac433d69b

bugs appear between 1min40 and 1min45

- With ffdshow not MT, there isn't this bug.
- With H264 codec of MPC-HC there isn't this bug.
- If in ffdshow-Mt, I select 1 in the number of decoding threads (only 1 core used) there is no bug. If I select 2,3 or 4 there is the bug
http://nsa05.casimages.com/img/2009/02/18/mini_090218120751123616.jpg (http://www.casimages.com/img.php?i=090218120751123616.jpg)

I notice that this bug appear only with blu-rays at 29.970 fps but I am not very sure because I don't have many blu-rays to test (with blu-rays at 24fps, I have never seen this bug)

My config:
Q6600 (quad core), gtx280, xp sp3,ffdshow-mt2694 or 2733

up!
thanks

[~bT~]

^ which version of ffdshow??

[ikarad]

^ which version of ffdshow??

ffdshow-mT 2694

[STaRGaZeR]

The changes made in rev2720 are supposed to affect the release builds or just the debug builds? Being able to change some settings in real time was really useful and I didn't experience any crashes.

[~bT~]

ffdshow-mT 2694

an update overdue?

http://www.xvidvideo.ru/content/category/1/4/5/

[ikarad]

an update overdue?

http://www.xvidvideo.ru/content/category/1/4/5/

I try the last version 2733, and the same problem exists.

This problem exists since the first release of ffdshow-mt project.

https://sourceforge.net/tracker2/?func=detail&aid=2612226&group_id=173941&atid=867360

[Shakey_Jake33]

^On that note, what's the difference between the standard x64 build, and the one built using VS2008? It's presumably significant enough for XvidVideo to continue doing 2 separate builds.

[clsid]

We all use VS2008 for most files. So I think it is about libavcodec.dll. GCC is used for that by default. VS2008 builds of it will have much worse performance.

[clsid]

Someone reported to me that ffdshow crashes WMP and Vista Media Center when "raw video" is enabled. Can anyone confirm that with a recent build? I am typing this on a XP box.

[yesgrey]

@clsid,
What happened to your ffdshow changelog link? Now the changelog does not appear...

[clsid]

I have changed it back. Does anyone know if it is possible to show only the last X log entries through the web interface?

[yesgrey]

I have changed it back.
Thanks.

[Leak]

I have changed it back. Does anyone know if it is possible to show only the last X log entries through the web interface?
I'm afraid not; as far as I have groked the ViewVC docs you *can* configure it to split the log into pages of a user-set size, but it will always read the whole log anyway and only return what's on the page you requested, so if you're trying to keep the server load down that's not going to work.

I suppose you could make a static page that shows, say, the last 100 log entries by setting up a post-commit hook (if that's possible on SourceForge) that runs a "svn log" command, pretties the result up a bit and writes that into said static file...

[Jeremy Duncan]

Playng the ntsc movie ' Blade Trinity' , and using float32 on the input and output. The first screen of the movie and after that would have a loud noisy snow sound that was very loud and you could not hear the movie.

I wonder if checking the float32 input and output works on some ntsc movies but not on others like blade trinity?

[rickardk]

Someone reported to me that ffdshow crashes WMP and Vista Media Center when "raw video" is enabled. Can anyone confirm that with a recent build? I am typing this on a XP box.

Confirmed. It does crash both WMP and VMC under Vista.
Also WMP11 on XP.

[dandy]

I still can't get ffdshow working in a push mode graph with ms mpegdemultiplexer

yes - I belong to this DVB crowd - sorry

MPEG 2 broadcasts -> libmpeg2 works fine (THANKS FOR THAT), libvacodec connects ok but no picture
H264 broadcasts (BBC HD / ITV HD) -> libvacodec and ffmpeg-mt connect ok but for both no picture

thanks

[albain]

Confirmed. It does crash both WMP and VMC under Vista.
Also WMP11 on XP.

Hi,

this means that I didn't fix the bug completely (or at all)
Haruhiko identified it on the colorspace from the input decoder that was not copied back into FFDShow colorspace converter.

I thought this was fixed because I had no more crash until I tried recent builds on another machine.

I will have a look at this

Damien

[B.F.]

Hi.
Any chance to someone fix not working postprocessing filter in ffdshow virtual dub and avisynth plugins?

[albain]

Confirmed. It does crash both WMP and VMC under Vista.
Also WMP11 on XP.

Hi rickardk,

crashes should not occur on Windows XP WMP11, because I don't use the compatible codec feature.
The regression appeared on Vista and and in XP but only with Media Center, not media player.

Do you confirm the crashes on this OS with WMP11 too ?

Thanks

Regards
Damien BT

[Leak]

Hi.
Any chance to someone fix not working postprocessing filter in ffdshow virtual dub and avisynth plugins?
How? Those filters depend on having the quantizer values for each macroblock, which only works if ffdshow is doing the actual decoding...

[rickardk]

Hi rickardk,

crashes should not occur on Windows XP WMP11, because I don't use the compatible codec feature.
The regression appeared on Vista and and in XP but only with Media Center, not media player.

Do you confirm the crashes on this OS with WMP11 too ?

Thanks

Regards
Damien BT

Maybe ffdshow is not to blame. But WMP11 under XP does crash using CoreAVC (v1.9) with latest build 2719 of ffdshow.
It does not crash using an earlier version of ffdshow (like ffdshow ~b2100).

[albain]

Maybe ffdshow is not to blame. But WMP11 under XP does crash using CoreAVC (v1.9) with latest build 2719 of ffdshow.
It does not crash using an earlier version of ffdshow (like ffdshow ~b2100).

I am pretty convinced that FFDShow is in fault, but that may be another bug...

[albain]

I think I have fixed the crash problem (revision 2735).

It seems that when an alternate codec is used (so FFDShow receives uncompressed stream), the output colorspace is not set (= 0) which makes it crash on ocsps.sort(pictOut.csp) (Tffdecoder.cpp:298).

Haruhiko, maybe you have a clue on this ?

EDIT : nice tool dbgview by the way, I was actually writing traces to a file which was not practical at all

Damien

[turbojet]

libavcodec and wmv9 can't decode this 1080i VC-1 clip (http://www.sendspace.com/file/s07gpn) or any of the other 6 1080i VC-1 clips from 300 (USA BD). Latest cyberlink handles it ok.

[Kurtnoise]

iirc, lavc doesn't support vc-1 interlaced streams...

[B.F.]

How? Those filters depend on having the quantizer values for each macroblock, which only works if ffdshow is doing the actual decoding...
I worked before, on any source. :confused:
Maybe some fake quantizer value helps?

[avivahl]

Small question... I've installed ffdshow_rev2738_20090303.exe (from XvidVideo.ru) on a clean Vista x86 SP1 machine.
I used defaults in the installation.
Then, I went to the Mixer part of the Audio Configuration and noticed that Normalize Matrix is OFF by default.
When pressing the Reset button, it was turn ON.

So... my question is what is/should be the default value for the Normalize Matrix? ON or OFF?

[avivahl]

And a new bug I've noticed that has to do with the Presets of the Video Configuration.
I use ffdshow to show Subtitles and always have 2 presets:
1st- Default. Subtitles are on.
2nd- Called "NoSubs". Subtitles are off. Automatically loaded when SubtitleWorkshop.exe is using ffdshow.

My steps to setting up everything:
- Install ffdshow.
- Configure "default" preset.
- Create new preset from "default" (it sets the new preset name to be "default1").
- Rename "default1" to be called "NoSubs" and configure it to be autoloaded w/ SubtitleWorkshop.
- Turn subtitles off in "NoSubs.

Everything seemed to be fine w/ the new revision, but when I restarted ffdshow it had 3 presets: "default", "default1", and "NoSubs"!
Any try to delete "default1" removes it from the list... but when I restart ffdshow it shows back up!

The bug: ffdshow fails to correctly delete presets and creates a new one when a preset is renamed.

Avi Vahl.

EDIT: If I manually delete HKEY_CURRENT_USER\Software\GNU\ffdshow\default1, this preset won't show up again... (until the next time I'll create/rename a preset?)

[haruhiko_yamagata]

I think I have fixed the crash problem (revision 2735).

It seems that when an alternate codec is used (so FFDShow receives uncompressed stream), the output colorspace is not set (= 0) which makes it crash on ocsps.sort(pictOut.csp) (Tffdecoder.cpp:298).

Haruhiko, maybe you have a clue on this ?

EDIT : nice tool dbgview by the way, I was actually writing traces to a file which was not practical at all

DamienpictOut.csp must be set correctly. Revision 2735 just avoids crashing there. Hope you can fix this.

[Jeremy Duncan]

that audio problem i had with float 32 went away when i changed it for 32 bit integer.
I'm using version 2734

[haruhiko_yamagata]

And a new bug I've noticed that has to do with the Presets of the Video Configuration.
I use ffdshow to show Subtitles and always have 2 presets:
1st- Default. Subtitles are on.
2nd- Called "NoSubs". Subtitles are off. Automatically loaded when SubtitleWorkshop.exe is using ffdshow.

My steps to setting up everything:
- Install ffdshow.
- Configure "default" preset.
- Create new preset from "default" (it sets the new preset name to be "default1").
- Rename "default1" to be called "NoSubs" and configure it to be autoloaded w/ SubtitleWorkshop.
- Turn subtitles off in "NoSubs.

Everything seemed to be fine w/ the new revision, but when I restarted ffdshow it had 3 presets: "default", "default1", and "NoSubs"!
Any try to delete "default1" removes it from the list... but when I restart ffdshow it shows back up!

The bug: ffdshow fails to correctly delete presets and creates a new one when a preset is renamed.

Avi Vahl.

EDIT: If I manually delete HKEY_CURRENT_USER\Software\GNU\ffdshow\default1, this preset won't show up again... (until the next time I'll create/rename a preset?)
Probably I have added this bug recently. I'll take a look.

[Superlanboy]

Probably I have added this bug recently. I'll take a look.

Yeah I got this bug as well. Only way to get rid of those other presets was by deleting their corresponding registry keys.

[Inventive Software]

Any recommendations as to whether ffdshow-tryouts is ready for a beta 7? There's been a LOT of big changes recently, both in ffmpeg and ffdshow-tryouts that could warrant a new beta.

[clsid]

There are a few regressions that must be fixed first. It is not yet the right moment for a new beta.