Thanks Steve.
Yes it is a confusing spec. The back section of my manual has more of my writing than theirs.
The Morpheus (and P2k) can retrieve the patch directly without having to load it into the edit buffer (emu seems to call the edit buffer a "Scratch" area)
Unfortunately I haven't been able to request or send the patch in the scratch area of the Morpheus.
Requesting a patch, as you said, is a CMD 00 request with the Patch number and Bank.
User 00 00 to 7F 00
ROM 00 01 to 7F 01
You can get a bank (127 presets) by using the same request with 7F in the Bank position and 00 for user and 01 for ROM
F0 18 0C 00 00 01 7F F7 gets all the ROM presets
In the P2k 7F 7F is the edit buffer, but there isn't a reply from the Morpheus with this request.
All the Parameter requests and sends effects the scratch area so you can get the patch by sending many parameter requests and the reverse to fill the scratch area with a new patch. That is a lot more data and without a checksum (which the bulk preset data has) it is possible there will be data corruption.
As you cursor down the list in my Library program it sends the highlighted patch to the synth 'scratch' buffer for testing. I find this a good way to go through the generated patches after a 'Mix' or 'Morph' as well as when I have forgotten the name of a patch that I need.
I would like to keep this feature, but I don't want to send every parameter separately.
So I could send the bulk patch data to patch 128 and send a patch change message to pop it into the scratch area.
On the other hand I don't want to constantly write to memory like flash that has a small finite life and have it stop working.
I think patch memory is just SRAM in the Morpheus (unlike the P2k), but I would like to be sure from those that know this kind of hardware.
Thanks
Royce