Questions about making a patch set for Prophet 5/10

[coolwav]

I made 16 patches with my Prophet 10 and will be releasing it as a free soundset

Questions:

- How do I make these compatible with Prophet 5? Do I just lower the Unison voice count to 5 and disable polyphonic unison (PU-2)? I'm not stacking different patches.

- If I export them as banks, do people have to load them in the same location? (Group 1 bank 1 and Group 1 bank 2)
Or can they load them anywhere?
How about if I export them as individual patches?

- I exported the patch banks with Bome SendSX and am thinking of not using SoundTower this time to export.
What's your experience with the Prophet 10 SoundTower editor and plugse? Is it stable with USB or MIDI connection?

- I'm using USB on Windows to connect to my computer. Have you found either USB/MIDI interface to be more reliable than the other for exporting patches?

- Would anyone be up for testing the patch banks to see if they load correctly?
https://drive.google.com/file/d/12WbZNq7wEAGPkjtjq8AJlKjoQ9UpTSY-/view

[gus]

No need to lower the voice count, the patches will do so automatically when loaded to the P5.

Patches import to the same slots where they were exported from. Something like F0F7 (free) or Soundtower would let users load patches to different slots. https://f0f7.net/fe/#/SysexLibrarian/SequentialProphet5 Most people just export the sounds as a bank, then indicate where they will load to in the file name.

Editor should be stable, and no real difference between MIDI/USB (though in many cases USB can be faster).

Presetpatch is a great website for sharing patches, which might be of interest. https://www.presetpatch.com/

Cheers!

[coolwav]

No need to lower the voice count, the patches will do so automatically when loaded to the P5.

Patches import to the same slots where they were exported from. Something like F0F7 (free) or Soundtower would let users load patches to different slots. https://f0f7.net/fe/#/SysexLibrarian/SequentialProphet5 Most people just export the sounds as a bank, then indicate where they will load to in the file name.

Editor should be stable, and no real difference between MIDI/USB (though in many cases USB can be faster).

Presetpatch is a great website for sharing patches, which might be of interest. https://www.presetpatch.com/

Cheers!

Thank you!

[558]

MIDI OX.  Best way.  Somewhere on this website or in the Prophet manual the MIDI OX program was recommended to me. 

Dave Smith did not invent the MIDI OX program; he is known for creating the Musical Instrument Digital Interface (MIDI) itself, which allows electronic musical instruments to communicate. MIDI OX is a software utility that helps manage MIDI data but was developed by a different creator.

[LPF83]

I would definitely recommend extensive testing of the patches in 5 voice mode.  Even though technically you don't need to change the patch itself, if they're all designed to play in 10 voice mode then its possible that the envelope retriggering behavior has side effects that can make a patch sound "buggy" or make the customer wonder what's wrong.  This applies mostly only to sounds like pad/string/synth sounds with longer releases, as opposed to bass/stab/pluck type sounds.

What I've done in the past is set up a DAW template that contains a few MIDI tracks, some that play these types of sounds in a typical scenario and some that play the sounds "less typically" such as with quicker key presses.  Then solo each track on each sound > fix bugs > save > rinse & repeat.  Sometimes it's eye opening what's learned about the sounds by doing this, because as sound designers we sometimes gravitate toward only playing as we intended, while someone else is likely the play the patch differently.

[coolwav]

MIDI OX.  Best way.  Somewhere on this website or in the Prophet manual the MIDI OX program was recommended to me. 

Dave Smith did not invent the MIDI OX program; he is known for creating the Musical Instrument Digital Interface (MIDI) itself, which allows electronic musical instruments to communicate. MIDI OX is a software utility that helps manage MIDI data but was developed by a different creator.

Thanks!

[coolwav]

I would definitely recommend extensive testing of the patches in 5 voice mode.  Even though technically you don't need to change the patch itself, if they're all designed to play in 10 voice mode then its possible that the envelope retriggering behavior has side effects that can make a patch sound "buggy" or make the customer wonder what's wrong.  This applies mostly only to sounds like pad/string/synth sounds with longer releases, as opposed to bass/stab/pluck type sounds.

What I've done in the past is set up a DAW template that contains a few MIDI tracks, some that play these types of sounds in a typical scenario and some that play the sounds "less typically" such as with quicker key presses.  Then solo each track on each sound > fix bugs > save > rinse & repeat.  Sometimes it's eye opening what's learned about the sounds by doing this, because as sound designers we sometimes gravitate toward only playing as we intended, while someone else is likely the play the patch differently.

Thank you! I'll run the patches in 5 voice mode with MIDI files. For patches where I use the PU2 unison voice mode, should I leave a note to Prophet 5 owners about which patches have them? That way they can know to disable unison to play them polyphonically as they patches were intended to. (as far as I know Prophet 5 doesn't have pu2 mode?)

[g3o2]

You can put your Prophet 10 into P5 mode, see global page 3. That way you can anticipate how your patches will behave on a P5.

[LPF83]

Thank you! I'll run the patches in 5 voice mode with MIDI files. For patches where I use the PU2 unison voice mode, should I leave a note to Prophet 5 owners about which patches have them? That way they can know to disable unison to play them polyphonically as they patches were intended to. (as far as I know Prophet 5 doesn't have pu2 mode?)

I honestly don't know how PU2 behaves on the P5 -- but yeah I would just add a note that they should disable PU2 on those sounds for best results.  If you're planning on giving the sound set away for free, you don't have to worry about anyone complaining really.

[coolwav]

You can put your Prophet 10 into P5 mode, see global page 3. That way you can anticipate how your patches will behave on a P5.

Yep I switched to P5 mode and played through the patches

[coolwav]

Thank you! I'll run the patches in 5 voice mode with MIDI files. For patches where I use the PU2 unison voice mode, should I leave a note to Prophet 5 owners about which patches have them? That way they can know to disable unison to play them polyphonically as they patches were intended to. (as far as I know Prophet 5 doesn't have pu2 mode?)

I honestly don't know how PU2 behaves on the P5 -- but yeah I would just add a note that they should disable PU2 on those sounds for best results.  If you're planning on giving the sound set away for free, you don't have to worry about anyone complaining really.

Yeah I made a txt file and put a note about which patches use PU2, so they can disable if needed