Re: [Audacity-devel] Windows pre-release internal 1.3.4 installers

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

    | From Vaughan Johnson <va...@au...> 
    | Sat, 06 Oct 2007 13:03:35 -0700
    | Subject: [Audacity-devel] Windows pre-release internal 1.3.4 installers
    | Gale Andrews wrote:
    | "http://audacity.sourceforge.net/latest/audacity-win-unicode-1.3.4rc0.0.exe".
    | "http://audacity.sourceforge.net/latest/audacity-win-1.3.4rc0.0.exe".
    | >
    | > I get an immediate crash when I launch either of those (either from within 
    | > the folder I installed to, or if I put the installed executable in the
    | > folder I
    | > normally run 1.3.3 from). I only have Dr Watson. Has anyone else got this 
    | > problem, or do you want me to get GDB and see what it reports? 
    | >
    | They both work fine for me, and I compared the downloads to what I 
    | uploaded and they're identical. So yes, any further info would help.

Audacity 1.3.3 was launching fine but 1.3.4 wasn't. I deleted audacity.cfg
but Audacity 1.3.4 was still failing to launch.   

As far as my brain could tell you need Cygwin to run GDB on Windows
so I stopped with Dr.Watson which was flagging up asio2ks (a generic 
ASIO driver for Windows):
http://www.asio2ks.de/

When I went to the ASIO2ks control panel I could see I had ASIO turned on
for the inbuilt sound device, but not for the USB sound device. Windows (and
Audacity, now that audacity.cfg was reset) was defaulting to the USB sound 
device, and before reset, Audacity preferences were explicitly set to the USB
device. I turned off ASIO for the inbuilt sound device, then 1.3.4 launched fine.   
I must admit I'm not sure what this means, given that 1.3.3 had no problem
with the ASIO2ks setting and I have always presumed simply doesn't see it 
and ignores it. 


Gale  

 




Outbound message virus free.
Tested on: 10/7/2007 5:46:52 PM