- This topic has 23 replies, 3 voices, and was last updated 10 years, 8 months ago by
.
-
Posts
-
Yes it’s like the 5th UI for the MIDI settings for a panel, and its again proven to be crap. So i turn to you dear users for an idea, such a window/UI needs to
– be resizable (from very small to very big if we are to overlay it on the panel)
– show the distinction between MIDI IN, MIDI OUT, devices/host connections
– somehow visualize the FLOW of MIDI dataif anyone has an idea… maybe i can rip some other applications UI or whatever, i just need to implement that will work for everyone and i’ll be able to leave for ever.
"atom":2fypyadk wrote:Yes it’s like the 5th UI for the MIDI settings for a panel, and its again proven to be crap. So i turn to you dear users for an idea, such a window/UI needs to– be resizable (from very small to very big if we are to overlay it on the panel)
– show the distinction between MIDI IN, MIDI OUT, devices/host connections
– somehow visualize the FLOW of MIDI dataif anyone has an idea… maybe i can rip some other applications UI or whatever, i just need to implement that will work for everyone and i’ll be able to leave for ever.[/quote:2fypyadk]
Has/Is the structure of the flow-of-midi-data changed/changing from how it is now in the Midi properties? If it’s clearly defined somewhere I could happily take a stab at it.
Monstrum Media | Music, Sound & Software Design, Chicago / San Francisco listen
No it should stay the same i think i’m not changing anything serious, only addition will be another MIDI IN device for Controller devices. But the layout is OK i guess, it just needs to be readable. If it’s possible to do that in the old Jucer application that would be super (https://sourceforge.net/projects/juce/f … e/download)
I’ll take a look. By adding a midi device to use as controllers – are these controllers going to be able to send midi clock? How many MIDI in devices are you adding, just one?
Monstrum Media | Music, Sound & Software Design, Chicago / San Francisco listen
Atom, could you define the terms as they relate to ctrlr of "channelize" and "comparator"? I know what a comparator is in general electronics (comparing voltage) but I don’t understand what the term refers to in ctrlr’s backend.
Monstrum Media | Music, Sound & Software Design, Chicago / San Francisco listen
Comparator here means, that messages hit a special Comparator class and are processed for matching to Modulator MIDI types and formulas and if a match is found the found modulator’s value will be changed, normaly MIDI from the host does not hit the comparator.
got it. ok, and "channelize" means what here??
Also what relationship does "Enable MIDI Thru" in the green and red boxes have with "Thru from Host to Device" and "Thru from device to Host"? If no relationship then what does it do? If Enable MIDI Thru is disabled in both the green and red boxes does that overide or effect in any way the "Thru from Host to Device" tick in the blue box, or "Thru from device to Host" in the purple box?
Similarly, what relationship does "Channelize THRU messages" have with the "Channelize" tick buttons in the blue and purple boxes?
I’ve always interpreted this current gui to say that the top green boxes are Host settings, the bottom red/pink boxes are panel settings. In this case I’d recommend referring only to "Host" and "Panel", not "Device"… it’s minor but I’d suggest they be labeled: "Thru from Host to Panel" and "Thru from panel to host" to be as clear as possible.
Sorry for all the questions, but the UI needs to be clear, so I need to to make sure I’m clear with definitions/functionality and how things are intended to interoperate.
Monstrum Media | Music, Sound & Software Design, Chicago / San Francisco listen
*bump*
Monstrum Media | Music, Sound & Software Design, Chicago / San Francisco listen
Yes the upper part is for the HOST<->CTRLR communication
channelize, means change the channel of the MIDI message.
MIDI-Thru dark green: messages from the host go back to the host, with channelize they go back with a different channel
MIDI-Thru dark red: the same but from INPUT device to OUTPUT device
MIDI Thru light blue: pass MIDI from the host to the MIDI OUTPUT device, if channelized change the MIDI message channel to the OUTPUT MIDI channel
MIDI Thru purple: pass MIDI from the MIDI INPUT device to the host, if channelized set the MIDI channel to the OUTPUT CHANNEL of the host (the green one)RED settings are for to DEVICES opened by CTRLR
GREEN settings are for HOST bases MIDI communication between CTRLR PLUGIN<->HOST (this should be disabled in Standalone mode, it has no meaning then)
GREY options are Snapshot relatedOk.. here’s a mockup of what I’ve got.. this is just in photoshop.. haven’t had the wherewithal to learn Jucer this week.
This is still a rough.. I want to be sure I have the signal flow down, then I can refine things a bit. With everything checked (second mockup below) it looks a bit crazy, no doubt.
The idea is that all of the components (channelize, comparator, thru, etc) do not appear in the gui if the checkbox that enables them is not checked, so the yellow arrows would only appear if you have the corresponding "THRU" toggle enabled, the Channelize boxes would not appear if the corresponding Channelize toggle was not checked, etc.
So here’s what this would look like with everything disabled/unchecked:
[img:3qvevdl1]http://www.monstrummedia.com/stuff/CTRLR-MIDI-PREFS-none-checked.gif[/img:3qvevdl1]And here’s everything turned ON:
[img:3qvevdl1]http://www.monstrummedia.com/stuff/CTRLR-MIDI-PREFS.gif[/img:3qvevdl1]
The only question I have with signal flow is if the comparator comes before or after the panel’s MIDI Input device.. Something tells me it actually should come after the MIDI input device.Another remaining question I have with the current MIDI preference panel GUI layout I’m basing this off of is I’m not sure I understand how the Host>Panel, Panel>Host THRU can get channelized if there is no where to set the channelized channel, if you will
” title=”Smile” />Monstrum Media | Music, Sound & Software Design, Chicago / San Francisco listen
The host->comparator does not go to the device it just goes to the comparator witch is part of the panel, it has nothing to do with devices.
Also the output from the panel to the host is not from the device (there might be a different set of messages on the device and to the host), it’s the panel that generates the MIDI messages and passes them to the device or to the host, i think it would be better if the whole gui would somehow show what generates messages what receives them, maybe i can even do some animation that shows witch way those messages are traveling.
[attachment=0:2nqtwhq2]ctrlr_midi_flow.png[/attachment:2nqtwhq2]
The only problem I see with your line drawing above is the midi devices selected from ctrlr are off in floating boxes. I understand what you’re getting at but it may be confusing. I wonder if MIDI messages that go through 5 pin DIN and MIDI messages that go through software need to be visually depicted/differentiated?
No doubt there’s lots going on and I see the challenge you’re faced here. I’ll try to make another sweep at this and get it as clean and sleek as possible. What I posted above was more a rough to convey the signal path than an actual GUI.
till next time..
Monstrum Media | Music, Sound & Software Design, Chicago / San Francisco listen
heads up, likewise I haven’t died or anything, just incredibly busy. Atom, you mentioned some of this stuff is/may change soon, shall I hold off on doing any more here until then? I’ve been neck deep working on the microwave wavetable/wave editor this past week. it’s been a little mind-bending but the hard work is paying off!
Monstrum Media | Music, Sound & Software Design, Chicago / San Francisco listen
Just saw this screengrab after checking out rekon’s pulse editor interface. Might be worth dissecting for ctrlr’s midi settings… ?
Monstrum Media | Music, Sound & Software Design, Chicago / San Francisco listen
I’m still thinking about some form of UI when in single instance mode (both restricted and not) so any ideas are welcome.
This UI is nice for just the device settings and MIDI routing, i actually had something similar in mind. I’ll post the Juce Plugin Host app here to let you see how it could look.
There is still a need for a midi program selection UI, getting programs, sending programs, organizing them in banks etc.
Here is how the plugin host looks like (it’s an example program from JUCE). The idea would be to represent various INs and OUTs in a movable way like plugins and ins/outs in this example.
You could connect them just like you can do here.
I wanted to do this like that, because i’d like to add a MIDI routing functionality to Ctrlr, where you can connect any IN to any OUT with a “filter” applied to that communication (where a filter is either a pre-defined simple filter or action or simply a LUA method).
I would like to propose something, but I need to know if
the rectangle of the plugins in/out has a size to be met
or will be the SVG image to give the shape and size?you might have a list of the things you need?
Midi In, Midi Out … and?“This application has failed to start because libgcc_s_dw2-1.dll was not found. Re-installing the application may fix this problem.”
that’s what I get when trying to run the exe…
windows XP sp3 here.Monstrum Media | Music, Sound & Software Design, Chicago / San Francisco listen
- The forum ‘News and releases’ is closed to new topics and replies.