Synapse Audio - Dune 3.5 Released

[e-musician]

But in this case I don't understand WHY you are spending time to fix your edit because what I posted above IS nothing but a completely fixed version of your very edit

Because my edit is designed to be the way I want it not the way you want it. There is nothing wrong with the WT editor or Browser or Filter routing to me.

I posted the fix for anyone who wants it not just for you. I didn't ask you to "fix" anything for me but thanks anyway.

No offense intended!

I was not criticising you in any way.
I thought you might have overlooked that some of these "pixel things" that you were getting right now had already been fixed.

Concerning this:

Because my edit is designed to be the way I want it not the way you want it.

I did not change the "design" of your edit in any way - out of respect, and in fact, as this is the way you wanted it to be!

I only posted the skin because you once did ask me to let you know if I found any inconsistencies (i. e., in Nov 2021), and it was easier and less complicated for me to make the changes myself rather than explaining things.
I simply dealt with some pixel issues / inconsistencies.

The only real "change" that I made: different air slits in the main pane (to go with all the other air slits in the skin).
You used the air slits from the Factory Light skin in the main pane and those from the Factory Dark skin in the other panes, and I considered that to be inconsistent.
So that point is indeed me interfering. I'm sorry if you feel that I have encroached on your work or contribution here. I didn't mean to.

Regarding the WT editor and the browser: in both cases, the side panels didn't go with those in the main pane.
But if that's okay for you and was intended, then that's fine, of course.

And two more things:
1) I wasn't assuming that you were fixing it "just for me". I still believe that this is a community, right?
2) I didn't say that there was anything wrong with the filter routing. I just pointed out that in my post the display is still white, not orange, like in your latest version.
Reason: When I had a look at your edit almost a year ago, it was white then - and, of course, back then, I didn't change that as this was the way you wanted it to be.

Thanks again for sharing your edit.

[Teksonik]

No offense taken.

Regarding the WT editor and the browser: in both cases, the side panels didn't go with those in the main pane.

They're exactly the same style, just a few pixels larger. Those windows are completely different than the main window. The side panel size is such a small and insignificant detail I've never noticed it until you mentioned it and I use DUNE 3 every day.

But if it bothers you then by all means change it.

[Chipi]

All the Synapse Factory banks are properly categorized and always have been with sub-folders.

Yes indeed, all our factory banks and all our expansions have always been fully categorized, both for NKS and for our browser. See image below as an example, all banks work like this.

So I assume this is about 3rd party banks, which are beyond our control. Note that even those are fairly easy to categorize using the drag+drop feature in the new browser. Some freebie bank I had downloaded had a rather weird way to sort presets, using multi-selection then drag+drop on categories it took me less than a minute to sort the whole thing So I'm confident sound designers will adapt quickly, as intro wrote earlier in this thread they can also define their own categories now if they wish.

Richard

Hi Richard,

I hope this message finds you well man.

Couple of concerns, and hopefully Dev can adjust it, why Dune 3.5 has low initial volume when you work with wav waves? It should have 12 db more output or at least give us the option to the user. I say this because when adding a wav wave it always sounds low and the wav is at 0.00 db, when I compare the original sound with the wav that Dune reads, the quality is mediocre although stereo, it is mediocre.

Another con that it has and I don't know how the Dev people don't think about this, is that when you select a sound from the 3.5 'browser' and edit it, etc. and when you save it and rename it, everything is fine, but now when you go back to the browser the sound is not there, you have to start looking for it throughout the library, it is incredible that they do not think and develop the most basic. When will they update this? in v10? of 2030...? Take a look at the Omnisphere library and sound structure, easy and practical, you are in that sound and you go out and come back and go back to where you were, easy and intuitive. I love the sound of Dune, don't get me wrong, it's a piece of sound beast, one of the best 3 on the virtual synthesizer market, whatever they say, final sound from my Yamaha HS80, unparalleled! Thanks Richard for this great instrument! ♥

[zvenx]

Did you try reload soundbank?
rsp

[Chipi]

zvenx thanks but the problem is something else, take a look at the next video
< NO AUDIO, STEPS ONLY >

• If I'm on the Dune edit page and I browse and select a sound, basically if I click on the new 'browser' it doesn't show up, you have to go through the folders looking for it.

• However, if you are in the browser and select a sound and then go to edit it, when you return to the browser it is there... WHY DOES IT WORK LIKE THAT? WHAT IS THE LOGIC?

https://www.awesomescreenshot.com/video ... 5b8a2a5172

[zvenx]

Hmmm that is not how it is working on mine..
Mac Intel.. Vst3 Cubase 12.
rsp

[zvenx]

I see what you are doing different... you still have a filter selected in your New Browser (the last soundbank you used.. if you deselect it, it will hilite the patch you have loaded..

The way you are using it, the new browser will use the last filters you had applied in it as its search parameters (I actually prefer it that way and I know some others do too)



rsp

[chagzuki]

Considering buying Dune, just wondering if there's a roadmap for development? Trying the demo, the aspect which sticks out in 2022 is the lack of modulation representation on the knobs, relying on the mod matrix panel instead.

[Richard_Synapse]

Global parameter lock, and a CLAP version with host-based multi-threading are two things rather close by There is more stuff of course, but it is too difficult right now to predict when/if it will happen.

Richard

[SLiC]

Nice One Richard, CLAP will be interesting- Love being a Bigwig user right now!

[Richard_Synapse]

Considering buying Dune, just wondering if there's a roadmap for development? Trying the demo, the aspect which sticks out in 2022 is the lack of modulation representation on the knobs, relying on the mod matrix panel instead.

DUNE 3 is a multi-layered synth, and it is fairly common for presets to contain several layers with completely different modulation in each layer. Also modulation from velocity, mw, aftertouch, expression etc. is rather common. Not saying it is useless to have some visual representation of the modulation, just that not every concept that works with other synths (perhaps designed around that feature) works equally well here

Richard

[Biome_Digital]

Global parameter lock, and a CLAP version with host-based multi-threading are two things rather close by There is more stuff of course, but it is too difficult right now to predict when/if it will happen.

Richard

Great I would love to see some more stuff on the audio-side: loop points/granular, that sort of thing would take Dune to another level.

[Richard_Synapse]

Great I would love to see some more stuff on the audio-side: loop points/granular, that sort of thing would take Dune to another level.

Ok, what exactly do you mean by loop points? (Wave files can be looped)

Richard

[aMUSEd]

Global parameter lock, and a CLAP version with host-based multi-threading are two things rather close by There is more stuff of course, but it is too difficult right now to predict when/if it will happen.

Richard

Will it be multi threading on Apple Silicon too? (at the moment I find performance is worse when I turn that on, on my M1 Max)

[MTorn]

Great I would love to see some more stuff on the audio-side: loop points/granular, that sort of thing would take Dune to another level.

Ok, what exactly do you mean by loop points? (Wave files can be looped)

Richard

Since you're asking about sample playback, let me sneak in a request to be able to use SFZ files in place of single samples. Like with the old Zampler, but ideally with a somewhat bigger set of recognized opcodes (I'd be happy to compile a list).

This would widen the capabilities of Dune immensely! Sharing sample sets of unusual oscillators and acoustic noises would be a lot of fun.

Though I bet you get similar requests a lot, but that you have no intention of taking Dune in that direction.