Peavey DPM3 midi sysex spec request

Pulling out your hair? Don't know what to do or where to go? Ask in here.
Forum rules
READ: VSE Board-Wide Rules and Guidelines

If your Help request has been solved, please edit your first post in order to select the Image Topic Icon to let others know your topic has been solved.
Post Reply
blueknob
Active Member
Active Member
Posts: 264
Joined: Sun Jul 06, 2008 12:30 pm
Gear: ESi32/E6400U, Novation Supernova, Ensoniq (a shedful), vintage Macs, Hamm C3/122
Location: England, UK

Peavey DPM3 midi sysex spec request

Post by blueknob » Sat Apr 29, 2017 1:29 pm

Now that I've got this Peavey DPM3se working, I am compelled to investigate it's inner workings. Reading Craig's manual page 8-6, section 8.4 he says "Attention software hackers.." aw bless ;) "To obtain a listing of the MIDI sys ex codes used in the DPM3se, send a self addressed, stamped envelope to.." Peavey etc.

That suggests the DPM3 understands editing over MIDI, I see MidiQuest do an editor, I could do an adaptation for SoundDiver (provided it stops going all wierd on me) or even a simple editor using Ctrlr.

As we now all seek to build archives for this old stuff, I was wondering if anyone has a copy of that spec. :geek:

Rasputin
Active Member
Active Member
Posts: 730
Joined: Thu Jul 21, 2016 4:52 am

Re: Peavey DPM3 midi sysex spec request

Post by Rasputin » Sat Apr 29, 2017 2:53 pm

Yo bluenote, is this it? Or at least close enough?


blueknob
Active Member
Active Member
Posts: 264
Joined: Sun Jul 06, 2008 12:30 pm
Gear: ESi32/E6400U, Novation Supernova, Ensoniq (a shedful), vintage Macs, Hamm C3/122
Location: England, UK

Re: Peavey DPM3 midi sysex spec request

Post by blueknob » Sat Apr 29, 2017 7:32 pm

Thanks for that Mr R, but I'm guessing that is possibly an addendum for the DPM V3, there might be a version for the DPM3. I'm saying this based on what I've got to work so far. I first notice the machine ID is different. If I send 2 (in the sysex string for machine ID as stated in the V3 doc) my DPM does noffin, but if I send 01 it responds. So I'm thinking this DPM 3 has the ident 1.

I have another clue in that: F0 00 00 1B 02 01 00 02 7D F7 does something, I think it is one program retrieve, which is not the same code as listed in the V3 spec.

Also, program names on the DPM3 have 6 characters, the V3 has 13.

As you know, we techs look for clues in the belief we eventually get our prey :lol:

Rasputin
Active Member
Active Member
Posts: 730
Joined: Thu Jul 21, 2016 4:52 am

Re: Peavey DPM3 midi sysex spec request

Post by Rasputin » Sat Apr 29, 2017 10:43 pm

blueknob wrote:Thanks for that Mr R, but I'm guessing that is possibly an addendum for the DPM V3, there might be a version for the DPM3.
Yeah, I knew it wasn't exact but I thought it might get you started in the right direction.

As an alternative, would it not be possible to capture MIDIQuest traffic with MIDIOx or the like and fill in any missing gaps in the document?

Rasputin
Active Member
Active Member
Posts: 730
Joined: Thu Jul 21, 2016 4:52 am

Re: Peavey DPM3 midi sysex spec request

Post by Rasputin » Sat Apr 29, 2017 10:58 pm

blueknob wrote:I have another clue in that: F0 00 00 1B 02 01 00 02 7D F7 does something, I think it is one program retrieve, which is not the same code as listed in the V3 spec.
Data Dump Request for the Current Program = F0 00 00 1B 02 01 00 02 7D F7
Data Dump Request for the Edit Buffer = F0 00 00 1B 02 01 00 02 7E F7
Data Dump Request for All Programs = F0 00 00 1B 02 01 00 02 7F F7
Data Dump Request for Specific Program = F0 00 00 1B 02 01 00 02 xx F7 (where xx is hex value of 00-99 in decimal)
Data Dump Request for Current Effect = F0 00 00 1B 02 01 00 05 7D F7
Data Dump Request for Edit Buffer Effect = F0 00 00 1B 02 01 05 7E F7
Data Dump Request for All Effects = F0 00 00 1B 02 01 00 05 7F F7
Data Dump Request for Specific Effect = F0 00 00 1B 02 01 00 05 xx F7 (where xx is hex value of 00-99 in decimal)
Data Dump Request for Sequences = F0 00 00 1B 02 01 00 03 F7
Data Dump Request for Globals = F0 00 00 1B 02 01 00 07 F7
Data Dump Request for Drum Kits = F0 00 00 1B 02 01 00 09 F7

blueknob
Active Member
Active Member
Posts: 264
Joined: Sun Jul 06, 2008 12:30 pm
Gear: ESi32/E6400U, Novation Supernova, Ensoniq (a shedful), vintage Macs, Hamm C3/122
Location: England, UK

Re: Peavey DPM3 midi sysex spec request

Post by blueknob » Sun Apr 30, 2017 8:05 am

Thanks for the codes Mr R, they are the only reference to the DPM3's sysex code I've found so far. I'm using the "current program" dump. I receive the sysex dump but... there must be some secret Peavey code as when I look for voice name, which should be ascii... noffin, so I'm yet to figure out how Peavey encoded their code! SoundDiver has easy options for different data encoding but none yet have yielded a result.

As you, I would have expected there to be similairities between the V3 and DPM sysex, anyway rain is forecast today so more head scratching planned. :lol:

Rasputin
Active Member
Active Member
Posts: 730
Joined: Thu Jul 21, 2016 4:52 am

Re: Peavey DPM3 midi sysex spec request

Post by Rasputin » Sun Apr 30, 2017 9:39 am

A possible solution to that is to change one letter in the name and then redump the patch. Compare and contrast to the initial dump to the secondary dump. That should be illuminating.

Sonus
Newbie
Newbie
Posts: 58
Joined: Sun May 31, 2015 5:33 pm

Re: Peavey DPM3 midi sysex spec request

Post by Sonus » Sun Apr 30, 2017 12:00 pm

blueknob wrote:there must be some secret Peavey code as when I look for voice name, which should be ascii... noffin
Each ASCII character has two 4-bit nibbles:

Image

Update: almost complete list, the minus sign is missing so there might be an error...
Last edited by Sonus on Mon May 01, 2017 7:30 am, edited 1 time in total.

blueknob
Active Member
Active Member
Posts: 264
Joined: Sun Jul 06, 2008 12:30 pm
Gear: ESi32/E6400U, Novation Supernova, Ensoniq (a shedful), vintage Macs, Hamm C3/122
Location: England, UK

Re: Peavey DPM3 midi sysex spec request

Post by blueknob » Sun Apr 30, 2017 4:31 pm

Yey! Thanks Sonus that list seems correct, I can now pick out the program names.

Sadly it takes 20 mins wresting with SoundDiver to 1 min of DPM investigation. SD is such a sod, things just don't work as they should, more bugs than in a tramp's underwear :lol: The SD Progamming manual is written in Germalish by our friend Michael H, geez it's a real pain. :roll:

******** UPDATE **********
I'm sure Mr R can share this moment with me.... YYYYEEEESSSS!!!!! :yahoo:

I've been wresting with the many quirks of SoundDiver plus it's very confusing Programming Manual, I finally managed to pick out the 4 words out of the whole document that gave me the clue.. SIN and BNK at the right place did the trick! I now got a bank editor running, with all the names shown as should be. So if any of you got SoundDiver + DPM3 and want a bank editor/librarian, just ask.

Next up a parameter editor although preliminary tests show this could be a very clumsy affair. The DPM seems to need 2 CC pointers to a parameter then multiple inc/dec messages to change it. I'd hope there is a better way.

Post Reply