Page 2 of 4

Re: Testers needed - Considering "fix" for CTRL and CMD fias

Posted: Wed Dec 31, 2008 10:04 pm
by kozikowski
I'm going to have to lie down for a minute. I never noticed those other services were behaving oddly.

<<<After the nightly build tonight>>>

Whose tonight, or tonight where? Do these go up tagged GMT?

Koz

Re: Testers needed - Considering "fix" for CTRL and CMD fias

Posted: Wed Dec 31, 2008 10:09 pm
by Leland
kozikowski wrote:I'm going to have to lie down for a minute. I never noticed those other services were behaving oddly.

<<<After the nightly build tonight>>>

Whose tonight, or tonight where? Do these go up tagged GMT?

Koz
Actually, to be honest, I'm not sure exactly when Paul has it scheduled for. I know the file dates are usually between 9 and 10pm and I think the servers that host my stuff are in Texas, so that would put it in the Central time zone.

Leland

Re: Testers needed - Considering "fix" for CTRL and CMD fias

Posted: Thu Jan 01, 2009 1:03 am
by kozikowski
Cool. I have enough fingers and toes to convert from there to LA time.

Koz

Re: Testers needed - Considering "fix" for CTRL and CMD fias

Posted: Thu Jan 01, 2009 5:08 am
by kozikowski
Mac Mini 1.83 GHz Intel Core Duo, 2G memory
Mac OS-X 10.5.6
Audacity 1.3.6a6 48000 KHz, 16 bit
Sound Clip piano2.wav from
http://www.kozco.com/tech/soundtests.html

Audacity 1.3.6a6 31 DEC??

The test action is to launch Audacity, open up piano2.wav, do a complete noise removal cycle, undo it, and close Audacity.

It took forever.

I opened Audacity multiple times and each time got different symptoms and never once completed the test cycle. SpaceBar Play fails, Apple-A (select all) fails, Timeline deselected at an odd time, Edit > Can't UNDO, Quit is gray. They didn't all happen on the same pass. It's like fixing a really old car. Replace the engine and the transmission falls out.

I restarted the machine and it went through the whole test cycle perfectly and absolutely correctly in one pass.


When I launch Audacity from the /Applications folder (I don't use a doc shortcut), I get the Exploding Audacity animation followed by two exploding outline animations. Most applications give me one of something, either the exploding outlines or the exploding icon. So something already isn't normal as the program is launching.


I have Audacity 1.3.7 on a different boot partition. What should I do with that? Was that a pre-a alpha test? It can live there for a while if it's convenient.

Koz

Re: Testers needed - Considering "fix" for CTRL and CMD fias

Posted: Sun Jan 04, 2009 8:35 pm
by Leland
kozikowski wrote:Mac Mini 1.83 GHz Intel Core Duo, 2G memory
Mac OS-X 10.5.6
Audacity 1.3.6a6 48000 KHz, 16 bit
Sound Clip piano2.wav from
http://www.kozco.com/tech/soundtests.html

Audacity 1.3.6a6 31 DEC??

The test action is to launch Audacity, open up piano2.wav, do a complete noise removal cycle, undo it, and close Audacity.

It took forever.

I opened Audacity multiple times and each time got different symptoms and never once completed the test cycle. SpaceBar Play fails, Apple-A (select all) fails, Timeline deselected at an odd time, Edit > Can't UNDO, Quit is gray. They didn't all happen on the same pass. It's like fixing a really old car. Replace the engine and the transmission falls out.

I restarted the machine and it went through the whole test cycle perfectly and absolutely correctly in one pass.
Can you try this with one of the nightly builds? Actually, can I ask that you do all of your tests with at least the nightly that will come out tomorrow.

We know there's problems with the 1.3.6 release and we've probably fixed at least some of them in the nightlies...basically, the nightlies can't be any worse than the 1.3.6 version (or rather...shouldn't ;-))
When I launch Audacity from the /Applications folder (I don't use a doc shortcut), I get the Exploding Audacity animation followed by two exploding outline animations. Most applications give me one of something, either the exploding outlines or the exploding icon. So something already isn't normal as the program is launching.
This will be fixed in tonight's nightly build. It actually wasn't a functionality problem, but it sure did look kind of bogus didn't it. Been doing that for a while, but I just never bothered to look into it.
I have Audacity 1.3.7 on a different boot partition. What should I do with that? Was that a pre-a alpha test? It can live there for a while if it's convenient.
If you got that one from the nightly build site, then you're probably already out of date. :-) I've been addressing several things lately and you may find it useful to download the latest night every so often.

Leland

Re: Testers needed - Considering "fix" for CTRL and CMD fias

Posted: Mon Jan 05, 2009 1:58 am
by kozikowski
One other item. Gale's been solving file export issues with me in 1.3.6x and you've been stamping out structural issues in 1.3.7x. That's why I've been keeping two clean partitions. Shouldn't y'all be in the same build?

Is that how you're keeping the different patches straight? Then merge later.

Koz

Re: Testers needed - Considering "fix" for CTRL and CMD fias

Posted: Mon Jan 05, 2009 3:50 am
by Leland
kozikowski wrote:One other item. Gale's been solving file export issues with me in 1.3.6x and you've been stamping out structural issues in 1.3.7x. That's why I've been keeping two clean partitions. Shouldn't y'all be in the same build?

Is that how you're keeping the different patches straight? Then merge later.
Actually, Gale isn't even running on a Mac, so I suspect he's just using the same version as you to be able to help properly. He's pretty damn good about that sort of thing. Just the other day I'd made a change to an external library and he actually tested it with Audacity 1.1.0!!!

But, he'll have to answer you to be sure.

Personally, I pretty much deal with current CVS HEAD since that's where all the development works takes place. The "1.3.7" version is the one that'll be coming out shortly and, since I just got back into it, I have a heap of "Mac only" types of problems that I'm trying to tackle before release.

Leland

Re: Testers needed - Considering "fix" for CTRL and CMD fias

Posted: Mon Jan 05, 2009 4:12 am
by kozikowski
============================================
Mac Mini 1.83 GHz Intel Core Duo, 2G memory
Mac OS-X 10.5.6
piano2.wav 16-bit Integer (Little Endian), Stereo, 48.000 KHz.
http://www.kozco.com/tech/soundtests.html
===========================================

audacity-macosx-1.3.7-alpha dated 5 JAN 09

The exploding graphics problem is licked. If the program is launched from /Applications, one exploding icon is visible. If the program is launched from the tool bar shortcut, no explosions are visible which is consistent with all the other applications.

Explosions within the program seems to be correct and consistent although I didn't check everything.

========================
Launch Audacity fresh. Open piano2.wav. The music arrives unselected, no yellow halo, and no Space Bar play.
Click inside the timeline and everything starts working.
========================


Illustration for Gray Quit during MP3 export.
http://www.kozco.com/tech/audacity/GrayQuit.jpg

Koz

Re: Testers needed - Considering "fix" for CTRL and CMD fias

Posted: Mon Jan 05, 2009 4:24 am
by Leland
kozikowski wrote:============================================
Mac Mini 1.83 GHz Intel Core Duo, 2G memory
Mac OS-X 10.5.6
piano2.wav 16-bit Integer (Little Endian), Stereo, 48.000 KHz.
http://www.kozco.com/tech/soundtests.html
===========================================

audacity-macosx-1.3.7-alpha dated 5 JAN 09

The exploding graphics problem is licked. If the program is launched from /Applications, one exploding icon is visible. If the program is launched from the tool bar shortcut, no explosions are visible which is consistent with all the other applications.

Explosions within the program seems to be correct and consistent although I didn't check everything.
Excellent. It was definitely "ugly".
========================
Launch Audacity fresh. Open piano2.wav. The music arrives unselected, no yellow halo, and no Space Bar play.
Click inside the timeline and everything starts working.
========================
Ah yes. Now I see what you mean. You can even just switch to some other application and come back to Audacity and the halo magically re-appears. I'll take a look.
Illustration for Gray Quit during MP3 export.
http://www.kozco.com/tech/audacity/GrayQuit.jpg
That's standard modal dialog graynesses. But, didn't you also say something about if if go over to your desktop and come back to Audacity, they are no longer gray?

Leland

Re: Testers needed - Considering "fix" for CTRL and CMD fias

Posted: Mon Jan 05, 2009 4:42 am
by kozikowski
<<<Ah yes. Now I see what you mean. You can even just switch to some other application and come back to Audacity and the halo magically re-appears. I'll take a look.>>>

I didn't pile up enough actions to derive a rule. The yellow halo just seemed to come and go at random. I have seen SpaceBar Play work without the yellow halo. What's the difference?


<<<That's standard modal dialog graynesses. But, didn't you also say something about if if go over to your desktop and come back to Audacity, they are no longer gray?>>>

I clicked on the desktop to get rid of the File dialog box.

So the gray Quit in that instance is normal. Works for me. However, I don't remember the version.....but when I came back to the export dialog box, Export failed...but only sometimes. I'll see if I can recreate that in the current version.

Koz