Rulers Was: Thorn Rev. 10476 compile error

View: New views
3 Messages — Rating Filter:   Alert me  

Rulers Was: Thorn Rev. 10476 compile error

by Julie S :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message


Dear Michael,

You wrote:

> Do I want something like this to follow my segment around
> from editor to
> editor?
>
> I don't really think so, no.
>
> So the other side of it is if I open a velocity, a pitch
> bend, a pan and a
> modulation ruler in a matrix view, do I really want the
> next matrix view
> (possibly of some completely different segment) to come up
> with those same
> rulers until I turn them back off?
>
> I don't really think so, no.
>
> I think for myself as a user, if these were quick to turn
> on and off, I would
> probably be content to create a ruler on the spot as
> needed, and let it
> evaporate when I was finished with that particular view
> window.
>

Good argument.  But if these are easy to turn off, then the user who only needed them for one segment can easly turn them off and be done with it.  Let's look at the efficiency of both cases.

One segment with local control:
3 actions

One segment with global control:
6 actions. (Twice the overhead for one segment).

Multiple segments with local control:
3*n actions

Multiple segments with global control:
6 actions.

So we have a linear vs. constant argument.  But, the constant method more overhead.

So there verdict is that global control is more efficient for multiple segments, but twice the overhead for single segments.

So after two segments the global control is more efficient.

So how do RG users actually use this feature.  I don't know.  I know one common scenario I use it for.

At the end of a song, I like to write a long sustained note and use a volume control to fade out.  I may have several segments that all need a similar fade.  So a global approach would be very handy.

I also like to record segments and tweak velocities depending on how thinks fit together.  In this case I need global control of the rulers.  As an aside, for a quick tweak the velocity ruler works well.

But, other use RG differently.  I do MIDI recording, tweaking of imported MIDI files, no audio, and occasional notation.

Sincerely,
Julie S.



     

------------------------------------------------------------------------------
Enter the BlackBerry Developer Challenge  
This is your chance to win up to $100,000 in prizes! For a limited time,
vendors submitting new applications to BlackBerry App World(TM) will have
the opportunity to enter the BlackBerry Developer Challenge. See full prize  
details at: http://p.sf.net/sfu/Challenge
_______________________________________________
Rosegarden-devel mailing list
Rosegarden-devel@... - use the link below to unsubscribe
https://lists.sourceforge.net/lists/listinfo/rosegarden-devel

Re: Rulers Was: Thorn Rev. 10476 compile error

by cannam :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

On Thu, Jul 9, 2009 at 1:17 PM, Julie S<msjulie_s@...> wrote:
> Good argument.  But if these are easy to turn off, then the user who only needed them for one segment can easly turn them off and be done with it.  Let's look at the efficiency of both cases.

I like the idea of using O(n)-style efficiency measures for user activity!

Don't forget about expectation though.  Something that requires one or
two actions each time a window is opened may be costly, but it isn't
necessarily more costly than something that requires one or two
actions only half the time when a window is opened, if the user can't
readily anticipate which half it will be.  If the action is a single
keystroke, the cost of hesitation probably outweighs the cost of
performing the action itself.

I think this probably weighs in favour of global control and
remembering state in the settings rather than the composition file.
But as you say, it really all depends on how users actually use the
feature(s).


Chris

------------------------------------------------------------------------------
Enter the BlackBerry Developer Challenge  
This is your chance to win up to $100,000 in prizes! For a limited time,
vendors submitting new applications to BlackBerry App World(TM) will have
the opportunity to enter the BlackBerry Developer Challenge. See full prize  
details at: http://p.sf.net/sfu/Challenge
_______________________________________________
Rosegarden-devel mailing list
Rosegarden-devel@... - use the link below to unsubscribe
https://lists.sourceforge.net/lists/listinfo/rosegarden-devel

Parent Message unknown Re: Rulers Was: Thorn Rev. 10476 compile error

by Julie S :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message


Dear Chris:

You wrote:
> I like the idea of using O(n)-style efficiency measures for
> user activity!

I was trying to avoid O(n) terms directly.  But that was exactly what I was thinking of.

But as we both seem to agree, it all depends on actual use and expectation.  Something with a large constant overhead and be very in-efficient to a user if they never break the payback barrier.

But global settings doesn't appear to be too costly for the one segment tweaker, and break even at two segments typically.

>From prior argument:
Two segments with local control:
3 * 2 = 6 actions

Two segments with global control
6 actions.

Sincerely,
Julie S.



     

------------------------------------------------------------------------------
Enter the BlackBerry Developer Challenge  
This is your chance to win up to $100,000 in prizes! For a limited time,
vendors submitting new applications to BlackBerry App World(TM) will have
the opportunity to enter the BlackBerry Developer Challenge. See full prize  
details at: http://p.sf.net/sfu/Challenge
_______________________________________________
Rosegarden-devel mailing list
Rosegarden-devel@... - use the link below to unsubscribe
https://lists.sourceforge.net/lists/listinfo/rosegarden-devel