I Agree, Ideally any window that holds presets should be searchable and possible to sort by column.
Trouble is, that preset data just comes straight from a .xml file and is not indexed as per the media bay style pop-ups, which allows for searching/sorting.
Because of that, You can at least sort the list how you want manually by editing the RAMPresets.xml file. i.e. moving the individual branches within the “ControllerLaneSetups” parent.
However, Editing .xml/text files is something Reaper users love as it offers them flexibility, but it shouldn’t be necessary in a ‘ready to go’ suite like Cubase.
You’d hope before every major update, someone at Steinberg is tasked with sweeping through the entire Cubase interface and flagging such items. Almost as a ‘usability’ safety net. - Once they’re on top of it, it should be easy to maintain.
regardless of .xml vs individual presets files… You’d think they could code the program to be able to interpret the .xml files in a number of ways… Alphabetize does work with macros if you close and re-open in the key commands window (or create a new macro), so some functionality can occur with the program reading .xmls. The downside seems to be having it done in real time, and or, the devs have to code this in each specific instance instead of using a recurring bit of file database and preset container code.
In this context of Controller Lane Setup, even a floating pop up window would be great - I would even factor that into my workspaces because then changing controller lane setups could be very quick on the fly.
They give us the PLE so we don’t have to scroll to a track.
They give us Markers so we don’t have to scroll to a section of a song.
But they give us stupid little menus and UI’s all over the place where the only way to find anything is to scroll.
Just doesn’t add up. They must have employed an idiot savant during this period of Cubase’s development.