BillB wrote: The Elf wrote:
Well it can't be any worse than the 'official' one. But looking at the spec I do reckon I can rustle one up in MIDI Designer in a couple of hours.
Correct me if I’m wrong, but MIDI Designer, TB MIDI Stuff etc cannot read incoming patches and parse the parameter values so that they are reflected in the editor settings. Unlike say Patchbase, Codeknobs , MIdiQuest etc editors. So you cannot effectively *edit* existing patches, but you can create them from scratch - perhaps starting with matching INIT values in the editor and the synth. Is that how you work?
I can certainly correct you as far as MIDI Designer goes! I can't speak for the others.
MD will not only reflect incoming MIDI and update the on-screen controls in real time, but it is also possible (with the use of a little plug-in called 'StreamByter') to parse entire sys-ex dumps and update the on-screen controls to reflect the current patch.
I've created several MD Layouts that take advantage of this - the Roland MKS-70 and MKS-80 for example. When I change patch on these devices I capture the incoming sys-ex data and my iPad screen shows me all of the current controls in their correct positions - then I can tweak from there. Anything I tweak on the synths themselves (or from the MKS editors) will also update the MD Layout.
At a pinch, when the device doesn't volunteer its sys-ex on patch-change (the reface series, for example), I can create a 'Get' button that asks the synth for a sys-ex dump. This is useful when I've been tweaking with the MD Layout active and I need to capture and store the current patch. I have reface CS, CP and YC Layouts that take advantage of this.
You can imagine, for such as the reface, which have no patch memories of their own, creating my own MD panels to catch and store their settings is a huge benefit!
From a quick look at the manual the Tetra looks like it has the necessary abilities for me to achieve what I need.