Just to help John get his problem squared away, I want to point out that
John's problems are actually with a Mac running OSX. In an earlier post,
John put this near the bottom:
>Running OS 10.3.4 (earlier had mistakenly said X.2) on a blue and white
>G3; 500 megs memory, plenty of free disk space.
And the puzzling thing about is that an earlier Audacity version seems to
have worked quite well for him, but whether that was before 10.3.4 or not I
cannot say -- we'll have to ask John. Seems that latest version of OSX
hasn't been out for very long, though, so perhaps that's a clue, too --
maybe something has changed in 10.3.4 that exacerbates problems for his
At 12:13 PM 6/25/2004 -0700, you wrote:
>John, I've seen several of your postings, and I think I recall you're on
>Windows, but I can't replicate the problem. On my systems, the release
>version has the same performance characteristics as the pre3. The only
>times I've seen significant slow-down is when I've been doing lots of
>edits & put up the History window -- but that happens on both pre3 & the
>release. It sounds like a memory shortage problem. Do you have something
>in place that limits the amount of memory available to the release
>version, or its priority?
>Sorry I can't help, but I want to let you know that the developers are
>seeing your postings. Thanks for your persistence.
>FWIW, I can't replicate the reported failure on recording after about an
>hour, either, even though it's been reported a few times for Windows users.
>>From: John Mayer <johnfmayer@...>
>>Subject: [Audacity-users] Interface Problems
>>My last posting on the matter of the unresponsive interface in 1.2.1
>>never made the last posting, but I'm not giving up. I'm really only
>>trying to help...
>>I'd reported that all aspects of the interface: buttons, menu commands
>>and keyboard equivalents, barely worked most of the time. Usually I'm
>>permitted the initial recording and one edit; then all commands are
>>grayed out. A long, long wait will restore everything to functionality -
>>for one edit, then back to non-function. It seemed that the interface
>>works, but in some kind of extreme slow motion.
>>I've recently observed, though, that if I start Audacity with no other
>>apps running it does pretty well, maybe with just a slight lag, but
>>usable. However, if I start it with other apps running it is
>>non-functional as above; shutting down all other apps at that point
>>doesn't help. I must quit Audacity and restart with, as I said, all apps
>>still off to make it functional.
>>I didn't have this trouble with the Pre3 version.
>>Does this info help in the diagnosis?
>This SF.Net email sponsored by Black Hat Briefings & Training.
>Attend Black Hat Briefings & Training, Las Vegas July 24-29 - digital self
>defense, top technical experts, no vendor pitches, unmatched networking
>opportunities. Visit http://www.blackhat.com
>Mailing list: Audacity-users@...
>To UNSUBSCRIBE, use the form at the bottom of this web page:
:::::::: 3D & 2D computer graphics Electronic Guitar ::::::::
::::: OFP A:M OSX Audacity Photoshop Roland VG88 ::::::