Dune v3.6

[enCiphered]

Congratulations to the latest update, Richard.

I would like to address one essential point for anyone using Dune with a Linnstrument or a different MPE controller and two things related to the genetics feature, which are very important for a proper and seamless sound design workflow.
I have previously highlighted everything in the other thread but it seems my points have gone unnoticed. So please forgive me for opening a new thread, I hope you can look into them:

1. We need a global pitch bend range lock function. If you work with a Linnstrument, you have to set the range to 48 up and 48 down to work properly. I have to do that ALL the time because the settings reset everytime you change the preset or use the genetics. So, with each preset change, click on "generate" or "auto", the pitch bend range is set back to 2 again.

2. The wavetable is not changing when using genetics. Whatever settings are changed randomly, the wavetable is always a sine. I have a bunch of custom wavetables which I cant use in my sound design process with genetics.

3. There is no way to exclude individual parameters from being randomized by genetics. This makes conrolled randomization a lot harder because you have to do it manually all the time.

I would love to assist with Beta testing if that helps, just let me know.

Thank you!

[tripleflows]

Good points, +1.

[chk071]

What's wrong with the original thread? viewtopic.php?t=516207&start=3300

I'm pretty sure the dev is much more prone to look there, than in potential other newly created threads. Maybe even subscribed to that thread, because he created it as well.

[Teksonik]

As always I encourage people to post at the official Synapse forums. You are much more likely to get a response there as Richard doesn't check here often.

https://forum.synapse-audio.com/

[Richard_Synapse]

Good points enCiphered!

Parameter lock is still on the todo list. We understand the importance of locking pb up/down, this is why both TL and Obsession have this feature already. I suppose we will add it as part of a smaller maintenance update like 3.61 or similar

Richard

[enCiphered]

Excellent, thank you very much Richard and everyone else for commenting.
This would make Dune one of my go to synths for MPE

[Lbdunequest]

Good points enCiphered!

Parameter lock is still on the todo list. We understand the importance of locking pb up/down, this is why both TL and Obsession have this feature already. I suppose we will add it as part of a smaller maintenance update like 3.61 or similar

Richard

while you replied here, is it ok to ask a reques to add reading regular wavetables format without importing them ?

[ThomasLehmann]

yes, nice update thank you.
While we're at it, could we get a function to copy the arpeggiator midi notes into the sequencer ? Maybe via drag and drop or as a midifile export...that would be great

[BoogerSnot]

Parameter lock is still on the todo list

This would be huge. I've seen it other plug-ins, where you can lock parameters before randomizing, and it is a great feature. Yes, add it to 3.6.1 please.

[Arashi]

This would be huge. I've seen it other plug-ins, where you can lock parameters before randomizing, and it is a great feature. Yes, add it to 3.6.1 please.

I'm here to say this is a great update to one of my favorite synths, but I also need to mention that's one fine username you have there. It really rolls off the tongue!

[teilo]

Is there some reason that there is no longer a VST2 for Mac? The installer only has VST3 and AU.

[Teksonik]

Is there some reason that there is no longer a VST2 for Mac? The installer only has VST3 and AU.

According to Richard in March of this year:

"We have to drop it (VST2) for M1, because not only Steinberg drops it, but Native Instruments does as well. NKS will not work on M1 with the VST2. Fixing this and going VST3 here was one reason for the (recent) update to begin with".

[zvenx]

Also I believe eventually every developer doing vst3 will have to drop vst2 eventually per signed aggrement to developer for vst3, I believe.

Edit: Seems this is definitely no longer true.

https://forums.steinberg.net/t/vst-3-sdk-license/201637
rsp

[chk071]

Also I believe eventually every developer doing vst3 will have to drop vst2 eventually per signed aggrement to developer for vst3, I believe.

Looking for proof, haven't found thus far.
My recollection is it was a requirement, then removed, then added back but with a long transition period... can't find the last leg as yet.
rsp

Would surprise me, especially as Steinberg will pull the plug on VST2 support in their DAWs anyway.

At some point, it will simply "solve" itself, when no DAW supports VST2 anymore. But, there will be years and years until that will be the case. Probably, we'll have VST4 by then.

[zvenx]

Yeah, seems it was changed and they took out vst2 cessation part completely out of any required signed agreement for developing of vst3 plugins.
rsp