The UX of digital equipment _really_ sucks. At first I thought it was because it was a new technology still in infancy, but things haven't improved since and we are still emulating analog controls. VST interfaces often have static background image (skin) and 'knobs' you control with your mouse. Actual hardware usually features rotary encoder or buttons to navigate the menu system with several layers of depth. This is tedious and hampers creativity. One positive example is Teenage Engineering OP-1, they seem to know what they are doing.
I'm currently building digital instruments for android phones and I refuse to add any UI elements until I figure out something that makes sense. Until then the interpreted Lua code is the user interface. I would be very interested in some new UI patterns for touchscreen that take good advantage of interaction between user actions and visual feedback.
It is completely baffling why software synths and routing software etc. feels the need to make itself look like a patch board and have rotary knobs and things. Can't we come up with a set of conventions for software-native synth UIs? Sure the physicality of real knobs and sliders is nice on real hardware, but on a screen - especially non-touch systems - there's no way it's the best option.
> but on a screen - especially non-touch systems - there's no way it's the best option
There is a good option - but the current, dumb UX fad, rejects it whoreheartedly. That option is keyboard. Give everything a keyboard shortcut and let the user learn them (if at least by providing a visual overlay listing shortcuts straight on the interface).
If something is a tool - not a shiny cloud SaaS toy intent on getting audience to drive the hockey-stick graph straight into acquihire - users will learn keyboard shortcuts.
I always let my users click on a knob to direct enter a value with the keyboard. But keyboard shortcuts to increase / decrease a value -- that's just a pain. Mouse drag / mouse wheel is far faster at going between coarse and fine adjust.
There are software synths that don't follow the "virtual patch panel" concept: Audiomulch and Supercollider come to mind.
Audiomulch has a graphical interface. Signals are processed by constructing a graph where each line represents an audio channel that can be routed between blocks that perform specific functions.
Supercollider is more like a programming language, you can think of it as a DSL for audio generation.
Both of them can interface with hardware, of course.
I think there will always be a strong demand for tactile hardware interfaces, regardless of what people come up with on a laptop application. The kinaesthetics of making sound by manipulating something physical is so satisfying and intimate.
Knobs are still the best option I've come up with, they act like sliders with the mouse, yet they are smaller so you can have more density. You can also draw a longer track for a given control size, 2pir > 2*r. They often get assigned to a knob on a midi controller anyway, so it makes sense.
My knobs look like software, I refuse to do screw heads, metal finishes, etc.
I haven't done much touch screen software, so no comments there.
Ableton Live in conjunction with the Push is a fantastic, very tactile, very musical solution to this. The Push is a very well-designed hardware instrument that, because of its tight integration with Ableton, has much of the flexibility of software. It's a really interesting approach and very productive from a music and creativity standpoint. This YouTube video gives a good sense of it:
I believe quite strongly that for most people, utilizing hardware of some kind (pad controllers, keyboards, etc.) is essential for making music. Music is generally made by playing instruments. It is the small errors, the groove, the emphasis, the spirit/heart/soul of playing an instrument, that makes music feel alive and interesting and vital. If you're just clicking around with a mouse, you're programming it, and programmed music sounds programmed. Overly precise, inhuman, etc.
In Glenn Gould's debut on US television, conductor Leonard Bernstein talks about - and then demonstrates - the difference between rote, mechanical playing of a score (i.e. "programmed music") vs. a performer's interpretation of it (i.e. the heart & soul that I'm talking about). The discussion starts around here:
You probably mean software equipment, because there is lots of digital music equipment with good UX. See for example Mutable Instruments' Tides or Rings modules, 4ms Spectral Multiband Resonator etc. - no menus, no displays, one knob one function (well there are sometimes 'special modes' and easter eggs of course).
For those boxes, 'digital' is just implementation detail. User interface and interface towards other equipment is still completely analog. I agree that they look very clean and usable.
I don't think there's anything wrong with displays. They offer immediate and quick insight into internal state and operation. The issues appear when you introduce modal workflow, with some features only available in some modes.
Worst offenders in category of hardware equipment are probably guitar multi-effects and synthesizer workstations. They cram so much functionality with so little thought given to flow and usability.
I would absolutely love to one day own an OP-1. Teenage Engineering does amazing work. All of their stuff has a certain tactility to it. They definitely put a lot of thought and love into their work.
For those that can't justify spending about $1k for one, their Pocket Operator series is pretty fantastic.
I also recently bought myself a Novation Circuit, which honestly has the feeling of Teenage Engineering's interface design (minus a lot of the whimsy). For about $300, it's a fantastic little groovebox that I'll be getting a LOT of mileage out of.
I'm sitting in a room full of synths from 1971 through 2017 and I still think my OP1 is one of the most delightful, amazing things in here. You can find them used for around $600.
I'm currently building digital instruments for android phones and I refuse to add any UI elements until I figure out something that makes sense. Until then the interpreted Lua code is the user interface. I would be very interested in some new UI patterns for touchscreen that take good advantage of interaction between user actions and visual feedback.