Synapse Audio - Dune 3.5 Released

[Touch The Universe]

MW as a destination to LFO.

Explain

I don't think that even makes sense. MW as an LFO destination?

MW as a Source to LFO as a Destination is already implemented. Maybe he meant that?


D3 111721-2.png

Haha you guys are funny Sure enough Teksonik.

I have 6-7-12 assignments to the MW. It sounds perttttttttty sweeet going scrolling that. But danggg, that sound is dope. I just want that to be embedded in the patch itself then.

Aka, dude, its not too far off my request for macros (spire, rapid, massive, yada,yada), which essentially, all what a MW is any. get wit it bro

[Teksonik]

I'm sorry I have no idea what you're rambling on about. I didn't say a word about Macros I was responding to this:

and MW as a destination to LFO.

Which makes absolutely no sense at all. So yea Bro get wid it....

I have no problems with Macro Knobs although I design my patches to be played not played with so don't normally use Macro knobs in the synths I own that have them........

[Sindikhate]

Do other skins work with the new update? And how do you change a skin? Apart from the size.

I have placed the Dark Ice skin on the Skins folder for example but when I right click on Dune I only get the 4 sizes of the default skin.

[zerocrossing]

I love this synth.

[Teksonik]

Do other skins work with the new update? And how do you change a skin? Apart from the size.

I have placed the Dark Ice skin on the Skins folder for example but when I right click on Dune I only get the 4 sizes of the default skin.

No the Dark Ice skin will not work. The new version of DUNE 3 has added several new graphics files to the skins and some entries in the config file so unless updated old skins will no longer work.

I took a look at the Dark Ice skin and have tried to mash it together with a copy of the new Large skin but so far no success.

When you right click where is says skin you should see this:

D3 111721-3.png

Place any third party skin in the User Folder. But again they will not work until updated to take advantage of the new features.

[Sindikhate]

Do other skins work with the new update? And how do you change a skin? Apart from the size.

I have placed the Dark Ice skin on the Skins folder for example but when I right click on Dune I only get the 4 sizes of the default skin.

No the Dark Ice skin will not work. The new version of DUNE 3 has added several new graphics files to the skins and some entries in the config file so unless updated old skins will no longer work.

I took a look at the Dark Ice skin and have tried to mash it together with a copy of the new Large skin but so far no success.

When you right click where is says skin you should see this:



D3 111721-3.png


Place any third party skin in the User Folder. But again they will not work until updated to take advantage of the new features.

You are right!
The Dark Ice is missing like 30 or so files. I was looking at the folder earlier.

It is sorted now.

[Teksonik]

Post the results. I'd love to see how it looks.

[pdxindy]

I haven't installed 3.5 yet. The installer requires Rosetta and I have not installed Rosetta. I'm gonna manually extract the files from the installer and install that way.

Someone from Synapse saw my post and messaged me with a link to a test installer that does not require Rosetta. So 3.5 is installed! Great service!

[Touch The Universe]

I'm sorry I have no idea what you're rambling on about. I didn't say a word about Macros I was responding to this:

and MW as a destination to LFO.

Which makes absolutely no sense at all. So yea Bro get wid it....

I have no problems with Macro Knobs although I design my patches to be played not played with so don't normally use Macro knobs in the synths I own that have them........

I want the MW to be a destination source for modulation, or macros. It is purposeful, believe it or not, as funner options exploring the patch, going wild. Go on then, go donk donk, so, no modulation complexity required i guess

[AnX]

I haven't installed 3.5 yet. The installer requires Rosetta and I have not installed Rosetta. I'm gonna manually extract the files from the installer and install that way.

Someone from Synapse saw my post and messaged me with a link to a test installer that does not require Rosetta. So 3.5 is installed! Great service!

Is that just for the mac vst? (Not au)

[Richard_Synapse]

Is that just for the mac vst? (Not au)

It was just about the Mac M1 installer specifically, the plugins are already native M1 (both AU and VST).

Right now a lot of stuff still requires Rosetta, e.g Ableton Live, so we cannot live without it and hence wouldn't notice if our installer asks for Rosetta. Glad it is fixed now

Richard

[DJ Warmonger]

I never noticed any significant memory usage with Dune 2/3, but can't complain if that was optimized ¯\_(ツ)_/¯

[Richard_Synapse]

I never noticed any significant memory usage with Dune 2/3, but can't complain if that was optimized ¯\_(ツ)_/¯

Right, it was an issue only with the previous version, v3.4. Memory consumption per instance went up quite a bit there (to about 350mb or thereabouts). While nobody complained about it, on a smaller 8gb RAM system with many instances it could potentially be an issue.

Richard

[Teksonik]

I want the MW to be a destination source for modulation, or macros. It is purposeful, believe it or not,

Maybe if you could explain in a coherent manner why you think MW as a destination would have any useful purpose people might get on board.

But to me it makes no more sense than having Aftertouch as a Destination.

I never said no modulation complexity is required. I'm all for useful modulation I'm just not a fan of modulation for the sake of modulation. Then it becomes more toy than tool.

But again as with any feature request present your case in a convincing manner and if it makes sense maybe Synapse will consider it. The fact that in all the years DUNE has been released no one else has ever made that same request really says a lot.....

[Teksonik]

Your eyes can only focus and read one line at a time in any case, and you have five visible patches at any one time

As opposed to 23 available now.

You will also see what is changing when using the Genetics feature whilst playing the synth in real-time.

No you would only see a small part of what is changed. You can only see what is changed on one Voice Layer. It's simply not useful.

I appreciate your efforts but sorry I think it's a poor concept.

No, you are just trying to find fault in something because that's your primary aim.

No I'm presenting my opinion of your concept. If it made sense and was a better concept than Synapse has created then I would agree with you. It doesn't so I don't. Simple as that.

You have a personal bias against in those you see as wanting improvements in Dune, not for the benefit of the product, but based on individuals that want to see things change.

No sorry that's a cop out. I have nothing against you personally. It's your poor idea that I am pushing back against. Again if it made sense to me I would agree with you. Who you are makes absolutely no difference. Come up with a good idea and I'll back you 100%.

I don't remember you calling for a new browser in previous threads.

You don't have access to all the fourms. I was one of the most vocal advocates for a new browser on the forum that matters even though I have zero use for one.

It's like you are trying to stand in the way of development and police what people ask for or suggest

I'm not standing in the way of any progress but you have to realize just because you want something doesn't mean it's progress. Not all change is progress try to understand that fact.

If you or anyone else has the right to say "I want this" then I or anyone else has the right to say "I'd rather development time be spent on something else".

Present what I think is a good idea and I'll support you. Bring up something that I think is not a good idea and I have as much right to disagree as you have to present the idea. Got it?