Still working - AI help - on refining the Mirage SoundProcess editor preset.
The Mirage is tricky… SoundProcess is tricky…
The issue we are struggling with right now is that the SoundProcess architecture is quite complex… One loads a disk which contains a number of programs. In each program there can be either one patch for the whole key range or a group of patches for certain key ranges. In the orignal SP OS there is no indicator of which patch is active, so one could edit away on a patch which isn’t even used in the Program one is hearing.
To counter that we decided to have button that is called Read Active which is like a patch request. But somehow it is not reliable… The Mirage sometimes doesn’t respond… Most of the times it does… But sometimes it doesn’t… When it responds all values are parsed and the controls are populated… Showing as well the key ranges of the active patches… But when it fails it is only really obvious when watching the midi monitor. So I wanted to basically have an indicator of the read status: IDLE, WAIT or SYNCED. I would be ok with it taking up its own slot but somehow we were only able to do something that had a little outlined box around it versus just the text…
Is there a better way of doing this? I of course thought: "Wow! This looks like an empty box… Can we not just put the Read Active button inside… That kind of worked but then everything got pushed down… With the Read Active contol more where the next line’s Group label should sit…
Our work around so far is to have the status indicated in the bottom status bar. Where of course we are waiting for the font size to be controllable hopefully soon… @martin Will there be control of the color of the fonts used as well?