Jokeyman123 wrote: Tue Jun 22, 2021 2:25 pm
I don't know of anyone who has been able to interface a DAW with 'autodetect" to see what the fusion will respond to with a DAW. And I think autodetect with for example Sonar, Protools or whatever software can do this-might be needing a sysex 'string'-or an instrument's hardware ID just to get into the Fusion-this is just a guess and as parametric has already verified-again-sysex was never switched "on", or developed at all for the Fusion, ouch.
I think I've mentioned before in here that I HAVE created a .reabank file for Reaper.
By default, Reaper comes with a GM .reabank file, which can be loaded and complies with the GM order of instrments . . .
My .reabank file covers the
ROM content of the as received Fusion, about 960 programs arranged in the Banks we are all familiar with.
Beyond these, each Fusion will vary as Banks are randomly added, so the ORDER of the additions will require a .reabank file matching
that order. So, if you wish to work this way, then you
can make a .reabank file to match your Fusion . . . .
Whether there is an instrument ID dormant in the Fusion is unknown?
I suppose it's a casualty of the sysex NOT being switched on?
I don't know enough about sysex to know if the ID is part of that instruction set - or independent of it . . . . ?
I thought it was part of the midi implementation . . .???
If you DO install the Fusion .reabank file in Reaper, then Reaper WILL have a dropdown of the Fusion's Programs -
and the programs can be selected in Reaper and the Fusion will select them via midi.
I uploaded the Fusion .reabank file to the Reaper-Stash - where you can download it.
In all likelihood, you can hack that file to suite other DAWs. (I used opensource notepad++ to do mine).
Chris