ffdswhow not showing as a possible compression codec in vfw

[radorn]

Hello:

I'm really sorry if this was already posted somewhere somewhen, but I searched the forums for about 2 hours without finding anything that would solve my problem.

The only post I found about this matter didn't help either.

I'm trying to encode things with ffdshow in virtualdub and other vfw apps, but the last beta version won't show up for selection. A couple of months ago the guy of the post I found had the same problem. He was told to edit some entry on the windows registry (wich I searched for without finding), but he ended up installing a previous version of ffdshow wich had the vfw interface working properly (yes, i tried that too, and it DOES work, but I want the NEWEST version)

I guess this error is due some misconfiguration done by the installer, so if anyone knows how to get this working (the registry entries to edit or whatever) I would be really thankful.

[celtic_druid]

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Drivers32\VIDC.ffds, change the program files to progra~1 and yes it is a problem with the installer.

You could also try a newer version, for a while now ffdshow has used a vfw wrapper which goes in the sys folder.

[radorn]

thanks for your answer, i'll try it now.

there's no newer version compiled in SF, but I ended up picking the last cvs build from you page (wich I discovered just yesterday :D), but I was interested in the "official" build for it has sse2.

Your build DOES show up as vfw (well, not that I'm telling anything new to you, hehehe), but since I'm on a p4 I guess the sse2 build would improve performance for me.

Well, enough chit-chat.

Thanks for your time :)

[celtic_druid]

Actually my build was mostly compiled with ICL8.1 so it should be pretty fast on a P4. Be interested to see what the exact speed difference is.

[radorn]

Originally posted by celtic_druid
Actually my build was mostly compiled with ICL8.1 so it should be pretty fast on a P4. Be interested to see what the exact speed difference is.

huh, not that I am the benchmark-man really, don't think I can help. But I'll let you know if you are interested in anything I could come up with.

See you

[radorn]

Originally posted by celtic_druid
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Drivers32\VIDC.ffds, change the program files to progra~1 and yes it is a problem with the installer.

I found that key, it's a REG_SZ that says "ff_vfw.dll". also, I am from spain, so I use a spanish version of windows, were the "program files" dir is "archivos de programa" (lousy translation really, made for the purpose, I think, of "easening" the learning task for the non-techy or non-english speakers, wich in turn ends up overcomplicating things for the techy user. it would be a lot better a unix like name like "bin" or at least "program"/s and that it would be the same for all windows versions or any other universal name. After all, even if they translate the program files dir name, "Documents and settings" still has the english name and not "Documentos y configuraciones", or something like that, as it should be in their logic), so it would be "archiv~1" in any case, but I don't know where are you telling me to put that.

Are you telling me substitute that key, "ff_vfw.dll", for the actual path to the dll in DOS style?

I'm sorry for the inconvenience.

[celtic_druid]

If you get ff_vfw.dll then it should be the VFW wrapper and no path should be required.

When ffdshow used ffdshow.ax in program files/archivos de programa for VFW the installer was supposed to use the short name for the vid.c entry however in the latest sourceforge.net build it doesn't.

Now that we are on the whole Spanish track... I have a mate who just changed his name to James Jesus, now would I be correct in calling him Diego Jesús?

[radorn]

huh? I'm a bit lost here. are you saying ffvfw is just a wrapper for the ffdshow filter you have installed?

I may be wrong in light of what you are telling me, but I perceived ffvfw like a standalone vfw filter on its own, and not a "interface" to the dshow binary you may have installed.

please, explain this fuss to me.

[celtic_druid]

There was ffdshow and ffvfw.
Then ffvfw was merged back into ffdshow and there was just ffdshow.ax.
Now there is a VFW wrapper for ffdshow, so there is a small dll in your sys folder that points to ffdshow.ax.

Guess maybe rather than a recent version of ffdshow you had an old version of ffvfw.

There is also an ACM wrapper by the way.

[radorn]

I had ffdshow (last "stable", last "official" beta and your last build) and I had also ffvfw, of wich I only know the existence of the last build by Milan Cutka.

Well, it doesn't matter now, I dumped all the old stuff in favor of just the last beta from sf and your cvs build. I use your's mainly, but have the offcial one just in case.

I don't normally use ACM, but I allways like to play with these things just for fun. I have googled for it but haven't found anything. It would be really nice if you told me where to find that little wonder :D

And anyways, BIG THANKS for all your time and explanations. You were really nice :)

[celtic_druid]

As far as I know ffdshow only uses ACM for decoding and I am not sure what formats.

[radorn]

I see. You provided interesting details to me. Thank you!

[NoX1911]

ffdshow-20050216.exe

I set ffdshow to raw video (vfw+video) but cannot use the selected ffdshow filters as preprocessors in virtualdub. ZoomPlayer works though.
Any solution for this?

Edit: It doesn't work the way i wanted it to be... I finally found out it's an own filter in vdub. I thought ffdshow could affect every output even the previews in vdub...

[Leak]

Originally posted by HeldImZelt
Edit: It doesn't work the way i wanted it to be... I finally found out it's an own filter in vdub. I thought ffdshow could affect every output even the previews in vdub...

It can affect every output via DirectShow - but VirtualDub uses the legacy VfW interface instead.