Thread: [Audacity-devel] 1.3.12 RC1 source tarballs and Windows builds up on Google Code
A free multi-track audio editor and recorder
Brought to you by:
aosiniao
From: Al D. <bus...@gm...> - 2010-02-24 02:32:00
|
http://code.google.com/p/audacity/downloads/list Is someone else in line to do the Mac builds? - Al |
From: Ed M. <edg...@wa...> - 2010-02-24 13:14:47
|
I just tried both the zip and the installer on Win7 and all went well. Will try on XP later today. --Ed > -----Original Message----- > From: Al Dimond [mailto:bus...@gm...] > Subject: [Audacity-devel] 1.3.12 RC1 |
From: Richard A. <ri...@au...> - 2010-02-24 21:32:38
|
On Tue, 2010-02-23 at 19:34 -0700, Al Dimond wrote: > http://code.google.com/p/audacity/downloads/list Not a big issue, but we don't normally put release candidates on Google Code because we can't delete them (policy by google) and there is only finite space there. I've always used sourceforge's developer web service because it's fairly trivial to put stuff on and take them back off once we have the release: http://sourceforge.net/apps/trac/sourceforge/wiki/Developer%20web Richard |
From: Al D. <bus...@gm...> - 2010-02-24 23:56:58
|
On Wednesday 24 February 2010 14:32:21 Richard Ash wrote: > On Tue, 2010-02-23 at 19:34 -0700, Al Dimond wrote: > > http://code.google.com/p/audacity/downloads/list > > Not a big issue, but we don't normally put release candidates on > Google Code because we can't delete them (policy by google) and > there is only finite space there. I've always used sourceforge's > developer web service because it's fairly trivial to put stuff on > and take them back off once we have the release: > > http://sourceforge.net/apps/trac/sourceforge/wiki/Developer%20web > Alright. I'll keep that in mind. - Al > Richard > > > ------------------------------------------------------------------- > ----------- Download Intel® Parallel Studio Eval > Try the new software tools for yourself. Speed compiling, find bugs > proactively, and fine-tune applications for parallel performance. > See why Intel Parallel Studio got high marks during beta. > http://p.sf.net/sfu/intel-sw-dev > _______________________________________________ > audacity-devel mailing list > aud...@li... > https://lists.sourceforge.net/lists/listinfo/audacity-devel > |
From: Gale A. <ga...@au...> - 2010-02-27 21:09:30
|
| From Richard Ash <ri...@au...> | Wed, 24 Feb 2010 21:32:21 +0000 | Subject: [Audacity-devel] 1.3.12 RC1 source tarballs and Windows builds up on Google Code > On Tue, 2010-02-23 at 19:34 -0700, Al Dimond wrote: > > http://code.google.com/p/audacity/downloads/list > > Not a big issue, but we don't normally put release candidates on Google > Code because we can't delete them (policy by google) and there is only > finite space there. I've always used sourceforge's developer web service > because it's fairly trivial to put stuff on and take them back off once > we have the release: > > http://sourceforge.net/apps/trac/sourceforge/wiki/Developer%20web Actually there is no defining reason not to upload rcs to GoogleCode. They can easily be deleted (I could still delete any 1.3.11 release item if I wished - click the left hand link for the file in the download list, and the delete link is to right of the Search button). Uploading rc's there may even be a good idea, providing we remember not to mark the rc's as featured, and clean them up after release. All the rc's would be in one place, and more visible. Gale |
From: Richard A. <ri...@au...> - 2010-02-24 21:36:55
|
On Tue, 2010-02-23 at 19:34 -0700, Al Dimond wrote: > http://code.google.com/p/audacity/downloads/list Minimal source tarball builds fine for me, looks good. Glad the script works for someone else as well! Richard |
From: Al D. <bus...@gm...> - 2010-02-24 23:43:30
|
On Wednesday 24 February 2010 14:36:50 Richard Ash wrote: > On Tue, 2010-02-23 at 19:34 -0700, Al Dimond wrote: > > http://code.google.com/p/audacity/downloads/list > > Minimal source tarball builds fine for me, looks good. Glad the > script works for someone else as well! > I made a couple changes because we moved from CVS to SVN that I'll check in soon. And I'll note on the wiki that unix2dos and some old versions of automake are required. That's not obvious unless you run the script in verbose mode because in quiet mode stderr is suppressed for many commands (end result: a tarball with bad configure scripts). Other than that, everything worked OK (AFAICT). - Al > Richard > > > ------------------------------------------------------------------- > ----------- Download Intel® Parallel Studio Eval > Try the new software tools for yourself. Speed compiling, find bugs > proactively, and fine-tune applications for parallel performance. > See why Intel Parallel Studio got high marks during beta. > http://p.sf.net/sfu/intel-sw-dev > _______________________________________________ > audacity-devel mailing list > aud...@li... > https://lists.sourceforge.net/lists/listinfo/audacity-devel > |
From: Gale (A. Team) <ga...@au...> - 2010-03-01 05:32:38
|
Just tried the Windows rc1 installer on Windows 7. I installed over 1.3.11 (fine), then uninstalled 1.3.12, deleted audacity.cfg and registry settings then installed again (also fine). My sound setup (such as it is) is that I don't yet have motherboard sound because there is no Win 7 driver available yet. The USB soundcard has a Win 7 driver available, but it always gives install errors, so it's running on Microsoft generic drivers. First thing I noticed when I went into Devices preferences was that DirectSound support has been removed (this is the same on XP, so nothing to do with the sound device). I searched -devel for "DirectSound" in the last three months but couldn't find anything relevant. DirectSound is sometimes the only way people can record overdub on Vista/7 without speed differences between the tracks (or low frequency distortions). Also on XP, DirectSound does give less latency than MME. So can you remind me Al why we took it out please? Back to my story, the soundcard plays fine in Media Player and in Audacity rc1 (and 1.3.11 Release), but both give "error opening sound device" on trying to record. Devices Prefs only shows a microphone input. System mixer has all three input devices already enabled, but changing the mic from "Default Communication Device" to "Default Device" in the system mixer then reveals the other inputs in the Audacity Devices Preferences. However the recording error won't go away, and the XP driver for the sound card (which does install) does not enable recording in Audacity either. The Windows Sound Recorder records OK with any driver. As soon as I install 1.3.10 or 1.2.6 I can record fine in Audacity, so I guess this may be another instance of the 1.3.11+ problem with USB devices not recording correctly (or at all) on some systems. I have no problem on XP. Gale -- View this message in context: http://n2.nabble.com/1-3-12-RC1-source-tarballs-and-Windows-builds-up-on-Google-Code-tp4623309p4652620.html Sent from the audacity-devel mailing list archive at Nabble.com. |
From: Al D. <bus...@gm...> - 2010-03-01 07:25:30
|
On Sunday 28 February 2010 22:32:30 Gale (Audacity Team) wrote: > Just tried the Windows rc1 installer on Windows 7. I installed over > 1.3.11 (fine), then uninstalled 1.3.12, deleted audacity.cfg and > registry settings then installed again (also fine). My sound > setup (such as it is) is that I don't yet have motherboard sound > because there is no Win 7 driver available yet. The USB soundcard > has a Win 7 driver available, but it always gives install errors, > so it's running on Microsoft generic drivers. > > First thing I noticed when I went into Devices preferences was that > DirectSound support has been removed (this is the same on XP, so > nothing to do with the sound device). I searched -devel for > "DirectSound" in the last three months but couldn't find anything > relevant. DirectSound is sometimes the only way people can record > overdub on Vista/7 without speed differences between the tracks > (or low frequency distortions). Also on XP, DirectSound does give > less latency than MME. So can you remind me Al why we took it out > please? > Err... I didn't take it out exactly. Apparently it was never built with DirectSound support on my system. I didn't really know about it... apparently I just have to have the DirectSound SDK installed and it builds automatically. Sorry. I'll add it to the release instructions (it's in the build guide, but not in a part of it that the release instructions ask you to read). This sounds like a pretty severe problem, so I'll post a Windows RC2 tomorrow morning (probably about 16:00 UTC). > Back to my story, the soundcard plays fine in Media Player and in > Audacity rc1 (and 1.3.11 Release), but both give "error opening > sound device" on trying to record. Devices Prefs only shows a > microphone input. System mixer has all three input devices already > enabled, but changing the mic from "Default Communication Device" > to "Default Device" in the system mixer then reveals the other > inputs in the Audacity Devices Preferences. However the recording > error won't go away, and the XP driver for the sound card (which > does install) does not enable recording in Audacity either. The > Windows Sound Recorder records OK with any driver. > > As soon as I install 1.3.10 or 1.2.6 I can record fine in Audacity, > so I guess this may be another instance of the 1.3.11+ problem > with USB devices not recording correctly (or at all) on some > systems. I have no problem on XP. > > If it's not a result of DirectSound not being there I can't test/fix it at all because no audio works on my Windows install at all. I'll check if anything changed in PortAudio for Windows between 1.3.10 and 1.3.11 tomorrow. - Al > > Gale > |
From: Gale A. <ga...@au...> - 2010-03-01 09:58:25
|
| From Al Dimond <bus...@gm...> | Mon, 1 Mar 2010 00:28:53 -0700 | Subject: [Audacity-devel] 1.3.12 RC1 source tarballs and Windows builds up on Google Code > On Sunday 28 February 2010 22:32:30 Gale (Audacity Team) wrote: > > Just tried the Windows rc1 installer on Windows 7... > > First thing I noticed when I went into Devices preferences was that > > DirectSound support has been removed (this is the same on XP, so > > nothing to do with the sound device). I searched -devel for > > "DirectSound" in the last three months but couldn't find anything > > relevant. DirectSound is sometimes the only way people can record > > overdub on Vista/7 without speed differences between the tracks > > (or low frequency distortions). Also on XP, DirectSound does give > > less latency than MME. So can you remind me Al why we took it out > > please? > > > > Err... I didn't take it out exactly. Apparently it was never built > with DirectSound support on my system. I didn't really know about > it... apparently I just have to have the DirectSound SDK installed and > it builds automatically. Sorry. I'll add it to the release instructions Thanks for doing that. I thought possibly this was something done in the code to help our mixer problems. > (it's in the build guide, but not in a part of it that the release instructions > ask you to read). It doesn't really help that it's listed there as "optional" (even though it is). I added a line to win/compile.txt to say that Audacity releases are now built with DirectSound support. > > Back to my story, the soundcard plays fine in Media Player and in > > Audacity rc1 (and 1.3.11 Release), but both give "error opening > > sound device" on trying to record. Devices Prefs only shows a > > microphone input. System mixer has all three input devices already > > enabled, but changing the mic from "Default Communication Device" > > to "Default Device" in the system mixer then reveals the other > > inputs in the Audacity Devices Preferences. However the recording > > error won't go away, and the XP driver for the sound card (which > > does install) does not enable recording in Audacity either. The > > Windows Sound Recorder records OK with any driver. > > > > As soon as I install 1.3.10 or 1.2.6 I can record fine in Audacity, > > so I guess this may be another instance of the 1.3.11+ problem > > with USB devices not recording correctly (or at all) on some > > systems. I have no problem on XP. > > >> >> If it's not a result of DirectSound not being there I can't test/fix it >> at all because no audio works on my Windows install at all. I'll check >> if anything changed in PortAudio for Windows between 1.3.10 and >> 1.3.11 tomorrow. Thanks. MME is default, so recording should work with that API, irrespective. Note that some people on Macs have the same issue with USB devices working in 1.3.10 but not 1.3.11. Gale |
From: Vaughan J. <va...@au...> - 2010-03-02 19:39:08
|
On 3/1/2010 1:58 AM, Gale Andrews wrote: > | From Al Dimond<bus...@gm...> > >> On Sunday 28 February 2010 22:32:30 Gale (Audacity Team) wrote: >> >>> Just tried the Windows rc1 installer on Windows 7... >>> First thing I noticed when I went into Devices preferences was that >>> DirectSound support has been removed ... > >> (it's in the build guide, but not in a part of it that the release instructions >> ask you to read). >> > It doesn't really help that it's listed there as "optional" (even though > it is). I added a line to win/compile.txt to say that Audacity releases > are now built with DirectSound support. > It is optional for people who want to build Audacity themselves, which was the original target audience for compile.txt. For example, I build with ASIO but without DirectSound for use on my machine with an ASIO-supported sound card. ASIO is far lower latency than DirectSound, so no reason to include DirectSound. But definitiely, we should always include it in releases because there are no license restrictions on doing so (unlike ASIO), plus the Vista/7 issues. Thanks, Vaughan |
From: Stevethefiddle <ste...@gm...> - 2010-03-01 17:50:17
|
Unable to run 1.3.12 RC1 on Windows XP. (downloaded today at about 12:00 GMT) Tried both the ZIP and the EXE on two XP machines: ZIP version: C:\Program Files\Audacity 1-3-12 RC1\audacity.exe This application has failed to start because the application configuration is incorrect. Reinstalling the application may fix this problem. EXE version: Unable to execute file: C:\Program Files\Audacity 1.3.12 Beta (Unicode)\audacity.exe CreateProcess failed; code 14001. This application has failed to start because the application configuration is incorrect. Reinstalling the application may fix this problem. No problems so far with 1.3.12 Nightly build. -- View this message in context: http://n2.nabble.com/1-3-12-RC1-source-tarballs-and-Windows-builds-up-on-Google-Code-tp4623309p4655789.html Sent from the audacity-devel mailing list archive at Nabble.com. |
From: Al D. <bus...@gm...> - 2010-03-01 18:40:43
|
On Monday 01 March 2010 10:49:59 Stevethefiddle wrote: > Unable to run 1.3.12 RC1 on Windows XP. (downloaded today at about > 12:00 GMT) > > Tried both the ZIP and the EXE on two XP machines: > > ZIP version: > > > > C:\Program Files\Audacity 1-3-12 RC1\audacity.exe > > This application has failed to start because the application > configuration is incorrect. Reinstalling the application may fix > this problem. > > > > EXE version: > > > > Unable to execute file: > > C:\Program Files\Audacity 1.3.12 Beta (Unicode)\audacity.exe > > CreateProcess failed; code 14001. > > This application has failed to start because the application > configuration is incorrect. Reinstalling the application may fix > this problem. > > > > > No problems so far with 1.3.12 Nightly build. > OK. It looks like for some reason my copy of VS is creating binaries that depend on both versions of the runtime DLL, and your system doesn't have the new one. My project/solution files are currently stock SVN... back when I was messing with them I couldn't figure out why I was still getting old version dependencies and now I can't figure out why I'm getting new ones. Meanwhile Gale's nightlies don't have dependencies to the new version, which is baffling. His VS and my VS take the same input and produce different output. I'm going to try to get rid of this dependency before putting up an RC2; if I can't do it then any Windows builds I produce will be useless. If this was any platform but Windows I'd call the dependency versioning situation "FUBAR". But as far as Windows goes it's merely "SNAFU". Situation Normal: All Fucked Up. - Al |