Fraunhofer L3Codec in WMP10 is unlimited

[gastorgrab]

Please update to new version; 04Oct2004

According to Doom9, Windows Media Player 10 includes MP3 codec which is unlimited.



After downloading and unpacking WMP10, i pulled out "L3Codecp.acm", and deleting the rest, I began adding what i though the registry entries should be.

Seems to work just fine on its own. No need to install WMP10!

Here's my INF file; (can be uninstalled from "Add-Remove Programs")
(INF-file last edited 04Oct2004 21:25 Detroit time)

I found an error......&Strings%....that has been fixed.
Updated INF-file should overwrite the prevoius.

; Fhg IIS MPEG Layer-3 Audio Codec v3.3.2.44
; Last edited 04Oct2004 21:25 Detroit time
; NT & 9x


[Version]
Signature = "$CHICAGO$"
Class = MEDIA

[SourceDisksNames]
1="WAGAud",, 0001

[SourceDisksFiles]
L3codecp.acm=1
L3Codecp.inf=1

[Installable.Drivers]
L3codec = 1:L3codecp.acm, "msacm.L3codecp", "Fhg IIS MPEG Layer-3 Codec (Professional)" , , ,

[DefaultInstall]
CopyFiles=WAGAUD.Copy,WAGAUD.Copy.Dec,WAGAUD.Copy. Inf
Updateinis = WAGAUD.Updateini
AddReg = WAGAUD.AddReg,WAGAUD.AddReg.9x,WAGAUD.DoReg
MediaType = SOFTWARE

[DefaultInstall.NT]
CopyFiles=WAGAUD.Copy,WAGAUD.Copy.Dec,WAGAUD.Copy. Inf
AddReg = WAGAUD.AddReg,WAGAUD.AddReg.NT,WAGAUD.DoReg
MediaType = SOFTWARE

[DefaultUninstall]
AddReg = WAGAUD.UnReg
DelReg = WAGAUD.DelReg
DelFiles = WAGAUD.Copy.Inf
UpdateInis = WAGAUD.DelIni

[WAGAUD.Copy]
L3codecp.acm

[WAGAUD.Copy.Dec]

[WAGAUD.Copy.Inf]
L3Codecp.inf

[WAGAUD.UpdateIni]
system.ini, drivers32,,"msacm.L3codec=L3codecp.acm"

[WAGAUD.DelIni]
system.ini, drivers32,"msacm.L3codec=L3codecp.acm",

[WAGAUD.AddReg]

[WAGAUD.AddReg.9x]
HKLM,SOFTWARE\Microsoft\"Windows NT"\CurrentVersion\drivers.desc,L3codecp.acm,,%L3P roAudio%
HKLM,SOFTWARE\Microsoft\"Windows NT"\CurrentVersion\Drivers32,msacm.L3codec,,L3code cp.acm
HKLM,SYSTEM\CurrentControlSet\Control\MediaResourc es\acm\msacm.L3codec,Description,,%L3ProAudio%
HKLM,SYSTEM\CurrentControlSet\Control\MediaResourc es\acm\msacm.L3codec,Driver,,L3codecp.acm
HKLM,SYSTEM\CurrentControlSet\Control\MediaResourc es\acm\msacm.L3codec,FriendlyName,,%L3ProAudio%

HKLM,%UnInstallPath%,DisplayName,,%UninstallDispNa me%
HKLM,%UnInstallPath%,UninstallString,,"%10%\rundll .exe setupx.dll,InstallHinfSection DefaultUninstall 132 %17%\%InfFile%"

[WAGAUD.AddReg.NT]
HKLM,SOFTWARE\Microsoft\Windows NT\CurrentVersion\drivers.desc,L3codecp.acm,,%L3Pr oAudio%
HKLM,SOFTWARE\Microsoft\Windows NT\CurrentVersion\drivers32,msacm.L3codec,,L3codec p.acm
HKLM,SYSTEM\CurrentControlSet\Control\MediaResourc es\acm\msacm.L3codec,Description,,%L3ProAudio%
HKLM,SYSTEM\CurrentControlSet\Control\MediaResourc es\acm\msacm.L3codec,Driver,,L3codecp.acm

HKLM,%UnInstallPath%,DisplayName,,%UninstallDispNa me%
HKLM,%UnInstallPath%,UninstallString,,"%11%\rundll 32.exe setupapi,InstallHinfSection DefaultUninstall 132 %17%\%InfFile%"

[WAGAUD.DoReg]

[WAGAUD.DelReg]
HKLM,SYSTEM\CurrentControlSet\Control\MediaResourc es\acm\msacm.L3codec
HKLM,SOFTWARE\Microsoft\Windows NT\CurrentVersion\drivers.desc,L3codecp.acm,,""
HKLM,SOFTWARE\Microsoft\Windows NT\CurrentVersion\drivers32,msacm.L3codec,,""

HKLM,%UnInstallPath%

[WAGAUD.UnReg]

[DestinationDirs]
DefaultDestDir = 11 ; LDID_SYS
WAGAUD.Copy = 11
WAGAUD.Copy.Inf = 17

[Strings]
L3ProAudio="Fhg IIS MPEG Layer-3 Codec (Professional) v3.3.2.44"
InfFile="L3Codecp.inf"
UninstallDispName="Fraunhofer MP3 Codec (Remove Only!)"
UnInstallPath="Software\Microsoft\Windows\CurrentV ersion\Uninstall\WAGTech_Audio"
MediaClassName="Media Devices"
Mfgname="WAGTech (Wild-Ass-Guess Technologies)"

[LisaB]

Thanks! Great tip! I used it, and it solved my problem.

(i.e., my LameACM encoder can now magically decode MP3's after I re-installed the Fraunhofer codec using your instructions...go figure!)

[erratic]

According to Doom9, Windows Media Player 10 includes MP3 codec which is unlimited.
After downloading and unpacking WMP10, i pulled out "L3Codecp.acm", and deleting the rest, I began adding what i though the registry entries should be.

Seems to work just fine on its own. No need to install WMP10!

Too bad I didn't read your post earlier. I have installed WMP10 a few weeks ago, but the XP MP3 codec was still limited to 56kbps. So I installed the Radium codec (which I have now uninstalled again).

Even if you install WMP10 you still have to install the new Fraunhofer codec separately to get 320kbps. I used your .inf file. It works.

Now I wonder if it would be sufficient to simply replace the old l3codecp.acm (in the system32 dir) with the new one from the WMP10 setup file? Has anyone tried that?

[gastorgrab]

Now I wonder if it would be sufficient to simply replace the old l3codecp.acm (in the system32 dir) with the new one from the WMP10 setup file? Has anyone tried that?

That's exactly what i did. I never installed Windows Media Player 10.

I downloaded the WMP-10 install file and used 7-zip to extract the file "L3codecp.acm".

I had no idea that WMP-10 didn't update the system to allow 320 kbs encoding. I guess that Windows Media Player 10 must access the "L3codec.acm" directly.

------edit-------

Oooohhhh, i see what your saying.

The INF file in the Radium codec SHOULD work to install the same file. Does it have the option to uninstall from "Add-Remove Programs"?

Just dropping the new file in the System32 directory should only require a restart to smooth everything out.

[erratic]

Let me specify my remark: I wonder if it's really necessary to use the .inf file for installing the MP3 codec. I'd like to know what happens if you simply copy the new codec over the old one in the system32 dir, without using an .inf file. Someone who hasn't installed the new codec yet (and hasn't used the .inf install obviously) should try it and report back.
Never mind, though, I'm glad it works.

[hrlslcbr]

Maybe this is a stupid question, but...after installing this codec, I can only use it to encode files, but if I play back any mp3 file, Media player classic uses a different version of the codec (1.50). Is this codec usable for encoding only or it can be used for decoding too?

[Shocker Milwaukee]

Someone who hasn't installed the new codec yet (and hasn't used the .inf install obviously) should try it and report back.

I'll volunteer, but I need bulletproof, step-by-step instructions, as I'm impaired (I won't elaborate). I haven't installed WMP 10 & don't care to. Let me know if there are any takers.

[gastorgrab]

Let me specify my remark: I wonder if it's really necessary to use the .inf file for installing the MP3 codec. I'd like to know what happens if you simply copy the new codec over the old one in the system32 dir, without using an .inf file. Someone who hasn't installed the new codec yet (and hasn't used the .inf install obviously) should try it and report back.
Never mind, though, I'm glad it works.

Do you mean over a Radium Install?

The Radium file is named L3codecp.acm, but the standard Windows file is named L3codeca.acm

Maybe this is a stupid question, but...after installing this codec, I can only use it to encode files, but if I play back any mp3 file, Media player classic uses a different version of the codec (1.50). Is this codec usable for encoding only or it can be used for decoding too?

For playback in Windows Media Player, a DirectShow Decoder is used. The standard decoder for Microsoft is named L3codecx.ax.

This MOD was only intended to allow Encoding / Decoding through VFW-type applications like VirtualDub.



Different files for different purposes.

[erratic]

The Radium file is named L3codecp.acm, but the standard Windows file is named L3codeca.acm

Your .inf file installs l3codecp.acm (3.3.2.44). It's in the WMP10 setup file. I kept it with your .inf file just in case I have to reinstall it later. I don't remember now if I had a l3codecp.acm file in my system32 directory before installing WMP10 and/or using your .inf file. I guess not then, so you can't copy it over the old codec. Forget I asked.

[gastorgrab]

I've reconsidered one thing in the INF-file;



If a person had WMP-10 and wanted to try this INF file, but then decided to uninstall, then the file "L3codecp.acm" would be deleted. (Which would be bad for WMP-10 users)

I'll edit the above so noone has to find out the hard way.
(updated INF-file should overwrite the old)

[hrlslcbr]

@ gastorgrab: Thanks.
BTW...when installing the codec with the *.ini you wrote, the name that appears under "audio codecs" in the device manager is a very strange one... I think it was %L3ProAudio%.
But I changed the name under [WAGAUD.AddReg.NT] in the ini you gave us and it works fine now.

[gastorgrab]

@ gastorgrab: Thanks.
BTW...when installing the codec with the *.ini you wrote, the name that appears under "audio codecs" in the device manager is a very strange one... I think it was %L3ProAudio%.
But I changed the name under [WAGAUD.AddReg.NT] in the ini you gave us and it works fine now.

I noticed it also late yesterday. This INF file was converted from another project and the mistake i made was in the Strings Section;

[Strings]
L3Decoder="Fhg IIS MPEG Layer-3 Codec (Professional) v3.3.2.44"

should have been;

[Strings]
L3ProAudio="Fhg IIS MPEG Layer-3 Codec (Professional) v3.3.2.44"

The "%L3ProAudio%" variable under the "[WAGAUD.AddReg.NT]" should be filled in with "Fhg IIS MPEG Layer-3 Codec (Professional) v3.3.2.44", but the wrong variable was listed in the Strings section (%L3Decoder%).

Sorry! I did update the INF yesterday, as i said, but maybe i should have announced it. Good that it was only cosmetic.

I also made one other change to the INF file.... On uninstall, it no longer deletes the "L3codecp.acm" file, only the INF. I decided that someone who wants to keep WMP-10, and not this mod, would be screwed by uninstalling it.

Anyway, Install the updated INF over the original and you should be good to go.

Here's mine;

[hrlslcbr]

Thanks gastorgrab now it works fine.

[erratic]

Apparently it is possible to replace the old limited codec with the new one without modifying the registry after all. I haven't tried it myself, but this is what I read in the Hydrogenaudio Forums:

No need for a registry hack. Just go to c:\windows\system32 and rename l3codeca.acm to l3codeca.bak. Then copy l3codecp.acm to l3codeca.acm (swaps the professional one in place of the old advanced one). Done.

[BogieV]

Pardon my ignorence but I couldn't get it how to do the trick?

I installed WMP10, havent tried it's MP3 encoding but hoped I can be able to use it externally for my TV PVR software. I couldn though - just like erratic I found I'm still limited to 56k.

Now I see the 2 files in system32 - l3codeca.acm and l3codecp.acm - versions 1.9.0.305 and 3.3.2.44 respectively.

In the sound & media though I see only (advanced) but no (professional) version - why and how can I enable it?

Do I need other than the modified .inf and the l3codecp.acm files?
Thanks in advance!

[erratic]

AFAIK you've got two options:

1. Use gastorgrab's .inf file. Copy it into your system32 folder, right click on it, and select install.

2. Rename l3codeca.acm to l3codeca.bak. Then copy l3codecp.acm to l3codeca.acm.

[BJ_M]

WORKS like a charm -- thanks

[BogieV]

Yeah! Just renamed the l3codecp.acm (simply changed the last letter from "p" to "a").
Now I can record directly in DivX with high quality MP3.
Yuhouo...

[gastorgrab]

Yeah! Just renamed the l3codecp.acm (simply changed the last letter from "p" to "a").
Now I can record directly in DivX with high quality MP3.
Yuhouo...

Can WMP10 still make use of the encoder? (curious)

------detail---------

The INF was originally intended to install only the files; "L3codecp.inf", and "l3codecp.acm" from a directory named "WAGAud". The INF file is copied to the INF directory, the ACM file to the System32 directory (in the case of Win2k-XP, or the System directory for Win98-Me). Registry entries are added for a quick un-install in the "Add-Remove" interface.

If you already have WMP10 and intend to use just the INF file you'll have to browse to the "L3codecp.acm" file in the System32 directory (or System directory for 98-Me).



--------edit-----------

I would suggest, that it would be better to COPY the "L3codecp.ax" to another directory, rename it to "L3codeca.ax", and then move it back (while renaming the original "L3codeca.ax" to "L3codeca.ax.bak").

It can't interfere with any functionality of WMP10 that way.

[gminnick]

Like another person on here, I installed WMP10 also but did not have the additional bitrates in programs like VirtualDub until I ran this INF file. I am curious to know if WMP10 uses the codec without the need for the registry entries that this INF file provides.

Thanks for putting this together. I have been using LAME ACM codec and have not had any problems. So not sure what this will buy me.

Anyone have any thoughts on LAME ACM over this new version in WMP10?

[gastorgrab]

I'm just starting out with WinXP 64-bit edition and i think that i figured out enough to make a *Safe* version to work on it. Now that i know a few of the differences etween 64-bit edition i can start making my own personal tweaks.

Here's #1

; Fhg IIS MPEG Layer-3 Codec (Professional) v3.3.2.44
; Last edited 15dec06 17:45 Detroit time
; For 32-bit codec on WindowsXP 64-bit Edition


[Version]
Signature = "$Windows NT$"
Class = MEDIA

[SourceDisksNames]
1="WAGAud",, 0001

[SourceDisksFiles]
L3codecp.acm=1
L3Codecp_x6432.inf=1

[Installable.Drivers]
L3codec = 1:L3codecp.acm, "msacm.L3codecp", "Fhg IIS MPEG Layer-3 Codec (Professional)" , , ,

[DefaultInstall]
CopyFiles=WAGAUD.Copy.Inf
AddReg = WAGAUD.AddReg
MediaType = SOFTWARE

[DefaultUninstall]
AddReg = WAGAUD.UnReg
DelReg = WAGAUD.DelReg
DelFiles = WAGAUD.Copy.Inf
UpdateInis = WAGAUD.DelIni

[WAGAUD.Copy.Inf]
L3Codecp_x6432.inf

[WAGAUD.AddReg]
HKLM,SOFTWARE\Wow6432Node\Microsoft\Windows NT\CurrentVersion\drivers.desc,L3codecp.acm,,%L3Pr oAudio%
HKLM,SOFTWARE\Wow6432Node\Microsoft\Windows NT\CurrentVersion\drivers32,msacm.L3codec,,L3codec p.acm
HKLM,SYSTEM\CurrentControlSet\Control\MediaResourc es\acm\msacm.L3codec,Description,,%L3ProAudio%
HKLM,SYSTEM\CurrentControlSet\Control\MediaResourc es\acm\msacm.L3codec,Driver,,L3codecp.acm

HKLM,%UnInstallPath%,DisplayName,,%UninstallDispNa me%
HKLM,%UnInstallPath%,UninstallString,,"%16425%\rundll32.exe setupapi,InstallHinfSection DefaultUninstall 132 %17%\%InfFile%"

[WAGAUD.DelReg]
HKLM,SYSTEM\CurrentControlSet\Control\MediaResourc es\acm\msacm.L3codec
HKLM,SOFTWARE\Wow6432Node\Microsoft\Windows NT\CurrentVersion\drivers.desc,L3codecp.acm,,""
HKLM,SOFTWARE\Wow6432Node\Microsoft\Windows NT\CurrentVersion\drivers32,msacm.L3codec,,""

HKLM,%UnInstallPath%

[DestinationDirs]
DefaultDestDir = 16425 ; SysWOW64
WAGAUD.Copy = 16425 ; SysWOW64
WAGAUD.Copy.Inf = 17

[Strings]
L3ProAudio="Fhg IIS MPEG Layer-3 Codec (Professional) v3.3.2.44"
InfFile="L3Codecp_x6432.inf"
UninstallDispName="Fraunhofer MP3 Codec (Remove Only!)"
UnInstallPath="Software\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall\WAGTec h_Audio"
MediaClassName="Media Devices"
Mfgname="WAGTech (Wild-Ass-Guess Technologies)"

This is to enable the 32-bit codec on XP 64-bit edition only! It will allow VirtualDub-Win32 (the standard version) to have the extended options. It will make no difference on VirtualDub x64.

It does appear that 32-bit VFW-ACM codecs can exist on the 64-bit system at the same time. Without a 64-bit version of L3codecp.acm, you options are limited. I can't create a *.inf-file for something that doesn't exist.

***Consider this 'A Work In Progress'.
.

[gastorgrab]

Does Vista use the 32-bit EMU?
.

[gastorgrab]

Here's #2

This one seems to be working for 32-bit version of AC3ACM on XP 64-bit;

AC-3 ACM Codec install file

; AC-3 ACM Codec install file - 15dec06
; Usage: right-click on this file and choose "Install"
; For 32-bit codec on WindowsXP 64-bit Edition

[Version]
Signature = "$Windows NT$"
Class = MEDIA

[Strings]
DisplayNameWin="AC-3 ACM Codec"
UninstallDispName="AC-3 ACM Codec (32-bit)"
UninstallPath="Software\Wow6432Node\Microsoft\Wind ows\CurrentVersion\Uninstall\AC3ACM"
MediaClassName="Media Devices"
mfgname="fccHandler"

[SourceDisksNames]
1=%DisplayNameWin%,"",1

[SourceDisksFiles]
AC3ACM_x6432.inf=1
AC3ACM.acm=1

[DefaultInstall]
CopyFiles = AC3ACM.Copy, AC3ACM.Copy.Inf
AddReg = AC3ACM.AddReg

[DefaultUnInstall]
DelFiles = AC3ACM.Copy, AC3ACM.Copy.Inf
DelReg = AC3ACM.DelReg

[AC3ACM.Copy]
AC3ACM.acm

[AC3ACM.Copy.Inf]
AC3ACM_x6432.inf

[AC3ACM.AddReg]
HKLM,SYSTEM\CurrentControlSet\Control\MediaResourc es\msacm\msacm.ac3acm,Description,,%DisplayNameWin %
HKLM,SYSTEM\CurrentControlSet\Control\MediaResourc es\msacm\msacm.ac3acm,Driver,,"AC3ACM.acm"
HKLM,SYSTEM\CurrentControlSet\Control\MediaResourc es\msacm\msacm.ac3acm,FriendlyName,,%DisplayNameWi n%
HKLM,"Software\Wow6432Node\Microsoft\Windows NT\CurrentVersion\Drivers32","msacm.ac3acm",,"AC3A CM.acm"
HKLM,"Software\Wow6432Node\Microsoft\Windows NT\CurrentVersion\Drivers.desc",AC3ACM.acm,,%Displ ayNameWin%

HKLM,%UninstallPath%,DisplayName,,%UninstallDispNa me%
HKLM,%UninstallPath%,UninstallString,,"%16425%\run dll32.exe setupapi,InstallHinfSection DefaultUninstall 132 %17%\AC3ACM_x6432.inf"

[AC3ACM.DelReg]
; HKLM,SYSTEM\CurrentControlSet\Control\MediaResourc es\msacm\msacm.ac3acm
HKLM,Software\Wow6432Node\Microsoft\AudioCompressi onManager\DriverCache\msacm.ac3acm
HKLM,"Software\Wow6432Node\Microsoft\Windows NT\CurrentVersion\drivers.desc","AC3ACM.acm",,""
HKLM,"Software\Wow6432Node\Microsoft\Windows NT\CurrentVersion\drivers32","msacm.ac3acm",,""

HKLM,%UninstallPath%

[DestinationDirs]
DefaultDestDir = 16425 ; SysWOW64
AC3ACM.Copy = 16425 ; SysWOW64
AC3ACM.Copy.Inf = 17 ; Inf

The only problem with it seems to be that on uninstall it will also kill part of the REG entries for the 64-bit version of AC3ACM. I havn't decided what to do about it.............A person could always reinstall the 64-bit 'AC3ACM.inf' though.

--edit--

The separate Uninstall entries appear like this in 'Add-Remove' list;

.
.

[uncajesse]

Holy crap this inf file is whack.

Try uninstalling the codec from Add Remove Programs, if you dare. I don't recommend doing it because, at least on my system, it deleted ALL of my audio and video codecs.

I've been working on getting them back onto my system, and dealing with cleaning up the codecs showing up in device manager, for like 6 hours now.

Just thought I'd let you know...

[uncajesse]

Lolz... well it's better than MDGx's version. His actually uninstalls ALL video & audio codecs when it tries to install.

[gastorgrab]

The last two *.INF's listed here are clearly marked "For 32-bit codec on WindowsXP 64-bit Edition". It won't work on XP-SP2 version 2002 (32-bit).





WinXP 64-bit edition (version 2003);

.

[uncajesse]

Yeah, I know. I'm talking about the INF on your 1st post.

[gastorgrab]

....it deleted ALL of my audio and video codecs.

....it's better than MDGx's version. His actually uninstalls ALL video & audio codecs when it tries to install

So mine "uninstalled all of your codecs", but it's better than MGDx's because his "uninstalled all of your codecs"?

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

Before the install;





Codec installed;




Codec removed;




After the uninstall;



.

[gastorgrab]

I've done a search for MDGx and i see few complaints about his 'donations to understanding'...........it's mostly praise.

Is it possible that your problems stem from another source?
.

[uncajesse]

Well yeh, certainly my experience with MDGx could have been caused by the initial messup of the INF from this 1st post. And that certainly could have been caused by something "weird" with my install, it is after all an OEM laptop setup. The only "codec pack" that I've ever installed on this computer is ffdshow, stable only, so... who knows.

I have since got back my codecs properly, and figured out how to have them not show up as sound&video devices after the fact. There is still something weird with the audio codecs, being multiples of a random from the list (only to disappear after viewing the properties of the codec) as well as one not showing up randomly. The video codecs list thankfully was not effected in this way. I also had to manually put back the windowsmedia mp3 encoding rates in registry which were removed by MDGx inf.

At any rate, thanks for the attention, I wish I knew more about what really happened so I could diagnose the problem and have you insert a safety routine into your inf, if that is even possible.

oh yeah, regarding the "uninstalling" vs "uninstalling"... yours uninstalled them when i ran the uninstall from the add/remove programs. the MDGx one uninstalled them when i right clicked on the inf --> install. but as i said above, the MDGx weirdness could have been just because of the initial event.