MP3 Export Crash

[Gale Andrews]

I'll roll-back to using 1.2.x/LAME 3.9x and/or using the new version with the WinLAME workaround for now... and Thanks! for the efforts.

OK, though I would be interested to know whether lame_enc.dll 3.98.2 will encode for you in 1.2.6. It is supposed to, and does here. Can you let us know?

Thanks


Gale

[ozboomer]

Hi, again..

OK, though I would be interested to know whether lame_enc.dll 3.98.2 will encode for you in 1.2.6. It is supposed to, and does here. Can you let us know?

Same story. Removed all traces of 1.3.7 (1.3.8 alpha), audacity.cfg, lame_enc.dll, etc -- nothing on the disk. Installed the 'standard' 1.2.6 version and retrieved my 3.97 and your 3.98.2 versions of lame_enc.dll.

Place the 3.97 lame_enc.dll into folders, not immediately recognized... but when browsed and loaded through 'Edit > Preferences", 3.97 library is identified, loaded and works Ok.

Using 3.98.3, nothing works. Not immediately recognized... when browsed to and loaded it remains unrecognized/no library found after loading. Naturally, no MP3 encoding is available.

So, it would seem we're talking about the 3.98.2 LAME may not be built to suit my Windows... hmm...

[...thinks...]

Now, I've just tried installing 1.2.6 and LAME 3.98 on my 'real' PC (Win XP Pro SP2) and guess what - this installation works Ok. Loads 3.98, recognizes it... and uses it on encoding. Shall I bite the bullet..?...

...

Yup. Installing 1.3.7 Beta and the 3.98.2 lame_enc.dll everything works as advertised; finds/identifies the library Ok, encodes clean, etc.

So, it looks like there's something with the un-patched/raw Windows (Win XP Pro, no service packs, no patches) that's causing the grief... or does Audacity and/or lame_enc.dll require .NET Framework to be installed?

Now... What to do about upgrading that silly Windows version... hmm... Sheesh, I don't want to do ANOTHER rebuild of that silly PC -- 2x Windows, 4x Linux + embedded VMS... let alone all the music software... *Dang*.

[Gale Andrews]

OK, though I would be interested to know whether lame_enc.dll 3.98.2 will encode for you in 1.2.6. It is supposed to, and does here. Can you let us know?

Same story. Removed all traces of 1.3.7 (1.3.8 alpha), audacity.cfg, lame_enc.dll, etc -- nothing on the disk. Installed the 'standard' 1.2.6 version and retrieved my 3.97 and your 3.98.2 versions of lame_enc.dll. Place the 3.97 lame_enc.dll into folders, not immediately recognized... but when browsed and loaded through 'Edit > Preferences", 3.97 library is identified, loaded and works Ok.

Using 3.98.3, nothing works. Not immediately recognized... when browsed to and loaded it remains unrecognized/no library found after loading. Naturally, no MP3 encoding is available.

So, it would seem we're talking about the 3.98.2 LAME may not be built to suit my Windows... hmm...

[...thinks...]

Now, I've just tried installing 1.2.6 and LAME 3.98 on my 'real' PC (Win XP Pro SP2) and guess what - this installation works Ok. Loads 3.98, recognizes it... and uses it on encoding. Shall I bite the bullet..?... Installing 1.3.7 Beta and the 3.98.2 lame_enc.dll everything works as advertised; finds/identifies the library Ok, encodes clean, etc.

So, it looks like there's something with the un-patched/raw Windows (Win XP Pro, no service packs, no patches) that's causing the grief... or does Audacity and/or lame_enc.dll require .NET Framework to be installed?

... Thanks, it's what I expected anyway (not a problem with Audacity Beta itself). 1.2.6 is not designed to detect lame_enc.dll manually. So we have a bit more to go on now.


Gale

[magnerj]

ok so here is what i have found.

i tried all the above mentioned solutions and had no luck.

after changing the directory from explorer, and deleting the cfg file several times, i kept getting back the directory name i had changed, which means audacity is likely saving the old file name in the registry somewhere and NOT just in the cfg file.

really being p.o.d. i went and just deleted every reference in the registry of the directory name it kept trying to reference as a location even though it had been changed and i had tried to browse to a different one several times and make that link...

after that audacity would then try and use a location with not path but just the lame_enc.dll name! it totally forgot the path even when i would try and put it in the cfg and it would be in the cfg....

so..................the problem is in how this version of audactiy is dealing with the windows registry.......or maybe NOT using the cfg file correctly.

fun and games in i have to go to bed land - jlm

[Gale Andrews]

magnerj, if you have ever used Audacity 1.2, there are Audacity settings in the Windows Registry (not otherwise). I have an older version of lame_enc.dll used by 1.2 (so the path is in the Registry), plus the correct version for 1.3.7 in Program FilesLame for Audacity, where Audacity autodetects it as intended without having to browse for it in the "Locate LAME" dialogue. Therefore there is no [MP3LibPath] in the .cfg file at all.

But, cfg can get tangled especially if you are playing around editing it. I suggest you reset 1.3 Preferences properly by exiting Audacity, removing all content from audacity.cfg except "NewPrefsInitialized=1" and saving the changes. Then get rid of all copies of lame_enc.dll from your computer and install LAME again.



Gale

[Gale Andrews]

So, it looks like there's something with the un-patched/raw Windows (Win XP Pro, no service packs, no patches) that's causing the grief... or does Audacity and/or lame_enc.dll require .NET Framework to be installed?

Someone else on a fully patched Windows XP SP3 system had the same problem and helped us debug. To cut a long story short, removing the embedded manifest:

<assembly xmlns="urn:schemas-microsoft-com:asm.v1"
manifestVersion="1.0">
  <dependency>
    <dependentAssembly>
      <assemblyIdentity type="win32" name="Microsoft.VC80.CRT"
version="8.0.50727.762" processorArchitecture="x86"
publicKeyToken="1fc8b3b9a1e18e3b"></assemblyIdentity>
    </dependentAssembly>
  </dependency>
</assembly>

from the 3.98.2 dll made it work for him. Would you (and anyone else with this issue) like to try it? It's here. Rename it to lame_enc.dll obviously.

Se we are figuring that removing the manifest means that lame_enc.dll can then use the runtime that was loaded at the start of the session without there being version conflicts. Audacity and the dll shouldn't in themselves require Microsoft.NET (or any specific version of it).

The bad news seems to be that the manifest-removed dll creates errors in Audacity 1.2.6, so if we can't work round that, we won't be able to offer this dll as a general replacement. We'll just have to keep this one for the very small number of cases where our dll has a problem.


Gale