Audacity Forum

That's a good idea. Mine is a little more brutal. I have a external Snow Leopard boot drive -- kept up to date -- and I install the program exactly like a user would. I clean out the program, plugins, and Library preference listings after each install.

Only one Audacity is ever installed on this "machine" at one time. The normal internal boot is a cross of Intel machine and older Tiger OS-X, so it's not as desirable for testing.

The Intel laptop is using Leopard, but that's the one I use for critical location recording, so I try to keep that one as stable and clean as I can.

"If everybody owned a horse, the world would be more stablized." Morey Amsterdam.

Koz

I converted the whole 50 min. 26 second stereo show. -86% tempo and -12% pitch. It took the machine an hour and a half to process, but was still standing when done. And it plays.

Koz

kozikowski wrote:I converted the whole 50 min. 26 second stereo show. -86% tempo and -12% pitch. It took the machine an hour and a half to process, but was still standing when done. And it plays.

Great! I'm a bit surprised at the slowness. Applying those settings to a 44100 Hz stereo track 50 minutes long on Windows 7 1.3.13 took about 80 minutes, even though effects processing has issues of being slow on Windows.

Thanks for the help on that one.


Gale

bgravato wrote: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).

Yes, Bug 44...

bgravato wrote: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. I was running audacity nightly build from withtin the dmg file, if that matters.

If it happens again, please post here.

Thanks for testing.



Gale

I was hoping to test the labels bugs too, but I didn't have the time...
I'm off for camping again this weekend so only monday I'll have some time again.

Have a nice weekend!

I tried to reproduce #30 in 1.3.12-beta but I was unable to. I think I'm not doing the correct procedure to reproduce it...

In step 4 it says:

4. Use shortcut to add label at playback position then hit ENTER to confirm label

What shortcut shall I use to add label?

bgravato wrote:I tried to reproduce #30 in 1.3.12-beta but I was unable to. I think I'm not doing the correct procedure to reproduce it...

In step 4 it says:

4. Use shortcut to add label at playback position then hit ENTER to confirm label

What shortcut shall I use to add label?

The one you normally use, or use Tracks > Add Label at Playback Position. I assume you will have changed the shortcut because if you leave it at default COMMAND - M it will minimise the window as per the global Mac shortcut.

Even if #30 doesn't occur in 1.3.12, I want to be sure it doesn't in the Nightly Build (and that nothing else related to adding labels during playback has broken either).



Thanks


Gale

I never used labels before so... yes the shortcut was set to CMD-M

I changed it to another key and I was able to successfully reproduce the bug in 1.3.12-beta.

I then tried the same in 1.3.13-alpha-Aug 12 2010 and it no longer happens.

I tried #177 but failed to reproduce it in 1.3.13-alpha-Aug 12 2010

The linking button does not exist in 1.3.12 so I can't be sure if it's the bug that is solved or if it's me who's not reproducing it correctly. Gale if you want me to make sure I'm doing it right please point me to a version which has the sync lock function and the bug still active.

bgravato wrote:... yes the shortcut was set to CMD-M ...

Bruno,

actually there are two shortcuts to help you:

1)CMD-M (or CTRL+M in Windows-land) which places a label at the current playback or recording position

2)CMD-B (or CTRL+B in Windows-land) which places a label at the current cursor position

WC