DUNE 3 is now available!!

[Dasheesh]

well... as soon as i praised the new gui i discovered the vst3 version loads funny in reaper anyway. it doesn't work.

DUNE 3.4
Fixing display problems (VST3)
HiDPI COMPATIBILITY MODES
DAW: Reaper 6 (build 19)
OS: Windows 7 and 10 (64)



Reaper's graphical problems and possible solutions are in the public domain and within the application itself. Here I post one of the ones that I have used successfully, in this case to solve problems with Synapse - Audio Dune 3.4 and other plugins in Windows 7 and 10 64 bits.

Some Reaper HiDPI modes in Advanced UI / system settings may cause graphical issues with DUNE 3.4 GUI (check video) This only happens when modifying the Scaling-Mode custom text on Windows 7 and 10 computers from its value of 100% by default.In my case at 125% and 150% (check video)

Check in the video the modes did not present problems with DUNE 3.4 . It is recommended to use the Reaper HiDPI compatibility mode to fix those issues when changing skin and size.
The HiDPI mode seem to work fine to both floating and windowed.

~ceart~

VALUABLE post! thank you.

[Richard_Synapse]

there is no need, or want for dual filters in an 8 layer unpteen thousand oscillator synth and i will be forever grumpy about that, but so it is. ill live with it. i've got it down to four instruments and sample drums on my travel machine and dune3 is one of them.

Well we cannot both implement a feature many want and not have it at the same time.

Btw the dual filter is actually ace when used with the new comb filter introduced in v3.4. If you use the comb filter alone, it is often way too bright and useless on its own. A low pass filter in series addresses this and is incredibly useful here. So I hope you will not be forever grumpy

Richard

[Richard_Synapse]

About the high DPI issue (occurring when using the VST3 in Win 10, with >100% DPI setting), note this has been fixed: https://forum.synapse-audio.com/viewtop ... =1&t=12986

Richard

[Dasheesh]

thank you, richard

i have so many filters to play with, all it did was add clutter and extra clicks for me. it was done for the preset makers.

i liked the sound and work of the single filter, especially when i had 8 layers to use, and can easily create any scenario i wanted with 8 filters.

i've said my peace tho. no need to keep going with it.

[AnX]

there is no need, or want for dual filters in an 8 layer unpteen thousand oscillator synth and i will be forever grumpy about that, but so it is. ill live with it.

you literally don't have have to use them, nor does it affect anything if you dont

[Dasheesh]

yeah? ill just fiddle around and turn them
off every time, like the audio settings... seriously guys! a global lock would save soo much strife!

[Richard_Synapse]

yeah? ill just fiddle around and turn them
off every time, like the audio settings... seriously guys! a global lock would save soo much strife!

We have the global lock in Obsession and The Legend already, it is just a whole lot more complicated in Dune 3, but I think it will come still.

One last remark about the second filter- our skinning system should be flexible enough to hide it. I'm not 100% sure about this, have to ask Marcin (who implemented it).

Richard

[Dasheesh]

yeah? ill just fiddle around and turn them
off every time, like the audio settings... seriously guys! a global lock would save soo much strife!

We have the global lock in Obsession and The Legend already, it is just a whole lot more complicated in Dune 3, but I think it will come still.

One last remark about the second filter- our skinning system should be flexible enough to hide it. I'm not 100% sure about this, have to ask Marcin (who implemented it).

Richard

i did not know this. now i want it REAL BAD lol. i will be patiently waiting. thank you again.

[AnX]

yeah? ill just fiddle around and turn them
off every time, like the audio settings... seriously guys! a global lock would save soo much strife!

the 2nd filter isn't on by default.... not sure what the problem is

[zvenx]

So we owe Dune's existence to you to a major degree.
Thank you.
rsp

[rezoneight]

And, no offense, but you do not know when there will be Apple Silicon builds of any of the major DAWs. In all likelihood, we won't see an updated Ableton build for at least a year. S1 will certainly take longer. We are in for a fairly extended transition period.

so you have more info than a dev? how did you get that info, or is it guess work?

Plugin devs are just people, with no more insight into the release plans of the major DAW publishers than the rest of us.

so guess work then

How would it not be guesswork? At any rate an educated guess says that DAW publishers, who quite simply have more code to worry about, probably will have bigger hurdles to overcome than small synth plugin developers and it's going to take them a lot longer.

There is absolutely no reason to not do a universal binary build for Mac at this point for *any* software. It's not black magic. And at some point (if its not available already) there will be a way to strip out the platform you don't need from the universal binaries if storage is a concern. They had this before in the old days of transitioning from PowerPC to Intel.

[AnX]

.

There is absolutely no reason to not do a universal binary build for Mac at this point for *any* software.

i wouldnt know, I'm not a coder/dev, and I wouldn't be so rude as to tell someone how to run their business....

[fisherKing]

There is absolutely no reason to not do a universal binary build for Mac at this point for *any* software.

i wouldnt know, I'm not a coder/dev, and I wouldn't be so rude as to tell someone how to run their business....

not rude at all. this is why developers get OS previews, for example. and it's the developer's (for better or worse) responsibility to keep their plugins up-to-date, just how it works.

EDIT: it's ok if developers want to show up here & complain tho... complaining is the lifeblood of internet forums...

[Teksonik]

this is why developers get OS previews, for example. and it's the developer's (for better or worse) responsibility to keep their plugins up-to-date, just how it works.

It's also the DAW developer's responsibility to keep their DAWs up to date as well.


If the DAW is not M1 compatible and the plugin is whose fault is it ?

[fisherKing]

this is why developers get OS previews, for example. and it's the developer's (for better or worse) responsibility to keep their plugins up-to-date, just how it works.

It's also the DAW developer's responsibility to keep their DAWs up to date as well.


If the DAW is not M1 compatible and the plugin is whose fault is it ?

am on logic, so, as an apple app, it's, by default, kept up to date. but i absolutely agree.