Having the ability to have blocks or sections within a Grid that are independent from the rest of the Grid might be good thing to have. As a simple example, for my Cubase Grid, I might have a Main grid with most used commands, Audio functions, MIDI functions, PLE’s etc, but there can be Blocks/Sections with their own set of buttons/functions, which can be dynamic/independent from the Rest of the grid. For eg. a Key Switches or Expression Map block/section which gets updated based on Track Name (like how Dynamic Focus Tracking works) but the rest of the Grid with my common functions remain constant/un-changed.
Or one or multiple sections with a grid with different set of functions can be switched with existing latching switches/switch groups functionality.
I understand this kind of behaviour can be kind of achieved by making separate Grids for each of the Expression Maps with common sections being replicated for each of the Grid. But, the issue with that is if I want to change one button in one of my common functionalities, I would have to go and manually change it in all of the individual grids for all of my expression maps which can be a lot of trouble
Not sure how feasible this is but I think it might be an elegant solution to a lot of common asks of composers.
yeah - we get this. We are thinking about the potential design for the “section” object - it is going to be quite complex regarding the handling etc. The challenges:
We would need somehow to store sections to enable DFT switching, right? And if so, how to handle different resolutions for the sections - for example you have got the section object 24x9 and you want to insert this into a 9x6 slot - how should the section behave, should we fit only the sections with matching resolution, how to handle this to be user intuitive.
System performance - that would give additional load to the system - it would function like a grid within the grid.
One of the idea to solve this is to create a section object that would be a “window” into another grid - for example this object would give you access to a dedicated portion of another grid based on the section object position on the grid. And then DFT would just change grids visible in this “window”. We are toying with various ideas but this one seems to be most straightforward.
Yeah, I understand the resolution handling issue. I think fitting the sections only with matching resolutions might be the way to go because scaling bigger sections to smaller sizes might not be functional after all.
One way to go about making it a little intuitive might be to filter the section objects by size i.e when the user adds the section object to a grid and then goes on to assign that section, the list only shows the section objects compatible with that resolution.
May be storing some sort of ‘size’ variable with the section objects that is then used in the filter.
Further filters can be added like showing sections only from a profile or a workspace etc. that the user can check if they want.
I really like the ‘window’ idea as well. It’s simple yet effective
I hope other community members can give their inputs on this as well and we brainstorm this to reality!
Yeah, I agree. It would just need a prompt that specifies the minimum and maximum size of the space required for the currently selected object. A bit like when inserting an X/Y Pad or Snap Shots.
And this ‘Object’ would solve the idea I had for globally editing identical elements across multiple grids. Like a transport section or a group of faders. I could edit/update the object and it would appear updated across every grid. Two birds with one stone.
- we get this. We are thinking about the potential design for the “section” object - it is going to be quite complex regarding the handling etc. The challenges: