View Full Version : ffdshow development
oddball
12th March 2003, 18:09
Any news on progress of this? It seems to have been a long time since there was any news on the devlopment of this filter. Things like playback of DiVX5.03 content (Mentioned by me in an earlier thread) and a working libmpeg2 implementation appear to have been put on hold. Also noted the test version of ffdshow that appears to crash for everybody.
Any news?
athos
12th March 2003, 21:29
i havent heard from milan for several months.
latest cvs commit for ffdshow was 2003-02-18 17:00 and for ffvfw 2003-02-11 06:41, i just checked both.
Chibi Jasmin
13th March 2003, 14:32
Can you get a working binary out of the latest ffdshow?
athos
13th March 2003, 15:31
well, i havent been able to, but if anyone succeeds, please let me know how.
kilg0r3
13th March 2003, 15:52
Isn't there any way to contact milan. I do not mean to press him to work on the filter. It would just be nice to know, whether everything is allright. It always feels strange when people disappear from the net just like that.
In any case, if ffdshow were not developed any further, it would be also nice to know which playback filter will realize the simple idct, that is necessary for proper playback of xvid files.
Sirber
13th March 2003, 22:06
Milan can be contacted here:
cutka(a)szm.sk
kilg0r3
14th March 2003, 09:55
Who will? I don't think that there is any point in flooding him with mail.
Gazza
28th March 2003, 03:04
Does anyone know if ffdshow development is still alive & well?
milan
28th March 2003, 10:00
I'm not working much on ffdshow currently. There are two development branches now: one for experiments (currently almost completely broken) and one "stable" where I'd like to make just bugfixes and then release it. However I'm now working mostly on ffvfw.
kilg0r3
28th March 2003, 10:12
hi milan, glad to hear all's well.
For ffdshow, imo, the most important thing is to make sure simple idct works so as to correctly decode xvid qpel. i understood that the qpel smearing, was due to some bug or incompatibility in this area. so, it would be really great of you, if you could have a look at this.
Thank you very much!
milan
28th March 2003, 10:23
Well, I'm not sure what could I do with that. It's related to libavcodec and XviD libraries and I'm not developer of any of them. But be sure I'll try to do something. The fact is I'm not using qpel for encoding yet, so I wasn't aware of this problem.
oddball
28th March 2003, 12:01
What about MPEG decoding? That is still broken. Would be nice if that worked. Also DiVX5.03 has issues with smudging. Probably a similar issue to the Xvid one.
Still..
sysKin
28th March 2003, 12:03
Originally posted by milan
It's related to libavcodec and XviD libraries and I'm not developer of any of them. But be sure I'll try to do something. The fact is I'm not using qpel for encoding yet, so I wasn't aware of this problem. It's actually very simple: please please pretty please, just make a working build with newest libavcodec :)
There were two problems 'working' together: one was a bug in libavcodec (mpeg4 standard got changed to be constent with.. reference software, yet libavcodec was not aware of the change) and there was a different problem on xvid side - our idct's imprecision was somehow amplified by quarterpel filter.
We are currently switching to 'simple' idct (can be easly selected form current ffdshow config). Libavcodec had its bug corrected somewhere in the middle of January (if I remember correctly).
All we need is this new libavcodec :)
Thanks,
Radek
milan
28th March 2003, 12:08
@oddball
I'll try.
@sysKin
Ok, this weekend I'll spend stabilizing ffdshow and next week there will be new alpha build. Not yet stable release, problems similar to that pointed by oddball should be fixed first.
kilg0r3
28th March 2003, 14:08
Thank you very much. All the best to you
Gazza
29th March 2003, 11:37
Hi Milan, good to hear from you again. Good also to hear that another update to ffdshow can be expected at some time in the future.
Considering that you are more involved with ffvfw at this time, I will have to also divert some time to see what it is all about.
Gazza
Owen
30th March 2003, 16:30
Milan,
I just want to thank you for your great work on ffdshow.
This is now an indispensable tool for HTPC's.
I have been using the Resize filter (Bicubic) with Luma & Croma Sharpening and find the results to be outstandingly good.
I started a topic in AVSForum on this.
http://www.avsforum.com/avs-vb/showthread.php?threadid=234832
I thing Resize and Sharpen had been overlooked until I started this thread. But now people are on to it and are very happy with the improvement in quality it provides.
Is there anything that can be done to improve performance with the Resize/ Sharpen filter and the Gradual denoise filter.
This combination of filters is hard to get running without stuttering.
Thanks again, and I hope the see future releases of ffdshow soon.
Regards,
Owen
athos
18th April 2003, 20:17
Finally, I managed to make a working build of ffdshow. It seems I had managed to screw up DirectX 9 SDK :\
Anyway, ffdshow-20030418.exe was built from a fresh checkout of the CVS tree, V1 branch, which is supposed to be stable. Did some quick testing only.
Take note: the property page (config) will crash unless you have ffvfw installed. I think this is due to milan working on integrating these two projects (either that or i screwed something else up ;)). For this reason I will not put up this build on sourceforge.
You can download this build of ffdshow, as well as my latest build of ffvfw from http://athos.web1000.com/ffvfw.html. I am aware that some people are having trouble downloading from this site, so please feel free to help me out by mirroring this file. I will put up a build at sf.net when the ffvfw issue has been resolved.
Also note that sh0dan has compiled later builds of ffvfw, located at http://cultact-server.novi.dk/kpo/avisynth/avs_cvs.html and nitrogen has mirrors at http://homepages.pathfinder.gr/ffvfw and http://nitrogen.kicks-ass.net/ffvfw/. I only tested with my ffvfw-20030325 build, dont know what other ones work.
the changelog for ffdshow since 20030103:
2003-04-16 14:05 milan_cutka
getParamStr2, autoload preset by file extension,
IffProc::processRGB_2, working on resizing using IffProc
2003-04-15 10:05 milan_cutka
file helpGrab.txt was initially added on branch V1.
2003-04-15 10:05 milan_cutka
"ffvfw needed for JPEG" info
2003-04-15 09:21 milan_cutka
also look in ffdshow.ax folder for dynamic libraries
2003-04-15 09:20 milan_cutka
no message
2003-04-15 06:47 milan_cutka
quantStride
2003-04-14 08:50 milan_cutka
updated VC6 project
2003-04-14 06:50 milan_cutka
file aws_api.h was initially added on branch V1.
2003-04-14 06:50 milan_cutka
file aws.obj was initially added on branch V1.
2003-04-14 06:50 milan_cutka
file TimgFilterWarpsharp.h was initially added on branch V1.
2003-04-14 06:50 milan_cutka
file TimgFilterWarpsharp.cpp was initially added on branch V1.
2003-04-14 06:50 milan_cutka
file Cwarpsharp.cpp was initially added on branch V1.
2003-04-14 06:50 milan_cutka
file helpWarpsharp.txt was initially added on branch V1.
2003-04-14 06:50 milan_cutka
file Cwarpsharp.h was initially added on branch V1.
2003-04-14 06:50 milan_cutka
file warpsharp.html was initially added on branch V1.
2003-04-14 06:50 milan_cutka
aWarpSharp (binary only) by Marc FD, separated warpsharping
filters, updated libavcodec and libmpeg2, quantizer array for
libmpeg2 (inspired by mplayer), newver IffProc interface for ffvfw,
support for temporary (in memory) presets
2003-03-31 16:27 milan_cutka
no message
2003-03-31 16:24 milan_cutka
libpostproc 5-tap lowpass deinterlacer switch
2003-03-31 16:11 milan_cutka
edge bug workaround switch
2003-03-31 15:51 milan_cutka
no message
2003-03-31 14:14 milan_cutka
updated libavcodec, updated postproc
2003-03-31 06:46 milan_cutka
trying to simplify startup, updated libavcodec
2003-03-28 06:46 milan_cutka
IffProc3
2003-03-27 16:35 milan_cutka
va_end
2003-03-27 06:36 milan_cutka
libswscale version
2003-03-16 21:59 milan_cutka
no message
2003-03-13 09:35 milan_cutka
fixed tray icon menu preset selection
2003-03-13 08:54 milan_cutka
dlls moved to ffdshow.ax directory, xvid_malloc->pp_malloc in
libmplayer
2003-03-13 06:50 milan_cutka
updated libavcodec, libmplayer can be static or dynamic, fixed mpeg
decoding with libavcodec, quantizer display, updated swscaler, and
maybe more...
2003-02-18 17:00 milan_cutka
new macro in nsis 2 script
2003-02-18 16:37 milan_cutka
V1
2003-02-18 15:48 milan_cutka
removed read only checkbox from open file dialogs
2003-02-18 09:51 milan_cutka
V2 cleanup
2003-02-18 09:50 milan_cutka
V1 cleanup
2003-02-18 09:02 milan_cutka
optimized uncompressed YV12 input
2003-02-17 19:19 milan_cutka
xvid stride fix
2003-02-17 19:08 milan_cutka
V2
2003-02-17 18:32 milan_cutka
no message
2003-02-17 18:21 milan_cutka
no message
2003-02-17 18:18 milan_cutka
no message
2003-02-17 17:05 milan_cutka
faster YV12,I420 uncompressed input
2003-02-17 16:30 milan_cutka
moved bswap
2003-02-17 16:24 milan_cutka
updated libavcodec (more encoding code removed)
2003-02-17 15:28 milan_cutka
updated postproc and swscale
2003-02-17 13:59 milan_cutka
updated legal headers, removed 3 from classes names
2003-02-17 13:55 milan_cutka
V1 - stable branch
2003-02-17 13:45 milan_cutka
V1 - stable branch
2003-02-17 13:42 milan_cutka
V1 - stable branch
2003-02-17 13:39 milan_cutka
V1 - stable branch
2003-02-17 06:49 milan_cutka
no message
2003-02-13 14:35 milan_cutka
I'm not sure...
2003-02-12 14:20 milan_cutka
trying to get colorspaces work
2003-02-11 06:40 milan_cutka
no message
2003-02-05 15:02 milan_cutka
no message
2003-02-05 13:39 milan_cutka
better showMV, working on ...
2003-02-05 07:17 milan_cutka
can connect to mpeg2 decoder filters (cyberlink, intervideo),
working on colorspaces
2003-01-29 15:45 milan_cutka
no message
2003-01-28 15:58 milan_cutka
no message
2003-01-27 06:47 milan_cutka
no message
2003-01-24 15:46 milan_cutka
no message
2003-01-23 07:06 milan_cutka
no message
2003-01-22 17:19 milan_cutka
saving ffdshow settings to bytestream (no loading yet), alligned
alocator for lavc
2003-01-22 06:46 milan_cutka
ffdshow is partially working again
2003-01-21 15:09 milan_cutka
trellis quant not allowed for mjpeg
2003-01-21 06:40 milan_cutka
working on better support for multiple colorspaces 3 (not working
now)
2003-01-20 15:07 milan_cutka
virtual base destructor
2003-01-17 14:21 milan_cutka
working on better support for multiple colospaces 3 (ffdshow can't
be compiled right now)
2003-01-16 15:23 milan_cutka
no message
2003-01-16 07:01 milan_cutka
Twindow for TffdshowPage, DPRINTF from XviD, working on better
support for multiple colorspaces 2
2003-01-16 06:59 milan_cutka
no message
2003-01-15 15:01 milan_cutka
Twindow
2003-01-15 11:12 milan_cutka
Twindow
2003-01-15 11:11 milan_cutka
updated libavcodec, Twindow
2003-01-15 10:00 milan_cutka
removed #undef ARCH_X86 - was left from debugging
2003-01-07 15:48 milan_cutka
working on better support for multiple colorspaces
2003-01-07 09:26 milan_cutka
fixed vc6 compilation
2003-01-07 06:41 milan_cutka
updated libavcodec, preliminary avisynth scripts support, subtitles
font autosize
edit: link fixed
Doom9
18th April 2003, 21:15
@athos: the link either goes to a web1000 search site and one in 5 times I tried I ended up on a swedish site.
mwillberg
18th April 2003, 21:20
if you remove the last "." from the link it seems to work ok...
cult
18th April 2003, 21:23
same here :(
Swede
19th April 2003, 00:04
I've just put up a mirror of these 2 files at:
http://leffe.dnsalias.com/ffdshow-20030418.exe and
http://leffe.dnsalias.com/ffvfw-20030325.exe
Hope this helps.
Best
19th April 2003, 02:47
I still cant get MPEG1 and 2 playback to work:(
am I doing somthing wrong or is it stil broken?
bbq@KL
19th April 2003, 04:32
Oh yeah, even Avisynth is added to ffdshow now. Is it working or not?
Thank you.
kilg0r3
19th April 2003, 10:14
Oh yeah, even Avisynth is added to ffdshow now. Is it working or not?
How is it supposed to work?
Ok, just tried it. You can just enter the filters you want, and levae the clip position unspecified).
This could be a nice weapon agains the black locking issue, without having to modify the the stream during the encode. It was suspected that the phenomenon is caused by luma values which are invalid for TV display. If this is true, a simple 'limiter()' inserted in ffdshow should do the trick.
Very nice! THANK YOU MILAN!
kairen
19th April 2003, 10:16
i wasn't able to configure ffdshow on Win Xp
it give me an exception on ffdshow.ax,configure
thank you
kilg0r3
19th April 2003, 10:29
@kairen
Have you installed ffvfw? It is required.
kairen
19th April 2003, 10:43
yes, but it was the older version, i'll try the newer version
really thank you
kastro68
19th April 2003, 10:44
@Kilgor3
Do you know if the latest ffdshow solves some of the earlier qpel/b-frame smearing?
kilg0r3
19th April 2003, 11:57
@kastro68 My only sources of info are the doom9 forum and the changelog. sorry.
Didée
19th April 2003, 13:05
Doesn't work for me, grrr!
I had shodan's compile of ffvfw from 04-15 installed: "exception on ffdshow.ax,configure"
Re-installed ffvfw from 03-25: "exception on ffdshow.ax,configure"
I tried every mathematically possible mutation of de-installing, rebooting and re-installing ffvfw and ffdshow ...
:devil:
BUT, atm I'm sitting at my old Athlon-Classic machine. Could it be that ISSE extensions are required (compiler options?) ... ?
The good news is, that for the first time ever, the input pre-processing in ffvfw is working ;)
moko
19th April 2003, 14:21
Where did the divx3, ms mpeg-4 and mpeg-1/2 support gone in ffdshow? tried to check it in the decoding tab in ffvfw but it didn't help either.
sysKin
19th April 2003, 15:26
Hi,
I just wanted to confirm that smearing, which used to be visible when decoding XviDs with quarterpel enabled, is history.
Thanks!
unplugged
19th April 2003, 15:46
Originally posted by sysKin
I just wanted to confirm that smearing, which used to be visible when decoding XviDs with quarterpel enabled, is history.
Hmmm... not be too sure.
To me smearing hasn't gone, not even with quant. 2. :(
I'm using ffdshow-20030418 and ffvfw-20030415 and tested these with XviD videos made with the good uManiac's build 20030414 (in fact is an excellent :) build, one of my suspects is that ICL7 or ICLx with its "aggressive" optimizations is penalizing quality of Koepi's ones; maybe?).
But, I could strongly advise to download latest version of Envivio MPEG-4 player (www.envivio.com) v1.5, with this updated version latest XviD videos look perfect and even better decoded than internal xvid routine!! :D.
(previously converted from AVI to MP4 container with MP4creator.exe by MPEG4IP 0.9.8 tools)
Edit: love love love how well works now XviD ISO MPEG-4 compilance
I have performed videos using Qpel, chroma me, B frames, VHQ4 and with all the incredible stuff xvid has, and it compresses and looks damn good with MP4 player!!
Congratulations to all developers!
P.S.: waiting DivX 7.0 for a worth web comparison/review :D.
athos
19th April 2003, 16:32
Please note that this build works even without ffvfw installed, but not the config page. I think milan intends ffvfw and ffdshow to be independent, but like I wrote, he is working on making them able to work together. I probably checked out the CVS in the middle of his work. But at least we have a working build after 4 months ;)
There should be no need for SSE instructions, I compiled it with Code Generation: Blend in VC6 and -march=586 -Mcpu=686 in gcc, ie should work on all processors.
sysKin
19th April 2003, 16:44
Originally posted by unplugged
[B]Hmmm... not be too sure.
To me smearing hasn't gone, not even with quant. 2. :(
I'm using ffdshow-20030418 and ffvfw-20030415 and tested these with XviD videos made with the good uManiac's build 20030414 (in fact is an excellent :) build
Umaniac's builds use old 'xvid' iDCT which can't cope with qpel correctly. Set ffdshow's idct to 'xvid' and maybe it will halp, maybe not - that's why Koepi uses 'simple' idct in his builds, and xvid will only use 'simple' soon.
P.S.: waiting DivX 7.0 for a worth web comparison/review :D.Aaaagh you're being mean! ;) You are going to allow DXN to create and tweak their 'standard' as much as they want, and you'll compare it against poor XviD which has to stick to some old and ugly mpeg4? Mean mean mean ;PPPP
I could tweak mpeg4 a lot and improve compression with my bare hands ;P yet I won't because I can't create my own codec just like that. Anyway, what I mean is, it's reasonaby easy :) so please, compare xvid against other mpeg4 codecs :D
Radek
Koepi
19th April 2003, 17:18
Originally posted by unplugged
build, one of my suspects is that ICL7 or ICLx with its "aggressive" optimizations is penalizing quality of Koepi's ones; maybe?).
NO! no. no.
As I wrote on that particualar thread, those optimizations don't affect the quality at all.
EDIT: rant deleted. But PLEASE forgot what you read there. It's like I replied there, NO quality loss due to compiler optimizations.
Regards
Koepi
cdrips
19th April 2003, 22:07
I didn't know what to search for for this, so don't hurt me. I was just wondering if the 6/17 ffdshow will decode qpel or GMC. I know the alpha does, but not sure if it is just me or the old build which doesn't. Also, are there any filter like qpel or gmc that would mimic what these xvid options do?
Originally posted by Koepi
EDIT: rant deleted. But PLEASE forgot what you read there. It's like I replied there, NO quality loss due to compiler optimizations.
Regards
Koepi
:( :scared: :( Why do I always read a post after the rant has been deleted! Poor me I never get to read a good rant :(.
ummon
19th April 2003, 23:54
I have the same Problem as moko. With the 20030418 version of ffdshow I can only select the Codecs played by xvid.dll everything that should be played by libavcodec is not selectable. Has anybody an idea why this happens? The older versions of ffdshow don't show this problem.
I use Win98SE, DirectX 9.0a, ffvfw-20030325
iago
20th April 2003, 01:15
@athos,
Thanks a lot for the new build.
Btw, latest ffdshow-20030418 OSD doesn't report QPEL frames I guess. Or is there something that I miss?
esby
20th April 2003, 03:06
Mmm I'm getting the same problem as Moko,
All i can encode to with ffvfw is:
Theora, Mpeg1 & Mpeg2
It's like if choosing an encoder discard the possibility
of using a default encoder profile,
one allowing div3 etc.
esby
drebel
20th April 2003, 04:10
Btw, latest ffdshow-20030418 OSD doesn't report QPEL frames I guess. Or is there something that I miss?
Confirmed with more than 5 qpel clips.The clips were encoded with umaniac's 14.04.03.No smearing though...
HarryM
20th April 2003, 06:24
This ffdshow build use forced-using xvid.dll for decoding. Logically- it can't q-pel smearing no more.
It using (only) external xvid.dll for decoding!
Kyo
20th April 2003, 09:22
whis a clip encoded with custom matrix (andreas_78) and qpel+ 2bframes I get this "evil" problem :(
See This Pic (http://pwp.007mundo.com/kyo/andreas+ffds.jpg)
The problem is gone when I check the "Use XviD"
CruNcher
20th April 2003, 10:52
@Kyo
thats a known dequantization problem with some custom matrices and libavcodec the same happens with Trbarrys SoftMatrix try to lower the quant values a bit and it should work XviD as decoder has no problems with it but ffdshow doesn't like it wich one now is doing it right thats a good question anybody knows the matrix specs ?
http://forum.doom9.org/showthread.php?s=&threadid=50673
Could someone merge this with this (http://forum.doom9.org/showthread.php?s=&threadid=48511) ?
EDIT by Koepi: Ok, done ;) Happy easter everyone!
cweb
20th April 2003, 15:07
Has anyone yet tested ffvfw to make analog captures using huffy-yv12 or
even mpeg2, using Virtualdub+vcr, or using VirtualVCR?
I think I'll have a go at it.. :)
cweb
20th April 2003, 15:17
I tried it with mpeg2 - Virtualvcr wouldn't capture
and gave me this error:
could not render filter
Smart Tee-> Compression Codec -> Flow Meter
I did use the highest possible bitrate and force yv12, so that might have something to do with the error :)
Edit: Back in the ffvfw codec I lowered the mpeg2 bitrate to 1470, changed the setting to Interlaced, and disabled force YV12.
I'll next try again but with the highest bitrate and see what happens.
Edit2: I raised the mpeg2 bitrate. Moving the Virtualvcr window
during the capture was more difficult - I guess more processing
power is going to the codec.
Now how do I play these 'avi's? They don't seem to playback
at all.. I used the default mpeg FOURCC, should I have used
something else?
Edit3: I read the ffvfw webpage and it's clear now. Only XviD
playback is supported so far. Ok, it will be interesting when
mpeg1 or 2 playback is added.
Next I'll try Virtualdub+VCR.
Valky
20th April 2003, 16:01
And has ANYONE had any divx-codec or mpg1 decoded with this one..?
athos
20th April 2003, 16:03
Originally posted by ummon
I have the same Problem as moko. With the 20030418 version of ffdshow I can only select the Codecs played by xvid.dll everything that should be played by libavcodec is not selectable. Has anybody an idea why this happens? The older versions of ffdshow don't show this problem.
I use Win98SE, DirectX 9.0a, ffvfw-20030325
I just checked and for me it's the opposite! But i think this is because i dont currently have xvid installed ... ;)
Check to see that libavcodec.dll is in the ffdshow dir.
HarryM
20th April 2003, 16:22
Originally posted by athos
I just checked and for me it's the opposite! But i think this is because i dont currently have xvid installed ... ;)
Check to see that lobavcodec.dll is in the ffdshow dir.
libavcodec.dll, maybe?
This library I have in ffdshow dir, but only XviD, Div4, DivX5 is selectable. For decoding is using xvid.dll. I cant deactivate 'use xvid.dll for decoding', it is forced!
I have Win98SE.
iago
20th April 2003, 16:30
Originally posted by drebel
... No smearing though... Yep, qpel smearing indeed seems to have gone when decoding with the latest ffdshow, and that's great!
ECY
20th April 2003, 19:16
did anyone get ffdshow-20030418 running on Win98 ?
There seems to be a problem that ffdshow can't use the "libavcodec.dll" on Win9x/me
can someone confirm this ?
Gaia
20th April 2003, 19:31
Originally posted by ECY
did anyone get ffdshow-20030418 running on Win98 ?
There seems to be a problem that ffdshow can't use the "libavcodec.dll" on Win9x/me
can someone confirm this ?
Works great with Win98se! So somenthing else is wrong.
ECY
20th April 2003, 19:43
Originally posted by Gaia
Works great with Win98se! So somenthing else is wrong.
you're sure you're not using XVID to decode ?
cause i get it running using the xvid option but not with libavcodec.dll
drebel
20th April 2003, 19:54
This ffdshow build use forced-using xvid.dll for decoding. Logically- it can't q-pel smearing no more.
It using (only) external xvid.dll for decoding!
No probs in Win2ksp3.Decodes all mpeg4 material without any codecs installed.Only a reliable (not damaged ang new) version of Libavcodec.dll is needed
GMC use is being reported fine...
Gaia
20th April 2003, 20:30
Sorry i was wrong, this really seems to be strange OS problem because i am forced to use Xvid as well and yes i have Libavcodec.dll in ffdshow directory.
Mistar Muffin
20th April 2003, 22:44
It seems that Mplayer pprocessing is broken in this release. Is it just me? (Win XP Pro SP1, Athlon 1.4ghz)
ummon
20th April 2003, 23:20
I just checked, all files including libavcodec.dll seem to be installed right. I also uninstalled XviD only with the result that Huffyuv and Raw video remain the only formats ffdshow can decode.
Seeing the other people having the same problems with Win9x/ME too I think libavcodec decoding under these OSs is broken. :( Regarding that milan said that he is currently changing ffdshow's COM interfaces, so that ffdshow, ffvfw and ffdub can cooperate, (http://forum.doom9.org/showthread.php?s=&threadid=42710&perpage=20&pagenumber=10) I guess the problem has something to do with the changes and will be hopefully fixed soon.
Or did anyone see a better solution than waiting and hoping for the next alpha?
Blight
20th April 2003, 23:23
I hope milan is still reading this, I've found two somewhat severe bugs (that exist prior to this release and still exist in it):
1. Using FFDShow as a post-processor along with VMR9 in a format that contain an internal AR flag (MPEG1/MEPG2, maybe WMV) will break the AR control for that format.
2. When trying to open the VMR9 property dialog, it will throw off a Division by Zero exception.
oddball
20th April 2003, 23:40
Are the options to playback MPEG2 in ffdshow a no go? I tried it and all I get is a blank screen and a blank screen with occasional colored blocks if I enable libmpeg2 as well.
Just curious as to why the options are there if they do not work. Or do they? Am I missing something?
Rober2D2
21st April 2003, 04:14
Mmm I'm getting the same problem as Moko,
All i can encode to with ffvfw is:
Theora, Mpeg1 & Mpeg2
It's like if choosing an encoder discard the possibility
of using a default encoder profile,
one allowing div3 etc.
esby
I have tried Theora and Xvid with no problem, but was unable to encode any MPEG1 nor MPEG2
athos
21st April 2003, 11:45
I have looked around a bit in the ffdshow code to see if it would be easy to fix the ffvfw dependency. I will try to do it later today using a proper "debug" compile, but i feel a little uncomfortable even if i could fix it as i might just introduce new bugs. i'd rather see milan do it. from what i understand ffdshow is supposed to check to see if ffvfw is present, but right now it seems it assumes it.
Zarxrax
21st April 2003, 17:23
I was going to try the MakeAVIS utility, but when I run it I get an error "failed to initialize avisynth". Do you have to have Avisynth 2.5 or something?
athos
21st April 2003, 21:03
I made a new build today. As Web1000 seems very unreliable (I cant even get in myself now!) I have asked Swede to mirror this.
It is the same CVS checkout as the last build, since there have been no updates to the CVS since 20030416. Therefore libavcodec.dll, libmpeg2_ff.dll, libmplayer.dll and TomsMoComp_ff.dll are exacly the same, not recompiled.
This time I did use the flag /QaxW to let ICL use processor extension (MMX/MMX2/SSE) which might provide some speed increases for non-optimized filters. Most likely there be few or no noticable improvements from this. Also, the usage of these extensions are not required, so it should still work on older processors.
I also managed to get the config page working without ffvfw! However, this is done through a pretty ugly hack, it seems the problem was in a function that tries to load ffvfw.dll to see if it is present, and if so, returns "true", else "false". I simply changed it to always return "false". I think this will only affect the jpeg output of the Grab function, but there might be other bugs. You might want to wait for milan to do a proper fix for this bug.
To conclude: bugs in this release might be caused by me.
Edit: uploaded it to SourceForge (http://sourceforge.net/project/showfiles.php?group_id=53761&release_id=154364)
Gaia
21st April 2003, 21:31
Just a little note, if you're using Win98se/Me you're still forced to use Xvid decoding in this latest build.
Swede
21st April 2003, 21:41
Originally posted by athos
Edit: uploaded it to SourceForge (http://sourceforge.net/project/showfiles.php?group_id=53761&release_id=154364)
Ah, then you might not need my mirror but I'd put it there anyhow. http://athos.leffe.dnsalias.com/ is for your builds.
Animaniac
21st April 2003, 22:21
Is chroma level fixing going to be implemented again? I believe it was in a much older build, and I'd like to see it again. Luminance level fixing alone seems to cause a lot of image loss in bright sections of the video, and maybe chroma level fixing would fix that. I hate the white fuzz DirectShow filters cause. >.< Thanks and awesome work.
((( atom )))
22nd April 2003, 01:16
i still get smearing with ffdshow from 21.04.03 and simple idct using koepis build of 05.04.03 and ffvfw from 15.04.03.
does anybody know if the qpel-situation is solved under linux meanwhile? i personally don't use anything else for watching my movies and just for editing i don't care..
athos
22nd April 2003, 01:51
Update: I took a deeper look at the code, and I think I managed to do a better fix to the ffvfw problem, a fix which should allow ffvfw to be used if present. I have mailed my solution to milan. I also compiled using ICL7.1 which allows the compiler to create separate code for MMX, SSE and SSE2 and then choose at runtime which to use. There is also generic code for processor which have none of these. This should allow Pentium MMX/II/III and Athlon (with SSE) users to take whatever benefit this compiler can create. Previously it only created Pentium4 and generic code.
I screwed up when sending this file to sourceforge, so for now it is only available at http://athos.leffe.dnsalias.com
Good night everyone.
Edit: Up on sourceforge now.
Animaniac
22nd April 2003, 01:53
I'm not sure what to make of this, whether it is a bug or if is the correct behavoir. ffdshow seems to choose the YUY2 colorspace over YV12 colorspace even when video is encoded in YV12 (XviD). Is this what should expected? Thanks.
athos
22nd April 2003, 11:19
Good news: milan has fixed the Win98 vs libavcodec bug, will be in next release.
ECY
22nd April 2003, 13:01
wow that's great news.
hope it will be release soon
esby
22nd April 2003, 13:41
My problem with the config was gone with reinstalling ffvfw without theora & mpeg1/2 support.
But anyone experienced a '1 frame lag'
when using ffvfw as decoder.
Meaning it will put as first frame
the one it has somewhere in buffer. ( from last clip decoded)
and for the second the first that should be used, etc.?
(I noticed that with dvx5 decoding)
esby
MoonWalker
22nd April 2003, 14:16
Originally posted by Animaniac
I'm not sure what to make of this, whether it is a bug or if is the correct behavoir. ffdshow seems to choose the YUY2 colorspace over YV12 colorspace even when video is encoded in YV12 (XviD). Is this what should expected? Thanks.
Are you using DVobSub for subtitles?? If so, try changing the colorspace order at the config tab of DVobSub..
MoonWalker
sapient
22nd April 2003, 14:47
Hi,
The new version of ffdshow has all the codecs (except the last 2) greyed out. I have win98, and I haven't installed ffvfw, divx or xvid. All previous versions worked without any of those installed, making ffdshow all anyone needed if he only wanted to watch and not encode mpeg4 clips. Why the change?
sapient
Animaniac
22nd April 2003, 17:15
Originally posted by MoonWalker
Are you using DVobSub for subtitles?? If so, try changing the colorspace order at the config tab of DVobSub..
MoonWalker
Hm you were right, the order was backwards there, but it still chooses YUY2. I didn't think that it would affect the video when subtitles aren't present. I'm also using Tobais's SubTitDS. That filter seems to always load, could it be the problem?
Edit: Yeah, uninstalling that fixed it. DVobSub can handle OGMs on it's own now, so that's great. Thanks.
athos
22nd April 2003, 18:21
Originally posted by sapient
Hi,
The new version of ffdshow has all the codecs (except the last 2) greyed out. I have win98, and I haven't installed ffvfw, divx or xvid. All previous versions worked without any of those installed, making ffdshow all anyone needed if he only wanted to watch and not encode mpeg4 clips. Why the change?
sapient
If you read just a few posts up you will see that this is a known problem with ffdshow and win98, and it has been fixed and will be in the next release.
Alxemi
22nd April 2003, 22:00
Hi all
I´ve been reading the forum and i´m a little confused..
I use win98 and i know the libacodec bug, the question is
It´s because this bug i can´t change the IDCT (forced to Xvid)?
The Qpel improvement in xvid decoding is only active using Simple IDCT, is´nt it?
Thank you all, and especially to ffdshow/ffvfw developers
Alxemi
22nd April 2003, 22:14
I have mirrored ffdshow-20030422, maybe it helps somebody
http://alxemi.cjb.net//ffdshow-20030422.exe
CruNcher
23rd April 2003, 20:33
im useing the new ffdshow-20030422.exe and experienced a strange problem with an older XviD encode 0.9 release stable simple profile it only displays Grey no picture only Grey could somebody test his old 0.9 encodes ? viewing through xvid.dll unstable works fine but ffdshow fails
Edit: Ok got around the problem useing ffdshows autodetect feature thx Cult for the tip :)
athos
24th April 2003, 22:23
I put up a new build on SF:
fixed dll checking = ffvfw not required, libavcodec works under Win9x
Alxemi
24th April 2003, 23:06
Great News!
I confirm that libavcodec is fixed. Now I´ll make QPEL comparisons :o)
Thank you athos and all developers
gamr
25th April 2003, 03:41
divx5 decoding under win2k (with and without use xvid ticked) not working. divx 5.02 installed, when i untick all the divx's it plays fine again. was working with 20030418.
on a lighter note, xvid works well :)
Edit: fixed, autodetect had to be ticked (unticked it playing with xvid goodies)
TNM
25th April 2003, 08:21
Originally posted by athos
I put up a new build on SF:
fixed dll checking = ffvfw not required, libavcodec works under Win9x
I couldn't access sourceforge :( Is there any other place where I can get this new build ? Thanks :)
kilg0r3
25th April 2003, 13:11
I would really love to see adaptive postprocessing implemented into ffdshow. IMO this is about the only advantage the rv9 has over xvid and the like.
Adaptive PP would mean that the strength of PP is tied to the amount of compression applied to a frame, which is indicated by the quantizer. So there is no need for difficult calculations involving resolution, motion and bitrate.
It would have to take into account the difference between b-frames and p-frames because b-frames usually look better at higher quants (never understood why btw). This could be accomplished by a simple offset parameter.
I like the idea:)
milan
25th April 2003, 13:22
But this is already present in ffdshow. Quantizer array is passed to postprocessing routines (both mplayer and Nic's) and it's their responsibility to properly use it. mplayer postprocessing routines even handle the b frames differently.
However, the quantizers for whole frame are constant unless you use some adaptive quantization during encoding which AFAIK common in MPEG2 and available in XviD and ffvfw, but not widely used.
Or do you mean that more image processing routines (like sharpenning) should be controlled by quantizers?
kilg0r3
25th April 2003, 15:35
It is _very probable_ that I am just making a fool of my self again.
I always thought that the amount of PP applied to a frame depends only on the values entered in the config dialog. In this case a frame with mean quantizer 2 would have been post processed in the same way and to the same degree as a frame with a mean quant of say 8. If this is not the case, I should better shut up and start actually using and experimenting with PP.
I have not really used PP very much, but I remeber having strange problems with it. For example, instead of making blocks less visible, it caused them to flicker.
Does anybody know what's the difference between mplayer's and Nic's PP on the one hand and RealOne's on the other. IMHO the PP of R1 hides blocks much better than the other two. :confused:
milan
25th April 2003, 15:45
The "processing strength" slider on the postprocessing page controls how ffdshow modifies the quantizer array before passing it to postprocessing routines. This is primarly targeted for mplayer postprocessing routines, because Nic's postprocessing has X and Y threshold controls. Mplayer postprocessing routines have some other parameters (not exposed in GUI currently), but my tests showed, that it's not possible to fine control, for example, the deblocking using them.
I'm not using Real so I can't compare its postprocessing to ffdshow's.
kilg0r3
25th April 2003, 16:18
Thanks for the explanations. :)
Rober2D2
25th April 2003, 18:49
I have made some test with Xvid + BFrames + Packed bitstream.
ffdshow version: 21-04-2003
xvid: Koepi 05-04-2003
Packed bitstream problem seems to be semi-solved now. Frames are displayed in correct order when xvid library is used to decode.
It is not completely solved without xvid, as ffdshow already makes a mess with frames order. Anyway I noticed an improvement as it doesn't happen with every sequence containing b-frames (It seems that is solved for some cases only)
Valky
25th April 2003, 19:12
Hmm..this latest build very well with divx and xvid codecs. Mpeg1 doesn't still work.
But something weird is happening..how come all my encodings and other movies look so much better now? I mean I have some poorly made films with older divx 3.11 movies where I know there is lot of trash on some scenes. I was going to test these blur/soften -filters, but all the movies look better already..I dont say that this is a bad thing, but it's almost like there is already some luma soften used even without any post processing?
Also the default PP-strength is set to 256 by default instead of 100. Any reasons for that? And I also noticed that using soften or luma soften in blur/soften section they all need much higher values to do anything than previous ffdshow I had from 2002. They are working, but e.g. Luma soften in previous version began to blur too much at settings above 100, but now movies are still watchable at setting 1500.
So what was the ratio compared to previous version from last december?
My main concerns is however, why all movies so look good now? (I can't believe I am actually complaining about this) :)
It's like there is some heavy post processing hiding somewhere inside the software..
CavalloPazzo
26th April 2003, 10:02
What about internal XVID deblocking? As anyyone tested it?I've done a little test and I like it: it seems it only smooth where it's necessary. I've tried to reach the same results with nic PP changing the X and Y Thr. value, but without success. It smooth more and sometimes has more blocks.
Is it possible to include that algo?
Could it be possible to use, for example deblocking from Nic and deringing from mplayer? I'm asking this because I found Nic's method better for deblock, but too aggressive for deringing, and it's not possible to configure deeringing with Nic.
I know Milan is working on FFVFW, and I know feature request is probably very long, so thanks anyway for your great work.
Originally posted by kilg0r3
I have not really used PP very much, but I remeber having strange problems with it. For example, instead of making blocks less visible, it caused them to flicker.
I've had this too. I simply switched to Nic's instead. For anime I usually overpostprocess like a bitch cause it doesn't really matter anyway (not much detail to be lost), but mplayer's PP really coughs on that. The deblocking gives flickering blurred macroblock edges on seemingly random places, while Nic's just gives a smooth postprocessed picture. Btw milan, I love the AVISynth function, I now have a Conv3D in my ffdshow by default! :D
codecmax
28th April 2003, 18:04
OK guys, I managed to download ffdshow-20030424 and I am wondering if this is the best codec for playing video files now?
I am kind of confused over whether if there is a need for the FFVFW now or if there is another version in a few days time.
I like many others would like the best way to get the best video. So any help rendered is much appreciated. :D
Psych
28th April 2003, 20:18
Is it just me being stupid, or is that even when ffdshow is set for all raw video, it doenst come up in bplayer's filter list?
this is a real pain since for some reason all my mpeg's play upside down in here, and ffdshow's flip would be the solution...
is this a bug in bsplayer or ffdshow?
athos
28th April 2003, 20:34
Originally posted by codecmax
OK guys, I managed to download ffdshow-20030424 and I am wondering if this is the best codec for playing video files now?
I am kind of confused over whether if there is a need for the FFVFW now or if there is another version in a few days time.
I like many others would like the best way to get the best video. So any help rendered is much appreciated. :D
IMO ffdshow is the best decoder for mpeg-4 files. It is fast, has lots of options, postprocessing etc and it handles all mpeg-4 (divx345+xvid etc). ffvfw is _not_ needed with this latest release.
oddball
1st May 2003, 17:03
I'd like to see something changed in the way ffdshow does it's resize. Currently you can set it to resize if it meets a specific criteria, like being larger than 640x480 etc. The problem is that if you set this with widescreen sources it messes up the aspect ratio. To give an example.
Movie is 704x384. I wish to resize it to 640x while maintaining aspect ratio. Now I can manually set that using a resize option but I have to work it out and it's a pain. If resize is left at default of 640x480 the aspect will look wrong for this movie ratio.
What I would like to see is an extra resize option that does a resize on the horizontal that you can specify like 576x or 640x and ffdshow auto resizes the vertical resolution to maintain aspect ratio.
Am I making any sense here?
It would save me messing about all the time with resize settings.
Blight
2nd May 2003, 13:09
oddball:
There is a maintain AR setting in that resize dialog...
So, while you may resize a 320x160 to 640x480, it will in reality be resized to 640x320
oddball
3rd May 2003, 03:13
Ah. I didn't realise it had any effect on resize. I always wondered what that option was for thanks ;)
Still would love a better less CPU intensive way to do black borders at some point in the future ;)
Oh and the crop and zoom tool never seems to work the way I think it's gonna work. Lets say for instance you have a movie where some bozo encoded the black boarders. For widescreen TV output it's a pain the butt as it looks wrong on the TV. In DiVXG400 it has an option 'Cut sides to horizontally fill at least 100% of the screen'. Which works great without pulling any CPU load. It crops the black bars automagically top and bottom and spits it out on the overlay correctly.
In ffdshow if you crop it seems to pull the image up and down but not crop the bars in the way I expect. It's very fiddly indeed.
Chibi Jasmin
3rd May 2003, 16:47
Originally posted by oddball
Still would love a better less CPU intensive way to do black borders at some point in the future ;)
Like DivXG400 does it :-) My words...
kastro68
3rd May 2003, 19:12
I noticed that the postprocessing for the 24-4-2003 ffdshow is not as strong as that of the 3-1-2003 ffdshow.
Using the 24-4-2003 ffdshow with postprocessing all the way up and with a processing strenght of 512 I hardly notice any PP taking place unless Nic's PP is ticked.
I'm not complaining, I'm just wondering if it may be a bug, or if PP has been deliberately watered down.
Have a nice day.
simon.mittag
4th May 2003, 05:58
Originally posted by kilg0r3
How is it supposed to work?
Ok, just tried it. You can just enter the filters you want, and levae the clip position unspecified).
This could be a nice weapon agains the black locking issue, without having to modify the the stream during the encode. It was suspected that the phenomenon is caused by luma values which are invalid for TV display. If this is true, a simple 'limiter()' inserted in ffdshow should do the trick.
Very nice! THANK YOU MILAN!
avisynth in ffdshow works fine for built in avisynth commands for me, however it behaves erratic when I try to load a plugin.
scripts that otherwise work as avs files fail with "unexpected error"
I observed that once entering only the load plugin statement into the script, commencing and pausing playback to allow it to load, then entering a second line running the plugin command seems to work.
Are there some problems with dynamic binding of the dll at runtime?
Anybody else tried that so far? I had problems like that with AutoCrop and WarpSharp plugins for 2.5
simon.mittag
4th May 2003, 12:26
I can make the description a little more precise after further testing.
I actually CAN run the AutoCrop plugin when applying the filter to an already running movie clip, meaning entering the AutoCrop(1) statement into the ffdshow dialog at playback time and hitting apply produces a working crop.
What doesn't work is starting playback when that value is already configured in the ffdshow tab - it then throws exception when I hit play in zoomplayer. seems something goes wrong with the ffdshow avisynth source filter at startup time?
Milan, Glenn, any ideas? Since it runs afterwards it can't be that grave an issue?
regards,
Simon
This might have something to do with the dynamic loading of dlls, as this was the cause of the libavcodec problems and the ffvfw trouble.
simon.mittag
6th May 2003, 04:19
Milan told me he is currently working on the avisynth plugin loader for ffdshow and I hope he will post us his test results when he's finished.
int 21h
12th May 2003, 03:14
Any chance we'll see the new Sorenson additions to ffmpeg in ffdshow?
simon.mittag
12th May 2003, 03:44
I am not yet sure when any possible next release for ffdshow will be, we'll have to wait for Milan.
Blight
12th May 2003, 23:40
VP31 decoding from ffmpeg could be useful too, ther TrueMotion one kinda sucks. Also, there's quirks in the huffyuv decoder which merit a look-over.
rjamorim
14th May 2003, 19:10
Originally posted by int 21h
Any chance we'll see the new Sorenson additions to ffmpeg in ffdshow?
Isn't Sorenson limited to the MOV container - that doesn't use dshow for playback (uses QT instead)?
Or is there something I don't know? :confused:
Blight
14th May 2003, 19:50
Parhaps someone should write an MOV parser... there is one for QuickTime v2 that comes with windows, but I doubt it applies anymore.
I always thought "a codec is a codec - no matter which kind of container format you wrap around". I remember early MOV <=> AVI converters which quite blindly exchanged the surrounding containers; so it was indeed possible to have a video format in an AVI where no VfW codec or DirectShow filter existed for.
From this point of view, it is no problem to have Sorenson video in an AVI. No matter how hard it could become to play it back... :D Probably, I wouldn't mind if Sorenson would create some software for Windows PCs, just as cross-platformed as 3ivx. But I doubt that this would definitely be my first choice then: On a 1800 MHz P4 it was almost impossible to play back the "Matrix Reloaded Final Trailer", created in Sorenson 3 Pro at 1000x540 pixels.
I transcoded it to MPEG2 to watch it on TV instead... And this did not work using the QuickTime 2 DirectShow import filter in AviSynth: I had to try the QuickTime VFAPI plugin and the VFAPI import snippets for AviSynth, and even had to pull down the frame rate by 25 (ever seen a movie at 600 fps?).
gabest
20th May 2003, 17:37
Originally posted by Blight
Parhaps someone should write an MOV parser... there is one for QuickTime v2 that comes with windows, but I doubt it applies anymore. Actually, the parser should be still fine for any mov. A few weeks ago I started to write a qt video decoder using the sdk, but the decompressor calls always failed for the incoming "svq3" data. With other encoding types I had success (mainly with "all-keyframe" types), but not with this sorenson codec.
Originally posted by gabest
Actually, the parser should be still fine for any mov. A few weeks ago I started to write a qt video decoder using the sdk, but the decompressor calls always failed for the incoming "svq3" data. With other encoding types I had success (mainly with "all-keyframe" types), but not with this sorenson codec.
Well that's where a new ffdshow would come in handy :D.
Blight
20th May 2003, 23:06
I'm not sure that the QT parser from QTv2 is still working as Apple inserted a lot of other video stream support and may have restructured the format beyond backward compatibility, can't really tell for sure.
But if FFMPEG can decode the contnet, perhaps it's possible to do. As far as writing your own QT Decoder, I know that Sorenson have some sort of licensing deal with Apple that their codec won't be used outside of their own player. Perhaps that is why it doesn't decode for you, it detects that your program instance is not valid.
raistlin2k
21st May 2003, 10:55
Actually, you can use MPC for playing QT WITHOUT installing Quicktime player :)
And I added those QT - filters to Media Center 9, so you can play QT there as well without Quicktime installation!
Isn't this enough quicktime-support?
Raist
HughMagoo
22nd May 2003, 15:33
I need a little help. I've searched around, but found no hints. I'm using the latest alpha.
1) when using the Resize function in conjunction with VMR9 and quick pans or scene changes, I am seeing lots of tearing, like the picture is broken in a line from left to right.
I've tried setting D3D vsync on to see if that has any effect, and I have also tried different Nvidia Dets, as well as Omega drivers. Nothing seems to work. my refresh rate is 60Hz. I don't know what has changed recently, but I am sure I wasn't seeing this tearing before.
2) when using Raw Video processing, the Info screen in the ffdshow panel says output 25.0fps... for every file with different fps. is this usual?
3) I'm not exactly sure about what colorspaces I should accept for Raw Video Processing, and what colorspaces I should output to, in the ffdshow codecs panel. gf4ti4600 --> YV12 forced for both?
thanks for any help.
the MS QT parser only support QT v1 and v2
since Apple is up to QT6, that's fairly out-of-date
QT3 introduced compressed movie header
QT4 introduced vbr audio tracks
etc
the 3ivx Media Splitter handles more modern (simple) mov files, but only for mpeg-4 variants (ie not sorenson)
athos
23rd May 2003, 18:31
New build is up on SF. This time I skipped ICL7 and used the regular MSVC++6 compiler, as the builds since 2002-12-13 has caused Explorer to crash when building thumbnails for video files in thumbnail view. This one doesnt seem to do that, at least not yet. Please post your findings regarding stability and possible performance loss (or gain?).
kastro68
23rd May 2003, 19:07
@athos
Thanks. I'll give it a try
@gabest
are you the same person that wrote vobsub and Media player classic?
Do you know where I can go to post suggestions and bugs for MPC?
I like doom9. I actually get to meet and chat to the people that develop and maintain the software that I use. It's a bit like meeting a celebrity :)
athos
23rd May 2003, 19:10
Originally posted by kastro68
@gabest
are you the same person that wrote vobsub and Media player classic?
Do you know where I can go to post suggestions and bugs for MPC?
yes it is the same person, check out the MPC thread:
http://forum.doom9.org/showthread.php?s=&threadid=29798
Originally posted by kastro68
I like doom9. I actually get to meet and chat to the people that develop and maintain the software that I use. It's a bit like meeting a celebrity :)
indeed ;)
kastro68
23rd May 2003, 19:31
Hi,
I just tried the latest ffdshow, and it works fine with WMP 6.4 but it crashes Media player classic. I just gave it a reboot.
I'll try reinstall former ffdshow now and see if MPC still crashes.
I just reinstalled ffdshow-20030424.exe and both wmp and MPC work fine with this. I uninstalled it and installed ffdshow-20030523.exe again and MPC crashes. WMP works fine though
Can anyone confirm same problem? If not, I'll post more details.
gabest
23rd May 2003, 19:37
Looks fine to me. Running MPC v6450.
kastro68
23rd May 2003, 19:40
Oh. I was running MPC 6.4.4.2
Sorry gabest, I just checked your site yesterday and it still had the old version up. You must've updated MPC very very very recently :)
@Gabest: Are you pulling my leg? :) I just came back from your site. I guess you didn't update your MPC files yet. Any chance I can get a copy of MPC 6.4.5.0 early?
kastro68
23rd May 2003, 19:49
MPC 6.4.5.0 is up now
Thanks.
Feedback: I don't experience any problems with latest ffdshow and MPC6450
Defiler
23rd May 2003, 20:07
Does the new (kinda) double-precision IDCT support SSE2 extensions?
Defiler
23rd May 2003, 20:13
Also.. I (still) see negative numbers in the "CPU Usage" OSD sometimes.
kastro68
23rd May 2003, 21:34
Hi,
I think there may be a possible bug with ffdshow-20030523 while 'Luma Smoother' feature of 'Blur & NR' it causes both MPC6450 and WMP to crash. I haven't found anything wrong with any of the other 'Blur&NR' features...just the luma smoother.
Thanks
Edit: Chroma smoother causes MPC and WmP to crash too.
HarryM
24th May 2003, 05:54
23052003 dont works on win98SE (for me).
24042003 works fine.
athos
24th May 2003, 12:15
Originally posted by HarryM
23052003 dont works on win98SE (for me).
What error messages do you get?
HarryM
24th May 2003, 13:18
Originally posted by athos
What error messages do you get?
Freezes without error messages. ZoomPlayer and MPC dont work with ffdshow 23052003!
Interest- WMP6.4 works(?)
Maybe cause in VMR7 (VMR7 is default renderer for win9x, best choice for win9x) using. If I switch for VMR9 (in ZoomPlayer), all is O.K.
But VMR9 works forced only in YUY2 (for me), degrades slightly quality and consumes much more CPU power...
:(
HughMagoo
24th May 2003, 14:31
I noticed that the tearing that I was noticing with resize in ffdshow and VMR9 is only when using YV12 output. I have not noticed the tearing effect with YUY2 output. If I enable almost all the output colorspaces, ffdshow uses YUY2 in all cases I have seen so far. So perhaps that is the best for my system? GF4ti4600, running nView
limited testing so far, but 23052003 seems to be a big improvement over 24042003 on my system. I use ZoomPlayer, and have not experienced any problems so far with Overlay or VMR9 modes and the new ffdshow.
HarryM
24th May 2003, 16:37
Originally posted by HughMagoo
I noticed that the tearing that I was noticing with resize in ffdshow and VMR9 is only when using YV12 output. I have not noticed the tearing effect with YUY2 output. If I enable almost all the output colorspaces, ffdshow uses YUY2 in all cases I have seen so far. So perhaps that is the best for my system? GF4ti4600, running nView
limited testing so far, but 23052003 seems to be a big improvement over 24042003 on my system. I use ZoomPlayer, and have not experienced any problems so far with Overlay or VMR9 modes and the new ffdshow.
Yes, VMR9 is more 'compatible' (it seems to me), but often use YUY2 for output.
I prefer VMR7 personally.
If you use Win2k/XP, your default overlay renderer is VMR9.
If you use Win9x/Me, your default overlay renderer is (old, good) VMR7.
faxmactor
25th May 2003, 09:00
Originally posted by HarryM
23052003 dont works on win98SE (for me).
24042003 works fine.
I have Win98 SE Hungarian.
The last one working eas 20021223
I haven't been able to use ffdshow sine 20030103...
I was unable to use 20030423 as well. :(
(On WinXP, it worked well)
At last, ffdshow-20030523 works on my Win98!! :p
But now I see from your post, that it still has problems with Win9x... :(
Will this issue ever be solved? The developers must have aware of this problem for almost half a year now. When a new ffdshow build released, it is still like gambling that it works or not on Win9x. Since it is kind of "random" I can imagine that it is quite difficult to track this bug down, but it would be just about time :scared:
faxmactor
25th May 2003, 09:07
Ah, sorry everyone, now I see HarryM, you had crashes on Win98, not that general problem, that even prevented ffdshow to get registered in Windoze.
Blight
25th May 2003, 20:09
HarryM:
you're wrong there matey...
VMR7 only exists under WinXP, there is no way you can get it under any other OS. What you get is Overlay and not VMR7. On my GF4, VMR9 has better scaling than overlay (using the 30.82 drivers, the 4x.xx drivers are buggy and give either aliasing or a slightly blurred image).
BTW, While "Theora" is listed as a codec, VP31 AVI files won't decode using ffdshow.
HarryM
25th May 2003, 21:52
Originally posted by Blight
HarryM:
you're wrong there matey...
VMR7 only exists under WinXP, there is no way you can get it under any other OS. What you get is Overlay and not VMR7. On my GF4, VMR9 has better scaling than overlay (using the 30.82 drivers, the 4x.xx drivers are buggy and give either aliasing or a slightly blurred image).
BTW, While "Theora" is listed as a codec, VP31 AVI files won't decode using ffdshow.
Sorry, my mistake. I think, that
'Video Renderer' = 'VMR7' (direct YV12 decoding, I prefer this)
'Video Mixing Renderer 9' = 'VMR9'. (I don't like this, YUY2 decoding, much CPU power needed)
Sigmatador
25th May 2003, 23:37
@Milan
since the beginning there's a color bug with awarpsharp
Animaniac
26th May 2003, 13:41
Two things I noticed with the latest build:
-Turing Warpsharp on while the stream is play causes WMP to crash.
-Perspective correction now makes the colors all funky.
As far as performance in this build, I can't really tell, but by virtue of looking at the Info section of the filter properties, I would have to say it's slower on my (P4) system, since the frame rate seems to dip lower more frequently and the data in the Info pane refreshes at a lower frequency. With the older builds, explorer rarely crashed when generating thumbnails.
sysKin
26th May 2003, 15:22
Hi,
Just to mention that I have some stability problems with this latest ffdshow. It crashed once when I enabled postprocessing, once when I seeked, several times when I opened a file.
I can only say much about the last example: I could open some files, couldn't open others. All were xvids with bframes, with dx50 fourcc. It crashed because of access violation at some big unrolled mmx function.
Changing decoder from libavcodec or xvid allowed to open the file.
My cpu is athlon xp, I'm using w2k (with service pack) and DX 8.0. Video is geforce2mx400 running at detonators 44.03.
Thanks for excellent work!
Radek
PS. ah and also, this version is still unable to say "qpel" in OSD.
Defiler
27th May 2003, 08:25
If I enable the highest level of post-processing, then Nic's (default settings), with "Nic's first" selected, I get repeatable crashes when opening DivX / XviD files.
Also, the Chrominance filter under "Blur & NR" seems to crash quite rapidly.
Finally, I've been unable to get this new version to post-process raw video (from the Sonic Cineplayer DVD decoder). It claims that ffdshow denied the attempt to attach a pin. (Yes, I have raw video enabled.)
The third item could easily be something I am doing wrong, though.
sysKin
27th May 2003, 13:50
Originally posted by Defiler
If I enable the highest level of post-processing, then Nic's (default settings), with "Nic's first" selected, I get repeatable crashes when opening DivX / XviD files. You were faster, Defiler :))
Yes, I confirm: the crashes I was talking about are strictly related to chroma deringing using "Nic's" method (for me: first or not first, just enabled). As I said, it's access violation in the middle of mmx code.
Regards,
Radek
drebel
27th May 2003, 15:47
@Defiler
I had the same problem with April's version, thing which kept me away from using Cinemaster's video filter for a while.Good compatibility with Intervideo's filter (Platinum) serves me well ,for the time being .But due to my hardware limitations i can't enable more than one pp filter now.In a very strange way , TheaterTek was "lighter" than ZoomPlayer3 with ffdshow
Chrominance filter under "Blur & NR" seems to crash quite rapidly.
confirmed
Defiler
28th May 2003, 15:33
Is there any preliminary documentation for the Avisynth features of ffdshow? What I'm really interested in is being able to refer to the input ffdshow passes to Avisynth by name, so that I can use it with functions that require clip names.
For example:
blah=ffdshowSource()
AwesomeStuff(blah,bugs=0,good_acting=true)
Is this, or something like it, possible?
So far, I've only been able to use functions that do implicit last.
Edit: Also, I've been unable to make any functions that refer to the previous frame in the video. I take it this isn't supported?
Try this, for an example:
ScriptClip(last,"Subtitle(String(YDifferenceFromPrevious()))")
Doesn't work. It just reports one value, and never changes. (for me)
However, this example:
ScriptClip(last,"Subtitle(String(YDifferenceToNext()))")
Works properly, and continuously updates.
I suppose this makes sense. We can't keep a lot of raw video lying around in memory. Perhaps it could keep the last few frames when in Avisynth mode? That would make the Avisynth feature significantly more powerful, since many filters need to refer to the previous frame in order to make correct decisions about the next one.
Originally posted by Defiler
Is there any preliminary documentation for the Avisynth features of ffdshow? What I'm really interested in is being able to refer to the input ffdshow passes to Avisynth by name, so that I can use it with functions that require clip names.
For example:
blah=ffdshowSource()
AwesomeStuff(blah,bugs=0,good_acting=true)
Is this, or something like it, possible?
So far, I've only been able to use functions that do implicit last.
I think you can do that with something like:
input = nop()
Or anything else that doesn't do anything to your input. I'd have to check though.
Wilbert
28th May 2003, 15:50
Is there any preliminary documentation for the Avisynth features of ffdshow? What I'm really interested in is being able to refer to the input ffdshow passes to Avisynth by name, so that I can use it with functions that require clip names.
For example:
blah=ffdshowSource()
AwesomeStuff(blah,bugs=0,good_acting=true)
I'm probably misunderstanding you, but can you use ffdshowSource in an AviSynth script? How does AviSynth recognize the command ffdshowSource. Again, I'm probably just misunderstanding you.
Defiler
28th May 2003, 16:08
Originally posted by Wilbert
I'm probably misunderstanding you, but can you use ffdshowSource in an AviSynth script? How does AviSynth recognize the command ffdshowSource. Again, I'm probably just misunderstanding you. "ffdshowSource()" is a command I just made up, because I don't know the actual name for it. Heh.
You can't use ffdshow as the source for an external Avisynth script (..yet.. heh..) but you can execute Avisynth scripts on an ffdshow output stream, as post-processing.
Like this:
http://hellninjacommando.com/temp/ffdshow-avisynth.png
My question earlier is about whether you can refer to the input that Avisynth (inside ffdshow) gets from the ffdshow decoder by a clip name, or as an input function.
pandv
28th May 2003, 19:39
blah=ffdshowSource()
AwesomeStuff(blah,bugs=0,good_acting=true)
Is this, or something like it, possible?
So far, I've only been able to use functions that do implicit last.
I tested it with the last ffdshow version and this works:
myclip=last
myclip2=SwapUV(myclip)
myclip=GreyScale(myclip)
return myclip2
returns the clip swapped (and not greyscaled).
So, I supose the key is the first line:
myclip=last
pandv
Defiler
28th May 2003, 20:05
Cool. Good work.
Using the avisynth function of ffdshow, I wanted to apply deen to a clip if the framerate is smaller than 25. This function works perfect in a "normal" avisynth script:
LoadPlugin("F:\avisynth\deen.dll")
Function SmallFPS_Deen(clip)
{
clip = (Framerate(clip) <= 25.000) ? deen(clip,"a3d",1,10,12,3).Subtitle("active") : Subtitle(clip,"inactive")
Return clip
}
SmallFPS_Deen()
But in ffshow it always displays "active", so every video gets filtered by deen, which my system can't handle :). Is there some other way I can get this to work?
Defiler
29th May 2003, 04:01
Originally posted by Tri
Using the avisynth function of ffdshow, I wanted to apply deen to a clip if the framerate is smaller than 25. This function works perfect in a "normal" avisynth script:OK. This is really bizarre.
I'm using a 29.97fps file as a test, to see if I can figure out the problem you are having.
Function SmallFPS_Deen(clip)
{
clip = (Framerate(clip) <= 25.000) ? GreyScale(clip).Subtitle("active") : Subtitle(clip,"inactive")
Return clip
}
SmallFPS_Deen()This code displays "active" on the 29.97fps file (inappropriately), and makes it greyscale.
However, if I change the "25.000" to "15.000", the same video shows "inactive", and is in color. Maybe the framerate is being reported incorrectly?
So, I delete that script, and just do this:
Subtitle(String(Framerate()))
Guess what? It always reports 25.000, no matter the frame rate of the file I feed it. Even, hilariously, with a 120fps AVI file.
oddball
30th May 2003, 03:21
You know I mentioned about resize screwing up aspect ratios if you set it to resize anything above a certain specified size? And you know how you said that the option 'Maintain aspect ratio' would resolve it? Well it doesn't.
I have a 720x400 AVI and I wish to resize anything greater than 640x to 640x. You can set the resize amount. I set it to 640x480 which is fine if you have a 720x480 video size for instance. This resizes down correctly. However if you have a widescreen video like 720x400 it resizes it to 640x480 with black bars top and bottom. I could set it to 640x352 but if I do that and playback a 720x480 clip it would screw that up. The resize command does not work in the way expected.
So basically I want to see resize take into account the aspect ratio and resize accordingly. Using the last version of ffdshow and the maintain aspect option does not seem to work.
milan
2nd June 2003, 14:43
@Defiler
Fixed now.
milan
2nd June 2003, 14:44
@Defiler
Fixed now.
Everytime when ffdshow will be able to determine input video frame rate (and it can't do this always) it will pass it to avisynth.
Takuto
3rd June 2003, 18:23
Just found strange ZoomPlayer behavior with FFDShow from May 23 2003.
Zoom Player crashes every time, when it played DivX 3 content and minimized into taskbar. It happens only with this version FFDShow, only with DivX 3 and only in Zoom Player (tested also MPC and MP 6.4).
Maybe its bug of Zoom Player (btw I used v. 3.10 beta 1 standard), but with previous FFDShow builds all was OK.
Windows XP, DirectX 9.0.
Defiler
3rd June 2003, 18:35
Do you have Nic's post-processing enabled? If so, turn it off.
gabest
3rd June 2003, 18:36
milan: Would it be possible to output VIDEOINFOHEADER2 structures too? I ask this because now that the matroska file format supports aspect ratio in the container format, it would be needed to pass the VIDEOINFOHEADER2::dwPictAspectRatioX/dwPictAspectRatioY fields towards the renderer just like the frame-rate is passed already.
Takuto
3rd June 2003, 19:33
Defiler: no, Nic postprocessing is not enabled. When I tried to enable it player crashes immediately.
But when I disabled any postprocessing at all, crashes disappeared.
Maybe some memory leak with DivX 3 postprocessing?
Defiler
3rd June 2003, 21:57
Originally posted by gabest
milan: Would it be possible to output VIDEOINFOHEADER2 structures too? I ask this because now that the matroska file format supports aspect ratio in the container format, it would be needed to pass the VIDEOINFOHEADER2::dwPictAspectRatioX/dwPictAspectRatioY fields towards the renderer just like the frame-rate is passed already. Oh yes! That would make my month.
gabest
4th June 2003, 03:33
Forget what I asked... it's already there in ffdshow! :)
HughMagoo
4th June 2003, 06:02
milan: Would it be possible to output VIDEOINFOHEADER2 structures too? I ask this because now that the matroska file format supports aspect ratio in the container format, it would be needed to pass the VIDEOINFOHEADER2::dwPictAspectRatioX/dwPictAspectRatioY fields towards the renderer just like the frame-rate is passed already.
this would probably explain why DVD content passes its aspect ratio through ffdshow, even though you might be resizing to a resolution like 1040x960 in ffdshow, and are using the "no aspect ratio correction". If we could always tell matroska what aspect ratio the encode is, and have that pass through ffdshow, for proper resize in the player, that would be great.
as it is currently, with everything but DVD I have to manually choose aspect ratio if I want to use a fixed resize resolution in ffdshow.
Defiler
4th June 2003, 07:26
I misunderstood what you were asking for then. Heh.
Lobuz
4th June 2003, 13:05
I just want to present recent experiences of playing xvid with ffdshow.
First I must admit it's great efficiency and speed even in HD resolutions.
But one thing is still working poorly - that is packed bitstream. In connection with qpel and b-frames there appeare strange gray halo spots. It could be easyli observed at testing clip from matroska thread. Without qpel or B-frames it seems to be ok. Aha, and there is a stuttering during the playback of that clip ( even if cpu is at 50% of load ).
And I have a small request if could be possible to make an intermediate buffer after decoder and before renderers. Sometimes the CPU load jumps and there is desync so that buffer could help at these situations.
I have plenty of free RAM so it could be used to reduce any jerkyness.
Regards
Lobuz
milan
4th June 2003, 13:22
The aspect ratio is now just passed in the VIDEOINFOHEADER2 to overlay mixer. It doesn't influence ffdshow internal resizing and ffdshow internal resizing doesn't influence the VIDEOINFOHEADER2 aspect ratio. I'd like to change this in (near) future.
Packed bitstream with qpel and b-frames is a known problem. I'll check if some bugs workaround option could solve this.
@gabest
I tested your matroska demuxer yesterday after reading that ffdshow always reports 25 FPS. Would it be possible for you to set the AvgTimePerFrame field in VIDEOINFOHEADER or can matroska handle variable frame rate and this would be impossible?
ChristianHJW
4th June 2003, 14:01
Originally posted by milan @gabest
I tested your matroska demuxer yesterday after reading that ffdshow always reports 25 FPS. Would it be possible for you to set the AvgTimePerFrame field in VIDEOINFOHEADER or can matroska handle variable frame rate and this would be impossible?
Yes, matroska can have variable framerate in principal, but not in the VfW compatibility mode. All the codecs ffdshow can decode and that can be stored in matroska for the time being, thats DivX, XviD, MPEG4V1/2/3 and DivX3 are all VfW based, and thus have a fixed frame rate.
IIRC the framerate is also easily accessable, as in VfW mode we store the complete BITMAPINFOHEADER in the KaxCodecPrivateDate field of matroska ....
EDIT / Correction :
There is no framerate in BITMAPINFOHEADER i was told, so we had created a new element called KaxVideoFrameRate for that weeks ago, and the specs say that every CFR ( Constant Frame Rate ) codec should use/set this field accordingly, making it manadatory for VfW mode also ...
Blight
4th June 2003, 17:53
Milan:
Since FFDShow can decode theora content, can you make it accept the VP31 sub-type & fourcc?
And now that 3ivx released a QuickTime splitter, it would be very cool if sorenson could be decoded.
Also, there's some bugs in the MPlayer post-processing... It flickers the video. Very noticable with HDTV content. Also, the whole effect as a whole seems weakened compared to previous versions of FFDShow.
Defiler
4th June 2003, 18:46
Originally posted by Blight
And now that 3ivx released a QuickTime splitter, it would be very cool if sorenson could be decoded.Hehe. You just want to get out of working on the Quicktime features of Zoom Player. I know your plan.. :D
milan
5th June 2003, 11:40
Since FFDShow can decode theora content, can you make it accept the VP31 sub-type & fourcc?
Are you sure that VP31 content can be decoded using theora routines?
And now that 3ivx released a QuickTime splitter, it would be very cool if sorenson could be decoded.
I didn't know that. I'll download this splitter immediatelly and see what can I do to use libavcodec SVQ1/3 decoding routines.
milan
5th June 2003, 15:18
Current progress:
1) theora decoder used by ffdshow is unable to decode sample VP31 clip
2) after few hack I was able to decode sample Animatrix mov clip using ffdshow. There is still a lot of work to be done, but thanks to libavcodec developers maybe we will have an opensourced SVQ3 directshow decoder filter.
BTW is there some AAC directshow decode filter which could be used with 3ivx quicktime demuxer?
BoNz1
5th June 2003, 15:30
Originally posted by milan
BTW is there some AAC directshow decode filter which could be used with 3ivx quicktime demuxer?
Yes, there is, check out this one, http://forum.doom9.org/showthread.php?s=&threadid=53863
Blight
5th June 2003, 16:12
milan:
There's the open-sourced one from corecodec team and the 3ivx audio decoder also does AAC. I believe Ahead software (makers of nero) also have one, but I haven't really seen it.
slavickas
5th June 2003, 20:55
Originally posted by milan
Current progress:
1) theora decoder used by ffdshow is unable to decode sample VP31 clip
vp3 and theora are quite different, but ffmpeg have own vp3 decoder i think (i don't have linux currently) by Mike Melanson
btw http://kyoto.cool.ne.jp/vp3/ is faster version of vp3 (at least decoder)
unplugged
5th June 2003, 23:12
I just want report that with latest build 23/05 the DScaler deinterlace/filter support plug-in doesn't work well as did previously.
Certain DLLs (like TomsMoComp.DLL) crashes ffdshow and most deinterlace filters have some flipped color tonality (blue instead of red...).
Instead all ok with 24/04 build.
I'm using filters from DScaler beta 4.1.6 (great great project, but... damn! no full line recording... yet :( :x)
Sorry if I miss something said in regard of this, haven't red the whole thread.
P.S.: Which could be one good deinterlacer plug-in (hey! I'm for 50fps! :D) to view MPEG-x recorded F1 Grand Prixes? (mixed high/low-motion)
For now I'm satisfied with Greedy2Frame...
DScaler: for really fast action, i usually go for simple bob. it's the 'purest' deinterlacer.
Blight
7th June 2003, 21:19
here's a bug report...
Playing HDTV encoded XVID content (1920x800) with Nic's Post Processing active would crash FFDShow when trying to release the filter. No issues at 1280x720, so I'm guessing the 1920 width may be an issue.
Animaniac
8th June 2003, 05:51
Bug for XviD clips:
OSD always shows I for Frame Type
OSD cannot determine Frame Mean Quantization
simon.mittag
9th June 2003, 12:20
Milan,
about the new avisynth sourcefilter, can I please point your attention to this thread: http://forum.doom9.org/showthread.php?s=&threadid=37204&perpage=20&pagenumber=4
The Autocrop plugin needs seeking (requesting frames) to work. This seems to cause problems with ffdshow in raw mode. Is there anything You can think of to make that work?
thanks for your time,
Simon
PkmoNk
9th June 2003, 12:43
I just want to note I've also had playback issue with the new ffdshow filter and uninstalling still caused playback problems with some avi files. so i uninstalled EVERY A/V codec and filters even ffvfw, and restarted, then install KazaaLite Codec FULL without the divx5.05 and the new ffdshow and everything works fine again! :)
Originally posted by PkmoNk
KazaaLite Codec FULL
:confused:
Blight
9th June 2003, 22:04
thop:
My analogy to PkmoNk's post is "So, my head was hurting real bad, so I took a gun, shot at my head, amazingly hit an tumor I didn't know I had and now my headache is gone".
simon.mittag
10th June 2003, 03:13
Blight :D :D :D
CruNcher
10th June 2003, 08:30
@ blight
buahahaha :rolleyes: :D :D
PkmoNk
10th June 2003, 12:24
Originally posted by Blight
thop:
My analogy to PkmoNk's post is "So, my head was hurting real bad, so I took a gun, shot at my head, amazingly hit an tumor I didn't know I had and now my headache is gone".
hey, I'm just trying to help out. It did solve my problems with playback. :rolleyes:
nadlabak
10th June 2003, 14:59
Hi,
sorry to interrupt this interesting discussion with my little wish...
Besides its great decoding capabilities, ffdshow is very powerful directshow video filter. I was always tempted to use it not only for video playback but also for video filtering during capture - deinterlace, crop and resize filters chained before video compressor are the most needed.
I was able to use it this way in Virtual VCR (and ffdshow is the only dshow resize filter that does not crash Virtual VCR when downscaling unlike the Moonlight bilinear scaler and Bicubic 1.3b filter) but ffdshow usability as a video filter has some shortcomings. Different settings for capture and playback operation can be achived by preset autoloading based on video size (full PAL - capture, any other resolution - playback). But raw video as the supported codec has to be enabled and ffdshow is then always loaded for any dshow video rendering happening on the system (in the selected color space). Video preview using Smart Tee filter in Virtual VCR could not be initialized when ffdshow is set as video prefilter, maybe because ffdshow is then running in two instances - one for prefiltering and second autoloaded for preview window.
It would be great if ffdshow could be compiled as a separate directshow video filter without decoding features with low merit (no autoloading) to be used for filtering purposes only and that could be installed on the same machine together with standard ffdshow filter used for video playback.
milan
10th June 2003, 15:06
I would prefer to maintain just one version of ffdshow. Would it be helpful to you if I would add possibility to select ffdshow's merit in its configuration dialog?
Blight
10th June 2003, 15:33
ChristianHJW:
You can't enable overlay mixer in FFDShow, it should be done on a Player level. As the overlay mixer breaks VMR9 support or any internal overlay mixer code in the player. Having it on by default would make ffdshow very unstable.
milan,nadlabak:
Not sure if it's possible, but if you can spawn two CLSIDs for FFDShow, one always RAW mode with a selectable merit and the other with never RAW mode and a very high merit. Each CLSID would have it's own registry tree.
That way you'd be using the exact same code base with only very minor checks to see which CLSID is running...
tcmjr
10th June 2003, 23:43
How can I get the best quality using ffdshow ?
I mean , which setting should I choose for best quality ?
lets say for playing dvix movies and xvid movies ?
I am using latest ffdshow (05/23) nvidia drivers 44.03 and win Xp.
Using both bsplayer and Zoom player
thanks.
ChristianHJW
11th June 2003, 08:56
Originally posted by Blight ChristianHJW: You can't enable overlay mixer in FFDShow, it should be done on a Player level. As the overlay mixer breaks VMR9 support or any internal overlay mixer code in the player. Having it on by default would make ffdshow very unstable.
Hmm .... thats sad :( . Seems we have to bug more player developers to support reading the mkv AR flag directly from the player .... |Blight| :D ?
EDIT : Can the player enable the overlay mixer in ffdshow if a .mkv is opened ?
BlackSun
11th June 2003, 09:04
Originally posted by Blight
ChristianHJW:
You can't enable overlay mixer in FFDShow, it should be done on a Player level. As the overlay mixer breaks VMR9 support or any internal overlay mixer code in the player. Having it on by default would make ffdshow very unstable.
I totally agree
JasonFly
11th June 2003, 18:47
I don't know if it has been report but I have a problem using ffdshow with andreas78 matrix.(this is a hi quality matrix)
The problem is a decoding problem(image is fine in VirtualDub) and seems related to ffdshow since the image is nice if decoded with Nic's decoder.
The problem happens on two encodes where I used andreas78 matrix and produce moving blocks in the image.(Looks like broken motion estimation)This happenned in a high motion scene with a complex motion of the hair of a person.
For these encodes,I used bframes(2-100-150-100) and vhq=1 but not qpel.Quantizers should be between 2 and 4 because the movie wasn't much compressed.
Sorry if this has already been reported.
Defiler
11th June 2003, 19:20
Does that matrix have a value lower than 16 in the top-left?
Lobuz
11th June 2003, 20:01
I don't know if it's useful but there are some optimisations to simple idct in mpeg2dec3 1.8 and lately in XviD too. So maybe it could serve to idct in ffdshow and gain a little more speed?
Regards
Lobuz
Blight
11th June 2003, 20:36
ChristianHJW:
ZP by default uses Overlay Mixer mode... VMR mode also works for AR as long as the filter passes the data in the VIDEOINFOHEADER2 structure.
JasonFly
11th June 2003, 20:50
Yes the matrix has vlaues lower than 16 in both the intra and inter matrix.
They look like this:
Intra:
8 13 15 19 ..
13 13 17 19 ..
15 17 19 ..
17 21 ..
21 ..
..
Inter:
8 11 13 15 ..
11 11 15 15 ..
13 15 17 ..
13 17 ..
17 ..
..
athos
20th June 2003, 14:48
I just wanted you to know that Milan is doing some heavy work on ffdshow right now. He has asked me to wait with putting up new builds on SF until he feels the state of the project is more stable. But there are some interesting development that I would like to try out, so I just might put up some private build, if Milan doesnt mind.. Here is the changelog since last alpha release:
2003-06-18 20:09 milan_cutka
mp3,mp2,ac3 decoding - ALL EXPERIMENTAL
2003-06-14 09:39 milan_cutka
updated vc6 projects
2003-06-14 08:00 milan_cutka
working on wma support (ffdshow.ax now contains an audio decoding
filter too)
2003-06-13 06:38 milan_cutka
msvidc
2003-06-12 11:29 milan_cutka
input bps in OSD, fix for mpeg1/2 decoding
2003-06-11 10:59 milan_cutka
second, raw video only, low priority filter
2003-06-11 06:46 milan_cutka
no message
2003-06-10 06:40 milan_cutka
working on better mpeg1/2 support
2003-06-09 16:04 milan_cutka
rgb gamma correction working in YUV (from mplayer's vf_eq2)
2003-06-09 13:35 milan_cutka
added skal's idct to libavcodec (almost untested, might be removed
if problems will occur)
2003-06-09 11:54 milan_cutka
updated libavcodec vc6 project
2003-06-09 11:23 milan_cutka
timestamps support in IffProc
2003-06-09 06:30 milan_cutka
subtitles use timestamps instead of frame numbers, timestamps
cleanup: mpeg1/2 now works a little bit better, possible new bugs
2003-06-06 06:44 milan_cutka
onSizeChange cleanup, SVQ1 support
2003-06-05 15:52 milan_cutka
experimental SVQ3 support, onSizeChange,onCSPchange
2003-06-05 14:10 milan_cutka
updated libavcodec
2003-06-05 08:05 milan_cutka
updated vc6 project
2003-06-05 06:42 milan_cutka
option to register ffdshow to selected media types only, resize
calculation cleanup
2003-06-04 08:04 milan_cutka
updated vc6 project
2003-06-04 06:30 milan_cutka
optional short osd message on keypress, XVID_CPU_ -> FF_CPU_, def
constants cleanup, remember selected item in codecs listview,
IffProc6 (removed backward compatibility)
2003-06-03 06:20 milan_cutka
YV12 simpleresize and warpedresize
2003-06-02 14:43 milan_cutka
use currect fps in avisynth filter
2003-06-02 12:02 milan_cutka
movies source codec from V1 branch to HEAD (this is HUGE commit,
but I don't know how to do this better)
2003-06-02 11:04 milan_cutka
file TfilterSettings.h was initially added on branch V1.
2003-06-02 11:04 milan_cutka
moved filters settings to separate files, TfilterSettings
descendants available globally
2003-06-02 08:31 milan_cutka
updated vc6 project
2003-06-02 06:43 milan_cutka
option to automatically select different IDCT for XVID, better way
to display subtitles below the video, frame sizes visualization,
displaying QPEL info again, nic's postprocessing accepts arbitrary
YUV chroma subsampling, "interlaced" resizing
2003-05-30 14:58 milan_cutka
3IVX, RMP4, DM4V
2003-05-30 14:44 milan_cutka
no message
2003-05-30 14:43 milan_cutka
3IV2 fourcc added
2003-05-30 12:42 milan_cutka
Visual Studio 6 project for building libmplayer.dll, fixed crash in
swscaler when copying images with equal negative strides
2003-05-30 11:12 milan_cutka
updated some code from mplayer,
2003-05-30 06:31 milan_cutka
separate swscaler blur and sharpen filters
2003-05-29 15:36 milan_cutka
updated libswscale and libpostproc, fast_memcpy
2003-05-29 11:30 milan_cutka
file dwstring.cpp was initially added on branch V1.
2003-05-29 11:30 milan_cutka
file dwstring.h was initially added on branch V1.
2003-05-29 11:30 milan_cutka
std::string -> DwString
2003-05-29 09:09 milan_cutka
fixed bad subtitles coloring introduced by previous commit
2003-05-29 08:17 milan_cutka
updated vc6 project
2003-05-29 07:00 milan_cutka
file image.cpp was initially added on branch V1.
2003-05-29 07:00 milan_cutka
file colorspace.cpp was initially added on branch V1.
2003-05-29 07:00 milan_cutka
file Tsubreader.cpp was initially added on branch V1.
2003-05-29 07:00 milan_cutka
file Makefile was initially added on branch V1.
2003-05-29 07:00 milan_cutka
file mem_align.h was initially added on branch V1.
2003-05-29 07:00 milan_cutka
file mem_align.cpp was initially added on branch V1.
2003-05-29 07:00 milan_cutka
cosmetic: XVID_CSP_ -> FF_CSP, xvid_malloc->aligned_malloc,... can
be compiled by gcc again, modifying string parameters and selecting
active preset via remote control framerate doubler works again,
fixed TomsMoComp chroma strides, underline and colored subtitles,
almost separate subtitle lines handling, little bigger trackbar
sliders
2003-05-27 15:32 milan_cutka
working on subtitles
2003-05-27 10:26 milan_cutka
warning fixes
2003-05-27 08:35 milan_cutka
file TsubreaderMplayer.cpp was initially added on branch V1.
2003-05-27 08:35 milan_cutka
file Tsubreader.h was initially added on branch V1.
2003-05-27 08:35 milan_cutka
file TsubreaderMplayer.h was initially added on branch V1.
2003-05-27 08:35 milan_cutka
working on subtitles parser deglobalization (currently broken)
2003-05-27 08:30 milan_cutka
fixed temporal smoother
2003-05-27 06:48 milan_cutka
hint generation and filter settings reset are now members of filter
setting struct, updated libavcodec
2003-05-26 11:56 milan_cutka
no message
2003-05-26 11:52 milan_cutka
don't display OSD lines which wouldn't fit to the image at the
bottom, always use full picture for OSD
2003-05-26 09:29 milan_cutka
memcpy -> TffPict::copy in bmp saving
So, we might see audio support, and perhaps working MPEG1/2 video soon!
-_- Does he really want to support everything and the kitchen sink?
thop
20th June 2003, 15:17
personally i'd prefer to have audio not decoded with ffdshow ... there are plenty of other filters for that available already. why reinvent the wheel when f.e. ac3filter already does a pretty good job?
The Link
20th June 2003, 15:41
personally i'd prefer to have audio not decoded with ffdshow ... there are plenty of other filters for that available already. why reinvent the wheel when f.e. ac3filter already does a pretty good job? Why not? :)
My impressions of ffdshow are, that it is milan's "baby" and in its form some kind of "proof of concept". I think milan does it for fun and to broaden his knowledge (which must already have the state of a compendium). The best part of it is that he lets us participate in his engagement! Arguments like "it is bloated" don´t count here IMHO because of its singular position in the video segment. Since ffdshow is fully configurable I don´t see any reason against audio support!
Regards,
The Link
edit: typos
gabest
20th June 2003, 15:50
The thing is dshow would allow only one filter to be the reader, parser, decoder, effecter and the renderer. But the power of dshow hides in its modularity and it is better to keep parts separate to be easily replacable. So, I also say it would be better to have an audio-only filter too, but that's only my opinion :)
Leak
20th June 2003, 20:05
Originally posted by gabest
The thing is dshow would allow only one filter to be the reader, parser, decoder, effecter and the renderer. But the power of dshow hides in its modularity and it is better to keep parts separate to be easily replacable. So, I also say it would be better to have an audio-only filter too, but that's only my opinion :)
Well, as long as this even remotely works like the video codecs it should be just another checkbox in the config dialog to deselect if you prefer some other audio decoder... :)
np; Senor Coconut - Smoke On The Water (ChaChaCha) (Fiesta Songs)
athos
21st June 2003, 03:23
well ffdshow is originally a dshow implementation of libavcodec, which eventually got added some elements of mplayer, nics dshow filter, etc. i think milan wants to implement as much as possible of libavcodec.
i agree that it would be cleaner and probably more practical too have a separate audio filter, which like ffdshow handles mpeg-4 and maybe some day mpeg-1 and 2, would handle most of the audio streams we handle. but it is still somehow cool to have all this stuff in one filter, and most of it works great! like low cpu usage and lots of options to play around with.
Blight
21st June 2003, 07:26
MP1/2 playback is tricky. A lot of non-microsoft filters that try to replace the microsoft one seem to break MPEG1 playback or introduce noises, screw with seeking, etc... I hope by default it'll be off.
MP3 on the other hand would be good as the current implementation chokes on MP3 files with headers containing a bitmap (that may actually have something to do with the source filter, unsure). And also the current MP3 decoder returns the wrong duration value for VBR, which would be a nice fix.
I wonder how milan is doing on the quicktime front, last message he wrote was about getting ffdshow to decode Sorenson3.
The RAW mode filter split is a good call as it will allow DVD-Only processing settings without effecting standard media playback.
I'd also root for milan to go for mpeg2, but the moment he does that (or sorenson for that matter), he should stop putting binaries on SF (See XVID).
qwerpoi
23rd June 2003, 22:19
A couple of things about ffdshow:
First, as someone mentioned in this thread earlier, i believe there is a color bug with the aWarpSharp filter (I'm running the 20030422 build since every other one crashes on my Win98 pc, but I didn't see any fix in the changelogs for the other builds). When the filter is on, the color on the bottom of the screen is messed up, even when the chroma mode is none. This bug disappears when I open my file via avisynth and ffdshow raw mode (don't know if that is helpful info or not).
Secondly, does anyone use the autoloading presets in ffdshow? I've never used them because it always seemed a bit clunky to me (and ffdshow seems to crash on my system when I try to set the autoloading conditions). I think a more graceful interface would be integrating some presets in the right-click interface. What I mean is that when you right click the video in a player such as mpc or zoomplayer, you can see ffdshow in the right click menu (if it's decoding the video). Instead of clicking on it to bring up the config dialog, make an additional menu (like directvobsub) which allows you to either bring up the config dialog or choose from a fixed number of custom presets (I can't imagine needing more than 5 or so, such as DVD, high quality avi, low quality avi, maybe some cartoon presets). I hope someone understands what I'm trying to say, I think it would be pretty handy :).
Lastly, can someone explain to me how the avisynth option is supposed to work in ffdshow? Are you supposed to load plugins that are already in your plugins directory? Do you need a line to load the file via avisynth? This is a pretty embarassing question, but I ask because every time I try to do anything (even something as simple as loadplugin), the player will crash. Maybe I'm stupid and completely misunderstand what needs to be done, I would appreciate it if someone would post exactly what they have in the avisynth box for something simple like applying convolution3d or something. Thanks.
ChristianHJW
24th June 2003, 10:36
@milan : please join #matroska irc.corecodec.com again, DaveEL has new, better native MPEG4 MKV samples made and we should discuss how we wnat to support playback with b-frames from ffdshow now soon .....
athos
29th June 2003, 19:35
i compiled a private build today (milan has asked me to wait for a while with releasing new builds on SF) and I can tell you that ffdshow now decodes mp3/mp2/aac/ac3/wma1,2,7 and 8! He has also implemented a framerate doubler with motion compensation! (as discussed here (http://forum.doom9.org/showthread.php?s=&threadid=36361)). This is very cool IMO, works very well, but there are some minor flickering sometimes. Aside from that, I think it helps make the motions flow better.
I only tried mp3 decoding of the audio filters yet, and it seems to work great! I think it is based on libmad which is good, its the best quality mp3 decoding i know of. There are very few options for the audio filters yet, but I guess milan will be adding more options later, like the rest of ffdshow.
I will put up a new build when milan asks me to.
oddball
29th June 2003, 20:58
I'm just waiting for him to fix the Avisynth script loader so I can use Autocrop correctly. BTW is there an Avisynth plugin that can add black bars on all sides (while shrinking the image)? I'm wondering if there is anything less CPU intensive than ffdshows own black border option. Good for overscan compensation on anime fansubs.
Blight
29th June 2003, 21:56
oddball:
You can just zoom the video in/out using most players. (+ / - keys in zoom player).
Sirber
29th June 2003, 22:00
Just a little bug report:
When I play with postprocessing, MPC crash...
oddball
30th June 2003, 19:57
Blight: No for TV out on a Matrox G400 you can't. ;)
Tueurne
1st July 2003, 12:54
Just a question about idct :
in misc
simple use simple idct
xvid use walken idct
but what about normal and reference ? why kind of idct are used ?
Lobuz
1st July 2003, 14:23
I made some PSNR tests of ffdshow decoding of xvid file. It's here (http://forum.doom9.org/showthread.php?s=&threadid=56190&perpage=20&pagenumber=7). It shows that with latest build nic's postprocessing is somehow broken.
It was said earlier that it's crashing but it actually gives worse picture. It behaves better after setting X offset from 20 to 30 and that green garabage at clip start disappeare too.
Regards
Lobuz
simon.mittag
5th July 2003, 09:39
Originally posted by oddball
I'm just waiting for him to fix the Avisynth script loader so I can use Autocrop correctly. BTW is there an Avisynth plugin that can add black bars on all sides (while shrinking the image)? I'm wondering if there is anything less CPU intensive than ffdshows own black border option. Good for overscan compensation on anime fansubs.
This would be my biggest wish at the moment as well! The avisynth plugin loader in ffdshow (the custom source filter) does not seem to support getframe(x) in raw mode. this was discussed in the autocrop thread on the avisynth board a while ago. i contacted the autocrop author but he said there is nothing he can do as long as getframe(x) does not deliver him the frames requested.
in raw mode, getframe() seems to deliver only the current frame as opposed to the requested frame, which prevents autocrop from calculating the right cropping information as it needs several frames for that.
milan if you read this, can we have your comments on the situation please?
autocrop for RAW mode would finally enable me to use ffdshow as a full blown postprocessor for DVD playback that lets me do positioning with zoom player based only on the picture information without the bars. this is what i am looking at doing with my projector setup and screen fitting.
will requesting frames in raw mode ever work or is this a streaming problem that can't be solved?
regards,
Simon
P.S. the reason why i need raw mode is because i want to use the sonic 1.5 mpeg2 filters for decoding as I just love the crisp image they produce. im using ffdshow as a postprocessor after the sonic filter b4 the video renderer.
oddball
5th July 2003, 10:04
simon.mittag: Have you ever tried DiVXG400 in a Zoom Player manual filter? I have used it (It only works using the WinDVD playback filter for DVD though) and it lets you crop black bars in the overlay to TV out. Very good for non-anamorphic movies if you have a widescreen TV as it will provide a 'false' anamorphic squeeze.
This makes for a nicer looking zoom than my own TV provides.
Can provide the filter settings if needed.
Would love to get ffdshow as a post processing filter though with autocrop. Would be easier.
simon.mittag
5th July 2003, 12:31
oddball: no I haven't tried that particular filter. I agree though that ffdshow/avisynth would be easier.
I am unsure if RAW mode will ever allow for seeking, as I don't know if ffdshow just acts as "listener" to the current frame provided by the mpeg decoder filter.
Can someone comment on this please? Is RAW mode a slave (listening)mode?
regards,
Simon
pandv
6th July 2003, 18:46
A little and cosmetic bug for this awesome program.
Using ffdshow 2003-05-23, levels->show histogram shows nothing.
Bye.
Animaniac
7th July 2003, 11:12
athos, milan
Any news on when the next build will be availible? I'm itching to try the audio decoding. ^_^
Chibi Jasmin
8th July 2003, 12:36
Originally posted by oddball
simon.mittag: Have you ever tried DiVXG400 in a Zoom Player manual filter? I have used it (It only works using the WinDVD playback filter for DVD though) and it lets you crop black bars in the overlay to TV out. Very good for non-anamorphic movies if you have a widescreen TV as it will provide a 'false' anamorphic squeeze.
This makes for a nicer looking zoom than my own TV provides.
Can provide the filter settings if needed.
Would love to get ffdshow as a post processing filter though with autocrop. Would be easier.
Yes, please let me know, how you get ZoomPlayer in DVDMode (with WinDVD) to work with DivXG400!
oddball
8th July 2003, 18:02
First off you need WinDVD installed and DiVXG400 obviously. You may also need AC3filter installed.
Paste this into a text file
DefineFilter(iviaudio.ax)
DefineFilter(ivivideo.ax)
DefineFilter(DiVXG400.ax)
DefineFilter(AC3Filter.ax)
LoadFilter({E30629D1-27E5-11CE-875D-00608CB78066},Default WaveOut Device)
LoadFilter({70E102B0-5556-11CE-97C0-00AA0055595A},Video Renderer)
LoadFilter({A753A1EC-973E-4718-AF8E-A3F554D45C44},AC3Filter)
LoadFilter({CD8743A1-3736-11D0-9E69-00C04FD7C15B},Overlay Mixer)
LoadFilter({6E8D4A20-310C-11D0-B79A-00AA003767A7},Line 21 Decoder)
LoadFilter({0246CA20-776D-11D2-8010-00104B9B8592},InterVideo Video Decoder)
LoadFilter({9B8C4620-2C1A-11D0-8493-00A02438AD48},DVD Navigator)
LoadFilter({9D2935C7-3D8B-4EF6-B0D1-C14064698794},DiVXG400)
ConnectPin(DVD Navigator,Video,InterVideo Video Decoder,Video Input)
ConnectPin(DVD Navigator,AC3,AC3Filter,In)
ConnectPin(DVD Navigator,SubPicture,InterVideo Video Decoder,Subpicture Input)
ConnectPin(AC3Filter,Out,Default WaveOut Device,Audio Input pin (rendered))
ConnectPin(InterVideo Video Decoder,Video Output,DiVXG400,In)
ConnectPin(DiVXG400,Out,Overlay Mixer,Input0)
ConnectPin(InterVideo Video Decoder,~Line21 Output,Line 21 Decoder,In)
ConnectPin(InterVideo Video Decoder,~Subpicture Output,Overlay Mixer,Input2)
ConnectPin(Line 21 Decoder,Out,Overlay Mixer,Input3)
ConnectPin(Overlay Mixer,Output,Video Renderer,In)
save it in Zoom Players dvdgraph scripting folder. Rename the file from .txt to .dvdgraph
Now load Zoom Player. Got to the DVD setup menu and select custom filters. Choose the new script and you are done.
Edit it to suit but be aware that not all filters work in the same setup/manner.
EDIT: Hmm. It does not work for me anymore after having to reinstall XP etc. I even tried connecting the video out from the Intervideo filter to the DiVXG400 filter and it would not accept the pin whereas it did before no problem. Blah!
Chibi Jasmin
8th July 2003, 18:26
Originally posted by oddball
First off you need WinDVD installed and DiVXG400 obviously. You may also need AC3filter installed.
Paste this into a text file
DefineFilter(iviaudio.ax)
DefineFilter(ivivideo.ax)
DefineFilter(DiVXG400.ax)
DefineFilter(AC3Filter.ax)
LoadFilter({E30629D1-27E5-11CE-875D-00608CB78066},Default WaveOut Device)
LoadFilter({70E102B0-5556-11CE-97C0-00AA0055595A},Video Renderer)
LoadFilter({A753A1EC-973E-4718-AF8E-A3F554D45C44},AC3Filter)
LoadFilter({CD8743A1-3736-11D0-9E69-00C04FD7C15B},Overlay Mixer)
LoadFilter({6E8D4A20-310C-11D0-B79A-00AA003767A7},Line 21 Decoder)
LoadFilter({0246CA20-776D-11D2-8010-00104B9B8592},InterVideo Video Decoder)
LoadFilter({9B8C4620-2C1A-11D0-8493-00A02438AD48},DVD Navigator)
LoadFilter({9D2935C7-3D8B-4EF6-B0D1-C14064698794},DiVXG400)
ConnectPin(DVD Navigator,Video,InterVideo Video Decoder,Video Input)
ConnectPin(DVD Navigator,AC3,AC3Filter,In)
ConnectPin(DVD Navigator,SubPicture,InterVideo Video Decoder,Subpicture Input)
ConnectPin(AC3Filter,Out,Default WaveOut Device,Audio Input pin (rendered))
ConnectPin(InterVideo Video Decoder,Video Output,DiVXG400,In)
ConnectPin(DiVXG400,Out,Overlay Mixer,Input0)
ConnectPin(InterVideo Video Decoder,~Line21 Output,Line 21 Decoder,In)
ConnectPin(InterVideo Video Decoder,~Subpicture Output,Overlay Mixer,Input2)
ConnectPin(Line 21 Decoder,Out,Overlay Mixer,Input3)
ConnectPin(Overlay Mixer,Output,Video Renderer,In)
save it in Zoom Players dvdgraph scripting folder. Rename the file from .txt to .dvdgraph
Now load Zoom Player. Got to the DVD setup menu and select custom filters. Choose the new script and you are done.
Edit it to suit but be aware that not all filters work in the same setup/manner.
Thanx a lot...!
oddball
8th July 2003, 21:22
OK figured why it was not working. You need the Elecard MPEG decoder installed. It uses that even though the Intervideo is in the fiulter chain. Weird.
Get it here http://www.elecard.com/ftp/pub/mpeg/decoder/EMpgDec20.zip
Install it and use that filter and you should have no probs cropping black bars off 4:3 letterbox DVD's to create an artificial 'zoom' on a 16:9 TV.
It's rather neat :)
Hello, I just wanted to note that libavcodec decoding still exhibits the smearing problem with xvid qpel encodes regardless of the IDCT type selected. Problem occurs both with XviD and Simple IDCT.
With codec's built-in XviD decoder, there's no smearing.
Nic's XviD Decoder also causes smearing.
regards,
iago
[latest ffdshow alpha (ffdshow-20030523) / latest XviD build by Koepi (24062003-1) / latest XviD build by uManiac (26.06.2003.1100)]
Animaniac
10th July 2003, 23:34
CVS comments show that ffdshow audio will have raw audio counterpart and have a built in equalizer and channel mixer!!! ffdshow is really going to become the one-stop A/V decoder! ^_^
oddball
16th July 2003, 00:33
I'm getting the same problem with DiVX 5.03 with smearing. I presume this is also because of qpel. It seems to happen randomly though. I thought that bug would have been squashed by now.
Mind you I've upgraded to an AMD XP chip and resintalled WinXP from scratch so I don't know how much that has to do with it. Also a new Geforce4 card. I hate bug tracking :)
simon.mittag
17th July 2003, 07:01
oddball... did you hear anything from milan regarding avisynth and autocrop? i haven't seen him here for a while but it probably doesn't make sense for all of us to start emailing him...
aydc
17th July 2003, 12:00
Hi all,
Could anybody please explain to me why mplayer postprocessing stopped working with the lastest releases? I used to rely on it rather than nic's because nic's pp seems to blur the image too much.
Or alternatively, could anyone please recommend me good postprocessing settings to use?
oddball
17th July 2003, 19:24
I dunno why but I seem to get random smearing and the odd static blocks with or without ffdshow in the equation. So it probably is not ffdshow causing my problem. If I play back the same scene after it smears it does not smear. Odd.
I dunno about autocrop. If Milan reads the ffdshow threads then I am sure he is on the case. Maybe...
Animaniac
17th July 2003, 21:27
Originally posted by aydc
Hi all,
Could anybody please explain to me why mplayer postprocessing stopped working with the lastest releases? I used to rely on it rather than nic's because nic's pp seems to blur the image too much.
Or alternatively, could anyone please recommend me good postprocessing settings to use?
Lobuz' PSNR table in this thread (http://forum.doom9.org/showthread.php?s=&threadid=56190&perpage=20&pagenumber=7) tests the 4-24 and 5-23 build of ffdshow. Nic's using default settings on the 4-24 produces the highest PSNR. The 5-23 seems to have problems with Nic's at lower thresholds.
kilg0r3
22nd July 2003, 09:33
1.
I would like to do the following in the avsynth box, or of possible somewhere else, in ffdshow. In order to get rid of the stepping/pixelation effects with intensive colors due to the low chroma res of YV12.
increase the chroma resloution (e.g. converttoyuy2), blur the chroma plane, merge luma of original with blurred chroma.
the problem is manly, how to define the video source.
2.
What does 'Add ffdshow video source' mean?
Best
22nd July 2003, 13:35
increase the chroma resloution (e.g. converttoyuy2), blur the chroma plane, merge luma of original with blurred chroma.
I belive if you uncheck YV12 as supported output colorspaces it would automaticly convert to yuy2.
oddball
22nd July 2003, 21:31
When will ffdshow support MPEG1/2 ?
ookzDVD
26th July 2003, 03:16
Build 2003-05-23,
I just found : enabling the xshapen "sometimes" will crash the MPC.
Soulhunter
28th July 2003, 00:30
ffdshow crash with "ConverToRGB32()" command in AviSynth-tab...!
Maybe read this thread > http://forum.doom9.org/showthread.php?s=&threadid=38304&perpage=20&pagenumber=2 <
I used:
WinME / ffdshow 23.05.03 / Avisynth is 2.5.2
This was the error code:
MPLAYER2 verursachte einen Fehler durch eine ungültige Seite
in Modul KERNEL32.DLL bei 018f:bff8e1ad.
Register:
EAX=c002fa54 CS=018f EIP=bff8e1ad EFLGS=00210212
EBX=0177ffbc SS=0197 ESP=0173feec EBP=01740188
ECX=00000000 DS=0197 ESI=00000000 FS=2acf
EDX=bff6682d ES=0197 EDI=bff69050 GS=0000
Bytes bei CS:EIP:
53 8b 15 f4 bc fb bf 56 89 4d e4 57 89 4d dc 89
Bye
Arcon
28th July 2003, 21:42
i just updated to 20030523 and use xvid.dll for decoding xvid. now i get some wrongly colored horizontal lines. i think that's what happens if one uses the wrong idct, but i chose xvid, not libavcodec as decoder, so the idct should be external and correct.
this effect only appears if i enable postprocessing (preset 4, nic's enabled). with the older build 20030424 i don't get this effect even with postprocessing enabled.
codec is xvid 24062003-1.
Soulhunter
28th July 2003, 22:21
Suggestion for additional Noise option;
I'm a big fan of ffdshow's noise option... It repruduces the original film-grain real good! :D
But I find there should be a option to scale between normal & uniform noise.
Normal noise adds less noise to dark arears and uniform noise adds to all arears the same amout...
For now I use mplayer-uniform-noise at a low amout 15/5 but in this way theres to much noise in dark arears, and not enough in bright ones... If I use normal-noise (not uniform) there's not enough noise in dark arears (for me)!
So I would find it nice to add a slider in the noise-option-tab to scale between uniform/normal noise.
Should look like this:
-----------------------------------------------------------
uniform noise 0% <-----I-----> 100% regular noise
-----------------------------------------------------------
0% = Uniform noise (dont take respect to the brightness/darkness of arears)
50% = Noise in very dark arears reduced to 50% in bright still 100%
100% = Noise only in very bright arears (Near like none in dark arears)
All % based of the noise amout you've choosen by noise strength-tab.
@All
Keep posting back ! :)
Bye
Ghim
29th July 2003, 01:03
Originally posted by Arcon
i just updated to 20030523 and use xvid.dll for decoding xvid. now i get some wrongly colored horizontal lines. i think that's what happens if one uses the wrong idct, but i chose xvid, not libavcodec as decoder, so the idct should be external and correct.
this effect only appears if i enable postprocessing (preset 4, nic's enabled). with the older build 20030424 i don't get this effect even with postprocessing enabled.
codec is xvid 24062003-1.
I had the same pb on a video and i simply changed X threshold from 20 to 30 in Nic postprocessing... It solved the problem for me...
Asmodian
29th July 2003, 04:39
had the same pb on a video and i simply changed X threshold from 20 to 30 in Nic postprocessing... It solved the problem for me...
Wouldn't that make the image rather blurry?
I have also noticed these problems (horizontal lines with wrong colors, especially at the ends -> green) with the 20030523 build of ffdshow (with Nic's PP at default thresholds). This build also crashes ZP in many different configurations and I haven't done the testing necessary to figure out exactly what causes the crash (but I am pretty sure it is something with this ffdshow because of when I would get a crash on video load and then turn off PP and the video would load, or I would just disable ffdshow and again the video would load – it seemed somewhat source dependent and sometime the PP didn’t cause problems). Has anyone else experienced a crash using this newest ffdshow?
Ghim
29th July 2003, 11:14
The image isn't that blurry at all... but the horizontal lines bug has really disappeard.
I also have experienced some random crashes with Nic's PP activated (I'm using ZP)...
kilg0r3
29th July 2003, 13:34
incresing the threshold values decreases pp strength
Ghim
29th July 2003, 14:06
I prefer this (X threshold 30) than a "horizontal line bug" or "no PP"...
Asmodian
29th July 2003, 23:09
incresing the threshold values decreases pp strength
Oops, I even knew that - I must have meant; doesn't increasing the threshold make the post processing less effective? :p
yes it is better to just turn up the threshold then have artifacts (pp created or from lack of pp), but this is a newly introduced problem that should be investigated (but work is very busy this week so I don't think I will be able to find the time to test). I also have quite a few videos compressed with xvid and divx (older builds) which play as solid gray video when decoded with libvcodec in the newest ffdshow but work fine if decoded with xvid.
I hope we can get to the bottom of this.
Didée
31st July 2003, 08:58
Originally posted by Asmodian
xvid and divx (older builds) which play as solid gray video when decoded with libvcodec
ffdshow/miscellaneous/Workaround ecoder bugs - [x]Autodetect
Know your tools
- Didée
Asmodian
1st August 2003, 01:37
Ah, I see - I usually don't change options in the miscellaneous tab, did the defaults recently change or did I just foolishly turn off autodetect workaround bugs (or were the defaults always autodetect off and I never needed it on before)?
Do you think this option would have an effect with regard to the crashing problem with nic's pp, or is it more likley that the crashing problem is not actually ffdshow's fault?
Takuto
2nd August 2003, 00:45
I have small feature request to ffdshow. It mostly decorative, but I think it can be useful and its not too hard in realisation.
Can OSD be 'temporary'? For example, user enable param 'delay' in ffdshow config, sets it to 5 sec, and OSD will on-screen for 5 secs when video starts, then it gone (with cool effects 8)) ).
And can be FOURCC of file included into OSD table? Not only 'decoder' info, but FOURCC too.
I think its convinient - starting playback of file and in 5 secs get basic info about it without going in config page or into other apps.
An I want to say BIG thanks to Milan and all contributing in ffdshow.
Its really my favorite decoder.
HarryM
2nd August 2003, 09:57
I think over simple/Walken iDCT automatic switching at ffdshow decoding.
Can anyone this make depending on 'date of file'?
from dd.mm.yyyy to dd.mm.yyyy -> use simple iDCT!
from dd.mm.yyyy to dd.mm.yyyy -> use Walken iDCT!
dTb
2nd August 2003, 10:16
Originally posted by Asmodian
Wouldn't that make the image rather blurry?
I have also noticed these problems (horizontal lines with wrong colors, especially at the ends -> green) with the 20030523 build of ffdshow (with Nic's PP at default thresholds). This build also crashes ZP in many different configurations and I haven't done the testing necessary to figure out exactly what causes the crash (but I am pretty sure it is something with this ffdshow because of when I would get a crash on video load and then turn off PP and the video would load, or I would just disable ffdshow and again the video would load – it seemed somewhat source dependent and sometime the PP didn’t cause problems). Has anyone else experienced a crash using this newest ffdshow?
I've experienced much the same thing all centred around nic's post-processing being enabled when opening a file. Opening the particular file without the pp enabled it will play and the pp can then be enabled during playback. When I get a chance I'll see if I can isolate which files this occurs with and any similarities between them. No problems with the mplayer pp.
Edit: I'm only experiencing the crashing in Zoomplayer not the other problem.
HarryM
2nd August 2003, 13:26
Originally posted by dTb
I've experienced much the same thing all centred around nic's post-processing being enabled when opening a file. Opening the particular file without the pp enabled it will play and the pp can then be enabled during playback. When I get a chance I'll see if I can isolate which files this occurs with and any similarities between them. No problems with the mplayer pp.
Edit: I'm only experiencing the crashing in Zoomplayer not the other problem.
If you use W9x, the last 'good' ffdshow version for you is 24/04/2003.
Newer builds of ffdshow crash on Win9x. Only one choice is = VMR9 activating for playing. With WXP no problem.
Lobuz
4th August 2003, 00:43
Is there a possibility to reduce CPU utilization while decoding mpeg4 even by the cost of the quality ( no pp ). I mean decoding only video with my old Pentium 200 is almost 100% fluent but with sound it's shaky. It could be useful to some portable devices and old PCs.
Regards
Lobuz
dTb
5th August 2003, 05:26
Originally posted by HarryM
If you use W9x, the last 'good' ffdshow version for you is 24/04/2003.
Newer builds of ffdshow crash on Win9x. Only one choice is = VMR9 activating for playing. With WXP no problem.
I'm using WinXP with the 23/5/03 alpha, I'm unsure what you mean by VMR9.
The problem occurs only with files with a fourcc of DIV3 as far as I can tell and I think I've narrowed it down to the Chroma Dering of Nic's pp. Most files can be opened when the pp is set on the fifth notch (ie. everything bar Chroma Dering) and then during playback the chroma dering can be enabled although for one file this didn't work. Just testing now, with only the chroma dering enabled via custom I get the same problem, file won't open in ZP.
Soulhunter
5th August 2003, 14:49
Suggestion for additional Noise option No.2;
Ive forgotten something in my last suggestion... :D
A second option to scale between standart and averanged noise would also be usefull!
Should look like this:
-----------------------------------------------------------
Averaged noise 0% <-----I-----> 100% regular noise
-----------------------------------------------------------
0% = Averaged noise (same as now with aktiv averaged)
50% = 50/50 blended (original and averaged)
100% = Regular noise (same as now without aktiv averaged)
Bye
vBulletin® v3.8.5, Copyright ©2000-2012, Jelsoft Enterprises Ltd.