On Wed, 5 Feb 2025 15:30:30 +0100
Kristian Amlie <[email protected]> wrote:
>Sure, I can do that, but the reason I arranged the buttons like this, is
>that if we put the undo/redo buttons to the right of the tabs, then we
>have an open space below the stereo button instead. And I thought this
>looked stranger than having open space next to the tabs. But it does
>restore symmetry, of course!
My reasoning was also that Undo/Redo don't fit in with the other controls in a
functional sense.
>> The Mode drop-down is much too long - it looks as if something is missing.
>
>This was again to fill empty space, but I can shorten it.
I think some empty space is inevitable, and sometimes not necessarily a bad
thing.
>> Did
>> you remember to also move the red warning background patch? Can't have legato
>> and drum mode).
>
>I did not! I'll make sure this is done.
Not that I know anyone else who ever forgot to adjust these backgrounds :P
>> Portamento has lost it's MIDI-Learnable colour and font.
>
>Oh, that's what that was! I thought it was just an unintentional
>leftover from earlier formatting. But why aren't all MIDI learnable
>controls blue?
Knobs and sliders are almost all midi learnable. In fact I think the only one
that isn't is the Master Detune, so don't need any identification. Previously I
put a pale blue border round learnable buttons and switches, but that looked
pretty naff :(
I can't think of any other way to identify these.
>> The Omni checkbox needs to be bigger - about the same as the 'On' one.
>
>I intentionally made it smaller to emphasize that "On" is "more
>important", since it disables everything. Shouldn't the channel and omni
>controls have the same font size?
You have a point there. OK, so leave it as it is.
>Currently, as I see it, omni will have no effect at all on MIDI Learn,
>since it is not bound to parts. And in MIDI learn you have a completely
>separate channel selector which is independent anyway.
Yes, thinking about it more, MIDI-Learn precedes all other MIDI controls.
>Vector will be affected, but only barely. When you enable Vector, the
>two parts that are involved will be automatically set to the same
>channel (already happens today). I'm thinking that omni will be handled
>in a similar way, and will be automatically turned off, if it is on.
>It's possible to change the channel and thus "mess up" the vector
>functionality after you have set it up, and I'm thinking the same with
>omni. It is by default set to the sensible setting, off, but the user is
>allowed to turn it on for esoteric use cases. If it is on for both
>parts, then those vector parts will respond to controller messages on
>all channels. I can't really see how this would be useful, but it's not
>worth banning it either.
Fair enough.
>If Omni is enabled for some parts, and you enter Solo mode, then
>essentially Solo will have no effect for those parts. I think this could
>be of great use though. It means you can set up parts that always sound,
>together with parts that only sound when solo is enabled for them. So
>for example you could have a bass part which is constantly enabled,
>while playing different strings on top, and use keyboard splits to split
>the bass and the strings.
>
>> Another idea...
>> The Chanel selector originally was a drop-down like the one in the Mixer
>> panel.
>> If it is changed back, an 'Omni' entry could be added instead of needing a
>> separate button. To all practical purposes Midi Learn already has this, only
>> there it's called 'All'.
>
>This we cannot do without breaking MIDI compatibility. You still need to
>have a dedicated channel selected in addition to the Omni setting,
>because MIDI CC Omni messages will *always* go to only one channel, even
>if omni is on. This is specifically documented in the MIDI spec.
Good point.
>MIDI Learn doesn't do traditional MIDI CC handling and is therefore ok
>with having All as a distinct value from any channel.
Actually, I don't think it was even thought of when the MIDI spec. was
developed. I don't know if MIDI 2 makes any allowance for it.
--
Will J Godfrey {apparently now an 'elderly'}
_______________________________________________
Yoshimi-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/yoshimi-devel
