Re: [Audacity-devel] Audacity 1.3.8 mp3 error

[Gale A. <ga...@au...>]

| From "David R. Sky" <dav...@sh...> 
| Fri, 7 Aug 2009 15:30:25 -0700 (PDT)
| Subject: [Audacity-devel] Audacity 1.3.8 mp3 error
> I just installed 1.3.8 - the first thing I tried to do was to listen to an 
> mp3 file I'd listened to in Windows Media Player. (Windows 2000)
> 
> It seemed to be loading the file all right, then exited to the Task Bar 
> without any warning. When I went back into Audacity it again asked me for 
> language preference.
> 
> I assume the first problem above was because I hadn't installed the lame 
> mp3 decoder anywhere, but Audacity didn't ask me where one was installed.
> 
> I installed the Unicode executable file, the first time I've installed 
> from a Unicode file - but there was no other Windows executable installer 
> on the download page at the time I grabbed the file (the day the 1.3.8 
> announcement went out).

The crash is probably because you are running a screen reader. 
Crashing when importing stereo files if a screen reader is running 
was only discovered after 1.3.8 release. See:
http://wiki.audacityteam.org/index.php?title=Known_Issues#Fixed_since_release

As indicated there, we have now fixed this in CVS, so to avoid the 
crash, you want the latest Nightly Build:
http://www.gaclrecords.org.uk/audacity-win-unicode-1.3.9-alpha.zip

Probably the easiest thing for you is to extract the contents of 
that zip directly into your 1.3.8 installation folder, and say yes to
replacing files if Windows asks. 

Audacity doesn't create the audacity.cfg settings file until you exit
cleanly without a crash.  Once it does exit cleanly, you won't be asked
for language on next launch. 

We aren't listing an ANSI installer or zip for 1.3.8 because 1.3.8 no 
longer supports Windows 98/ME, due to our switch to building Audacity
with Visual Studio 2008. There is no point in an ANSI version of 1.3.8 
for 2000/XP/Vista because those are Unicode operating systems. 

I hope we will make one more build for 98/ME which I understand  means
building an  "all-in-one" version with wxWidgets linked in, but therefore
without ability to use wxWidgets plug-ins. I tend to think the best time
to do this may be after 2.0 is out and settled down, when we should have
the greatest chance of a stable version to build against.  


> (From second post)  Same problem as below after I installed a lame .
> .dll file. 

That's because lame_enc.dll is nothing to do with MP3 importing or 
playback, but is an encoder used to write (export) MP3 files. Audacity
already comes with MP3 playback (decoding) built-in. 


> I did get an  error message that an error file was logged somewhere,
> but I couldn't find one in the Audacity folder - where should I look and
> for what file name?

It depends how your system is set up, but most likely that will only be 
appcompat.txt generated by Windows, which probably wouldn't have 
helped deduce anything in this case. 




Gale