Re: Morpheus Memory
2017-12-13 by smw-mail@...
I just spent about 1/2 an hour looking up the
manual and replying in the P2K group. Lemme get you the replies for the
benefit of anyone else who is interested. Not sure this will help, but maybe.
ONE:
------------------------------
I have never used a Morpheus, so the sysex data transfer i/o is a bit confusing to me. It does not appear to be as straight forward as the P2K sysex i/o. I have looked at the manual.
From this:
" There is only one edit buffer each for the current preset, the current hyperpreset, and the current midimap. Only one preset, hyperpresetor midimap can be edited ata time via SysEx commands and changing the current preset, hyper or midimap erases the associated editbuffer."
it almost sounds like when you make a dump request, the preset is put into the edit buffer, and then you get it from the edit buffer.
" Preset data may also be transmitted or received in a single block (one complete preset) using system exclusive commands. A preset data request may be issued by a host computer, to which the machine will respond sending the data block for the requested preset. Conversely, the computer may send new preset data which will replace the specified preset currently in the machine."
This seems to be consistent with what I am guessing happens.
(1) Make a request.
(2) The preset data goes into the edit buffer.
(3) The Morpheus send you the data requested from the edit buffer.
However, if I am right, when you send a preset to the Morpheus you might not just be putting it into an edit buffer, but into the slot as well. However, it could be that "the specified preset currently in the machine" refers to just the edit buffer and then the user has to save it before it gets stored. I would hope its the latter. That would make sense when it says that if you change to another preset the edit buffer gets erased.
Command 00 seems to be the preset request--followed by ll mm for the preset number.
Again this is just what I am getting from the manual..
Hope I understand what you are looking for and hope this helps.
Steve
TWO:
--------------------------------
From page 252 of 284 in the Morpheus Manual pdf (Rev C) online:
ONE:
------------------------------
I have never used a Morpheus, so the sysex data transfer i/o is a bit confusing to me. It does not appear to be as straight forward as the P2K sysex i/o. I have looked at the manual.
From this:
" There is only one edit buffer each for the current preset, the current hyperpreset, and the current midimap. Only one preset, hyperpresetor midimap can be edited ata time via SysEx commands and changing the current preset, hyper or midimap erases the associated editbuffer."
it almost sounds like when you make a dump request, the preset is put into the edit buffer, and then you get it from the edit buffer.
" Preset data may also be transmitted or received in a single block (one complete preset) using system exclusive commands. A preset data request may be issued by a host computer, to which the machine will respond sending the data block for the requested preset. Conversely, the computer may send new preset data which will replace the specified preset currently in the machine."
This seems to be consistent with what I am guessing happens.
(1) Make a request.
(2) The preset data goes into the edit buffer.
(3) The Morpheus send you the data requested from the edit buffer.
However, if I am right, when you send a preset to the Morpheus you might not just be putting it into an edit buffer, but into the slot as well. However, it could be that "the specified preset currently in the machine" refers to just the edit buffer and then the user has to save it before it gets stored. I would hope its the latter. That would make sense when it says that if you change to another preset the edit buffer gets erased.
Command 00 seems to be the preset request--followed by ll mm for the preset number.
Again this is just what I am getting from the manual..
Steve
TWO:
--------------------------------
From page 252 of 284 in the Morpheus Manual pdf (Rev C) online:
Request preset. Uses preset index values (not the same as program
numbers). Request for card presets will be ignored if card is not
present. Preset numbers are: 0-127 RAM, 128-255 ROM, 256-319
CARD. Values 0x0400+ the bank number (0-2) represent request for
banks. (Banks are blocks of 128 presets.)
F0
SysEx Status Byte
18
E-mu Mfg. ID
0C
Morpheus Product ID
dd
Device ID 0-15
00
Command ID
ll
lsb Preset Number
mm
msb Preset Number
F7
End of SysEx Status