Testers needed for Mac 1.3.13 Alpha to resolve bug fixes

[kozikowski]

Mac Mini
1.83 GHz Intel Core Duo
2GB memory
Mac OS-X 10.6.4 Snow Leopard
Audacity 1.3.13 Aug 11 2010
Fresh Install. Default values.

35 MP3 files, each about 38 seconds long.

It didn't appear to change at all between the earlier Audacity and 1.3.13. Alpha. The History panel seems to update immediately and not slow the machine at all. I executed 25 edits of deletions and silences and the History kept up with me.

I noticed one difference. The old Audacity would take 2 seconds to gather itself and play that many clips at once when I spacebar. The new one takes only 1.5 seconds.

My two different Mac OS-X installs are on different spinning drives.

I would say I've never experienced this History Delay problem. You suggested there was time to go make a nice Earl Gray while the machine was recovering.

Koz

[kozikowski]

I tried the sliding scale #170.

Screen shot 2010-08-11 at 8.23.00 PM.png (48.06 KiB) Viewed 1240 times

It didn't crash with those settings. I did note that the performance pitch went up a half-tone at the beginning of the effect. It was not zero effect. Does the effect have trouble with 48000 sound clips?

Koz

[Gale Andrews]

Mac Mini
1.83 GHz Intel Core Duo
2GB memory
Mac OS-X 10.6.4 Snow Leopard
Audacity 1.3.13 Aug 11 2010
Fresh Install. Default values.

35 MP3 files, each about 38 seconds long.

It didn't appear to change at all between the earlier Audacity and 1.3.13. Alpha. The History panel seems to update immediately and not slow the machine at all. I executed 25 edits of deletions and silences and the History kept up with me.

Thanks, Koz for your help. We can treat that as fixed then (and not fixed on Mac because it wasn't a problem in the first place).

I noticed one difference. The old Audacity would take 2 seconds to gather itself and play that many clips at once when I spacebar. The new one takes only 1.5 seconds.

1.3.13 does have new code that should at least make it possible to load hundreds or even thousands of tracks (which wasn't possible before). I think it's helped a little too as regards the number of tracks that can be played on a particular system, but there is still a limit of several dozen tracks.


Gale

[Gale Andrews]

I tried the sliding scale #170. It didn't crash with those settings.

Thanks. Would it be possible to test those settings with a longer selection like 30 minutes or so? The length seemed to affect its robustness before.

I did note that the performance pitch went up a half-tone at the beginning of the effect. It was not zero effect. Does the effect have trouble with 48000 sound clips?

Yes thanks, that's known about (Bug 172) and still waiting for Clayton to test and commit a fix.



Gale

[kozikowski]

<<<Thanks. Would it be possible to test those settings with a longer selection like 30 minutes or so? The length seemed to affect its robustness before. >>>

Ummm. Select a one second segment out of a 30 minute or longer show? Or just any segment just so the show is longer?

Koz

[kozikowski]

That is a very seriously disturbing effect.

I pulled up a show at 50 min 26 sec. 44100, 32-bit floating, Stereo and applied -86% tempo and -12% pitch to a 3 min 25 sec. segment and it did it. Audacity did not crash or hang.

I can't listen to that.....

Koz

[Gale Andrews]

I pulled up a show at 50 min 26 sec. 44100, 32-bit floating, Stereo and applied -86% tempo and -12% pitch to a 3 min 25 sec. segment and it did it. Audacity did not crash or hang.

Hi Koz

I meant select all of the longer piece so in this case apply Time Scale with the same settings to the 50 min 26 sec track. If it does that, it should do anything,

I can't listen to that.....

Fortunately, having to listen to it isn't part of the test.



Gale

[bgravato]

I downloaded audacity-nightly-2010.08.12-03.15 on a MacBookPro 2.4GHz Intel Core 2 Duo, 2GB RAM, Mac OS X 10.6.4 Snow Leopard.

Regarding bug #170, I opened a 26 min long mono track.

Selected 10 seconds in middle of it and applied Sliding Time Scale/Pitch Shift with the following options:
- tempo -90 to +150;
- pitch +12 to -12
- sharpening on

It worked fine I think, no crashes. Same with sharpening off

Then I selected 23 min segment in the middle of the 26 total and applied the same effect with those same options.

It took about 9 minutes to process but didn't crash.

[bgravato]

I don't know if this is a known bug but after the previous tests the following happened:

I opened a new track in a new window about 3 minutes long, keeping the other 26 min track still open.

I applied change speed effect to it a couple of times followed by undo. I then applied Sliding Time Scale/Pitch Shift effect to the whole track.

While it was processing the second track I switched to the window of the first track. Tried to click on the track to select or the toolbar buttons but nothing worked to mouse clicks (I think this is normal behaviour when an effect is being applied to a track). Using space bar to start/stop playing worked (this is an interesting behaviour, because when processing effects the interface seems to be blocked to mouse clicks but not to keyboard shortcuts).

After some time the effect applied to the 2nd track had finished (at least the progress bar window had disappeared) but the interface was still unresponsive to mouse clicks, on both windows.

I closed the second track window and it asked me if I wanted to save the file and I said No.

Then after a few seconds audacity crashed and all windows were closed.

I tried to reproduce this but I was unable to. It all worked the same way, except that when the effect was finished all windows' interfaces
would become responsive to mouse clicks agains.

Edit: I was running audacity nightly build from withtin the dmg file, if that matters.

[billw58]

I was running audacity nightly build from withtin the dmg file, if that matters.

Bad idea. You should never run a program from within the dmg file.

If you're playing with the nightly builds, but want to keep the settings separate from your "production" version, this is what I do.
In my Applications folder I have a separate folder named "Audacity 1.3.13". Inside that folder is a "Portable Settings" folder. Drag the entire contents of the dmg into the "Audacity 1.3.13" folder. Replace the previous contents if needed. Audacity will put all of it's settings files (including - most importantly - "audacity.cfg") in the Portable Settings folder.

For testing purposes I have Audacity versions 1.3.8/9/10/11/12 and 13 on my machine. Each has its own Portable Settings folder.

-- Bill