rezoneight wrote: ↑
Fri Dec 06, 2019 12:44 pm
perpetual3 wrote: ↑
Fri Dec 06, 2019 9:56 am
Haven’t followed all the pages, but it seems to me that the analysis settled on using theoretical UI principles to determine what is bad / good UI. In my opinion it’s reasonable to assume that not everyone reads every post of every thread and that perspectives that drop in at deeper levels of the thread can indicate the direction a thread has taken.
This particular part of the conversation is one page back I believe. Nobody has settled on anything. I asked stefken to say why he thinks the MX UI is bad.I completely disagree not only with the opinion but with the premise that it can all be scientific. Everyone is entitled to their opinion. I'm curious about why some think the UI isn't good. The thread *is* titled "Opinions on Massive X". So, we're sharing our opinions.
I’ve barely touched MX since the 1.1 update so some things I remember might have changed. I’m also traveling without laptop right now so I cannot check if any of these things have changed.
MX is the most click heavy softsynth I have. There are many tabs and lots of little menus all over. There is no support in MX for mousewheel. So one cannot hover over a menu and use mousewheel. It is necessary to click to open the menu, click to select and then click to close. There is also no support for arrow keys to move through menus and other lists.
There are no parameter values displayed. There are also no options for copy/paste of say an Osc. If I have an Osc in one preset that I might want to use in another, it is impossible to do that.
MX has no undo/redo. Okay, this I can work around when I want to try something by looking at the existing parameter value, edit it and go back to the original value if I don’t want the edit. But MX does have parameter values either. So then I would have to save it as a preset, try the edit and the reload the preset to make sure I get exactly back where I was. Quite clunky.
If I want to see all possible parameters that might be controlled by a macro in an existing preset, it is necessary to click on 18 different tabs to check as there is no visual feedback which tabs have modulations.
I vaguely remember that this might have changed, but there was no FX bypass... one had to bypass each of the FX individually and could only do so on the routing page. SO that is 5 clicks for a task that is 1 click on other synths I use. Etc.
These are a few things off the top of the head why I didn’t like working with MX... visually I like the appearance of MX, but I found the workflow tedious in comparison to other synths I regularly use.