SWAY - a synth modeled after the Yamaha SY77

[Spitfire31]

This is an easy one. Option Number Two, most definitely!

I guess that the number of people who will actually create multisamples is pretty low, compared the those who might prefer to buy expansion cards from enthusiasts or commercial patch producers. It seems to me that expansion cards should be the much preferable solution.

Besides, people are fired up when it seems that a 1.0 version is not too far away. If they now realise that the premiere might be another half a year or more in the future for a feature that may not even have a general appeal, some might lose interest.

Go with Option Two!

Kind regards/JHS

[Uncle E]

Quick update: I think the next build could be a release candidate for version 1.0, so the code is nearly there.

Congrats!

I've made almost 80 presets so far. I'm not 100% decided yet, but my current idea is to make 128 in total for the initial release. Not a lot, but enough to showcase the capabilities I guess. I wonder if this is a good idea though, because factory preset libraries influence my own purchase decision quite a bit. I like making presets as a synth user, but it also takes a lot of time so if I'm going to be dropping money on a synth I want a lot of new sounds out of the box. Especially if it's a synth with a lot of controls, like SWAY. The idea that I would spend more than 4 years on this project and then people aren't buying it simply because I didn't take the time to make enough presets...

80 is a lot by today's standards. You could release with 80 now and then release an update with 128 later, and people will say "woo it's the gift that keeps giving!"

Another way is this: I just make an external expansion card editor. This way you can only add custom samples by making custom expansion cards. It's less flexible, but it would massively simplify everything. The plugin itself wouldn't even have to be changed, since it already supports expansion cards right now! An external editor means that you could still open it from the plugin, but it launches an external Windows/Mac app in a new window outside of your DAW. When you save changes to your card you refresh them in the plugin and you're good to go. I could probably make this external editor in 4 weeks or so, because I can use web technology which is just easier and faster.

The reason I believe importing other sample formats is better is because they'll include loop points. If I'm understanding you correctly, the two options you've presented don't provide that.

[IvyBirds]

Question about custom samples, for in the future: there are several ways I could go about it and I'd like to hear your thoughts....Another way is this: I just make an external expansion card editor. This way you can only add custom samples by making custom expansion cards. It's less flexible, but it would massively simplify everything. The plugin itself wouldn't even have to be changed, since it already supports expansion cards right now! An external editor means that you could still open it from the plugin, but it launches an external Windows/Mac app in a new window outside of your DAW. When you save changes to your card you refresh them in the plugin and you're good to go. I could probably make this external editor in 4 weeks or so, because I can use web technology which is just easier and faster.

Thoughts about this? Would the second option disappoint you?

I would 100% go with this second option, and I would publicly release and sell version 1.0 without this and market it saying custom sample import will be added in the 1st or 2nd quarter of 2026. Then make that external card editor available as a separate piece of software

I like the idea of a separate piece of software that makes virtual expansion cards as it's a great way to organize samples

[sheaf]

Thanks for the input all. Importing SFZ is a great idea!

I think I'll make the external card editor then, and add the SFZ import there. If I allow direct SFZ import in the plugin there is still the issue that samples need to be embedded or linked inside the patch structure, massively complicating things. I guess I could always add it later if customers really want it.

To clarify, what I meant with an editor was not a full blown audio editor like Sound Forge or Audacity, but more like the very basics of Kontakt. Something that allows you to add waveforms as zones and to set loop points. Nothing more complicated than that really.

The custom sample loading or the external editor was not for planned 1.0, but for 1.1. I'm not postponing the release to implement any of this, but I already want to think about the options.

[lalo]

Thanks for the input all. Importing SFZ is a great idea!

I think I'll make the external card editor then, and add the SFZ import there. If I allow direct SFZ import in the plugin there is still the issue that samples need to be embedded or linked inside the patch structure, massively complicating things. I guess I could always add it later if customers really want it.

To clarify, what I meant with an editor was not a full blown audio editor like Sound Forge or Audacity, but more like the very basics of Kontakt. Something that allows you to add waveforms as zones and to set loop points. Nothing more complicated than that really.

The custom sample loading or the external editor was not for planned 1.0, but for 1.1. I'm not postponing the release to implement any of this, but I already want to think about the options.

Smart solution! Great to see SWAY arrivin' pretty soon....i can avoid to substitute LCD on my TG77

[bnz]

x.factory will already work?

[EvilDragon]

If I allow direct SFZ import in the plugin there is still the issue that samples need to be embedded or linked inside the patch structure, massively complicating things.

Errr, no. You just need to reference the SFZ itself, that's all! SFZ itself usually contains relative paths to all the samples, so it's all good!

To clarify, what I meant with an editor was not a full blown audio editor like Sound Forge or Audacity, but more like the very basics of Kontakt. Something that allows you to add waveforms as zones and to set loop points. Nothing more complicated than that really.

Yeah I know what you meant, but even that is work you don't really NEED to do for 1.0! 1.1 can exist

[Uncle E]

Thanks for the input all. Importing SFZ is a great idea!

I think I'll make the external card editor then, and add the SFZ import there. If I allow direct SFZ import in the plugin there is still the issue that samples need to be embedded or linked inside the patch structure, massively complicating things. I guess I could always add it later if customers really want it.

To clarify, what I meant with an editor was not a full blown audio editor like Sound Forge or Audacity, but more like the very basics of Kontakt. Something that allows you to add waveforms as zones and to set loop points. Nothing more complicated than that really.

The custom sample loading or the external editor was not for planned 1.0, but for 1.1. I'm not postponing the release to implement any of this, but I already want to think about the options.

If Sway has its own file format, you could simply provide the details to Moss and ask him to add it to Convertwithmoss. Personally, I would already need to use Convertwithmoss since none of my libraries are sfz's, so it'd be nice just to be able to do it all from there. Adding waveforms or setting loop points is unnecessary in that case.

[cslevine]

I just make an external expansion card editor.

100% for this second option !
Very clever. + SFZ or SF2 import, later...

i made some firsts video me playing on SWAY , telling that i playing my TG77 compositions back from 34 years !.... i think all of us could make some little video telling our enthousiasm, when SWAY will be gold v1.0 released and sold, so that it will bring visibility.

( of course : NO public youtube release before public release of SWAY.
not yet edited )

[mmccarthy]

Thanks for the input all. Importing SFZ is a great idea!

I think I'll make the external card editor then, and add the SFZ import there. If I allow direct SFZ import in the plugin there is still the issue that samples need to be embedded or linked inside the patch structure, massively complicating things. I guess I could always add it later if customers really want it.

To clarify, what I meant with an editor was not a full blown audio editor like Sound Forge or Audacity, but more like the very basics of Kontakt. Something that allows you to add waveforms as zones and to set loop points. Nothing more complicated than that really.

The custom sample loading or the external editor was not for planned 1.0, but for 1.1. I'm not postponing the release to implement any of this, but I already want to think about the options.

Sounds like a solid plan! Super excited to get my mitts on this!

[commodore]

Been keeping an eye on this project for sometime now and can't wait. Been wanting a TG77 for a while and cant justify the price unfortunetly, so really looking forward to this. I appreciate all the effort in to this project, the demos sound great!

[Fette Töle]

Any news about Sway? I hope everything is going well and the release is imminent.

Sorry for my impatience, but with all the temptations in the run-up to Black Friday, I'm finding it hard not to spend the money I've set aside for Sway on something else (Omnisphere 3, Proxima, Kontrast, etc.).

[mmccarthy]

Any news about Sway? I hope everything is going well and the release is imminent.

Sorry for my impatience, but with all the temptations in the run-up to Black Friday, I'm finding it hard not to spend the money I've set aside for Sway on something else (Omnisphere 3, Proxima, Kontrast, etc.).

Don't forget the Korg Trinity!

Sorry, that's not helping is it?

[mi-os]

Don't forget the Korg Trinity!

Which Korg plugin is closest to the SY77? Trinity?

[Uncle E]

None. Opsix would be closest and it doesn’t have samples.