1. If expanding a device in a rack it would be useful to show it's control panel, like it does when expanding from the 'Devices' panel.
2. To have the 'save/save as/clear/open/reload device' options when focused on a device. Currently these are all labeled as patch options, despite the patch editor windows stating 'device' and also saving to '.device' format, however opening a device doesn't work. This only works when clicking 'open device' (from the context of the device panel header). I can't be sure if it's related but I've found myself having to 're-patch' certain devices and I'm unsure why this is happening. This results in any 'temp' devices having to be renamed from .pat to .device too, unless temp folder contents are moved to library, then they can be added as a subpatch group.
3. A 'group' option for racks. Say I'd like to make visible 10 specific racks, but not use 10 grid columns worth of screen space. Kinda like a 3D grid. This could be expanded by having a 'top rack', or 'focused rack' whose controls/patch's parameters could then be automated, or rather visually exposed to the user.
3.5 An option to automate invisible items with the grid.
4. The option to show/open control panels of patches belonging to either a specific rack, or a 'rack group', in the IB.
5. 'Align to Grid' options for the IB, just like patches.
6. Quicker browser response. Not sure whether this is 'parsing', is that right? Does HH 'parse' the files from whatever folder has been clicked to expand? I'm sat here watching memory increase by between .2 and .7 MB per second as a folder of midi files (no subfolders) are loading into the 'non responding' Usine Browser. Takes a good 5-6 minutes to list the content of about 6000 midi files. Should it take this long? Also, if after regaining the power to respond, I then reset the browser, and expand the same folder it goes through the same process again. Shouldn't the reset button be just to reset the search and minimize all folders? If there's are conversion happening can this not wait until dropping the file because no real action can be performed on them in the browser, unlike the audio files? Or at least keep them in memory? Or is it a graphical display issue?
I've just embarked on a mission to use Powershell to achieve this type of thing (optimal file/preset creating/accessing) in the background.
7. Is multitouch within other window classes easy to implement? Ie for using multi-touch patches and/or mixer from the toolbox fully?
8. Resizing of the preset panel's x and y lengths independently?
9.5 Resizing of the other panels, ie mixer, devices panel, binds panel, etc.
9. A 'Show Grid' pin on the 'Grid' module, or a data bind for the main button. I've been trying to link the main 'show grid' button by sending an OSC message from my other HH instance to an OSC in device, and creating a midi message for the 'Show Grid' button to learn.
I solved the above problem in between typing this message, tending to my attention craving cat, and other activities and it's led to far too many device related discoveries and questions which I must create a separate thread for later today after some sleep.
And I'm still not aware of how to correctly use OSC midi.
the preset panel is only zoomable. The preset is improved in HH2