That's you but when a synth has over 500 presets, I'll be damned if I am going to go through all of them again every time I want to use one for a particular thing. It's easy in Orion, the dozen or so go-to sounds for DUNE 2/3 are stored as Orion presets so they show up at the head of the preset list. OTOH, in Massive and Battery they are just favourited, which is less effort and a much tidier solution. Of course, non-Orion people could get around it by loading DUNE into Komplete Kontrol or Maschine but I imagine they'd rather just use something that makes it easier.
Teksonik wrote:I was editing my last post to say I've seen more people ask for Drag and Drop Automation Routing and that's a feature that would actually make creating patch easier.
Of course, there is a really obvious problem with D'n'D - you can't see everything at once. Look at the way something like Massive is designed - everything you need to D'n'D is always visible, even if it's just as a tab. D'n'Ding an LFO output to Osc 2's pulse width in DUNE, for example, would require you to make sure that Osc 2's controls were visible as well as exposing the LFO controls. It's not ideal which means a complete GUI overhaul if we want D'n'D to be any good.
Teksonik wrote:Another perfect example. I don't have a problem with "workflow" and patches are falling out of Dune 3 with little effort. Dune 3 is already fun to program and dead simple to me.
Well, again, that's you. Patches don't fall out of DUNE 3 for me because I absolutely hate using it. There is krap everywhere - velocity is on the Settings screen, the Wavetable Editor is buried three screens down, you have to go hunting for LFOs, the way layers work is poor and the preset browser is woeful compared to pretty much every other synth in the same price range. If you want to see what I mean, try the demo of any of Sugar-Bytes synths. Their browsers are great.
Don't get me wrong, our next album is going to sound great because of DUNE but it might sound even better if DUNE was easier to work with. As it stands, though, I'm far more likely to go for Thorn, or Equator or V-Station or Vacuum Pro if I want to make a new sound because they are all extremely capable synths that I actually like using. It's only if I cant get something out of them that I'll think about DUNE and, even then, I am far more likely to go to DUNE 2 because it's simpler and easier. In fact, I should probably install the original DUNE, at least everything is where you can see it and get to it and there is very little in it that I wouldn't use at some point.
Honestly, by now I would have thought I'd be over it, especially given that my favourite thing for the last 6 months has been TRK-01 and you can't see anything on it's front panel. The difference, I think, is that a lot more thought has gone into the workflow side of TRK-01 to the point that the way they hide and expose things actually makes sense, where in DUNE it mostly feels like they've put things wherever they could squeeze them in. Even the simple gesture of showing the LFOs by default, not a keyboard that 90% of people will never use, would give some indication that there has been some thought given to workflow but, as it stands, it feels like there has been none at all, which is really frustrating for me and, obviously, others.