[audacity4blind] Special Groups on the Forum
- From: Robert Hänggi <aarjay.robert@xxxxxxxxx>
- To: audacity4blind@xxxxxxxxxxxxx
- Date: Mon, 24 Nov 2014 22:06:00 +0100
2014-11-19 14:50 GMT+01:00, David Bailes <david_bailes@xxxxxxxxxxx>:
> Hi Thomas,
> in fact someone recently submitted some code for importing the cues in wav
> files into audacity, and creating a label track out of them. Unfortunately
> this code apparently still needs some work, so I've no idea if or when it
> might end up in Audacity. However, this does seem to be roughly along the
> lines that you were suggesting,
>
> David.
>
>
> On Monday, 17 November 2014, 20:35, Thomas Byskov Dalgaard
> <tbd@xxxxxxxxxxxxxxxxxx> wrote:
> Hi!
>
> 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
>
> Thomas
>
>> 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
> //www.freelists.org/webpage/audacity4blind
>
> Subscribe and unsubscribe information, message archives,
> Audacity keyboard commands, and more...
>
> To unsubscribe from audacity4blind, send an email to
> audacity4blind-request@xxxxxxxxxxxxx
> with subject line
> unsubscribe
>
> The audacity4blind web site is at
> //www.freelists.org/webpage/audacity4blind
>
> Subscribe and unsubscribe information, message archives,
> Audacity keyboard commands, and more...
>
> To unsubscribe from audacity4blind, send an email to
> audacity4blind-request@xxxxxxxxxxxxx
> with subject line
> unsubscribe
>
>
--
Freundliche Grüsse
Robert J. Hänggi
Schulstr. 10
4247 Grindel
Email: aarjay.robert@xxxxxxxxx
Mobile: 079 518 23 01
Hi to all
The Audacity Forum has recently been updated.
There's an interesting section called "Special Interest Groups"
http://forum.audacityteam.org/viewforum.php?f=66
I asked myself if it wouldn't be worthwhile to apply for an
accessibility subforum, something like
"Accessibility Tools and Techniques" - perhaps under "Audacity in Education".
A lot of questions on this forum come up repeatedly. It would be nice
if some guidelines and procedures could be stored at a central point.
Forum posts can be kept updated (e.g. newest scripts, recommendations
for latest Audacity versions etc) whereas emails can't.
Thus, a link to David Bailes excellent Jaws guide could be placed
there (or the text itself or some extracts) and just be referenced in
our emails.
There is a big deal of valuable information in the archive that awaits
summarization. A forum would be the ideal place to store some of it.
I would even offer to join the forum crew in order to maintain this sub forum.
Please let me know what you think.
Best regards
Robert J. Hänggi
The audacity4blind web site is at
//www.freelists.org/webpage/audacity4blind
Subscribe and unsubscribe information, message archives,
Audacity keyboard commands, and more...
To unsubscribe from audacity4blind, send an email to
audacity4blind-request@xxxxxxxxxxxxx
with subject line
unsubscribe
Other related posts:
