EXPERIMENTAL_MODULES

67 Messages Forum Options Options
Embed this topic
Permalink
1 2 3 4
David Bailes-2
Re: EXPERIMENTAL_MODULES
Reply Threaded MoreMore options
Print post
Permalink
Hi,

On 6/14/08, Gale Andrews <gale@...> wrote:

>>
>> If there's no selected time-range, the left and right arrow move the
>> cursor. If there is a selected time-range, the left and right arrow
>> move to the start and end of the selected time-range respectively.
>> (Similar to Microsoft Word)
>
> And similar to many other document editors too I see, thanks.
> Personally I just hardly ever use arrow with a selected region
> because it destroys the selection. Sometimes you want that, but
> more often I use the menu items, which allow you to keep the
> selection region. So though I'd be happy to give those two
> menu items a shortcut, I don't see that could be left/right arrow,
> because that behaves differently.

In Audacity 1.3.3, using either the menu items to move to the start or
end of a selection
or the left and right arrows has the same effect: the cursor is placed
at either the start or end of the selection, and the selection is
removed. This is how I think it was intended to work.

In Audacity 1.3.4 and later, the arrow keys still have the same
effect. If you use one of the menu items, then nothing happens the
first time, and then if you immediately repeat the menu item, then the
selection is removed and the cursor is moved to the start or end of
the track. I think this is a bug or it's now working as intended and
I've lost the plot.

>
>
>> This then implies CTRL + SHIFT + HOME
>> > for "Select Track Start to Cursor" and CTRL + SHIFT + END for "Select
>> > Cursor to Track End. CTRL + SHIFT when used for selections, contract
>> > them, but this usage expands them. David?
>> Two issues:
>> - people are used to using home and end with their current meanings,
>>  there has to be a strong reason for changing them.
>>- as pointed out by Gale, using ctrl+shift+home/end doesn't fit well
>> with ctrl+shift+left/right arrow to contract a selected time-range.
>
> I think greater similarity to document usage plus Vaughan's mnemonic
> reasoning could add up to a strong case for changing them. Is it
> possible to use ALT + SHIFT + arrow for the contractions? That also
> removes the objection that in this case CTRL is being used to do
> something "smaller".

I was under the impression that alt was being avoided because there
isn't a mac equivalent? Though it would be useful to have about eight
more modifier keys.

A case could be made either to leave Home and End to move to time zero
and end of all tracks, and then have Ctrl + Home and Ctrl + End to
move to start and end of selected tracks - the overriding
consideration being not to change the existing meanings of Home and
End.

Or to have Ctrl + Home and Ctrl + End to move to time zero and the end
of all tracks, and have Home and End to move to the start and end of
the selected tracks - the overriding consideration being to fit in
with the convention that Ctrl implies a larger effect.

In both cases one would just ignore the slight mismatch with
ctrl+shift+left/right arrow contracting the selection.

Or there's always J and K!

>
> And as a sighted user I've always wished that if I expand a selection
> right, that left arrow would contract that same edge, then a modifier
> would let me use left or right arrow to modify the opposite selection
> edge. I can't say how many times I've instinctively tried to use
> the opposite arrow key to contract the same edge. Anyone else
> feel this, and would such a change be impossible for VI users?

I don't think it would be a problem for VI users. It's probably easier
for them to use the spin boxes in the Selection bar, because using the
arrow keys they miss out on the visual feedback as to how much they're
changing the selection.

I found it initially confusing, but not a big issue.

David.

-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
_______________________________________________
Audacity-devel mailing list
Audacity-devel@...
https://lists.sourceforge.net/lists/listinfo/audacity-devel
Gale Andrews
Re: EXPERIMENTAL_MODULES
Reply Threaded MoreMore options
Print post
Permalink

| From "David Bailes" <drbailes@...>
| Mon, 16 Jun 2008 20:33:22 +0100
| Subject: [Audacity-devel] EXPERIMENTAL_MODULES

> On 6/14/08, Gale Andrews <gale@...> wrote:
> >> If there's no selected time-range, the left and right arrow move the
> >> cursor. If there is a selected time-range, the left and right arrow
> >> move to the start and end of the selected time-range respectively.
> >> (Similar to Microsoft Word)
> >
> > And similar to many other document editors too I see, thanks.
> > Personally I just hardly ever use arrow with a selected region
> > because it destroys the selection. Sometimes you want that, but
> > more often I use the menu items, which allow you to keep the
> > selection region. So though I'd be happy to give those two
> > menu items a shortcut, I don't see that could be left/right arrow,
> > because that behaves differently.
>
> In Audacity 1.3.3, using either the menu items to move to the start or
> end of a selection
> or the left and right arrows has the same effect: the cursor is placed
> at either the start or end of the selection, and the selection is
> removed. This is how I think it was intended to work.
 
> In Audacity 1.3.4 and later, the arrow keys still have the same
> effect. If you use one of the menu items, then nothing happens the
> first time, and then if you immediately repeat the menu item, then the
> selection is removed and the cursor is moved to the start or end of
> the track. I think this is a bug or it's now working as intended and
> I've lost the plot.

When you use the menu items the first time, the cursor is moved to
start or end of the selection, but you can't see the cursor until you
play the selection or use the arrow keys to move the cursor a little
way from where it is. I sometimes find this useful, but it's the
selection that's played, not from the cursor; and if you play, the
selection disappears on stop. As you say, running the menu item
a second time jumps to track start or end, so I think you're right,
it's a bug and needs to revert to 1.3.3 behaviour.
   

> >> This then implies CTRL + SHIFT + HOME
> >> > for "Select Track Start to Cursor" and CTRL + SHIFT + END for "Select
> >> > Cursor to Track End. CTRL + SHIFT when used for selections, contract
> >> > them, but this usage expands them. David?
> >> Two issues:
> >> - people are used to using home and end with their current meanings,
> >>  there has to be a strong reason for changing them.
> >>- as pointed out by Gale, using ctrl+shift+home/end doesn't fit well
> >> with ctrl+shift+left/right arrow to contract a selected time-range.
> >
> > I think greater similarity to document usage plus Vaughan's mnemonic
> > reasoning could add up to a strong case for changing them. Is it
> > possible to use ALT + SHIFT + arrow for the contractions? That also
> > removes the objection that in this case CTRL is being used to do
> > something "smaller".
>
> I was under the impression that alt was being avoided because there
> isn't a mac equivalent? Though it would be useful to have about eight
> more modifier keys.

That had slipped my mind, I know the Mac Option key that does for ALT
won't work with menus - anyone confirm it can't be used as a shortcut
modifier either? If true, unfortunately we seem to have 18 instances of
ALT for shortcuts already.....

>
> A case could be made either to leave Home and End to move to time zero
> and end of all tracks, and then have Ctrl + Home and Ctrl + End to
> move to start and end of selected tracks - the overriding
> consideration being not to change the existing meanings of Home and
> End.
> Or to have Ctrl + Home and Ctrl + End to move to time zero and the end
> of all tracks, and have Home and End to move to the start and end of
> the selected tracks - the overriding consideration being to fit in
> with the convention that Ctrl implies a larger effect.
> In both cases one would just ignore the slight mismatch with
> ctrl+shift+left/right arrow contracting the selection.
>
> > And as a sighted user I've always wished that if I expand a selection
> > right, that left arrow would contract that same edge, then a modifier
> > would let me use left or right arrow to modify the opposite selection
> > edge. I can't say how many times I've instinctively tried to use
> > the opposite arrow key to contract the same edge. Anyone else
> > feel this, and would such a change be impossible for VI users?
>
> I don't think it would be a problem for VI users. It's probably easier
> for them to use the spin boxes in the Selection bar, because using the
> arrow keys they miss out on the visual feedback as to how much they're
> changing the selection. I found it initially confusing, but not a big issue.


Home/End for start/end of project confused me for a while when I first
used Audacity, so if Home/End changed to start/end of track, we could
count greater intuitiveness for new users as an offsetting benefit. I don't
think it unreasonable for the majority of users who will come to 1.4
from 1.2 that they should find some shortcuts different. If we make
that change, we can better fit the convention of CTRL implying a larger
effect. Even if we did not make that change, moving to SHIFT + left/right
arrow operates on left selection edge, CTRL + SHIFT + left/right works
on right edge might make less of a mismatch in that CTRL does not
exclusively contract. And for us two at least, it would have confused us
less when we started to use Audacity.



Gale
       



-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
_______________________________________________
Audacity-devel mailing list
Audacity-devel@...
https://lists.sourceforge.net/lists/listinfo/audacity-devel
Gale Andrews
Re: EXPERIMENTAL_MODULES
Reply Threaded MoreMore options
Print post
Permalink
In reply to this post by David Bailes-2

| From "David Bailes" <drbailes@...>
| Mon, 16 Jun 2008 20:33:22 +0100
| Subject: [Audacity-devel] EXPERIMENTAL_MODULES

Gale said: "moving to SHIFT + left/right arrow operates on
left selection edge, CTRL + SHIFT + left/right works
on right edge might make less of a mismatch in that CTRL
does not exclusively contract."

Or a more devious solution that asserts the supremacy of
"CTRL is larger": reverse the shortcuts so that CTRL + SHIFT +
left/right arrow expands rather than contracts (though I
still prefer the first idea).


Gale
       



-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
_______________________________________________
Audacity-devel mailing list
Audacity-devel@...
https://lists.sourceforge.net/lists/listinfo/audacity-devel
David Bailes-2
Re: EXPERIMENTAL_MODULES
Reply Threaded MoreMore options
Print post
Permalink
Hi,

On Tue, Jun 17, 2008 at 8:28 AM, Gale Andrews <gale@...> wrote:

> Gale said: "moving to SHIFT + left/right arrow operates on
> left selection edge, CTRL + SHIFT + left/right works
> on right edge might make less of a mismatch in that CTRL
> does not exclusively contract."

Minor point, but if people go along with this sort of idea, it might
be better to allocate shift + left/right arrow to the right hand edge.
Most people probablly normally select left to right, and if you select
from left to right in a text editor, shift + left/right arrow then
adjusts the right hand edge (in a text editor there is only one active
end to a selection, so you can't adjust the other end).

David.

-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
_______________________________________________
Audacity-devel mailing list
Audacity-devel@...
https://lists.sourceforge.net/lists/listinfo/audacity-devel
Gale Andrews
Re: EXPERIMENTAL_MODULES
Reply Threaded MoreMore options
Print post
Permalink

| From "David Bailes" <drbailes@...>
| Tue, 17 Jun 2008 10:24:43 +0100
| Subject: [Audacity-devel] EXPERIMENTAL_MODULES

> On Tue, Jun 17, 2008 at 8:28 AM, Gale Andrews <gale@...> wrote:
> > Gale said: "moving to SHIFT + left/right arrow operates on
> > left selection edge, CTRL + SHIFT + left/right works
> > on right edge might make less of a mismatch in that CTRL
> > does not exclusively contract."
>
> Minor point, but if people go along with this sort of idea, it might
> be better to allocate shift + left/right arrow to the right hand edge.
> Most people probablly normally select left to right, and if you select
> from left to right in a text editor, shift + left/right arrow then
> adjusts the right hand edge (in a text editor there is only one active
> end to a selection, so you can't adjust the other end).

Very good point, agree (and think that here too, making our behaviour
more like document behaviour is a good reason to change). Does anyone
think we really should not change selection contract/expand and the
HOME/END behaviour? Vaughan, does HOME and END for move to
start/end of track work for you, with CTRL modified moving to start/end
of project?
 
David, no-one really answered you about whether we should "advertise"
1.3.6 (or 1.3.4) as the recommended version for blind users, given the
the field navigation in dialogues/Selection Bar problems in 1.3.5. My
feeling is that none of the points where we've tagged 1.3.6 so far are
really suitable, and that 1.3.4 is better, especially given that you
have your JAWS guide for that version. Would it be sufficient to
slightly modify:
http://audacity.sourceforge.net/help/faq?s=general&i=blind-users

to "quietly suggest" 1.3.4, and "more strongly" suggest this on the
Wiki page that FAQ points to:
http://audacityteam.org/wiki/index.pl?AudacityForBlindUsers

 
Gale




-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
_______________________________________________
Audacity-devel mailing list
Audacity-devel@...
https://lists.sourceforge.net/lists/listinfo/audacity-devel
David Bailes-2
Re: EXPERIMENTAL_MODULES
Reply Threaded MoreMore options
Print post
Permalink
Hi Gale,

On 6/17/08, Gale Andrews <gale@...> wrote:

> David, no-one really answered you about whether we should "advertise"
> 1.3.6 (or 1.3.4) as the recommended version for blind users, given the
> the field navigation in dialogues/Selection Bar problems in 1.3.5. My
> feeling is that none of the points where we've tagged 1.3.6 so far are
> really suitable, and that 1.3.4 is better, especially given that you
> have your JAWS guide for that version. Would it be sufficient to
> slightly modify:
> http://audacity.sourceforge.net/help/faq?s=general&i=blind-users
>
> to "quietly suggest" 1.3.4, and "more strongly" suggest this on the
> Wiki page that FAQ points to:
> http://audacityteam.org/wiki/index.pl?AudacityForBlindUsers

Leland was going to try and fix up the accessibility of 1.3.6, but I'm
not sure how far he's got. If there's going to be a recommended
version for users of screen readers, then it would be best if it was
clearly shown on the home page, otherwise chances are they won't find
it.

David.

-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
_______________________________________________
Audacity-devel mailing list
Audacity-devel@...
https://lists.sourceforge.net/lists/listinfo/audacity-devel
Gale Andrews
Re: EXPERIMENTAL_MODULES
Reply Threaded MoreMore options
Print post
Permalink

| From "David Bailes" <drbailes@...>
| Tue, 17 Jun 2008 18:49:23 +0100
| Subject: [Audacity-devel] EXPERIMENTAL_MODULES

> On 6/17/08, Gale Andrews <gale@...> wrote:
>
> > David, no-one really answered you about whether we should "advertise"
> > 1.3.6 (or 1.3.4) as the recommended version for blind users, given the
> > the field navigation in dialogues/Selection Bar problems in 1.3.5. My
> > feeling is that none of the points where we've tagged 1.3.6 so far are
> > really suitable, and that 1.3.4 is better, especially given that you
> > have your JAWS guide for that version. Would it be sufficient to
> > slightly modify:
> > http://audacity.sourceforge.net/help/faq?s=general&i=blind-users
> >
> > to "quietly suggest" 1.3.4, and "more strongly" suggest this on the
> > Wiki page that FAQ points to:
> > http://audacityteam.org/wiki/index.pl?AudacityForBlindUsers
>
> Leland was going to try and fix up the accessibility of 1.3.6, but I'm
> not sure how far he's got.

There's also the question of stability, and features/changes not
documented by us or you.  


> If there's going to be a recommended version for users of screen readers,
> then it would be best if it was clearly shown on the home page, otherwise
> chances are they won't find  it.

That would be Vaughan's call really, but I'm not sure we could really
point to an alternative version for VI users on the home page (either
older, or newer, unless we actually decide to post a3). I was hoping
that people might search for "blind" or "accessibility" before deciding to
download, so we could direct them more subtly.


Gale    

 

-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
_______________________________________________
Audacity-devel mailing list
Audacity-devel@...
https://lists.sourceforge.net/lists/listinfo/audacity-devel
Vaughan Johnson
Re: EXPERIMENTAL_MODULES
Reply Threaded MoreMore options
Print post
Permalink
Gale Andrews wrote:

> | From "David Bailes" <drbailes@...>
> |
> ...
>  
>> If there's going to be a recommended version for users of screen readers,
>> then it would be best if it was clearly shown on the home page, otherwise
>> chances are they won't find  it.
>>    
>
> That would be Vaughan's call really,

Gosh, you make me feel like a potentate. Not sure why it would be my call...

I think we shouldn't be publicizing the alphas until they're more
complete/tested. So if 1.3.5 is really no good for VI users, we should
probably put 1.3.4 back up on the the downloads page as "for VI users"
or some such. I agree it doesn't warrant being on the home page.

- Vaughan

-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
_______________________________________________
Audacity-devel mailing list
Audacity-devel@...
https://lists.sourceforge.net/lists/listinfo/audacity-devel
Gale Andrews
Re: EXPERIMENTAL_MODULES
Reply Threaded MoreMore options
Print post
Permalink

| From Vaughan Johnson <vaughan@...>
| Tue, 17 Jun 2008 12:04:57 -0700
| Subject: [Audacity-devel] EXPERIMENTAL_MODULES

> Gale Andrews wrote:
> > | From "David Bailes" <drbailes@...>
> >> If there's going to be a recommended version for users of screen readers,
> >> then it would be best if it was clearly shown on the home page, otherwise
> >> chances are they won't find  it.
> >>    
> I think we shouldn't be publicizing the alphas until they're more
> complete/tested. So if 1.3.5 is really no good for VI users, we should
> probably put 1.3.4 back up on the the downloads page as "for VI users"
> or some such. I agree it doesn't warrant being on the home page.

OK then we'll do that if David agrees and no-one else disagrees (just
the 1.3.4 for Windows, given Mac screen reader support is not as
good, or 1.3.3 for Mac as well)?

Either way, I don't think our FAQ "Does Audacity work with screen-reader
programs for blind users?" really does us justice, and people could
easily bypass us without clicking the Wiki link. Is there any real reason
to not at least mention the Beta series' accessibility support in the
text there?


Gale




>
> - Vaughan
>
> -------------------------------------------------------------------------
> Check out the new SourceForge.net Marketplace.
> It's the best place to buy or sell services for
> just about anything Open Source.
> http://sourceforge.net/services/buy/index.php
> _______________________________________________
> Audacity-devel mailing list
> Audacity-devel@...
> https://lists.sourceforge.net/lists/listinfo/audacity-devel



-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
_______________________________________________
Audacity-devel mailing list
Audacity-devel@...
https://lists.sourceforge.net/lists/listinfo/audacity-devel
David Bailes-2
Re: EXPERIMENTAL_MODULES
Reply Threaded MoreMore options
Print post
Permalink
In reply to this post by Gale Andrews
Hi Gale,

On Tue, Jun 17, 2008 at 7:35 PM, Gale Andrews <gale@...> wrote:

>
>> If there's going to be a recommended version for users of screen readers,
>> then it would be best if it was clearly shown on the home page, otherwise
>> chances are they won't find  it.
>
> That would be Vaughan's call really, but I'm not sure we could really
> point to an alternative version for VI users on the home page (either
> older, or newer, unless we actually decide to post a3). I was hoping
> that people might search for "blind" or "accessibility" before deciding to
> download, so we could direct them more subtly.

Why would a user of a screen reader do a search before downloading
from the home page?

David.

-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
_______________________________________________
Audacity-devel mailing list
Audacity-devel@...
https://lists.sourceforge.net/lists/listinfo/audacity-devel
David Bailes-2
Re: EXPERIMENTAL_MODULES
Reply Threaded MoreMore options
Print post
Permalink
In reply to this post by Gale Andrews
Hi,

On Wed, Jun 18, 2008 at 2:25 AM, Gale Andrews <gale@...> wrote:
> OK then we'll do that if David agrees and no-one else disagrees (just
> the 1.3.4 for Windows, given Mac screen reader support is not as
> good, or 1.3.3 for Mac as well)?

In the absence of a stable 1.3.6, 1.3.4 would be best for users of
screen readers,

David.

-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
_______________________________________________
Audacity-devel mailing list
Audacity-devel@...
https://lists.sourceforge.net/lists/listinfo/audacity-devel
Gale Andrews
Re: EXPERIMENTAL_MODULES
Reply Threaded MoreMore options
Print post
Permalink
In reply to this post by David Bailes-2

| From "David Bailes" <drbailes@...>
| Wed, 18 Jun 2008 15:39:35 +0100
| Subject: [Audacity-devel] EXPERIMENTAL_MODULES

> On Tue, Jun 17, 2008 at 7:35 PM, Gale Andrews <gale@...> wrote:
> >
> >> If there's going to be a recommended version for users of screen readers,
> >> then it would be best if it was clearly shown on the home page, otherwise
> >> chances are they won't find  it.
> >
> > That would be Vaughan's call really, but I'm not sure we could really
> > point to an alternative version for VI users on the home page (either
> > older, or newer, unless we actually decide to post a3). I was hoping
> > that people might search for "blind" or "accessibility" before deciding to
> > download, so we could direct them more subtly.
>
> Why would a user of a screen reader do a search before downloading
> from the home page?

Given poor accessibility support in most other multi-track editors, to
find out if it was worth downloading Audacity?  That's why I think
we should mention Beta in the text of the "screen readers" FAQ.
But if we're happy to link to 1.3.4 on the Windows download page,
then that's fine too, to cover those who already know the Beta
series has good accessibility support.


Gale


-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
_______________________________________________
Audacity-devel mailing list
Audacity-devel@...
https://lists.sourceforge.net/lists/listinfo/audacity-devel
David Bailes-2
Re: EXPERIMENTAL_MODULES
Reply Threaded MoreMore options
Print post
Permalink
In reply to this post by Gale Andrews
Hi,

On Sat, Jun 14, 2008 at 9:26 AM, Gale Andrews <gale@...> wrote:
>
> | From Martyn Shaw <martynshaw99@...>

>> Still missing an idea for a shortcut for Timer Record...
>
> Shift + T ?

Ctrl + Shift + T would probably be better. My guess is that it would
make it easier for developers to ensure that the shortcut worked
whatever the current focus. If there was ever a text box in the main
window which accepted letters, then clearly shift+t wouldn't work when
the text box had the focus.

David.

-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
_______________________________________________
Audacity-devel mailing list
Audacity-devel@...
https://lists.sourceforge.net/lists/listinfo/audacity-devel
Gale Andrews
Re: EXPERIMENTAL_MODULES
Reply Threaded MoreMore options
Print post
Permalink

| From "David Bailes" <drbailes@...>
| Thu, 19 Jun 2008 13:37:17 +0100
| Subject: [Audacity-devel] EXPERIMENTAL_MODULES

> On Sat, Jun 14, 2008 at 9:26 AM, Gale Andrews <gale@...> wrote:
> >
> > | From Martyn Shaw <martynshaw99@...>
>
> >> Still missing an idea for a shortcut for Timer Record...
> >
> > Shift + T ?
>
> Ctrl + Shift + T would probably be better. My guess is that it would
> make it easier for developers to ensure that the shortcut worked
> whatever the current focus. If there was ever a text box in the main
> window which accepted letters, then clearly shift+t wouldn't work when
> the text box had the focus.

Same applies then for Loop Play (SHIFT + Spacebar) and Append
Record (SHIFT + R)?  Timer Record... really needs a shortcut, so can
we decide?

Martyn, it's struck me looking at the Transport menu that perhaps
"Play While Recording" isn't clear (described like that, you could
easily say software playthrough does just that). Suggestions:

* "Play While Recording New"
* "Overdub Recording"
* "Multi-Track Recording" (correct, but I don't like it for newbies)
* Change "Software Playthrough" to "Monitor While Recording"


Gale


 
 

-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
_______________________________________________
Audacity-devel mailing list
Audacity-devel@...
https://lists.sourceforge.net/lists/listinfo/audacity-devel
Vaughan Johnson
Re: EXPERIMENTAL_MODULES
Reply Threaded MoreMore options
Print post
Permalink
Gale Andrews wrote:

> | ...
>
> Martyn, it's struck me looking at the Transport menu that perhaps
> "Play While Recording" isn't clear (described like that, you could
> easily say software playthrough does just that). Suggestions:
>
> * "Play While Recording New"
> * "Overdub Recording"
> * "Multi-Track Recording" (correct, but I don't like it for newbies)
> * Change "Software Playthrough" to "Monitor While Recording"
>
>
>  

I vote for "Overdub Recording".

- V

-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
_______________________________________________
Audacity-devel mailing list
Audacity-devel@...
https://lists.sourceforge.net/lists/listinfo/audacity-devel
Martyn Shaw-2
Re: EXPERIMENTAL_MODULES
Reply Threaded MoreMore options