Mastermind GT Editor Feature Request

skracus

Well-Known Member
Hi Ron,

When populating songs into the setlist would it be possible to have the song number in the set list automatically advance once a song is selected from the "Available Songs" to eliminate having to go back to the Songs In The Setlist, click the next song number and then go back to available songs to select the next song? Would save a lot of clicks if it could advance on its own and we could stay in the available songs area and just click the next song. If an error was made we could always select the song number again and correct the selection and continue on from there. Also, would it be possible to put a "clear" or "reset" button in the setlists page that would clear all the songs in the selected setlist? I've been impoting blank setlists into my GT22 to erase them but it would be helpful to be able to do this in the editor. Thank you for your consideration.

Best regards,

Steve
 
Hi Ron,

When populating songs into the setlist would it be possible to have the song number in the set list automatically advance once a song is selected from the "Available Songs" to eliminate having to go back to the Songs In The Setlist, click the next song number and then go back to available songs to select the next song? Would save a lot of clicks if it could advance on its own and we could stay in the available songs area and just click the next song. If an error was made we could always select the song number again and correct the selection and continue on from there. Also, would it be possible to put a "clear" or "reset" button in the setlists page that would clear all the songs in the selected setlist? I've been impoting blank setlists into my GT22 to erase them but it would be helpful to be able to do this in the editor.
I like your suggestion of auto-incrementing the setlist programming.
For your second request, I can see how that would be useful for managing a library of set lists.
 
Another request for the editor, and one that I solved for myself by writing a little Mac application, but it'd be super handy if it were directly in the editor:
Upon opening the editor, if a Mastermind unit is identified as being connected
(1) Read the config file from the MM
(2) Save it in the default local location, naming it using the template [yyyy-mm-dd] + [timestamp including seconds]

This ensures that every time you power up the editor, it makes a backup of the sysex from the unit.
 
Another request for the editor, and one that I solved for myself by writing a little Mac application, but it'd be super handy if it were directly in the editor:
Upon opening the editor, if a Mastermind unit is identified as being connected
(1) Read the config file from the MM
(2) Save it in the default local location, naming it using the template [yyyy-mm-dd] + [timestamp including seconds]

This ensures that every time you power up the editor, it makes a backup of the sysex from the unit.
My solution was to write a MacOS wrapper application that launched the MM editor and executed the steps outlined above. It required giving my application permissions to access the Finder and launch the MM editor app. I actually wrote it for a touring friend who repeatedly accidentally over-wrote his sysex without backing up first :)
 
My solution was to write a MacOS wrapper application that launched the MM editor and executed the steps outlined above. It required giving my application permissions to access the Finder and launch the MM editor app. I actually wrote it for a touring friend who repeatedly accidentally over-wrote his sysex without backing up first :)
Well done!
 
Back
Top