View Full Version : ffdshow tryouts project: Discussion & Development
Atak_Snajpera
12th January 2008, 22:04
Does it work if you change the number of decoding threads in ffdshow options to 1?
Yes! If I change to 1 thread sample plays without problems. BTW I'm using Vista.
fastplayer
12th January 2008, 22:10
how about some AR buttons for easy access so I don't need to use the virtual keyboard on my PCHC to reach 1.85 ?
just 4 buttons : 1.33 / 1.78 / 1.85 / 2.35 :p
And I want my 1.25, 1.0, 0.75, 0.5 and 0.001 button... :rolleyes:
leeperry
12th January 2008, 23:01
your movies have weird AR sir :D
well, I can't reach 1.85 with the mouse, only 1.84 or 1.86.....I need to use the keyboard arrows to reach it :rolleyes:
if buttons are a no go, how about making it slow down if right button is pushed or sumthing ?
ACrowley
13th January 2008, 09:57
@Delerue
yes and cabac / reconstruction parallelism, the code decodes up to 128 macroblocks in one thread while doing prediction+idct+deblock of the previously decoded 128 blocks in another thread.
Since this Patch i can play all x264/H264 1080p totally smooth on my X2@5000
Its a huge Improvement imho. Both Cores are running with ~max 85% ( BluRay AVC)
Its faster then Cyberlink in Software Mode and not far from CoreAVC
Thats the latest Patch what im talking about. Before this Patch it was only "the one Slice per Thread" Solution
Keepitsimple
13th January 2008, 13:39
Perhaps time for next offficial beta release then?
ImAhNoBoDy
13th January 2008, 15:32
Anyone notice when you install ffdshow-rev1763_20080108_xxl Directshow filters does not work in Graphedit? When I try to get into the list it gives the error "DirectShow SDK Filter Graph Editor has stopped working."
I uninstalled ffdshow and I was able to get all the filters under Directshow Filters. I reinstalled graphedit and ffdshow, same issue. Not sure if it's a bug or not.
clsid
13th January 2008, 16:15
Perhaps you have an old version of GraphEdit? I have never had such problems with GE build 061102.
ImAhNoBoDy
13th January 2008, 18:41
I have Graphedit DirectX 10.0 - Build: 060822. I think that's the most recent version I could find. But when I look at your build, your's look more recent. When did yours come out?
clsid
13th January 2008, 19:22
I don't remember where I got it. Maybe the latest DirectX SDK. Windows SDK 6.0 contains build 061030.
ImAhNoBoDy
13th January 2008, 19:39
After searching the forums for a while I found this http://forum.doom9.org/showthread.php?t=104234
It's Build 061030. Still the same issue. If I uninstall FFDShow, the filters under Directshow filter will show up without a problem. The last version I had of FFDShow was around September and thought I'll upgrade but now Graphedit crashes when I try to pull up directshow filters. I can pull up any other filters just fine except directshow filters. Not sure what else to do.
clsid
13th January 2008, 21:12
GE 061030 also works fine for me.
Do you have Vista? If so, see if disabling UAC makes a difference.
ImAhNoBoDy
13th January 2008, 22:23
Yes I do have Vista. UAC has been turned off from day one =). I only think it's this verison of FFDShow considering it was working with the September release. Which version of FFDShow are you using? Are you using yours or xxl's? Whatever version you have I'll uninstall mines and install the one you have and see if I have the same problem.
clsid
13th January 2008, 23:12
I am using my own builds.
There is a huge archive of (old) builds on the sourceforge website:
http://sourceforge.net/project/showfiles.php?group_id=173941&package_id=199416&release_id=436746
leeperry
14th January 2008, 01:00
the opposite would have been quite funny :D
I am using xxl's builds.
:eek:
Inventive Software
14th January 2008, 03:12
Nice joke leeperry! :D
I think I found a bug in ffdshow's MPEG-2 decoder.
*breathe*
MPEG-2 video in Matroska with the Aspect Ratio set doesn't display correctly in Media Player Classic 6.4.9.1 or WMP11 (the only 2 media players I have). I tried both libmpeg2 and libavcodec, both wouldn't give me a correct aspect ratio (though ffdshow's Info panel gives the correct SAR and DAR), and I have no idea whether it's the splitter (Haali Media Splitter) or the decoder because using MPC's internal MPEG-2 decoder it displays correctly.
AAAAAAAAAAAARRRRRRRRRRRRRRGGGGGGGGGGGGHHHHHHHHH!
*breathe calmly*
I cut a 30 second MKV sample that I'm uploading [CUT uploaded, link: http://rapidshare.com/files/83628092/Monzasplit-001.mkv]. The video in question is 352x576 anamorphic 4:3. This kinda defeats my posting this in a way, but if I set the AR manually in MPC, it displays correctly, but what's the point of having to set it manually when Matroska has the option and it works with every other freakin' video I've muxed so far?!
Can ya tell I'm just a bit highly strung? :D
iron2000
14th January 2008, 07:29
I have a question.
In Dscaler, ffdshow appears in the filters menu.
So does ffdshow work in Dscaler?
I played with the settings and one of it cause Dscaler to not show and UI.
Turning the filter on and off seem to not show any difference.
ImAhNoBoDy
14th January 2008, 09:11
Thanks clsid, I downloaded your most recent build ffdshow_rev1771_20080113_clsid.exe and the same thing happened. I downloaded ffdshow_rev1738_20080101_xxl.exe and directshow filters are showing without crashing. Keep up the good work you guys.
Delerue
14th January 2008, 11:14
Everytime I install a new build, the VC-1 codec change from 'libavcodec' to 'wmv9'. Is it normal?
haruhiko_yamagata
14th January 2008, 13:36
MPEG-2 video in Matroska with the Aspect Ratio set doesn't display correctly in Media Player Classic 6.4.9.1 or WMP11 (the only 2 media players I have). I tried both libmpeg2 and libavcodec, both wouldn't give me a correct aspect ratio (though ffdshow's Info panel gives the correct SAR and DAR), and I have no idea whether it's the splitter (Haali Media Splitter) or the decoder because using MPC's internal MPEG-2 decoder it displays correctly.
I can reproduce. The fix shouldn't be too hard.
Can ya tell I'm just a bit highly strung? :D
Nice report. :thanks:
haruhiko_yamagata
14th January 2008, 14:22
how about some AR buttons for easy access so I don't need to use the virtual keyboard on my PCHC to reach 1.85 ?
just 4 buttons : 1.33 / 1.78 / 1.85 / 2.35 :pI have a simple question, why do you have to specify aspect ratio manually?
clsid
14th January 2008, 15:08
Everytime I install a new build, the VC-1 codec change from 'libavcodec' to 'wmv9'. Is it normal?
I'll improve the installer to allow users to choose the VC-1 decoder.
leeperry
14th January 2008, 15:14
I have a simple question, why do you have to specify aspect ratio manually?
because several codecs can't achieve perfect AR, because it needs to be possible to divide the width and height by 16.
so for 2.40 HD movies, you would need to achieve 1280*533, but most ppl encode to 1280*528....which gives an AR of 2.42
same for 1.85 and SD movies, you would require 720*389 but they are encoded in 720*384....which gives an AR of 1.875
in KMPlayer my simple fix was to output from ffdshow without any AR, and then choose it in the player.
but with MPC, you only have a choice of 4:3 or 16/9
so my only option to get perfect AR is to "fix" it with ffdshow, and it's pretty annoying that you can't reach 1.85 with the mouse....only 1.84 or 1.86
I have to use the keyboard arrows to reach 1.85
and I believe I'm not the only guy in the world that wants to watch his movies with perfect AR :D
actually 6 buttons with the most common AR would be awesome.....alternatively, you could just give an option to set them to whatever the user wants.
1.33(4:3)
1.66(old movies or movies such as http://www.imdb.com/title/tt0107688/ )
1.78(16/9)
1.85(most DVD's use it)
2.35(cinemascope)
2.40(narrow cinemascope, used on HD discs mostly)
all possible cases are covered, if the AR is different, you can just check OAR(Original Aspect Ratio)
or if that's too much trouble, if you could make the AR selection slower if the right button is pushed or something, so 1.85 can be easily selected :cool:
Inventive Software
14th January 2008, 15:37
Narrowing the range of the AR slider might be a more practical option. Who has an AR of 5:1 (5.00) or 1:10 (0.10) these days anyway? :) Going from 0.1 to 3 would make things nicer I think. ;)
Thunderbolt8
14th January 2008, 15:39
1.85 is more common with US movies, while 1.78 and 1.66 are/were for europe or also asia. so its more a choice of studios or a cultural habit than the difference of being on dvd or HD. the change from 2.35 to 2.40 was made due to technical reasons (which ones I dont know though, just read that somewhere in a film study book)
Thunderbolt8
14th January 2008, 15:46
that VC-1 decoder choice implemented in the installing process was a really useful change. it was already getting a bit anoying to change to libavcodec each time manually after each new version.
thanks for that!
edit: can someone please explain what that kakaoke change for ass subs is?
SeeMoreDigital
14th January 2008, 16:03
I think I found a bug in ffdshow's MPEG-2 decoder.
*breathe*
MPEG-2 video in Matroska with the Aspect Ratio set doesn't display correctly in Media Player Classic 6.4.9.1 or WMP11 (the only 2 media players I have). I tried both libmpeg2 and libavcodec, both wouldn't give me a correct aspect ratio (though ffdshow's Info panel gives the correct SAR and DAR), and I have no idea whether it's the splitter (Haali Media Splitter) or the decoder because using MPC's internal MPEG-2 decoder it displays correctly. I have just tried doing the same using "ffdshow_rev1771_20080113_clsid.exe" and MediaPlayer Classic (with its internal Matroska selected).
For me, if I set FFdshow's "MPEG-2" decoder filter to "libavcodec", MPC is unable to connect to the decoder. However, if I set FFdshow's "MPEG in AVI" decoder filter to "libavcodec", MPC plays and displays the MPEG-2 video correctly.
Cheers
leeperry
14th January 2008, 16:10
Narrowing the range of the AR slider might be a more practical option. Who has an AR of 5:1 (5.00) or 1:10 (0.10) these days anyway? :) Going from 0.1 to 3 would make things nicer I think. ;)
indeed, good idea.
as long as 1.85 is easily reachable, that is ;)
LoRd_MuldeR
14th January 2008, 19:21
All recent builds have it, since the patch was committed to SVN.
Does that mean the "CABAC Multithreading" patch was committed to the ffmpeg/libavcodec SVN and will be included in recent MPlayer builds as well?
Or was the patch "only" committed to ffdshow's own SVN? Couldn't find any suitable entry on the ffmpeg/libavcodec SVN log...
clsid
14th January 2008, 21:03
It has not been committed to FFmpeg SVN. The patch is still experimental.
xxl has recently committed it to ffdshow SVN.
LoRd_MuldeR
15th January 2008, 00:05
It has not been committed to FFmpeg SVN. The patch is still experimental.
xxl has recently committed it to ffdshow SVN.
I see. thanks for clearing that up.
Yong
15th January 2008, 14:15
Audio filter bug: winamp2 filter
"click to select winamp 2 directoty..." button is not working, it doesnt pop up a windows and let me choose directory, when configure it offline.
it does work for me when im playing video/audio, but still, it doesnt show up the plugin(Signal processing studio DSP, yes i select winamp5 as dir, not the plugin dir)
_xxl
15th January 2008, 17:17
Can't compile ffvdub with MSVC2003.
Delerue
15th January 2008, 17:18
I'll improve the installer to allow users to choose the VC-1 decoder.
Thanks, man.
Inventive Software
15th January 2008, 19:46
@devs: Any news on the MPEG-2 decoder bug I reported a couple days ago?
foxyshadis
15th January 2008, 20:53
because several codecs can't achieve perfect AR, because it needs to be possible to divide the width and height by 16.
I'd think it would be less work if you watch things more than once to just set the AR of the file itself, via remuxing or mpeg4modifier, so you don't have to hassle with always setting ffdshow's.
SeeMoreDigital
15th January 2008, 22:57
because several codecs can't achieve perfect AR, because it needs to be possible to divide the width and height by 16. Well this is how I do it when generating anamorphic MPEG-4 encodes: -
http://forum.doom9.org/showthread.php?p=1034465#post1034465
leeperry
16th January 2008, 00:30
I'd think it would be less work if you watch things more than once to just set the AR of the file itself, via remuxing or mpeg4modifier, so you don't have to hassle with always setting ffdshow's.
well I'm not gonna remux my files when one click in ffdshow can fix the problem :D
anyhow, outputting without AR from ffdshow and setting in the AR in the player is even easier, because it seems that noone wants to make setting the AR(like 1.85) easier in ffdshow...I already asked for this feature a few years ago :(
and anyway MPC HC is a fantastic player, but it doesn't work fine at 48Hz(required for my videoprojector), it's giving a lot of judder and duplicated frames....everything's fine at 60 or 72.....and KMPlayer doesn't work with EVR w/o random freeezes on XP :mad:
so I'm trying Zoom Player atm because it also supports EVR......hopefully it will work fine at 48Hz and will let me choose the AR :)
Well this is how I do it when generating anamorphic MPEG-4 encodes: -
http://forum.doom9.org/showthread.php?p=1034465#post1034465
thanks for the tip!
but I'm already having a hard time getting this damn computer to output a good picture, so I can't be hassled with all the commandline arguments of x264 :D
some ppl really master the x264 encoding(who said ESIR? :D ) so I'll leave it to them :D
blizard
16th January 2008, 01:43
Could anybody explain what is the difference between CLSIDs Nightly build generic and ICL10? I have an Athlon X2 which should have support for MMX, SSE2, SSE3 and even x86-64 ;-) but I don't know which if those builds that would be the best for this CPU. From release notes I can not find out more then there is different compilers and some are said to be supporting SSE.
I dl CLSIDs generic build (r. 1771) and looks like it will use SSE, so what is the point with ICL10 build which is claimed to be for SSE? From what I can see it Mightly build looks stable, but is there any big difference from beta4a build which is called stable?
(On a side note: Thanks for your build CLSID and all other compilers for FFDSHOW tryout!)
foxyshadis
16th January 2008, 03:52
ICL is just a better compiler than MSVC, which usually translates into faster code that takes advantage of newer CPUs. This only makes any difference if you use filters that don't already have hand-optimizations (most of them), which are still better than compilers most of the time. It makes zero difference for decoding most formats.
fastplayer
16th January 2008, 10:58
I dl CLSIDs generic build (r. 1771) and looks like it will use SSE, so what is the point with ICL10 build which is claimed to be for SSE? From what I can see it Mightly build looks stable, but is there any big difference from beta4a build which is called stable?
All this has been asked and discussed a gazillion times. Search is your friend...
Anyway, in addition to what foxy said, read the FAQ:
http://ffdshow-tryout.sourceforge.net/html/en/faq.htm
Nightly builds sometimes break some existing feature(s) or add new features that are not working 100%. The devs are very fast fixing 'em though. So in the end, it does not matter which build you use.
clsid
16th January 2008, 13:44
The ICL builds require at least a SSE capable CPU. The generic builds only require MMX. However, ALL builds contain hand-written assembly code with SSE/SSE2/3dnow instructions, which will get used if and only if your CPU supports it.
The difference in builds only applies to the ffdshow.ax file. All builds use GCC for compiling libavcodec. So the decoding performance is EQUAL for all builds. The only situation where the ICL build might give a bit better performance is when you make use of the internal filters in ffdshow. And even then, there is only a gain for some of the filters.
haruhiko_yamagata
16th January 2008, 14:17
@Inventive Software, leeperry
Please be patient. We are receiving a lot of bug reports and requests.
leeperry
16th January 2008, 14:25
@Inventive Software, leeperry
Please be patient. We are receiving a lot of bug reports and requests.
Yeah sorry Haruhiko, I'm just really disappointed that MPC HC doesn't work properly at 48Hz....which is the most used refresh rate on videoprojectors.....because it outputs perfect 24FPS movies :(
:thanks: for all your help, and your great great work :)
if you could make selecting 1.85 AR easier by making the AR slider range shorter, that'd be totally awesome! :p
blizard
16th January 2008, 14:59
The ICL builds require at least a SSE capable CPU. The generic builds only require MMX. However, ALL builds contain hand-written assembly code with SSE/SSE2/3dnow instructions, which will get used if and only if your CPU supports it.
The difference in builds only applies to the ffdshow.ax file. All builds use GCC for compiling libavcodec. So the decoding performance is EQUAL for all builds. The only situation where the ICL build might give a bit better performance is when you make use of the internal filters in ffdshow. And even then, there is only a gain for some of the filters.
Thanks CLSID, fastplayer and foxyshadis for your explanation. I did see that page you linked to before I posted, fastplayer, but I am not a compiler so it is not easy to understand all choices in type of compiles and what those will mean for end user. Searching for an answer is not an easy task when some threads are around 100 pages and search will only point to first thread and not where in those thread there is an actual search term to be found.
fastplayer
16th January 2008, 15:07
Searching for an answer is not an easy task when some threads are around 100 pages and search will only point to first thread and not where in those thread there is an actual search term to be found.
Ever heard of google.com? :p
Add "site:doom9.org" as a search parameter plus what you want to actually search for on the D9 forums.
You want to search for "ffdshow ICL generic difference" for example. Here's what you get:
http://www.google.com/search?hl=en&q=ffdshow+ICL+generic+difference+site%3Adoom9.org
fastplayer
16th January 2008, 15:12
@clsid:
Your 1787 build is Unicode-only now? No Win98 support anymore, right?
cc979
16th January 2008, 15:45
rev.1787 i get some errors when compiling with normal gcc-4.0.4:
gcc -c -mno-cygwin -mdll -fno-rtti -mthreads -pipe -D_WINGDI_ -DUCLIBCPP -D_GLIBCPP_HAVE_MBSTATE_T -D_WIN32_IE=0x0500 -DARCH_IS_IA32 -DARCH_IS_32BIT -DHAVE_MMX -mmmx -w -DNDEBUG -UDEBUG -DFFDEBUG=0 -I. -I.. -Iuclibc++ -Ibaseclasses -I../baseclasses -IimgFilters -I../imgFilters -Implayer -I../mplayer -Isettings -I../settings -Isettings/filters -I../settings/filters -Icodecs -I../codecs -Isubtitles -I../subtitles -Iconvert -I../convert -Idialog -I../dialog -IaudioFilters -I../audioFilters -Icygwin -I../cygwin -Iffmpeg -I../ffmpeg -Iacm -I../acm -Ifilters -I../filters -Imuxers -I../muxers -I/dx/Include -L/dx/MingLib -ldx9 -O2 -march=pentium-mmx -mtune=i686 -fomit-frame-pointer -finline-functions -finline -frename-registers -fweb -funit-at-a-time -MMD -o ffdshow_all.o ffdshow_all.cpp
TffdshowBase.cpp:47: error: specialization of 'Tinterface* TffdshowBase::getBaseInterface() [with Tinterface = IffdshowBaseA]' after instantiation
TffdshowDec.cpp:36: error: specialization of 'Tinterface* TffdshowDec::getDecInterface() [with Tinterface = IffdshowDecA]' after instantiation
TffDecoder.cpp: In member function 'virtual void TffdshowDecVideo::getChapters()':
TffDecoder.cpp:1848: error: cannot convert 'char_t*' to 'const wchar_t*' for argument '1' to 'int wcscmp(const wchar_t*, const wchar_t*)'
TffDecoder.cpp:1849: error: cannot convert 'char_t*' to 'const wchar_t*' for argument '1' to 'int wcscmp(const wchar_t*, const wchar_t*)'
TffDecoder.cpp:1850: error: cannot convert 'char_t*' to 'const wchar_t*' for argument '1' to 'int wcscmp(const wchar_t*, const wchar_t*)'
TffDecoder.cpp:1851: error: cannot convert 'char_t*' to 'const wchar_t*' for argument '1' to 'int wcscmp(const wchar_t*, const wchar_t*)'
TffDecoder.cpp:1852: error: cannot convert 'char_t*' to 'const wchar_t*' for argument '1' to 'int wcscmp(const wchar_t*, const wchar_t*)'
TffDecoder.cpp:1873: error: no matching function for call to 'IAMExtendedSeeking::GetMarkerName(int&, char_t**)'
D:/msys/1.0/dx/Include/qnetwork.h:258: note: candidates are: virtual long int IAMExtendedSeeking::GetMarkerName(long int, OLECHAR**)
TffDecoder.cpp:1883: error: cannot convert 'char_t*' to 'OLECHAR*' for argument '1' to 'void SysFreeString(OLECHAR*)'
TffDecoder.cpp: In member function 'virtual long int TffdshowDecVideo::GetMarkerName(long int, OLECHAR**)':
TffDecoder.cpp:1960: error: cannot convert 'char_t*' to 'OLECHAR*' in assignment
TffDecoder.cpp:1961: error: no matching function for call to 'strcpy(OLECHAR*&, const char_t*&)'
d:/mingw/bin/../lib/gcc/i686-pc-mingw32/4.0.4/../../../../include/string.h:45: note: candidates are: char* strcpy(char*, const char*)
char_t.h:45: note: wchar_t* strcpy(wchar_t*, const wchar_t*)
make: *** [ffdshow_all.o] Error 1
haruhiko_yamagata
16th January 2008, 16:34
rev.1787 i get some errors when compiling with normal gcc-4.0.4:
I asked albain to fix this.
fastplayer, clsid had to give up ANSI build because of these compilation errors.
Inventive Software
16th January 2008, 16:34
98 support was dropped towards the end of 2007. :search:
clsid
16th January 2008, 16:57
98 support was dropped towards the end of 2007. :search:
And was restored quickly thereafter.
My unicode only build is temporarily until the compilation errors for the ANSI build are fixed.
vBulletin® v3.8.11, Copyright ©2000-2026, vBulletin Solutions Inc.