Audacity Forum

And, as it happens, because for some reason, it didn't work for me.

1) Place music bed as first track vertically in workspace.
2) Assemble all voice clips into the second track.
3) Select first track by clicking on control panel; observe that the entire track is selected.
4) Choose Effects->Auto Duck.
5) Accept defaults, click OK.
6) Note that no discernable progress dialog comes up.
7) Observe by playback that the music bed on track 1 was not ducked.

Did we mean "select the audio in the music bed track", which is different from "select the track"? Or is something else wrong.

[ Tries it, cause Gale is going to ask ]

Yup. Selecting the track is insufficient; you must doubleclick in the audio field. Ok; lessee how it sounds.

It's not bad. Having to rerender whenever you move something is annoying, but only mildly so.

Tnx.

Baylink wrote:And, as it happens, because for some reason, it didn't work for me.

1) Place music bed as first track vertically in workspace.
2) Assemble all voice clips into the second track.
3) Select first track by clicking on control panel; observe that the entire track is selected.
4) Choose Effects->Auto Duck.
5) Accept defaults, click OK.
6) Note that no discernable progress dialog comes up.
7) Observe by playback that the music bed on track 1 was not ducked.

Did we mean "select the audio in the music bed track", which is different from "select the track"? Or is something else wrong.

[ Tries it, cause Gale is going to ask ]

Yup. Selecting the track is insufficient; you must doubleclick in the audio field. Ok; lessee how it sounds.

I don't know what documentation you are quoting but if that is a direct quote it isn't http://manual.audacityteam.org/o/man/auto_duck.html.

Clicking outside a control in the audio track control panel selects all the audio in the track. Double-clicking in the waveform selects all the audio in the clip you click in. So if you have separate clips, double-clicking does not select all the track.

On http://manual.audacityteam.org/o/man/auto_duck.html "Select" in "Select the track(s)" is a link. You can click the link to see how to select.


Gale

steve wrote:

Baylink wrote:I'm a documentation guy; I think that everything we know about a program should be in the manual.

Fantastic, (and yes I agree that the manual should be comprehensive).
As you will no doubt appreciate, documenting Audacity is a huge task, so volunteers to help with the task are always welcome. Do you want to volunteer?

For that task, absolutely.

Gale Andrews wrote:

Baylink wrote:Did we mean "select the audio in the music bed track", which is different from "select the track"? Or is something else wrong.

[ Tries it, cause Gale is going to ask ]

Yup. Selecting the track is insufficient; you must doubleclick in the audio field. Ok; lessee how it sounds.

I don't know what documentation you are quoting but if that is a direct quote it isn't http://manual.audacityteam.org/o/man/auto_duck.html.

Clicking outside a control in the audio track control panel selects all the audio in the track. Double-clicking in the waveform selects all the audio in the clip you click in. So if you have separate clips, double-clicking does not select all the track.

Well, perhaps I am missing something, but the result I get from clicking on the 'background' of the control panel for the music bed track does not show the *audio* being highlighted as selected, though the control panel itself is highlighted, and when I did it that way, I got no progress dialog, and no ducking. I had to double-click-select the actual audio in the track for it to work.

I gather that's not how it's supposed to work, then?

[ For the record: I am pretty sure I was reading the included local doco, from the Help menu link ]

Baylink wrote:Well, perhaps I am missing something, but the result I get from clicking on the 'background' of the control panel for the music bed track does not show the *audio* being highlighted as selected,

Shift + Left Click will toggle the track selection.
Use Shift + Left Click on each track to select multiple tracks.

Other ways to select audio are described here: http://manual.audacityteam.org/o/man/au ... ction.html

Well, I clicked at a different spot in that non-control-widget part of the pane, but yes, it did a "darken the entire control area and outline the track". It just didn't *darken the audio waveform area* to denote that that was also selected, and it, presumably therefore, didn't duck it.

I am wondering if there's a possibility that I have a bad build, a bad install, or a 10.10.0 incompatibility; I've had a number of crashes on this machine -- Audacity has never crashed on me on any other platform.

I just caught the 10.10.2 upgrade; I will report if anything's better behaved.

Baylink wrote:

steve wrote:

Baylink wrote:I'm a documentation guy; I think that everything we know about a program should be in the manual.

Fantastic, (and yes I agree that the manual should be comprehensive).
As you will no doubt appreciate, documenting Audacity is a huge task, so volunteers to help with the task are always welcome. Do you want to volunteer?

For that task, absolutely.

Which is "that" task ? Do you want to be signed up with an account on the Manual?

Gale

Baylink wrote:Well, I clicked at a different spot in that non-control-widget part of the pane, but yes, it did a "darken the entire control area and outline the track". It just didn't *darken the audio waveform area* to denote that that was also selected, and it, presumably therefore, didn't duck it.

I am wondering if there's a possibility that I have a bad build, a bad install, or a 10.10.0 incompatibility; I've had a number of crashes on this machine -- Audacity has never crashed on me on any other platform.

Have you ever said what version of Audacity you have? See Audacity > About Audacity... . Audacity 2.0.6 does not officially support Yosemite.

Some people find Audacity crashes on Yosemite when saving a project, or just after starting a new one. Does that sound like your crashes?

If you were able to use the latest -alpha build (if you are not already doing so) that might help us diagnose the problem. It's the latest build at the top of http://www.audacity.homerow.net/index.p ... order=desc. Those latest builds "should" be almost release-worthy, so should be no more risk than 2.0.6, perhaps even less.

If you have any crash reports from either 2.0.6 or 2.1.0-alpha, please post them. They should be at /Library/Logs/DiagnosticReports/. I would suggest starting a new topic about "Yosemite crashes".

Thanks

Gale

Well, y'know, yeah, I did, but it was at the beginning of the help thread that spawned this one, not this one proper. I am on 2.0.6, yes, as it was the most recent release; I don't remember seeing any warnings near the download that it wasn't supported for 10.10; was I supposed to?

Be happy to try the RC; I'm not close enough to any walls that I can't live with it.

I'll try to get a crash thread up this afternoon.

What has been making it fall over is not clear, but a recurrent theme is that once it does crash with the lockfile still existent, the application modal splash screen blocks you from clicking OK on the "should I whack the lock file" dialog. At that point it becomes necessary to Force Quit it and then remove the lockfile manually. After that, it generally behaves ok.

I have noted down what was happening in most of the OS/X crash/restart dialogs.