On 04.02.2025 16:33, Will Godfrey wrote:
On Tue, 4 Feb 2025 06:49:06 +0100
Kristian Amlie <krist...@amlie.name> wrote:
After our agreement I started implementing the omni channel, and I'm
currently working on the UI. I've been looking for a place to put the
Part-state, and what you see in the attached picture is my proposal.
Let me know if you have any comments.
But of course I have comments :P
That's why I asked!
I've always tried to avoid dramatic changes to the UI (muscle memory don'cha
know), and there's quite a lot of change here!
It's a good idea to move the Pan Law - that always bothered me a bit.
I like the overall idea but...
The Undo/Redo buttons could be moved into the blank area alongside The Sys/Ins
tabs. It also emphasises the fact these don't relate to the other
buttons.
These tabs are padded out with spaces. If you take a space out of either side
of the System tab it will give a little more wiggle room.
If you try to drag them in Fluid, it'll probably throw a hissy fit thinking
you're trying to walk over another group. However, if you double-click on the
entries and edit the numbers directly all is sweetness and light :)
The Vectors button can then be made the same size as the others, improving the
symmetry.
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!
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.
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.
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?
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?
It occurs to me that this may have an effect on MIDI-Learn, Vectors and Solo.
Have you done any tests for these?
Not tests, but I have been reading a lot of both code and documentation
to make sure I understand them well, in preparation for the actual
implementation. Which has yet to start.
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.
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.
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.
MIDI Learn doesn't do traditional MIDI CC handling and is therefore ok
with having All as a distinct value from any channel.
--
Kristian
_______________________________________________
Yoshimi-devel mailing list
Yoshimi-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/yoshimi-devel
