Prophet 5 Sysex

Hi,

i own 2 Prophet 5 with winecountry MIDI Kit installed and i can't do the Sysex works with the Pro-53. I followed the instructions fromt he manual but nothing. Holding RECORD then PROGRAM 2 to send the SYSEX information and then play any note on the keyboard. but nothing, i hear the same presets from the pro53 and no knob from pro53 are moved. What's wrong ? i guess the winecountry are the exact copy as the original one, or maybe the software ROM 10.5 of the Prophet 5 are different as the original one ? some codes are missing ? Anyone was able to do the sysex transfer ?

regards,

 

Hi,

As a test can you record the sysex into a daw to check that it is sending the data.

If it is save the recorded midi and zip it and attach it to a post here and I will try sending it to the plugin.

Cheers

Andy

 

Sure, here's just one program atached.

Hope can work for you.

regards

 

Also i noticed when using MIDI-OX i need to set the buffer input at 20 bytes in order to receive the sysex. The default setting is 256 bytes and the MIDI-OX don't reveice anything. The Bome's SendFX sysex utility don't have this problem. The Snoize Sysex Librarian for Mac works fine, but not with a Mbox 2 midi, i had to use another midi interface to send the sysex (Motu fastlane).

 

Hi,

I am a bit busy today and tomorow, I will have a look at this on Sunday for youy.

All the best

Andy

 

Hi,

I have had a look at this and the sysex you have sent has 33 bytes, I have other sysex files from a prophet 5 and they are 53 bytes so this is a little strange.

I have tried getting the pro53 to take your sysex and also the examples I have and have had no luck.


I don't know if anyone has ever got this to work, maybe Eric (Ewistrand) can offer some advise?

Edit: I have sent an email to Eric to see if he can help us out

Cheers

Andy

 

I can tell you why the OP's sysex probably isn't working; it's the WineCountry kit. As far as I know, sysex transfer will only work with a Rev3 Prophet with the original Sequential interface. Why? Because the third party MIDI conversions added various parameters that are included in the sysex dump.

Is your sysex from a Rev3, Andy?

ew

 

Hi Ew,

Thanks for getting back to us.

I have rev 3 sysex files, using the standalone app and sending the sysex from a librarian through a physical midi loop to the app, I get no joy at all!

Maybe it is a problem with the OSX version, I will boot up into XP latter and give it a go.

All the best

Andy

 

Can you slow down the sysex transmission rate, Andy?

I haven't tried loading sysex into Pro-53 in a long time, and when I did, it was full banks. If you want to send me a .zip of the patches, I could try it here.

ew

 

Hi Ew,

I will have a look to see if I can slow it down.

I have included a zip with some rev 3 sysex banks.

Cheers

Andy

 

I just stumbled over this thread when searching for something similar regarding sounddiver and prophet on google.

I have a Prophet 10 and there is one thing to keep in mind when sending sysex from it: There is no termination string ($F7) sent. Same applies to the Prophet 5. The prophet5 might send $F0 again for termination. The Prophet10 sends nothing, though.

I don't know how the pro53 handles sysex files(don't have it), but if you look at the midi hexdump there might be a chance that the sysex packages don't terminate with $F7. Maybe here lies the problem? You could try to manually add the termination code.

Here you can read some further information about this: http://analog.no/patch/patch_info.htm#prophet-5

 

HI,

Thanks for the info, I did have a look before and they had the F7 byte at the end.

Cheers

Andy