To help find the needed input quicker, it would be great if we could have the rows of inputs easier to define. For example I would like the first row of inputs all be NDI inputs (10 inputs), the second row be PTZ camera 1 (6 preset) and the third row be PTZ camera 2 (8 presets). If we could require an input to start on a new row then I would define input 11 to start on a new row and input 17 to start on a new row. Work flow would be much faster and the likely hood of having a PTZ camera moving while being the active window would be reduced..

The problem is that vmix places the inputs dynamically to the app windows. It#s not predicable how many inputs fit into the area. Expanding the audio section can be used to get a certain amount of real estate for the video section but even then you can add a cariage return into the inputs if there are less than needed for a given row.

The best option would be to use the coloring as doggy said. That way you have just the inputs of interest visible.