Hello Michael,
Concerning:
> I'm just not liking "use MIDI note velocity, if available"
> as a velocity combo
> box entry. It's long and hard to translate
> succinctly, and it's potentially
> confusing.
I hadn't pinned it down exactly. You are correct theat there is potential for
confusion. I initially I thought the entries may be: MIDI, 0-127 for the
Velocity combo box.
I also had suggested this solution as an alternative to putting another option
in the configuration dialogue, which was initially suggested.
Concerning:
> What about just disabling the velocity combo when step
> recording is active,
> and using the recorded velocity? That eliminates the
> possibility of pre-
> selecting the velocity with the combo, but does anyone
> really care?
That certainly simplified things. I mentioned, the velocity is initially
captured and transmitted, but in the sequence of signal routing, it is dropped
midway, and the velocity is replaced with a hard coded value of 100.
Currently, when step recording in Matrix / Percussion mode, we do not disable
the Velocity combo box, and we do not honor the value in the box. So there is
a bit of a disconnect there. Adding that state information should not be very
complex.
I also noticed that the step record icon state was not propagated across to the
other views. I have not untangled the complexities involved in our current
design. This will require further investigation before any final decisions
concerning the Velocity combo box state are made.
My initial impression is that I would only disable the velocity combo of the
window that the step record button has been enabled.
Concerning:
> > * The Matrix, Percussion and Notation views will have
> a Velocity combo box.
>
> That would be consistent, but the absence of a velocity
> combo in notation has
> never bothered me. (When I'm hand-entering stuff, I
> just use Adjust->Notes
> ->Interpret to humanize it after I'm done.)
I haven't used that option, nor looked at its code. If we where using the note
velocity from the MIDI notes that are captured, would this cause some
unintended consequences to the "humanize" adjustment?
Since you use it, you may be more familiar with how this works. When I get a
bit of time, I'll have to experiment with it and see how it reacts to different
data sets.
If using humanize is a typical work flow step for users than we want to make
certain they get the consistent results they have traditioanlly counted on.
...
Thanks for your input.
Sincerely,
Julie S.
------------------------------------------------------------------------------
_______________________________________________
Rosegarden-devel mailing list
[email protected] - use the link below to unsubscribe
https://lists.sourceforge.net/lists/listinfo/rosegarden-devel
