Log in

View Full Version : ffdshow development


Pages : 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 [16] 17 18 19 20 21 22 23 24 25 26

Andy2222
19th March 2004, 13:38
Originally posted by Sirber
mplayer or VLC :) www.videolan.org

I dont think this will work since both player's (mplayer and VLC) also using the libavcodec libary from the ffmpeg project like ffdshow for MPEG4, H263, WMV/A ... playback.
But feel free to test it.

jk888
19th March 2004, 18:05
I tried VLC (using the default settings), and yes it produces the artifacts in the exact same manner as ffdshow.

P0l1m0rph1c
19th March 2004, 22:22
Hmm...even with this new build, ffvfw still desn't show on VirtualDubMod. Installing regular ffvfw works. Anyone having the same behavior?

iradic
19th March 2004, 23:39
read somewhere in forum that ffdshow install path without spaces gives solution to your not showing problem... try and see :)

athos
19th March 2004, 23:51
oh i put up a new build, forgot to post.
i tried to solve the path-problem by adding quotes around the path in the installerscript, but that didnt seem to solve it so i let it go. im guessing milans "Program Files"-equivalent does not contain spaces ;)

Edit: I realized I was using GCC 3.2.3 so I upgraded to 3.3.1. I'm not sure what implications this will have.

P0l1m0rph1c
20th March 2004, 01:43
Yeah, with no spaces it works :)

Another thing....

2004-03-14 18:47 milan_cutka

added support for skal's mpeg4 encoding library



Should skal's codec appear in ffvfw? Or is it just merged?

celtic_druid
20th March 2004, 03:06
Drop skl_drv_mpg.dll in the ffdshow directory and it will show up under the VFW config. No idea if it works, but it does show up.

Ok in my limited one test it worked fine.

LigH
20th March 2004, 09:18
Would have been nice if someone included a link to this DLL - I did not know about it yet. I found the sources on skal's MPEG4 page (http://skal.planet-d.net/coding/mpeg4codec.html), but who has a precompiled Win32 version?

celtic_druid
20th March 2004, 11:32
I have one, but that is only because I compiled it myself. Could give you a link if you really want it?

echo
20th March 2004, 12:20
Encoding with masking enabled does not work at all for me in the latest merged ffdshow/vfw version. It does not matter if the options are checked or not, masking is not used anyway. Also the simulation button in the 2-pass page crashes everything (virtualdub exits with no warnings). Anyone else seeing these?

regards
echo

APF_Gandalf
20th March 2004, 13:37
Originally posted by athos
oh i put up a new build, forgot to post.
i tried to solve the path-problem by adding quotes around the path in the installerscript, but that didnt seem to solve it so i let it go. im guessing milans "Program Files"-equivalent does not contain spaces ;)

looks like an old DOS "8.3" limitation, if you can somehow convert "c:\program files\" to "c:\Progra~1\" (and any "c:\xxxxxxxxxxxxxxxx\" to "c:\xxxxxx~1\") when it's added to the registery, it should work... I guess...

athos
20th March 2004, 13:41
Originally posted by APF_Gandalf
looks like an old DOS "8.3" limitation, if you can somehow convert "c:\program files\" to "c:\Progra~1\" (and any "c:\xxxxxxxxxxxxxxxx\" to "c:\xxxxxx~1\") when it's added to the registery, it should work... I guess...

I'll try this for next builds. I think it is allready done on Win9x platforms, so I'll just have to exchange a few variables.

LigH
20th March 2004, 14:01
@ celtic_druid:

Would be nice - if you can't provide a download address, write a PM to find a way for me to get it; afterwards, I could even host a copy if desired.
__

@ athos:

Using short path names (PROGRA~1) is one option, quoted paths ("Program Files") could be another. But I'm not sure which part of the installation process (script; registry storage) requires which kind of quotation. For path names, I found double quites quite often, but for registry key names, I also spotted single quotes sometimes.

Andy2222
20th March 2004, 20:20
little info:

the "keep org. aspect ratio" bug aka wrong AR in resize mode is finaly FIXED by Milan!

That bug was live since the first 06/2003 release and its finaly fixed :)

Means u now can use that setting again and use resize without getting your AR messed.

Thx so much milan. So the next Athos release will have it fixed too.

Didée
20th March 2004, 20:39
Hooray!

Someone tell ChristianHJW - he insists (http://forum.doom9.org/showthread.php?s=&postid=459765#post459765) on this bug being not there ... (also on the page before)

- Didée

celtic_druid
21st March 2004, 00:34
http://celticdruid.no-ip.com/skl_drv_mpg.7z

gitoshi
21st March 2004, 05:46
I don't know about resize bug (never use before), but the jerky playback remain here when your player use OverlayMixer, everything work fine if the player use VMR9.


G

jk888
21st March 2004, 09:56
small update to the Xvid SixOfNine-HVS matricies issue:

http://forum.doom9.org/showthread.php?s=&postid=461994#post461994

I changed the resolution and target filesize, then areas which are affected by artifacts have changed. Which I think means that the issue isn't related to certain frames.

Andy2222
21st March 2004, 10:15
Originally posted by gitoshi
I don't know about resize bug (never use before), but the jerky playback remain here when your player use OverlayMixer, everything work fine if the player use VMR9.


G

Arno could fix that by just disabling overlay mixer in the player (bsplay) and enabling it in ffdshow, or disable it at all.
For what files ffdshow has this jerky playback for u? Is it also Nic's PP related or always?

gitoshi
21st March 2004, 19:20
Arno could fix that by just disabling overlay mixer in the player (bsplay) and enabling it in ffdshow
Sure, if the player don't use overlay mixer the problem is gone.
For what files ffdshow has this jerky playback for u?
Most of the files show jerky playback. Including old DIVX5.
Is it also Nic's PP related or always?
It is always. Nic PP make no diference.

Also I try usign XVID4 as decoder for FFDSHOW and the problem remain, so I don't think that it is a problem of libavcodec. Look like a problem with the overlaymixer.

@Andy2222.
Did you check my previous posts, I post a link to the same problem in XVID RC1 - RC2 (solved in RC3) (and posible solution , just a line of code). I also post a link to the bug page of CoreMediaPlayer.

G

TripleA
22nd March 2004, 11:52
Originally posted by APF_Gandalf
looks like an old DOS "8.3" limitation, if you can somehow convert "c:\program files\" to "c:\Progra~1\" (and any "c:\xxxxxxxxxxxxxxxx\" to "c:\xxxxxx~1\") when it's added to the registery, it should work... I guess...

For any concerned I can confirm that telling the ffdshow-20040312.exe installer to install to "C:\PROGRA~1\ffdshow" resulted in "ffdshow Video Codec" showing up fine in VDub.

I have no idea if it works or not, though.

bond
22nd March 2004, 22:40
i get choppy playback with any content when i enable the overlay mixer option (meaning overlay mixer2 gets used)

this is surely not related to the source, which is decoded, as i get the same behaviour with the 3ivx decoder (with om2) and gabests realmedia decoder (with om2)

shitowax, meant that this can be fixed on the decoder side and "non-compressed ouput media samples should be always considered as keyframe"

hope this helps :(

timeismoney
23rd March 2004, 03:32
I think just move ffdshow.ax to system dir will be nice, and needn't change progra~1

Andy2222
23rd March 2004, 11:07
Originally posted by bond
i get choppy playback with any content when i enable the overlay mixer option (meaning overlay mixer2 gets used)

this is surely not related to the source, which is decoded, as i get the same behaviour with the 3ivx decoder (with om2) and gabests realmedia decoder (with om2)

shitowax, meant that this can be fixed on the decoder side and "non-compressed ouput media samples should be always considered as keyframe"

hope this helps :(

mhh the question is why just a few have that choppy playback? I tested many ffdshow version's (im using my own atm but also testing Athos version always) and i never ever had choppy playback. I play any kind of divx3-5/3ivx and xvid 3-4 also dvd's and im using zoomplayer and crystal player with and without overlaymixer. But for ffdshow i used overlay mixer1 and 2. Btw whats the difference? I also already used ffdshow as raw filter after the decoder and now using libav for all....

PS: maybe its processor, video card/driver related?

Didée
23rd March 2004, 12:49
Me too suffers from choppy ffdshow playback, and I have no clue what exactly could be the cause, sorry.

But let me report the following wired observations I made:

- it plays smooth when disabling OM in both ffdshow and ZoomPlayer, but that's not the real option.

- with OM on in ffdshow, I usually get choppy playback - but *not always*. Let's say, in 90%-95% after opening a file. Sometimes it just plays smooth ...

- even better: when I activate "resizing" in ffdshow, then playback is mostly smooth (!) - but not always. Let's say, in 90%-95% ...

The last point is the one I don't understand at all: plainly playing a 704*528 XviD through OM plays choppy; if it's additionally resized by ffdshow to e.g. 1280*720, then it plays fluid !?!

I can confirm this ATM for an Athlon XP1800 + ATI 8500DV.

- Didée

Ronin73
23rd March 2004, 13:39
Is the ffdshow from http://athos.leffe.dnsalias.com/ffdshow-20040319.exe
Optimized with asm or is using the slow c routines?

Andy2222
23rd March 2004, 13:52
Originally posted by Ronin73
Is the ffdshow from http://athos.leffe.dnsalias.com/ffdshow-20040319.exe
Optimized with asm or is using the slow c routines?

Athos version's use all optimized inline asm stuff since its a VC6 compile for the ffdshow.ax and he use mingw gcc for the libav/mplayer dll's.

Only a gcc compiled version of ffdshow.ax would not use the asm optimized version's.

I realy have no clue why those choppy playback happens for u... Question: Can some1 confirm that choppy (overlay mixer) playback for nvidia cards or does it just happens with ATI card's?

Can some1 make a link to a short file wich play's choppy and tell me the exact filter config, ffdshow version, player and stuff wich cause that bug? If we cant reproduce that error it's prolly hard to fix.

Slave01
23rd March 2004, 14:23
I have that problem too (xp 1700 + ati 7500). But it is so important using Overlay mixer?
Which are the pros?



Slave01

Didée
23rd March 2004, 16:49
Slave01:

There are several reasons. Many people encode to anamorphic resolutions these days, and you kinda need OverlayMixer to get the correct AR on playback. Then, using OM is most times required to pipe the data as YV12 to the video card, for fastest-possible performance (HDTV resolutions may need every single possible CPU/GPU cycle). Without OM, with normal renderer or VMR9, the performance is not as good, in most cases.


Andy2222:
Have also another machine, with an Intel-Celeron + an ATI card. I'll check if I can reproduce the choppy playback on that configuration. (It's the MM system for my wife, therefore *no problems allowed* ;) , therefore still ffdshow 23-05-2003 ...). Will test that tomorrow.


- Didée

Andy2222
23rd March 2004, 17:58
If u have an Athlon-XP or Pentium3 and those "choppy" playback can u try this testversion for me pls? get it here: http://mitglied.lycos.de/ieggei2/ffdshow/

It has no installer just copy the 3 files into your ffdshow directory.

There are ONLY version's for athlon-xp+ and pentium3+. Pls dont publish this link or lycos will kick me again. (Its just a Testversion to get an idea what cause the choppy playback)

PS: so tell me if it fixed the choppy playback and maybe also gimme feedback on the speed compared to your old version.

Try to use the fixed "keep org. AR settings" button in resize mode and set your player to keep source AR.

bond
23rd March 2004, 21:27
with the overlay mixer problem its important to mention that this bug happens with "overlay mixer2", which is different to "overlay mixer"

Originally posted by Andy2222
Can some1 confirm that choppy (overlay mixer) playback for nvidia cards or does it just happens with ATI card's?i have a nvidia tnt2

Can some1 make a link to a short file wich play's choppy and tell me the exact filter config, ffdshow version, player and stuff wich cause that bug? If we cant reproduce that error it's prolly hard to fix.i am pretty sure that it doesnt depend on the source

as i said i had the problem with xvid (with b-frames with packed bitstream or without) and realvideo content

and

i always had the problem when the decoders used overlay mixer2 (namely ffdshow, 3ivx and gabests realmediasplitter)


maybe shitowax can comment on this problem, as he seemed to have found a way to solve this bug in the 3ivx decoder ;)

Andy2222
23rd March 2004, 21:48
Is there a special reason why u want use overlay mixer2? If i set zoomplayer to costum mode and manualy select the overlay mixer2 as render, i still need select overlay mixer2 in ffdshow and this results in a black screen for me in zoomplayer.

Could it be that bsplay is the only player wich can use overlay mixer2? Since zoomplayer/crystal player and i think mpc all just use OM1?

bond
23rd March 2004, 22:01
well overlay mixer2 is needed for anamorphic encodes and when decoding realvideo with it, it needs far less processor power

Andy2222
23rd March 2004, 22:24
Originally posted by bond
well overlay mixer2 is needed for anamorphic encodes and when decoding realvideo with it, it needs far less processor power

mhhh

MSDN says: "The Overlay Mixer 2 filter is identical to the Overlay Mixer filter, except:

It supports only VIDEOINFOHEADER2 formats."

Since OM1 also support VIH2 u can decode anamorphic as well, dunno why u need OM2 for encodes? Sorry im a total encode noob :)

oki i installed the latest bsplayer and mpc and i could not force to use OM2 over OM1 (i checked the merits and OM2 has indeed a higher merit) but all player installed (bsplayer/zoomplayer/mpc/crystal) all use OM1 in auto mode. I surely set bsplayer to use OM2 but OM1 was still used... How u force your player to use OM2?


"it needs far less processor power"

The only way i could check OM2 was by using graphedit and forced ffdshow to use OM2. I still got no choppy playback (but just tested 2 files) but i tested the CPU usage, but for my Athlon-XP system there is no diff. using OM1 or OM2.

So u realy tested OM2 over OM1 for speed? Im confused now. Since for me OM2 just look like a more compatible mixer for VH2 or player's wich cant correct init OM1+VH2?

bond
23rd March 2004, 22:33
the point is as good as everyone uses "overlay mixer2" when doing anamorphic encodes (even the commercial stuff like 3ivx)
and its buggy

arno
23rd March 2004, 22:38
I get the choppy playback on my Duron 1.2 GHz + ATI Radeon 8500 + BS Player. Note that as far as I know this issue was introduced when the "overlay mixer" option was introduced in ffdshow (although I'm not sure)....

loni_blues
23rd March 2004, 23:42
Hi,

Is there any way to recover ffdshow defaults? Without touching the registry manually, of course.

Thanks for any help,
loni_blues

LigH
23rd March 2004, 23:53
Except "uninstall - reinstall"? Not that I knew...

gitoshi
24th March 2004, 01:05
get the same choppy playback with the test version.
I can reproduce the problem in Celeron 1GHZ (tualatin core)+ Intel 815.


But it is so important using Overlay mixer?
Yes, CoreMediaPlayer only use overlay mixer 2 mode.
Also DVobsub work best with OM2.


G

loni_blues
24th March 2004, 04:31
@ LigH,

I´m sorry and a little ashamed. I´ve just realized that uninstalling - reinstalling did the thing.

Thanks a lot,
loni_blues

dapipa
24th March 2004, 12:51
Originally posted by LigH
Except "uninstall - reinstall"? Not that I knew...

what about saving defaults to file after installing and restoring them when needed?not that it'd help,when you messed up the config already...
:)

Blight
24th March 2004, 17:23
Any reason why Zoom Player should try to use Overlay Mixer 2 if possible? I can probably check the filter to see if it uses VIDEOINFOHEADER2 and then use OM2 and if not use OM1.

Is this a course I should take?

athos
25th March 2004, 11:32
New build today. ffdshow vfw shows up in VirtualDub, I changed it to use the abbreviated win9x path (C:\Progra~1).

Same bat-location, same bat-changelog.

dapipa
25th March 2004, 11:47
Originally posted by Andy2222
If u have an Athlon-XP or Pentium3 and those "choppy" playback can u try this testversion for me pls? get it here: http://mitglied.lycos.de/ieggei2/ffdshow/

hi!i've got an athlon XP and i can confirm,that your build works flawlessly(i think it's the first build after 20030523 which keeps correct AR and hasn't choppy playback,which the latest releases had)...
:)

arno
25th March 2004, 11:51
Originally posted by dapipa
hi!i've got an athlon XP and i can confirm,that your build works flawlessly(i think it's the first build after 20030523 which keeps correct AR and hasn't choppy playback,which the latest releases had)...
:)

I just tried it with BSplayer + overlay mode 2 (mixer) but it still gives me choppy playback on my AMD Duron 1.2GHz (+Radeon8500). Note that I'm not sure where you intended to fix this issue too with this build.

Andy2222
25th March 2004, 14:15
Originally posted by arno
I just tried it with BSplayer + overlay mode 2 (mixer) but it still gives me choppy playback on my AMD Duron 1.2GHz (+Radeon8500). Note that I'm not sure where you intended to fix this issue too with this build.

I played around with some overlay and VH2 settings, but i leak the fully understanding of some parts in ffdshow and some dshow programming skills.

Some1 realy need to mail this bug/issue to milan with some very detailed info's and maybe he can contact shitowax too to fix that.
I realy think this problem is also system/graphic card/directx related?

Problem is i tryed all my xvid/divx files in graphedit and used OM2 and i could not reproduce the choppy playback for my system wich make's me realy useless for fixing that bug.. sorry

shitowax
25th March 2004, 14:50
My understanding of the problem is that:
- it's very related to video card drivers using overlay mixers 2 i.e using VIH2.
- It seems that systems not using overlay mixers like XP or DX9 ones using the new DX9 renderer, don't present this problem.

To fix that, you may have to :
- be sure that all output samples are syncpoints
- be sure of your output timestamps (some splitters don't output either stop or even any timestamp)

If it's not enough, try forcing a discontinuity on all the output samples.

hope that helps.

Originally posted by Andy2222
I played around with some overlay and VH2 settings, but i leak the fully understanding of some parts in ffdshow and some dshow programming skills.

Some1 realy need to mail this bug/issue to milan with some very detailed info's and maybe he can contact shitowax too to fix that.
I realy think this problem is also system/graphic card/directx related?

Problem is i tryed all my xvid/divx files in graphedit and used OM2 and i could not reproduce the choppy playback for my system wich make's me realy useless for fixing that bug.. sorry

CavalloPazzo
25th March 2004, 16:00
In latest build they seems only to work with 2 pass mode (maybe in 1 pass CBR) but not in 1 pass quantizer nor quality mode... In some old build (don't remeber which) instead it worked in these 2 modalities also...mencoder and ffmpeg also ignores that parameter in quality based encoding...I'd really like to encode at constant quantizer with bframe moltiplier actived

Mystiqq
25th March 2004, 16:15
Hi

Ive tryed to get the aWarpSharp to work properly but failed at it.
The screen is green when i turn the aWarpSharp on and changing the chroma mode will just give me different error on screen.
Is there any fix for this?
Anyone here ever got that aWarpSharp to work right?

Thanks in advance.

Cheers...

gitoshi
25th March 2004, 20:01
@shitowax:
To fix that, you may have to :
- be sure that all output samples are syncpoints
- be sure of your output timestamps (some splitters don't output either stop or even any timestamp)


@sysKin
CXvidDecoder::Transform(blahblah)
{
blahblah;
decode_frame_blah(and blah);
more_blah;
if (xvid_frame_type & VOL) { // we had a VOL header, most likely a keyframe
some_more_blah();
pOut->SetDiscontinuity(TRUE); // removing this fixed the problem
}
}


Yeah, the solution has been in page 33 of this threat for years, check sysKin post.