NOTE: For best possible quality, all wave files on this site are recorded directly from the instrument, and tested that they load back again. If you have a problem read through the info below.

Please don’t send requests for other files, I have made everything I have available at these pages.


Loading Sysex files:
The sysex files are raw dumps from the synths. Most will load them back without having you to set any parameter.
Some must be in a special “sysex mode” to work. An example is the MKS-80. Consult your manual for details.

Loading wave files:
These are just recorded from the tape outputs of the instruments, you load them back just as if they were coming from a real cassette player.
Loading presets from “cassette” can be more or less tricky. Some synths have a reliable interface (Korg Polysix) and some are very bad… (Roland JP-6).
If you’re having problems, try different volumes. Most synths prefer a non-distorted, high level signal.
It might help to run it through your mixer and adjust the level there. Try using a headphone output, some synths need a pretty hot signal (OB-8).

All banks on this page have been loaded previously with success.
One way of verifying your setup is to sample a dump from your instrument and load it back again.
If this works the the patches found here should also work as long as you use the same volume during playback.

Saving wave files:
If you already have a patchfile on an audio cassette, load it to the synth first and then sample directly from the synth’s cassette output. Sampling directly from the cassette will add a “generation” and reduce quality.
Some synths have a very weak cassette output and it might be necessary to run the signal through your mixer to get an acceptable S/N ratio. Maximize volume in your wave editor.
Try 22kHz 16 bit first as this to my knowledge will work with any synth. If you want to reduce the filesize, trim off unnecessary header/trailer signals. For most synths only a second or so header is sufficient.
However, certain models requires the load button to be pressed after the tape interface has received the header, and it’s then necessary to make it a bit longer.
Then try to reduce sampelrate and bit resolution until the file wont load back reliably. Most synths will be happy with an 11k 8 bit file.
Compressed formats like MP3 etc. won’t work.

Notes on OSCar sysex:
The first dump is believed to be the factory patches. But obviously some parameters have been changed
before I got it. (ex. patch -6). If someone has an unmodified dump I’d like to hear from you.
The OSCar_alt banks: These are midi files. See the enclosed textfile for details.

Notes on Prophet-5 sysex:
The P-5 has got a pretty awkward way of handling sysex.
First, you have to request each patch individually, bulkdump not possible.
And when the P-5 sends a patch, it’s not terminated with F7.
(This can make it difficult to successfully dump the P-5 since many sysex programs will wait for an F7 before they continue sending requests.)
If one patch is requested it’s terminated with F0, making the total number of bytes equal 52.
But if several patches are requested then the last patch for some reason won’t have the F0 added.
So the size of a 40prog dump is 39*52+51=2119bytes. You then have to manually add an F7 to make the dump acceptable for some seq. programs
giving a total of 2120bytes for a complete bank dump of 40 progs.
That’s what you get when you download the banks at this site.
Then there it’s the problem of bank allocation.
When loaded from tape the patches always ends up in the active bank.
In the sysex code each patch is given a number from 0-119.
All factory sets found here will end up in bank1.
To be able to load them into bank 2 and 3 I’ve made a simple Win3.1 conversion program.

Here you can download the Prophet-5 midi implementation.

Notes on Prophet-10 sysex:
Same comments as for Prophet-5, but the dumpsize is 69 bytes per patch, 68 for the last patch in the dump.