UI suggestions
UI suggestions
hello, i thought we could gather suggestion on user interface improvements here, ways to make the workflow more efficient and intuitive. Including shortcuts.
- middle mouse button for panning (already said that in another thread, i know )
- add shortcuts to the context menu like other softwares do that:
here with beautifully painted lines under the letters to show which key would be the shortcut.
- maybe 'space' for opening the context menu?
- have the "snapping" of noodles done in a bigger area, so it's easier to drop them on another node
- connect multiple nodes to another node by shift-dragging the noddle, which results in draging noodles out of all selected nodes.
- shortcut for connecting two selected nodes. press shortcut again for inverted connection (by default magic could connect the OUT of the node which is more left, to the IN of the node which is more right, because current layout is from left to right). if it goes from left to right, you could even do more than two nodes.
- eg ctrl-click on node for auto-connecting its OUT to the magic-node (alternatively add this option to the context menu of a node)
- ability to drop-insert a node on the existing connection of two other nodes. hover with the node above the connction, the connection gets highlighted, drop it and it's inserted inbewteen the two nodes.
- and vice versa: rip out a middle-node (leftnode---middlenode---rightnode) without disrupting the noodle. drag a node with alt-click away, and its connections get deleted, but left-node is still connected to rightnode.
I have to admit, almost everything above, i "stole" from blender, so my suggestions might be biased. they do strike me as useful though .
\\edit: some keywords (had troule finding this topic again): user interface, gui, experience.
- middle mouse button for panning (already said that in another thread, i know )
- add shortcuts to the context menu like other softwares do that:
here with beautifully painted lines under the letters to show which key would be the shortcut.
- maybe 'space' for opening the context menu?
- have the "snapping" of noodles done in a bigger area, so it's easier to drop them on another node
- connect multiple nodes to another node by shift-dragging the noddle, which results in draging noodles out of all selected nodes.
- shortcut for connecting two selected nodes. press shortcut again for inverted connection (by default magic could connect the OUT of the node which is more left, to the IN of the node which is more right, because current layout is from left to right). if it goes from left to right, you could even do more than two nodes.
- eg ctrl-click on node for auto-connecting its OUT to the magic-node (alternatively add this option to the context menu of a node)
- ability to drop-insert a node on the existing connection of two other nodes. hover with the node above the connction, the connection gets highlighted, drop it and it's inserted inbewteen the two nodes.
- and vice versa: rip out a middle-node (leftnode---middlenode---rightnode) without disrupting the noodle. drag a node with alt-click away, and its connections get deleted, but left-node is still connected to rightnode.
I have to admit, almost everything above, i "stole" from blender, so my suggestions might be biased. they do strike me as useful though .
\\edit: some keywords (had troule finding this topic again): user interface, gui, experience.
-
- Posts: 712
- Joined: Sun Sep 14, 2014 8:15 am
- Location: UK
- Contact:
Re: UI suggestions
Extra-fine adjustment of numeric module parameters when dragging etc.
The present /10 sensitivity achieved by holding down Ctrl(Cmd) is very useful, but sometimes is still far too coarse. Keyboard input is then required, and adjustment and optimisation becomes very much slower.
Add a /100 option when additionally holding down Shift.
I think I saw a prior request for finer control, but failed to find it with a forum search for "parameter".
The present /10 sensitivity achieved by holding down Ctrl(Cmd) is very useful, but sometimes is still far too coarse. Keyboard input is then required, and adjustment and optimisation becomes very much slower.
Add a /100 option when additionally holding down Shift.
I think I saw a prior request for finer control, but failed to find it with a forum search for "parameter".
Re: UI suggestions
Ok, good ideas. Thanks!
-
- Posts: 176
- Joined: Tue Aug 26, 2014 11:22 am
Re: UI suggestions
another little one about UI :
About adjusting the gain , it could be very useful to have the gain windows directly on the audio midi windows. with live musicians, you need to tweak them a lot, and using the menu it is not very convenient. you loose too the visual cue of the fader One great option in my opinion will be the possibility to have a midi learn fonction on this fader, so you can easily tweak them on stage.
and thanks for all the previous update, Magic is really become a reference for digital art !
About adjusting the gain , it could be very useful to have the gain windows directly on the audio midi windows. with live musicians, you need to tweak them a lot, and using the menu it is not very convenient. you loose too the visual cue of the fader One great option in my opinion will be the possibility to have a midi learn fonction on this fader, so you can easily tweak them on stage.
and thanks for all the previous update, Magic is really become a reference for digital art !
Re: UI suggestions
Ok that sounds good. There's probably enough room to have the gain sliders in the Audio/MIDI window instead of in a separate popup.About adjusting the gain , it could be very useful to have the gain windows directly on the audio midi windows. with live musicians, you need to tweak them a lot, and using the menu it is not very convenient. you loose too the visual cue of the fader One great option in my opinion will be the possibility to have a midi learn fonction on this fader, so you can easily tweak them on stage.
Thanks! More cool features are coming!and thanks for all the previous update, Magic is really become a reference for digital art !
-
- Posts: 712
- Joined: Sun Sep 14, 2014 8:15 am
- Location: UK
- Contact:
Re: UI suggestions
Please may we have the option to reduce as well as boost gain?Eric wrote: There's probably enough room to have the gain sliders in the Audio/MIDI window
-12dB to + 24dB adjustment maybe.
Re: UI suggestions
Sure, no problem.
One thing to be aware of though (which you may already know): once the signal has clipped, you can't un-clip it. Reducing the gain would therefore give you a quieter but already-distorted signal.
One thing to be aware of though (which you may already know): once the signal has clipped, you can't un-clip it. Reducing the gain would therefore give you a quieter but already-distorted signal.
-
- Posts: 712
- Joined: Sun Sep 14, 2014 8:15 am
- Location: UK
- Contact:
Re: UI suggestions
Thanks Eric!Eric wrote:Sure, no problem.
With respect, I think it is more likely that clipping would occur within Magic because the gain has been increased. Pre-recorded music is usually normalised to peak just below clipping level, so when the source is a music player inside the host PC it's likely the signal will be clipped if level raised further (especially with +24dB gain available).Eric wrote:...once the signal has clipped, you can't un-clip it. Reducing the gain would therefore give you a quieter but already-distorted signal.
I posted some related further thoughts here:
http://magicmusicvisuals.com/forums/vie ... p=824#p824
-
- Posts: 176
- Joined: Tue Aug 26, 2014 11:22 am
Re: UI suggestions
one other suggestion, ( maybe I miss this of course) :
the possibility to have the midi learn fonction for the prev et next entry button , that's will be very useful on stage. Btw , 1.5.2 is really a great update, congatulations !
the possibility to have the midi learn fonction for the prev et next entry button , that's will be very useful on stage. Btw , 1.5.2 is really a great update, congatulations !
Re: UI suggestions
Yep, I was specifically referring to live input. That's what I originally intended the audio gain to be used for. But I can see now that it would be useful to lower the gain for file playback as described in http://magicmusicvisuals.com/forums/vie ... ?f=4&t=236.With respect, I think it is more likely that clipping would occur within Magic because the gain has been increased. Pre-recorded music is usually normalised to peak just below clipping level, so when the source is a music player inside the host PC it's likely the signal will be clipped if level raised further (especially with +24dB gain available).
Thanks . I know that more MIDI control is something everyone wants and I'm making it a priority.one other suggestion, ( maybe I miss this of course) :
the possibility to have the midi learn fonction for the prev et next entry button , that's will be very useful on stage. Btw , 1.5.2 is really a great update, congatulations !
Re: UI suggestions
-hey, i noticed that we can press spacebar to maximize/minimize modules. would be great, if we could select multiple modules and then also press space for this. this does work, when the modules are selected with ctrl-click, but not when dragging a selectiono area over them.
-also as space is also used as "enter" on selected buttons or icons, it quickly gets confusing when i press space to maximize a module, mouseclick on the bypass to bypass it, then want to press space to minimize it again, but instead it unbypasses it.
-also to be able to opt in that bypass/power param's are always shown in modules.
-also as space is also used as "enter" on selected buttons or icons, it quickly gets confusing when i press space to maximize a module, mouseclick on the bypass to bypass it, then want to press space to minimize it again, but instead it unbypasses it.
-also to be able to opt in that bypass/power param's are always shown in modules.
Re: UI suggestions
Actually what's happening is that when you click on a module, the minimize button is the first button, so it gets focused by default. Pressing the Tab key will then go through all the buttons/boxes in order, focusing each one. Pressing the Space bar will toggle whatever button/box is currently focused.hey, i noticed that we can press spacebar to maximize/minimize modules. would be great, if we could select multiple modules and then also press space for this. this does work, when the modules are selected with ctrl-click, but not when dragging a selectiono area over them.
The shortcut for toggling minimize on any selected modules is Ctrl/Cmd-M.
Sure, that's a good idea.also to be able to opt in that bypass/power param's are always shown in modules.
Re: UI suggestions
aah, alright, so i'm wrong trying to use space anyway. okay thanks .
- also faster scroll speed, vertical and horizontal, with the mousewheel, i mean.
- zooming out.
- also faster scroll speed, vertical and horizontal, with the mousewheel, i mean.
- zooming out.
Re: UI suggestions
- add "replace with>paste" to the context menu. like the rmb>insert paste on an existing connection.
Re: UI suggestions
Ok sounds good. Zooming out will have to wait for Magic 2.0 though, as it will require a major UI redesign.
Re: UI suggestions
UI related ideas:
To be able to change the color of scene tabs. I was also wondering whether having different colors for modules would be useful, but it could get distracting.
Another idea would be to have the scene tabs (optionally) running vertically down the left side of the screen.
To be able to change the color of scene tabs. I was also wondering whether having different colors for modules would be useful, but it could get distracting.
Another idea would be to have the scene tabs (optionally) running vertically down the left side of the screen.
Re: UI suggestions
I actually had that as an option in the original Magic prototype, but a lot of the testers didn't like reading the text sideways, so I just took it out. Ended up being easier for me anyway .Another idea would be to have the scene tabs (optionally) running vertically down the left side of the screen.
Yeah some other people have suggested that. I've wanted to keep the interface clean and not worry about coming up with an algorithm to determine the selection color based on the background color. But I have it on my list of things to look into later.To be able to change the color of scene tabs. I was also wondering whether having different colors for modules would be useful, but it could get distracting.
Re: UI suggestions
-ability to organize the noodling with colors or frames. an example from blender nodes:
-display the amount of available vram like this: 1'970'680 or 1,970,680 instad of : 1970680. for better readability.
-display the amount of available vram like this: 1'970'680 or 1,970,680 instad of : 1970680. for better readability.
Re: UI suggestions
A couple people have suggested being able to choose colors for the modules (instead of just the default blue). I'll start thinking about how to do this in a way that wouldn't be too messy.ability to organize the noodling with colors or frames. an example from blender nodes
Ok that's easy. At some point I may also change it to MB instead of KB since KB is not too significant any more.display the amount of available vram like this: 1'970'680 or 1,970,680 instad of : 1970680. for better readability.
Re: UI suggestions
Actually I imagined the tabs arranged vertically but still with the text horizontal, so it would look like a list.Eric wrote:I actually had that as an option in the original Magic prototype, but a lot of the testers didn't like reading the text sideways, so I just took it out. Ended up being easier for me anyway .Another idea would be to have the scene tabs (optionally) running vertically down the left side of the screen.
-
- Posts: 109
- Joined: Tue Jun 23, 2015 7:42 pm
Re: UI suggestions
Hey I think a great idea would be, add sticky notes with the abiltity to change between a couple of colors, that way we can put a few notes by modules to keep track of projects that get a little overwhelming. Just a thought, because I was gonna suggest different colored modules as well, but I can see thats already been said. I think sticky notes would be a nice addition for organizing scenes. IDK if you can do this in Quartz Composer but being able to minimize these notes to just a single header of a word or two would be ace.
Thanks for all your hard work Eric
Thanks for all your hard work Eric
Re: UI suggestions
Ok thanks. You can also check out https://magicmusicvisuals.com/downloads ... uleOptions and scroll down a bit to the Annotations section. Let me know if it helps.
-
- Posts: 109
- Joined: Tue Jun 23, 2015 7:42 pm
Re: UI suggestions
Yeah I'm sure that will help a ton. I'm currently working on a project that mainly is on one scene so things have gotten a little hairy, this will definately help me keep track of everything much better.Eric wrote: Let me know if it helps.
-
- Posts: 109
- Joined: Tue Jun 23, 2015 7:42 pm
Re: UI suggestions
The only other thing I could say after using the Annotations is too have a option to make the note visable when the module is minimized. That would be perfect
-
- Posts: 712
- Joined: Sun Sep 14, 2014 8:15 am
- Location: UK
- Contact:
Re: UI suggestions
I agree, and have already requested this. Eric suggested "Temporarily I suppose what you could do is put another module near your minimized module(s), such as DepthTest which has no params, but don't connect it anywhere… so its entire purpose would just be to show an annotation".SplatterBrainz wrote:The only other thing I could say after using the Annotations is too have a option to make the note visable when the module is minimized. That would be perfect
There are further comments too - follow this link for full details:
viewtopic.php?f=4&t=281&p=1011&hilit=+annotation#p1011
Re: UI suggestions
Some minor suggestions:
1) instead of audio 0 and audio 1 as the two audio channels, rename them 'left' and 'right'. So also e.g. microphone left / right, instead of microphone 0/1. Even if it's mono, or the left and right are swapped, it might look simpler (for a while I didn't understand why the audio inputs were duplicated!)
2) rename the vidCap module to vidCam. Again, video camera seems a more representative labelling than video capture (which makes me think of recording a video to a hard drive).
Bigger suggestion:
3) move some of the audio editing functions to the audio window. For example, in the 'audio editor' you would have together the volume select, frequency select, and also parameters such as gate, threshold etc. Critically would be to have a visible output of the audio (volume meter). Ideally then to have this editor for each input, so the user could set up multiple versions of the audio (e.g. one bass with a fast response, another for the high end, etc etc). The reason for this, is that at the moment if I want to fine tune the audio signal I have to do it in each module that takes that signal, so I'm often duplicating sets of parameters. Having the audio edited before it gets fed to the modules would keep it all in one place.
1) instead of audio 0 and audio 1 as the two audio channels, rename them 'left' and 'right'. So also e.g. microphone left / right, instead of microphone 0/1. Even if it's mono, or the left and right are swapped, it might look simpler (for a while I didn't understand why the audio inputs were duplicated!)
2) rename the vidCap module to vidCam. Again, video camera seems a more representative labelling than video capture (which makes me think of recording a video to a hard drive).
Bigger suggestion:
3) move some of the audio editing functions to the audio window. For example, in the 'audio editor' you would have together the volume select, frequency select, and also parameters such as gate, threshold etc. Critically would be to have a visible output of the audio (volume meter). Ideally then to have this editor for each input, so the user could set up multiple versions of the audio (e.g. one bass with a fast response, another for the high end, etc etc). The reason for this, is that at the moment if I want to fine tune the audio signal I have to do it in each module that takes that signal, so I'm often duplicating sets of parameters. Having the audio edited before it gets fed to the modules would keep it all in one place.
Re: UI suggestions
The main reason for the numbering is that many users have professional audio cards which have more than two inputs. Like this:1) instead of audio 0 and audio 1 as the two audio channels, rename them 'left' and 'right'. So also e.g. microphone left / right, instead of microphone 0/1. Even if it's mono, or the left and right are swapped, it might look simpler (for a while I didn't understand why the audio inputs were duplicated!)
In this case, "left" and "right" wouldn't really make sense, because there are 8 analog inputs. So what would the remaining 6 be called ? Originally when I designed Magic several years ago, one of the main concepts was to allow users to create visuals that respond differently to many simultaneous live audio/MIDI instruments, or many simultaneous audio tracks.
Keep in mind that if the default naming is confusing, you can always rename the inputs:
Fair point. I've actually thought about renaming it, since it was originally intended only for web cams, and some people do get upset when their fancier capture devices don't work. The only reason I haven't changed it is so that people don't get confused. But I may change it in the future.2) rename the vidCap module to vidCam. Again, video camera seems a more representative labelling than video capture (which makes me think of recording a video to a hard drive).
This will actually be addressed in Magic 1.7 . There will be a separate window where you can define and customize global inputs, including choosing an audio/MIDI source and adding modifiers. This input can then be a source for any module parameter, and any adjustment you make to it will be automatically reflected everywhere it's used. Know what I mean?3) move some of the audio editing functions to the audio window. For example, in the 'audio editor' you would have together the volume select, frequency select, and also parameters such as gate, threshold etc. Critically would be to have a visible output of the audio (volume meter). Ideally then to have this editor for each input, so the user could set up multiple versions of the audio (e.g. one bass with a fast response, another for the high end, etc etc). The reason for this, is that at the moment if I want to fine tune the audio signal I have to do it in each module that takes that signal, so I'm often duplicating sets of parameters. Having the audio edited before it gets fed to the modules would keep it all in one place.
Re: UI suggestions
Okay I didn't even consider the multiple soundcard inputs; I often forget the luxury some people have
Regarding the other stuff it sounds like you've got it all under wraps
Regarding the other stuff it sounds like you've got it all under wraps
-
- Posts: 109
- Joined: Tue Jun 23, 2015 7:42 pm
Re: UI suggestions
I figured this was the best place to post this, instead of making a new thread, but im working right now and I got a complex scene going on, thought that it would be really nice when you grab to move a module if you could make it so the connectors got highlighted or turned another color, at least while you move the module.. honestly not a big thing for me because I can see it fine if i move it a bit, but i think it would be a nice touch.
Re: UI suggestions
Sure that's a reasonable suggestion .