Hey wow, I'm answering this 2 months later (didn't see it originally, sorry, and a forum search brought the thread up).zvenx wrote:I am curious to know what you don't like about the preset browser?noiseboyuk wrote:.........
For what is mostly a preset machine, the patch browser is an archaic horror, designed in 1984. ........
I actually like it a lot....I assume you know you can make your own new favourites and new search categories....
so for example, if you want to access all patches that start with BL....create a new search call BL and it will put all patches with BL in the name in that folder,etc.
The two letter prefixes are the bluntest of blunt instruments. Leads, pads, bells.... yeah sure... what about warm pads, aggressive leads, deep basses? Omni 2 may have gone tag bonkers (it now has the opposite problem of a gazillion similar but slightly different tags all in different places), but the principle of needing tags to sort presets is pretty fundamental.
Nowhere is this more acute than Nexus - easily (and not unfairly) dismissed as a preset machine, the one thing you need if you're dealing almost exclusively in presets is a way to manage them effectively. Nexus 2 doesn't have that. All you have are the crude searches and two letter prefixes. They need useful descriptors like pure, warm, aggressive etc, also genres - dubstep basses may well appear in places other than named dubstep expansions, for example.
I do hope Nexus 3 is in the pipeline, with a tag browser and an overhauled gui so we can work with a window bigger than a postage stamp. I'd love multi outs too, so we can break out the multilayers and route / treat them in the DAW. However, I do like the simplicity of the front panel controls - the key is to retain the quick basic editing simplicity, while greatly enhancing the browser and editing.
Speaking of which, 2.7.2 has a revamped mixer page. At first it seemed confusing, but it is actually something of an improvement - the final tab in Mix, Lay now has a visible signal / fx / chain for each layer, making it considerably easier to see what's going on and tweak it:
There's a ton of room for improvement there still mind - helpfully, none of the editing parameters are labelled in any way whatsoever (FWIW they are oscillator on / off, level, pan, course and fine pitch) and good lord we could do with some indication of when they are triggered (a little flashing dot or something) - at the moment, as it has always been, it's just a case of stabbing all the on/off buttons til you figure it out.
Anyway, my pros and cons above still very much stand to me. Despite my gripes, it's a valuable tool - it could be so much more though, even without giving us full control.