Forums

    4 posts

  • avatar
    33 sounds
    162 posts
    Synth1 Soundbank (S.O.S)


    Hoping that I picked the right category for this subject.. ok here it goes...
    I've recently been using Synth1 again after a few years, and have created quite a few patches in the past. I'm wanting to give them away as a soundbank for other Synth1 users to have.

    How does one go about this??

    Have been looking for answers all day. Maybe I'm just horrible at searching the web?
    The files never come out to be ".sy1", but ".fst" instead. I've been using fl studio. Should I be using my cubase or ableton instead? Does DAW matter in this particular subject? So lost...

    If anyone has any suggestions it would be greatly appreciated!

  • avatar
    243 sounds
    552 posts


    Whatever DAW you use, you don't have to use the DAW preset handling but Synth1's internal one.
    I've recently done a few patches myself, and a non-destructive way I thought of was to clone one of the soundbank* directories and name it soundbankCC.
    Once verified that Synth1 could access it, I've done some patches and saved them via the red "write" button; it pops up a dialog where you can choose bank, patch and name, not necessarily the same you were working on.

    Synth1 can also read patches from zip files, so once your set is done you can simply share the zipped directory; KVR Audio may be a proper place to publish it, it already hosts a few banks.

  • avatar
    33 sounds
    162 posts


    copyc4t to the rescue! Thanks a lot. I'll try to do what you suggested. Shouldve known the answer was in Synth1 instead of fl. Yeah, I was thinking about uploading them to KVR. Seems to be the hot spot for Synth1 soundbanks. I'll be visiting that site everyday this month anyway due to the 2014 KVR developers challenge. Might as well be "productive" about it.
    Thanks again!

  • avatar
    243 sounds
    552 posts


    You're welcome! smile

    .fxb and .fxp are quite common formats for banks and patches (LMMS, just to name one, is able to load and save them for any synth using that format) so whenever you see a different extension like .sy1, that's often a clue indicating internal handling.

    4 posts