« Reply #3 on: Jan 17 th, 2015, 11:09pm »įirst a gentle warning about the sysex and your setup.ģ* MIDI Global Channel *0-F = Channel1-16 Can you please give me a rundown of what they should be please?īy the way, I have my M1 set to Global Channel 2 instead of 1 because during a gig I use it in a multi-keyboard setup and have them chained together. I don't use MIDI-OX very often so I'd like to make sure I've got all the options set corectly in MIDI-OX. « Last Edit: Jan 16 th, 2015, 7:47pm by Breath » Of course when you send the data back you will overwrite what was there and so your edits will be lost forever so I would test your dumps by first.Ĭopy an edited patch to a spare patch in the M1 (call up the patch and save it to a new location) now dump just this new location's patch to MidiOx.Īs an extra precaution if you are unsure about the data, just repeat the dumps a few times to new file names so you have copies. You could have any number of sysex messages from any synths in the same file if you wanted to ( I use to do this for each piece I wrote so it was all in the one spot). When you press the Done button it closes the file. The manual dump routine in MidiOx opens a file after you tell it what the name is and just grabs any sysex messages that come in and adds them to the file. You might like to start naming the file based on what you have downloaded - the single patch or Combi name and the groups of data with common prefix so it is all grouped together. When it receives a sysex start byte it thinks 'oh this must be a new message.'įrom memory, the M1 will allow you to dump 1 program (patch) or all programs or 1 Combi or all Combis or all the data. Your synth knows where the data finishes when it receives a sysex end byte. You can store this message in a file, but you can also have as many sysex messages in the one file. System Exclusive message = Sysex is stored in a file with syx at the end.Ī Sysex message is just a Sysex start byte then data then the Sysex end byte. I'm not sure if I'm doing something wrong or what. Now that I performed a Data Dump All from the M1 to the PC, I figured the dump process would create numerous files the same way but it didn't. When I first loaded the M1 with the factory sounds, I have no idea if these files were used (or any others for that matter). It created numerous files named "Programs01.SYX", "Prog_Comb01.SYX", "Factory.SYX" etc. The reason I question it is because when I first obtained the factory sounds, they were in a zipped file which of course I unzipped. I connected my M1 to my PC, performed a DATA DUMP ALL and it appears that it worked however I'm not 100% certain that it backed up everything. I have since tweaked patches on the M1 and now I wish to save everything on my PC in case the battery goes dead or some other problem occurs. Replaced with a new battery and loaded in the M1 factory sounds. When I first received my M1, the battery was dead. I have all the necessary hardware (MIDI>USB cable) and software (MIDIOX). I have a Korg M1 that I need to backup to my PC. Topic: Korg M1 Data Dump questions (Read 8819 times) Questions and Discussion (Moderator: Jamie OConnell) « MIDI-OX User Forum - Korg M1 Data Dump questions »
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |