D U N E user waveforms

[ufo]

Would be very cool if we could load some OSC wave forms into Dune.
Would be very cool if we could load custom waves into LFOs.

mmmmmmmmmmmmmmmm Dune

[Mark]

That would be sweet!

[Teksonik]

Sweeter still......sfz support.......... +1 for user waveforms.

[Kriminal]

lots of ppl like this idea, i dont care either way myself, but its easily the most requested addition.

[Teksonik]

Just think of the added possibilities for sound design..........

[HYPNAGOGIA]

I'm just wondering how those would be shared. I guess you'd have to send a waveform along with the patch.

[Andy-b]

I'm just wondering how those would be shared. I guess you'd have to send a waveform along with the patch.

I think they can be embedded in .fxp patches,like Toxic Biohazard

[Teksonik]

That would be the way to go with single cycle wavs since they are so small.....if .sfz support was added (I don't think that will happen anyway) you'd have to send the samples/sfz file with the patches.

[Andy-b]

That would be the way to go with single cycle wavs since they are so small.....if .sfz support was added (I don't think that will happen anyway) you'd have to send the samples/sfz file with the patches.

I think single cycle are a good upgrade option,about .sfz I don't know,they can be transform a great straightforward synth in a bloatware thing

[Teksonik]

It's only bloatware if you're forced to use .sfz files. As an option it would only help expand DUNE's capabilities.......but like I said I don't think .sfz support will be added........Shame too as you could get some great wavestation type sounds by assigning a different .sfz file to each of the 8 voices and then cycling thru them.....

[HYPNAGOGIA]

Support for SoundFont (sfz and sf2) files would be an option only whether you'll use SoundFonts or not, but it will be permanently visible on the GUI. Being that they are multi-sampled files, you will need a mean to swift through them. Making it visible on the GUI is rather obvious way to do it; ModMatrix doesn't seem like a good place for it.

Another thing to consider is the size of these files. SoundFonts can hold samples of any sizes, so your patches might get quite big. And while we're on that, I'm guessing that passes the use of waveforms, since they would cease to be that. Realistically, there wouldn't be anything to stop you from using eight 3 minute samples, encoded in 96KHz in 24-bit rate, right?

Unless you guys have some good options to overcome all those issues, quite frankly, thinking about it, I just don't see that kind of support coming. Loading a .wav waveform, sure, but SoundFonts? As much as the idea of loading each waveform to separate voices using SoundFont sounds enticing, no, sorry, I don't see it coming.

[Kriminal]

Support for SoundFont (sfz and sf2) files would be an option only whether you'll use SoundFonts or not, but it will be permanently visible on the GUI. Being that they are multi-sampled files, you will need a mean to swift through them. Making it visible on the GUI is rather obvious way to do it; ModMatrix doesn't seem like a good place for it.

Another thing to consider is the size of these files. SoundFonts can hold samples of any sizes, so your patches might get quite big. And while we're on that, I'm guessing that passes the use of waveforms, since they would cease to be that. Realistically, there wouldn't be anything to stop you from using eight 3 minute samples, encoded in 96KHz in 24-bit rate, right?

Unless you guys have some good options to overcome all those issues, quite frankly, thinking about it, I just don't see that kind of support coming. Loading a .wav waveform, sure, but SoundFonts? As much as the idea of loading each waveform to separate voices using SoundFont sounds enticing, no, sorry, I don't see it coming.

sfz's are good for several things, one being multi samples

i can have a single cycle wavefrom sampled on every note, from a hardware synth, and use that, the file would still be tiny.

i think user wavetable are a better idea myself tho, along with an app or at the very least in depth instructions for everyone to create them

[Teksonik]

Support for SoundFont (sfz and sf2) files would be an option only whether you'll use SoundFonts or not, but it will be permanently visible on the GUI. Being that they are multi-sampled files, you will need a mean to swift through them. Making it visible on the GUI is rather obvious way to do it; ModMatrix doesn't seem like a good place for it.

Another thing to consider is the size of these files. SoundFonts can hold samples of any sizes, so your patches might get quite big. And while we're on that, I'm guessing that passes the use of waveforms, since they would cease to be that. Realistically, there wouldn't be anything to stop you from using eight 3 minute samples, encoded in 96KHz in 24-bit rate, right?

Unless you guys have some good options to overcome all those issues, quite frankly, thinking about it, I just don't see that kind of support coming. Loading a .wav waveform, sure, but SoundFonts? As much as the idea of loading each waveform to separate voices using SoundFont sounds enticing, no, sorry, I don't see it coming.

Nobody said anything about Soundfonts...........

Overcome what issues? There are several synths that quite successfully use the .sfz format and Alchemy just added the feature.

Of course any addition may cause some changes to the GUI or otherwise. That's unavoidable and I don't see any problem with it....the other option would be to leave DUNE as it is.......Who cares if "your patches might get quite big"? The concept would be to increase the types of sounds DUNE can create. Single cycle wavs although a welcome addition would only bring a limited amount of new sound colors to the palatte....while sfz support would bring a huge new capability to DUNE but as I've said before I don't see it happening as Rich has never commented on the subject. I don't think there are any disadvantages to adding .sfz support it may just be that it's not within the vision plan that Rich has for DUNE...........

[Teksonik]

i can have a single cycle wavefrom sampled on every note, from a hardware synth, and use that, the file would still be tiny.

i think user wavetable are a better idea myself tho, along with an app or at the very least in depth instructions for everyone to create them

How would user wavetables differ from the .sfz format ? Would it be the same concept just a different format where you define what samples are loaded and what key range they play? Sort of like the Wavefusion concept but with full sized samples? I could support that concept as well. It's just that there are several sources for .sfz format sample sets now and that would open up the possibility of third party expansions for DUNE. However I could see the advantage of a closed format for DUNE where all expansion content comes from Synapse....Again it may not be Rich's vision for DUNE that it becomes a sample based synth. Still I'd love to be able to load some nice samples and route them through DUNE's Effects and Mod Matrix....like I said before you could get some great Wavestation or PPG sounds....if the idea is to grow DUNE and to create a DUNE 2 I can't think of anything that would add more bang for the buck than .sfz support or a similar proprietary format for loading full multi-samples

[HYPNAGOGIA]

sfz's are good for several things, one being multi samples

i can have a single cycle wavefrom sampled on every note, from a hardware synth, and use that, the file would still be tiny.

SF2 are multi sampled too, aren't they? I really can't tell the difference. Maybe the support for the format, I don't know.

And I agree for cycle waveform samples, but the question is what happens when people start throwing in long samples encoded in HQ? You will get big files very quickly. Of course, that would be on the them to use (or not) lengthy samples.
So, should the use of sfz's be limited then? I don't see how that's possible, maybe if you limit the file size used or something, or do extensive check for sample times, as a measure of prevention from using X minutes long samples across the key range.

Nobody said anything about Soundfonts...........

Then you should consider what .sfz is.

Taken from the Cakewalk's page, it's a collection of samples put inside one file. So, how is that different from a SoundFont definition? There is none. The only difference is structural and functional implementations, with added compression for sfz. But it still falls under the SoundFont category.

Who cares if "your patches might get quite big"? The concept would be to increase the types of sounds DUNE can create. Single cycle wavs although a welcome addition would only bring a limited amount of new sound colors to the palatte....while sfz support would bring a huge new capability to DUNE

I think patch creators would disagree when they need to upload big archives with such patches, though if that happens, it's entirely on them (read reply to Krim above).

----------------------------------------------------------
I'll just add here quick note, which isn't a direct reply to anyone here, that personally I have nothing against adding the sfz support. In addition to the possibilities they would bring (I wholeheartedly agree with Tek on the subject of DUNE's sounding variety), I'm also trying to look at the negative aspect of it as well.

Carry on