Re: [Audacity-devel] Cancel bug (was Re: bugs/rewordings?)

[Vaughan J. <va...@au...>]

Gale Andrews wrote:
>     | From Vaughan Johnson <va...@au...> 
>     | Mon, 29 Oct 2007 13:24:05 -0800
>     | Subject: [Audacity-devel] Cancel bug (was Re:  bugs/rewordings?)
>     | Gale Andrews wrote:
>     | > I can't avoid the impression that Audacity is temperamental between
>     | > different achines (different platforms or not). Look at Vaughan's icons
>     | > issue, greatly increased times on some machines to export MP3s
>     | > compared to 1.3.2, snapping to labels/time zero only works half the 
>     | > time for me.  
>     | 
>     | That's all alarming. Any way we can document it or get confirmation from 
>     | other sources so we can try to address it? Do you get a lot of that kind 
>     | of thing on the -help or forums, i.e., one-off weird behaviors that 
>     | happen only on some individual machines? Of course, we are talking about 
>     | Windows here, primarily. Things like this on Mac or Linux, too?
>
> The issue with very slow MP3 exporting in 1.3.3 has been reported several times
> on Mac as well as on Windows.  
>
> Generally yes we always used to get at least one Windows report a week on 
> -help list of some behaviour that had not been heard of before and which had
> no obvious explanataion. The only one I can recall being mentioned more than 
> once was export resulting in only a few short pieces of the audio being present, 
> the rest being silence, but not as much as to make up for the whole length of 
> track. Running Audacity in compatibility for a previous Windows version cured it
> and may in a few instances cure other one-off problems. It doesn't seem to
> help with my particular one-off issues, and one or two others still appear 
> fleetingly then disappear. For example I generated a click track of 3 minutes 
> yesterday in 1.3.4 rc.02 and got 8% less than asked for (a difference amount 
> I often found in 1.3.3). I undid Click Track and repeated then it worked properly
> and has done since.  It's noted on the watch list to look out for Nyqust 
> generation being of incorrect length. 
>
>
>
> Gale 
>
>
>   

Thanks, Gale. Not sure there's any action to take based on those, but 
thanks for tracking them.

- V