Synapse Audio - Dune 3.5 Released

[Teksonik]

The samples are baked into the presets. This brings a bank of about 105 patches weighing around 47MB though, not bad by any count considering the quality of the sound of Dune with only single waveforms.
The full multi-samples will be available in other soundsets, like from Rapid, Halion, etc. I plucked the best sounding single waveforms out of hundreds and imported into dune 3.5

Ok speaking only for myself I am far more likely to buy a soundset to gain access to good usable samples than I am to gain more presets.

I'm not a patch snob and I'll use other people's presets in a heartbeat if I find them useful although I always reach for my own first. I just find it hard to justify spending money on presets for DUNE 3 since I've made so many of my own and obviously those are the kinds of sounds I like and will use.

Of course we could just load one of your patches that uses a sample and then edit it but it's far easier to start with an INIT patch and work from there.

On the subject of samples....I'd love to encourage people to develop sample content that can be used in D3'S Osc. Of course we'd all much rather have multi-sample import but for reasons explained by Synapse earlier in this thread that is not likely to happen for D3 so we make use of what we are given.

For example there are Gigs of sample content for Zampler which is also a Synapse plugin and a lot of that content is free. I've found some of those samples work well across a fairly large range of the keyboard if they are looped well. Usually a sample at C3 or C4 works best.

[fisherKing]

just joining the conversation. great update, and good to have the browser. looking forward to a scrolling option... it's the reverse of how i scroll on my mac (confusing!), but glad to see all the 'new', for what is one of my essential synths.

[THE INTRANCER]

And having an extra 18 patch names to scan with your eyes doesn't make it much faster than typing a letter or two to find what you want.

See this is an example of how you're not thinking it through. For example my qwerty keyboard sits behind my midi controller keyboard as it should since ergonomically the thing I use to make music should have focus. So no, "typing a letter or two to find what you want" is not faster.

I have two synth synthesizers at different levels, each of them have QWERTY keyboards on them and if I want to park my keyboard at the front, I side it under the desk so I can use the synth which I actually use as a desk as well. They both have a section to place things on the right side.

My point is that it's not natural to make things difficult for yourself in your music setup unless you enjoy futility.

You know what's really fast? Click in the Patch name on the main monitor screen which opens up a folder with over 200 patches viewable at one glance, then select the one you want by clicking a second time. Any patch just two mouse clicks away. Any other bank just a couple more away.

That is the efficiency of the old patch handling system which thankfully still exists since if you know how to organize any file on your computer is a fast and elegant method.

You can't do that if you are using any of the other tabs such as the arp ect, I previously mentioned.

The Genetics feature by it's very nature feels like it belongs as part of the main GUI functionality rather than hidden away on yet another screen. It will be one of the most used things of Dune

Again you're not thinking it through. The Genetics won't be "one of the most used things of Dune" for me or anyone who actually knows how to make their own patches.

Sure it's a fun little feature but it's not something I'll be using all the time so no I don't want it showing all the time. It's perfect right where it is.

The vast majority of users of Dune will though, not everyone has the patience to try and carve out any particular sound in an instant and whilst in the midst of creating a track. Not everyone will find Dune to be that intuitive from the outset. It actually isn't...

Let's break it down....what you are saying is that you know better than the people who designed this synth (who by the way have been in this business from the very beginning) how these updates should have been done. I'm saying no you don't. Your concept is in no way superior. I can say that with great confidence having owned DUNE since version one and spent hundreds of hours or more with it programing patches and using multiple instances of it in every project.

It's not about me knowing better than the developers, it's about proposing an expansion to what's been developed, it's not an alternative thing that replaces another. It's a different approach that compliments the other. This isn't a competition in who has a better idea or solution here and knows more. This is about communication of ideas to help improve a product that a developer may look at doing but were not at the point of doing, or may not have even considered at the time. Things are prioritised in development too, and ideas can develop from them later on and that's what I have here, highlighting the reasons I have for it.

Sure you can use the old listing method, but it's not as fun or effective as the new browser system.

Is DUNE 3 perfect? No of course not nothing is prefect and there is always room for improvement but what you are proposing is simply not an improvement.

Simply stating that what I'm proposing isn't an improvement doesn't' make it so, when you have nothing to counter argue my points and reasons on. You failed to recognise the intent of what I'm proposing based on your post here in the way you think that I'm proposing better solution than what's being provided already. That's not the case, it's about providing alternative methods like different doors to a building to access things in slightly different ways. Some people might like to take a lift, some people might prefer the stair.

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.
Someone could come up with something amazing but because of prerequisite feelings of who created it, you would never allow yourself to be upfront to say how good it was once you have already stated what you think based on that. It's easier to try and defend your stance than risk losing an argument, because that would show to others that people can easily win arguments against you.

Let me spell it out again. I don't care if it was Richard himself who proposed what you are proposing I would have pushed back against it from the very first minute because it doesn't make sense.

It's the same system, it's just presented in a different way and this type of bottom patch browser worked perfectly well with U-HE's Zebralette synth.

Now he might not have listened to me but since he didn't do what you proposed but instead came up with a better plan well you can take it from there.

I designed the concept based on the actual graphics of what's been delivered in this update, not before.

Again it's not about you it's about your idea. To think otherwise it to simply a cop out.

Replied to that as above..

why would you waste time being vocal about something you don't have any use for, just because there's an opportunity to do so, to part of the in crowd ?

No because I knew that's what other people wanted even though I had no use for it because my goal was to make the plugin better for everyone. If I thought what you are proposing was in any way better I would be supporting it too.

Gonna have to agree to disagree on that one.

As for development, there really isn't much that Richard needs to do to provide a browser to the front of the interface.

But he didn't because it doesn't make sense. Look I get it you fancy yourself some sort of UI/UX expert and in some ways you may be but in this case with this concept you are simply wrong. Accept that fact and move on.

So you are now able to use telepathy to read Richards mind now...

You've apparently misunderstood the intent of the concept, it is however a solution with many benefits, which I've clearly explained in detail. There is no wrong in this, it's the same but slightly different in approach which provides an effective way to access new features in their making.

GUI development isn't just as is, it's about having foresight to see how things can be developed in the future, because not everyone plays or expects things in the same way.

[maximoog]

Hello,

I have found a bug in the browser. As soon as I load a fourth instance of DUNE I can't open the browser in this and the following instances.

Cubase 11, Cakewalk, Windows 11, DUNE VST3.

[LFO8]

Hi Richard, any reason as to why the demo download is version 3.4 instead of 3.5?

We have not finished the 3.5 demo yet, and we have not decided whether to include the new patch browser in the demo.With the demo version being limited to <100 patches, the browser is not that useful, neither for browsing nor for the new Genetics function which greatly benefits from having at least the full factory library installed (1000+ patches).

Richard

Please consider including the patch browser (and all features) in the demo. I (and I think many others) would certainly want to check all of it out before committing to a purchase. Thanks.

[franciscosta]

May I suggest that a link to the web-hosted PDF User Manual is included across your products, for example an icon/logo to the far right of the text "Differential Unison Engine"?

Or pointing to a new page on your website which shows a number of product images and then User Guide buttons/links for each. This page is also where users would regularly go to and they'd find not only the manuals but also see any relevant marketing information, offers, videos, soundbanks, etc.

Its an additional way to keep your users coming back and maybe explore other products in your line.

It will also allow Demo users to see that there is substantial depth to the product and satisfy their curiosity (some may get scared, many brains don't like user mammals).

Thank You.

[kvmorgan]

Hi Richard, any reason as to why the demo download is version 3.4 instead of 3.5?

We have not finished the 3.5 demo yet, and we have not decided whether to include the new patch browser in the demo.With the demo version being limited to <100 patches, the browser is not that useful, neither for browsing nor for the new Genetics function which greatly benefits from having at least the full factory library installed (1000+ patches).

Richard

Please consider including the patch browser (and all features) in the demo. I (and I think many others) would certainly want to check all of it out before committing to a purchase. Thanks.

Agreed.

[Teksonik]

So you are now able to use telepathy to read Richards mind now.

I don't have to read his mind I can see the results of his decisions in the version that was just released. He didn't do what you are proposing because it doesn't make sense. Period.

You've apparently misunderstood the intent of the concept, it is however a solution with many benefits, which I've clearly explained in detail. There is no wrong in this, it's the same but slightly different in approach which provides an effective way to access new features in their making.

I'm not going to argue with you any further. Your concept is not a solution anywhere but in your mind.

You have failed to come up with anything better than what already is and in fact your concept would make things worse and you would realize that if you took the time to think it through.

Luckily Synapse knows what's right and wrong so there's no need for me to push back against your concept any further. So I will say no more on the subject. Let it go.......

[Teksonik]

Hello,

I have found a bug in the browser. As soon as I load a fourth instance of DUNE I can't open the browser in this and the following instances.

Cubase 11, Cakewalk, Windows 11, DUNE VST3.

As I said on the Synapse forum I have run the test here with 5 instances and can not reproduce what you are reporting.

Can you give a little more information? What exact steps are you taking? I'll do the same steps and try to reproduce what you are reporting.

Of note I am on Windows 10 so if the issue is related to Win 11 and I'm not saying it is then our results will naturally be different.

[Teksonik]

Please consider including the patch browser (and all features) in the demo. I (and I think many others) would certainly want to check all of it out before committing to a purchase. Thanks.

I believe they are working on that as we speak.

[maximoog]

Thank you for the quick reply.

I started a new song yesterday to be done only with DUNE 3.

I started normally with an empty song in Cubase. Then played the first three tracks, selected the sounds in the browser and from the fourth track I could not open the browser.

I tried the whole thing again in an empty project in Cubase and Cakewalk, loaded four instances of DUNE each, in the first three I can open the browser normally and from the fourth again not.

I hope it's really not Windows 11, unfortunately I have no way to test on Windows 10.

[Teksonik]

Hmmm well we seem to be doing the same thing. I tried it both with closing each browser and leaving them all open. I don't have any version of Cubase to test in.

Let's see if anyone else can run the test and what they report.

[Caine123]

Thank you for the quick reply.

I started a new song yesterday to be done only with DUNE 3.

I started normally with an empty song in Cubase. Then played the first three tracks, selected the sounds in the browser and from the fourth track I could not open the browser.

I tried the whole thing again in an empty project in Cubase and Cakewalk, loaded four instances of DUNE each, in the first three I can open the browser normally and from the fourth again not.

I hope it's really not Windows 11, unfortunately I have no way to test on Windows 10.

Can test very later today maybe but yeah sounds assy but why did you upgrade to win11 already? Sorry but anyone who updates so early is really too optimistic with OS'es... it never changed so wait wait wait instead of upgrading asap...

[zvenx]

Thank you for the quick reply.

I started a new song yesterday to be done only with DUNE 3.

I started normally with an empty song in Cubase. Then played the first three tracks, selected the sounds in the browser and from the fourth track I could not open the browser.

I tried the whole thing again in an empty project in Cubase and Cakewalk, loaded four instances of DUNE each, in the first three I can open the browser normally and from the fourth again not.

I hope it's really not Windows 11, unfortunately I have no way to test on Windows 10.

I have Nuendo on my PC Windows 10...
Same codebase as Cubase as I am sure you know.
Let me go try it now.
rsp


edit:
I just opened six instances vst3, on Windows 10, Nuendo 11 whatever the latest is.


rsp

[fisherKing]

different OS (of course), but just opened 8 instances of dune 3.5 in logic, and the browser is there in each one...