ffdshow 32-bit + 64-bit

[Rebooter]

I wanted to use VirtualDub 32-bit in Windows 7 64-bit, but after searching and trying everything, I can not get the 32-bit LameACM to install so that VirtualDub can see it. I was able to install VirtualDub 64-bit + LameACM 64-bit, and the 64-bit VirtualDub can see it. But now the problem is that I really need to be able to use the ffdshow filters through ffvdub.

Basically what I want to do is be able to use the h264vfw + LameACM + ffdshow filters together in 64-bit Windows.

Is it possible to install both the 32-bit and 64-bit versions of ffdshow together, or would this cause a conflict? Same with 32-bit and 64-bit version of h264vfw and AViSynth?

If I tried to install all 64-bit versions of all the above, I assume this would cause problems with any 32-bit video editing/payback apps?

[Ai Haibara]

I haven't experienced any conflicts (that I'm aware of) having both 32 and 64-bit builds of ffdshow installed under Vista64. Haven't tried the others, though.

(I also have both 32/64-bit versions of VirtualDub on the system, as well as MPC-HC... all works great, although I was never quite able to get subtitles working properly under the 64-bit version of MPC-HC (which is one of the main reasons why I set up the 32-bit versions on the system in the first place... )

[hydra3333]

So, can I install ffdshow 32 bit successfully on Windows Vista 64bit (and after an upgrade, Windows7 64 bit) so that MediaPlayerClassic uses it ? I use that as my standard player.

Is there anything special I have to do to get it to install/work ?

edit: oops meant vista 64bit

[wolfdogg]

i am running into the same exact question, issue. i have 64bit virtual dub, with ffdshow64, and huffyuv 64 bit codecs installed on my win7 ultimate x64 system. i have had bad audio capture problems when using pcm, then i tried other audio compressions, and same problem. i opened up a copy of vdub 32, and am not having these audio issues. my installs are brand new, and there has never been any other codecs installed on this system yet to date.

the easiest thing for me was to just use 32bit vdub to do my captures, and was hoping to use 64bit version for recompression and filtering on the basis that i assume its faster. so now that i go back to 32bit version to do a capture, i dont see the huffyuv codec listen in there(doh my bad), nor the ffdshow codec. so i am about to install the 32bit ffdshow on my system that already has the 64bit version.

furthermore, i had alot of problems getting the lame mp3 codec installed, however, the acm portion of it has worked, which is better to use for me anyway, since i would rather use a lossless, if i can get all the same choices at bit rates/flexibility that the lame mp3 offered. so im fine with this.


---------------------------------------

heres what i did, and what i see now;

i installed the huffyuv64, i installed the lameacm/mp3 32/64 using the cmd prompt rundll method(finally worked for the 64bit version after downloading several different versions), i also installed the lameacm/mp3 32/64 using the right click on .inf method, selecting install (was hoping that would handle the 32 bit version of it), and i installed ffdshow 64bit.

i have not yet installed the 32bit ffdshow, but will shortly and will follow up with a post.

what i see now is on the 32bit vdub in capture mode, under video compression, i dont see ffdshow, or anthing but (no recompression: YUY2), under audio compression nothing but the defaults.

what i see now in the vdub64bit under capture mode is under video compression is the ffdshow codec, with the full suite of codecs, including the huffyuv, and under audio, i have been seeing the 1st that falls after the default to be a blank entry which i assume is the lame mp3, doesnt work, but the next entry is the working lame acm choices, and the rest are the default. so far so good, except for the lame mp3 that i decided to not pursue anymore.

now i will install ffdshow32

[jagabo]

the easiest thing for me was to just use 32bit vdub to do my captures, and was hoping to use 64bit version for recompression and filtering on the basis that i assume its faster.

It won't be significantly faster. The only real benefit of 64 bit Windows/programs is that they can access more memory. VirtualDub doesn't need much memory.

Regarding 64 bit and 32 bit software: All you have to do is keep in mind that 32 bit programs/codecs essentially run in a virtual machine under 64 bit Windows. It's like having a separate 32 bit Windows inside your 64 bit Windows. 64 bit programs only use 64 bit codecs, 32 bit programs only use 32 bit codecs. 32 bit programs can't see 64 bit codecs. 64 bit programs can't see 32 bit codecs.

[wolfdogg]

ok, after installing ffdshow 32, i now see the ffdshow codec in vdub 32bit, and it also shows huffyuv in there too. as far as audio, still dont see the acm, guess thats expected, i need to figure out how i can get teh 32bit lame acm codec installed properly with the 64bit already being installed.

the 64bit vdub still looks teh same, ffdshow is in there, and still has the full suite of codecs installed, and the audio compression entries look the same as my last post as well.

so i will do some testing, and report back if theres any problems, otherwise, looks like it worked.

[jagabo]

32 bit LAMEACM in 64 bit Windows:
https://forum.videohelp.com/threads/271712-Lame-MP3-Encoder-on-Vista-x64#1723154

[wolfdogg]

all is well, the 64bit system seems to work fine with them both installed for me.

The only real benefit of 64 bit Windows/programs is that they can access more memory

i do realize this, and tis not the reason i was posting the difference, i was just posting them incase some configuration files along the lines got messed up. such as vdubs... incase it cross referenced something by using both, as a bug. looks like it held up to the test however.

VirtualDub doesn't need much memory

, thanks for pointing that out, i forgot this, so is the 64bit even worth it? i have seen in the past that its not much for advantage.

64 bit programs only use 64 bit codecs, 32 bit programs only use 32 bit codecs. 32 bit programs can't see 64 bit codecs. 64 bit programs can't see 32 bit codecs.

although this is true, it appears that some are cross compatible. for instance, the lameACM-3.98.4 package. it appeared to me that it was just the way you installed the file as to what portion of the registry it affected, in turn making it one or the other.