During a recent hardware beta test, production documentation was not available to the testers, such as the details of the patches and multis/programs and associated settings. The beta testers could go individually through all patches and multis/programs to see what is of interest to test, but with a SysEx enabled synth, why not automate the process?
In this case, MDP2 provides the “macros” to send the SysEx queries to the synth, a midi monitor captures the output, which is processed in a Numbers spreadsheet to provide the desired output.
Read more here
Leave a Reply