Audacity Forum

<<<You've lost me here.>>>

It certainly caught me off-guard.

The idea is to load my short piano trill on the timeline...

http://www.kozco.com/tech/soundtests.html

...select the first musical note by clicking and dragging and then Analyze > Plot Spectrum. Simplicity itself, except it didn't work. I would click and nothing would happen, then drag and the click point would snap left to the next integer. Then I would let go and the exit point would snap to the next higher integer. So my selection of 1.864 to 3.247 would snap to 1 and 4. It took me a good long while to figure out what was happening because I was selecting a really small segment close to Zero and I couldn't see where the left selector went.

I eventually did it in one of the other Audacities...

http://www.kozco.com/tech/audacity/piano_G1.jpg

That's one concert grand piano note.


I'm preparing a triple boot Mac. External bootable FireWire drive with two Leopard OS-X 10.5 installs. I'm going to put 1.3.6 on one and 1.3.7 on the other, so this will represent what's going to happen to anybody buying a new Intel Mac...for a while, at least.

Then put 1.3.5 back on the home drive. I miss that one. It was talented and stable.

This weekend I finally got enough time to build the external drive and put Leopard on it that I bought last week. I must have bought a bit of an older license because it's taking three massive passes at Software Update to get all the OS patches. I have two Macs, so I did email on the laptop while the Mini was grinding away. I have killer DSL (I'm two dog barks away from the phone company central office) and it still took most of the evening to get everything and I don't have Audacity yet.

Koz

kozikowski wrote:<<<You've lost me here.>>> The idea is to load my short piano trill on the timeline...http://www.kozco.com/tech/soundtests.html ..select the first musical note by clicking and dragging and then Analyze > Plot Spectrum. Simplicity itself, except it didn't work. I would click and nothing would happen, then drag and the click point would snap left to the next integer. Then I would let go and the exit point would snap to the next higher integer. So my selection of 1.864 to 3.247 would snap to 1 and 4. It took me a good long while to figure out what was happening because I was selecting a really small segment close to Zero and I couldn't see where
the left selector went.I eventually did it in one of the other Audacities...

Are you sure this isn't just snap-to being on (just to left of selection bar), with the selection format as default (seconds)?

kozikowski wrote:I'm preparing a triple boot Mac. External bootable FireWire drive with two Leopard OS-X 10.5 installs. I'm going to put 1.3.6 on one and 1.3.7 on the other, so this will represent what's going to happen to anybody buying a new Intel Mac...for a while, at least.Then put 1.3.5 back on the home drive. I miss that one. It was talented and stable.

Sounds really good. If you have some time to test, I have some really interesting cases for you to play with, but I'd better start those in separate threads.

Gale

I have one of the two Leopards finished--the one with 1.3.7 on it. You don't remember all the auxilliary stuff you put on a machine to make it homey. Let's see, MacJanitor, FireFox ...

I'll start a fresh new thread when I get both running and I'm ready to start testing. This will be exciting. Two computers that don't do anything else. No competing software or drivers.

Koz

OK. Started the new one.

http://audacityteam.org/forum/viewtopic.php?f=17&t=7677

Koz

ENowlan wrote:When Mac users edit Keyboard shortcuts their preferences do not always get saved as expected. E. g. if I cleared Cmd+S and replaced it with Ctrl+S and click on OK it does not stick and when I come back to edit the key bindings in preferences it is Cmd+S again. If I had set it to Ctrl+Alt+Cmd+S it would now read Cmd+Alt+Cmd+S.

Gale Andrews wrote:The only thing that is going through my mind at present is to hard code all the Mac CTRL shortcuts to Command, but I really don't know if that would work with wxMac or not at the moment.

We have managed to look into this, and at the moment, It seems to be an issue in the Widgets interface toolkit we use - it is not checking for CMD modifiers when it parses the menu text for keyboard accelerators, so can't distinguish between CMD and CTRL. So unless we can work around it in our code somehow, a fix depends on Widgets fixing it.


Gale

Proto Mac

Mac Apple key = Win Ctrl key (though positions are flipped)
The additional modifier key on the mac is usually 'option' (and for one button mice, option-click = right click)
Control is usually more specialized on the mac, for invoking third level font / character functions, for terminal work, etc.