The new forums will be named Coin Return (based on the most recent vote)! You can check on the status and timeline of the transition to the new forums here.
The Guiding Principles and New Rules document is now in effect.
Getting LAME working with VirtualDub [SOLVED]
Ayulin
Registered User regular
Registered User regular
Exactly what it says on the [strike]tin[/strike]topic, I can't get VirtualDub to work with LAME. At all.
I downloaded the LAME 3.98.2 ACM, and extracted it. Then I right-clicked the INF file, and hit Install; Vista pops up a UAC prompt, I hit Allow, and it shows it as copying some files to system32 (I think). Great!
But... LAME doesn't show up in the VirtualDub audio compression dialog.
Any ideas? I'm using Vista 64-bit, but the 32-bit version of VirtualDub (the other codecs I use are only available in 32-bit). Would that have something to do with it?
Right now my workaround is to use VirtualDub to save the audio as WAV (the source is recorded by Fraps, so it should be uncompressed... right?), then stick that WAV into a LAME frontend (to the CLI encoder extracted elsewhere), and using VirtualDub to splice in that resultant MP3. But it's a few extra steps, and a bit of a pain.
It seems like I'm missing something really simple here
I downloaded the LAME 3.98.2 ACM, and extracted it. Then I right-clicked the INF file, and hit Install; Vista pops up a UAC prompt, I hit Allow, and it shows it as copying some files to system32 (I think). Great!
But... LAME doesn't show up in the VirtualDub audio compression dialog.
Any ideas? I'm using Vista 64-bit, but the 32-bit version of VirtualDub (the other codecs I use are only available in 32-bit). Would that have something to do with it?
Right now my workaround is to use VirtualDub to save the audio as WAV (the source is recorded by Fraps, so it should be uncompressed... right?), then stick that WAV into a LAME frontend (to the CLI encoder extracted elsewhere), and using VirtualDub to splice in that resultant MP3. But it's a few extra steps, and a bit of a pain.
It seems like I'm missing something really simple here
Ayulin on
0
Posts
edt posted 2007 Jun 27 10:19
I'm not sure where I should be posting this thread, so please feel free to move it if necessary.
I've been trying to install the Lame ACM encoder on my Vista 64 bit OX but it just won't install properly. I know that I have to use a slightly different method of installing 32bit encoders on a 64 bit OS. I've managed to successfully install Huffyuv and Lagarith (both 32 bit) on my system by:
1. Opening up a command prompt by typing "cmd" in the run box and pressing Ctrl+Shift+Enter (to run as Administrator).
2. Changing directories to sysWOW64 ("cd C:\windows\syswow64")
3. Typing the following (example_path replaced with the actual path to the extracted files), then hit enter: rundll32.exe setupapi.dll,InstallHinfSection DefaultInstall 0 c:\Temp_Folder_Path\codecXXX.inf
I've also tried installing using the conventional method but to no avail. I've even manually added registry entries to the ControlSet and copying the LameACM.acm and LameACM.xml files to the SysWow64 and System32 folders.
I've tried using Lame version 3.97 and Lame 64 bit. Lame 64 bit causes VirtualDub to crash whenever I try to open the Audio Compression settings window. Newer versions of Lame do not have the ACM files.
Any help or suggestions would be much appreciated.
Thanks in advance.
Solution
edt posted 2007 Jul 01 06:33
I finally figured out the problem (after about 8 system restores after each failed installation).
For some reason, Vista had a block on the LameACM.inf, LameACM.acm and lame_acm.xml because the files "came from another computer". How silly... and there were no indication whatsoever that the files were being blocked. I so happened to right click and view the properties of the files and found that they were blocked. I simply "Unblocked" each of the files and installed it by:
1. Opening up a command prompt by typing "cmd" in the run box and pressing Ctrl+Shift+Enter (to run as Administrator).
2. Changing directories to sysWOW64 ("cd C:\windows\syswow64")
3. Typing the following (example_path replaced with the actual path to the extracted files), then hit enter: rundll32.exe setupapi.dll,InstallHinfSection DefaultInstall 0 c:\Temp_Folder_Path\codecXXX.inf
And now Lame shows up as an encoding option in VirtualDub! I wonder how many more of these ridiculous "hidden security features" windows has to waste my time with.
Hope this helps others out there.