> One of my basic concerns is whether or not it is appropriate to make all
> options available to all controllers. Is vibrato really appropriate for
> Pan (10), Chorus (93), Reverb (91), or Sustain (64)? Perhaps the
> appearance of vibrato options in the dialog could be made conditional,
> based on the controller chosen.
Hmmm. My take on it is that I don't want to deny options just because I
can't think of a use for them right now. FWIW, I have used a vibrato-like
effect with Pan (In "Much Brass", the mysterious section where horn chords
are surrounded by percussion that pans slowly around).
> A problem with the term "Vibrato" is that it refers to the frequency
> modulation of an audio tone. "Tremolo," on the other hand, usually
> implies amplitude modulation.
Yes, I think so too. I didn't say "Tremolo" because that would be overly
specific too: just expression and volume.
> Perhaps replacing "Vibrato" with
> "Vibrato / Tremolo" would make it clear that this option is not limited
> to frequency.
No good generic terms present themselves:
* "Vibrato or Tremolo". But then controllers are saying that they might
do vibrato, which is false, and it's still not a generic term.
* Yamaha used to call that generic thing "Low Frequency Oscillation", but
that might be even more confusing.
* "Sinusoidal variation"?
I am sure that whatever the right term is, it would be unwieldy to label
each field "Sinusoidal variation start amplitude" etc. Even I would
recoil at seeing that. Concatenating "Vibrato" etc onto "start amplitude"
could make our translators' work harder.
So part of the solution will probably be to group those 3 items in their
own labelled box. With that, a sensible approach becomes clearer. The
box label has more freedom to express an exact term, since it's not
concatenated to anything. Its label could be:
* For Pitchbend, "Vibrato"
* For Expression and Volume, "Tremolo"
* For anything else, "Low-frequency variation" unless someone can suggest
a better term.
> "Vibrato wavelength" seems a bit murky. I think it would be clearer if,
> instead, the number of vibrato cycles in the selection could be specified.
> Or, better still, the vibrato frequency in hertz. The number of half
> cycles of vibrato could be calculated from the available time interval,
> the vibrato frequency, and the current tempo.
Heck, I didn't even know how it was actually calculated until I revamped
this!
Cycles per selection is easier to add, but as you probably saw, it still
has the problem that using the "same" setting twice gives different
results if one selection is longer than the other.
I'm not sure hertz is the right unit. Perhaps cycles per quarter note?
Perhaps both?
I would very much like to hear from more people before I try this. The
other stuff is just renaming and rearranging and has little potential to
frustrate old users.
EVERYBODY: If you use the pitchbend dialog, if the "Vibrato wavelength"
field changed to "cycles per quarter note" or "hertz", would that be
easier or harder for you to use? I really don't know. Perhaps everybody
has been muddling thru with a tricky interface.
I'll ask on the user list too.
> Yes, I think these changes would greatly clarify the dialog.
Great!
> I have no problem with "Preset," but I found "User 1, User 2, User 3, ..."
> a bit confusing. My first impression was that it was an attempt to set up
> user accounts within a controller dialog.
I never thought of that. That *is* confusing! Historically, you know,
there was one lonely setting called "User" among the built-ins - the one
and only thing that the user could preset. Now with my patches it's
almost taken over.
> Perhaps "User Setting 1,
> User Setting 2, User Setting 3, ..." would make clear what's going on
> here.
OK. How about "Saved setting 1" etc?
> When an arrow is held down, the spinBox performs normally for the first
> second or so, after which it kicks into a high-speed mode.
Thanks.
Tom Breton (Tehom)
------------------------------------------------------------------------------
Introducing AppDynamics Lite, a free troubleshooting tool for Java/.NET
Get 100% visibility into your production application - at no cost.
Code-level diagnostics for performance bottlenecks with <2% overhead
Download for free and get started troubleshooting in minutes.
http://p.sf.net/sfu/appdyn_d2d_ap1
_______________________________________________
Rosegarden-devel mailing list
[email protected] - use the link below to unsubscribe
https://lists.sourceforge.net/lists/listinfo/rosegarden-devel
