[audacity4blind] Re: Labels

  • From: Thomas Byskov Dalgaard <tbd@xxxxxxxxxxxxxxxxxx>
  • To: audacity4blind@xxxxxxxxxxxxx
  • Date: Mon, 17 Nov 2014 21:34:38 +0100


Thank you so much for the discussion regarding labels.
I do see some situations where I myself would love labels. In fact I really 
hope that labels one day could be replaced by standard markers.
My reason for saying this is that some digital recorders like the Zoom H-series 
can make markers while recording files, and that will be extremely helpfull for 
Audacity since it could import markers from any wave-file and then from a lot 
of different editors so it might be easier for people to switch to Audacity.
Then the way labels work now could be something like making regions so from 
marker a to b there would be a region in between those, so the sound inside the 
marker could be moved around. If you have an interview for example, this would 
be very easy to structure later on, if something just needs to be structured 
while editing.

I don’t know if there is any workaround for this, or any plans for this in the 
future, but this was just my thoughts on labels

Best regards

> Den 17/11/2014 kl. 21.20 skrev Robert Hänggi <aarjay.robert@xxxxxxxxx>:
> 2014-11-17 19:10 GMT+01:00, David Bailes <david_bailes@xxxxxxxxxxx>:
>> Hi Robert,
>> yes, I do build Audacity from source, as do at least a couple of others on
>> the list.
>> I'll reply to other points shortly, but this is just about helptext.
>> Unfortunately, I don't think it's going to be very usable to do this. If you
>> include helptext, then by default jaws says "insert f1 help" after reading
>> the name of the control, and this can get really annoying. You can switch it
>> off either by changing the verbosity level to intermediate of advanced, or
>> by setting smart help to off in the beginner verbosity settings. But I don't
>> think that a user, especially a beginner should have to do this. As a far
>> more minor issue, narrator on window 8 reads out the help text, and I don't
>> know of any way of switching it off. Not sure how voiceover handles help
>> text on the mac.
>> So mainly do the Jaws's behaviour, I don't think that help text if a useful
>> route to go down.
>> As an alternative, perhaps a track could have a properties dialog?
>> thanks for all you suggestions,
>> David.
> Hi David
> I'll attach the patch anyway.
> I believe that a property dialog isn't helpful either.
> I have the principle that all that is available to normal users with a
> single glance should also be available to us with a single key stroke
> or even automatically.
> The first line of the helptext string can as well be added to the
> normal name string itself.
> We can reduce the information overload by removing values that are
> common to the project settings.
> Thus, 44100 Hz and 32-bit float would never be displayed if the
> project has those values as default.
> We can also omit stereo, as it is probably the most common track type
> and there would be displayed Mono".
> Actually, "Left" and "Right" are already reported with the patch
> applied, I find that extremely useful after a "Split Stereo" to
> discriminate the two channels that do normally share a single name.
> The word "Label Track" could be replaced by the first line of the
> helptext for label tracks.
> E.g. "No Labels defined" etc.
> Robert
> <TrackPanelAx.cpp.patch>

The audacity4blind web site is at

Subscribe and unsubscribe information, message archives,
Audacity keyboard commands, and more...

To unsubscribe from audacity4blind, send an email to
with subject line

Other related posts: