Dune 3
-
- KVRAF
- Topic Starter
- 2505 posts since 26 Jul, 2004
If I would have one desire about the next version of Dune3, or the next update that is coming, it would be the following.
When working with the genetic preset randomiser, it would be a really great help to have the possebilety to edit the preset number the plugin is giving the new sound when storing it in the genetics bank, just to have it easyer to find it again.
Ore, if you are creating pads ore bass or drums or what ever, it would be cool to set a folder where to store the new presets so that they are not mixed with other sound types, bevor starting to create new presets.
May be they are lucking to this topic and like my idea and it wouldn´t be to much work to do change this:)
Would be great I think:)
When working with the genetic preset randomiser, it would be a really great help to have the possebilety to edit the preset number the plugin is giving the new sound when storing it in the genetics bank, just to have it easyer to find it again.
Ore, if you are creating pads ore bass or drums or what ever, it would be cool to set a folder where to store the new presets so that they are not mixed with other sound types, bevor starting to create new presets.
May be they are lucking to this topic and like my idea and it wouldn´t be to much work to do change this:)
Would be great I think:)
-
- KVRAF
- 3679 posts since 1 Sep, 2016
My only nitpick about Dune is the tabbed oscillators. It's just a workflow that irritates me. If it were up to me I'd get rid of that big square display and rejig the oscillators to fit them all on the front panel. That design is very much the synth's visual signature though.
-
- KVRer
- 13 posts since 8 Nov, 2011 from London Bridge, London.
"When working with the genetic preset randomiser, it would be a really great help to have the possebilety to edit the preset number the plugin is giving the new sound when storing it in the genetics bank, just to have it easyer to find it again."
Just go to the Genetic Soundbank, right click on the preset, and rename it.
Or am I misunderstanding what you are saying?
Just go to the Genetic Soundbank, right click on the preset, and rename it.
Or am I misunderstanding what you are saying?
My Bloody Valentine, Velvet Underground, Doors, Byrds, Killing Joke, Joy Division, Sigur Ros, Burzum, Dinosaur Jr, early Pink Floyd/U2, Neil Young. REAPER.
https://writheuk1.bandcamp.com/track/lo ... cryin-live Play LOUD!
https://writheuk1.bandcamp.com/track/lo ... cryin-live Play LOUD!
-
- KVRAF
- Topic Starter
- 2505 posts since 26 Jul, 2004
Thats what I am doing now.
But, if the little popup window in the genetics fild would be changed, so that you can do this right in there AND may be assign it to a specific folder, like for pads, bass and so on, it would be greate.
But, if the little popup window in the genetics fild would be changed, so that you can do this right in there AND may be assign it to a specific folder, like for pads, bass and so on, it would be greate.
writheuk wrote: ↑Sun Oct 13, 2024 10:53 am "When working with the genetic preset randomiser, it would be a really great help to have the possebilety to edit the preset number the plugin is giving the new sound when storing it in the genetics bank, just to have it easyer to find it again."
Just go to the Genetic Soundbank, right click on the preset, and rename it.
Or am I misunderstanding what you are saying?
- KVRian
- 763 posts since 3 Nov, 2023
- KVRAF
- 5804 posts since 25 Dec, 2004
that would be great
sketches... http://soundcloud.com/onesnzeros
some artists i support... https://bandcamp.com/spectraselecta
some artists i support... https://bandcamp.com/spectraselecta
- KVRAF
- 18750 posts since 16 Sep, 2001 from Las Vegas,USA
I've been having some health issues recently so I don't have the stamina to carry on drawn out running discussions but I will address the Osc Tabs issue. I've seen a handful of people over the years express the desire to see all three Oscs at once but I've never seen anyone do a mock up of how that would actually be accomplished, even people who would have the talent to do such a mock up (which I do not). I've done very crude mock ups of moving the Mod Matrix and Arp/Seq down to the bottom section which went nowhere and I can't even come up with a concept of an idea of how to get all three Oscs to display at once with each of the four different synthesis types. VA,FM,WT and Sample. I'm not even sure it would be possible with the current .ini file.
I'm not opposed to optional GUI workflows I just don't know if they would be possible on a technical level or practical on a functional level. Make the GUI larger and people will complain it's too large. Stuff as much as possible on one page and people will complain that it's too crowded. Make it tabbed and well, as we see here people will push back.
The more complex a synth is the more complex its workflow will be. How it's handled in other synths really doesn't apply since architectures vary wildly from one to the next. Take VPS Avenger for example, it is a tab fest and only one Osc can have visual focus at once. Want another Filter? No problem, just add one but then the filters become tabbed as well and so on. But again I don't know how it could technically be improved so I've just learned to use it and love it as is. Parawave Rapid shows all three Oscs of each layer at the same time but its Osc architecture is different and so on.
Third party skins are great but whoever makes them needs to commit to updating them any time the synth gets an update that adds new features and functions. I've lost track of the number of times I've had to update my simple color edit of the default skin but that's a good thing since it meant the synth was growing as a musical instrument.
So since these concerns about DUNE 3's workflow have been raised before going back many years and it still hasn't changed that would indicate it's not an easy or practical task to undertake. Who knows how man hours it would take when we make a feature request. Hours, days, weeks, months, who knows? I've always been of the opinion that those man hours would be better spent on features and functions that improve the range and/or quality of sounds a synth can make. Workflow can be learned and any perceived workflow imperfections adapted to and tolerated. New features can't be added by the end user. I know not everyone will share my opinion and that's fine.
I will leave you a tip on DUNE 3's Workflow that I've been using for many years to create the thousand plus patches I've made for it.
Instead of using Osc 2 in Voice (Layer) 1, I will use Osc 1 in Layer 2. That gives us the ability to have each Osc run through different filters with different ADSR settings, etc. We can Solo/Mute the layers which can't be done with individual Oscs on a single layer, we can copy/paste a layer to another (even from different instances of D3) which can't be done with individual Oscs. Yes that "limits" us to 8 Oscs which are enough to do some serious sounds and we can easily mix synthesis types (3xVA, 2xFM ,2xWT, 1x Sample) or any combination thereof. We can create templates for different combinations and if 8 Oscs aren't enough we can always reach for the other 16.
Yes only one Layer can be viewed at a time with my method and you'll still need to click tabs but the added flexibility makes it well worth the effort, at least to me.
The other tip I'll give is to express your wishes at the Synapse Audio forums as I'm not sure that Rich and Marcin frequent KVR these days so your concerns are more likely to be seen there.
Ok that's it for me, I'm spent for today. I'm not sure when I'll be back.......
I'm not opposed to optional GUI workflows I just don't know if they would be possible on a technical level or practical on a functional level. Make the GUI larger and people will complain it's too large. Stuff as much as possible on one page and people will complain that it's too crowded. Make it tabbed and well, as we see here people will push back.
The more complex a synth is the more complex its workflow will be. How it's handled in other synths really doesn't apply since architectures vary wildly from one to the next. Take VPS Avenger for example, it is a tab fest and only one Osc can have visual focus at once. Want another Filter? No problem, just add one but then the filters become tabbed as well and so on. But again I don't know how it could technically be improved so I've just learned to use it and love it as is. Parawave Rapid shows all three Oscs of each layer at the same time but its Osc architecture is different and so on.
Third party skins are great but whoever makes them needs to commit to updating them any time the synth gets an update that adds new features and functions. I've lost track of the number of times I've had to update my simple color edit of the default skin but that's a good thing since it meant the synth was growing as a musical instrument.
So since these concerns about DUNE 3's workflow have been raised before going back many years and it still hasn't changed that would indicate it's not an easy or practical task to undertake. Who knows how man hours it would take when we make a feature request. Hours, days, weeks, months, who knows? I've always been of the opinion that those man hours would be better spent on features and functions that improve the range and/or quality of sounds a synth can make. Workflow can be learned and any perceived workflow imperfections adapted to and tolerated. New features can't be added by the end user. I know not everyone will share my opinion and that's fine.
I will leave you a tip on DUNE 3's Workflow that I've been using for many years to create the thousand plus patches I've made for it.
Instead of using Osc 2 in Voice (Layer) 1, I will use Osc 1 in Layer 2. That gives us the ability to have each Osc run through different filters with different ADSR settings, etc. We can Solo/Mute the layers which can't be done with individual Oscs on a single layer, we can copy/paste a layer to another (even from different instances of D3) which can't be done with individual Oscs. Yes that "limits" us to 8 Oscs which are enough to do some serious sounds and we can easily mix synthesis types (3xVA, 2xFM ,2xWT, 1x Sample) or any combination thereof. We can create templates for different combinations and if 8 Oscs aren't enough we can always reach for the other 16.
Yes only one Layer can be viewed at a time with my method and you'll still need to click tabs but the added flexibility makes it well worth the effort, at least to me.
The other tip I'll give is to express your wishes at the Synapse Audio forums as I'm not sure that Rich and Marcin frequent KVR these days so your concerns are more likely to be seen there.
Ok that's it for me, I'm spent for today. I'm not sure when I'll be back.......
None are so hopelessly enslaved as those who falsely believe they are free. Johann Wolfgang von Goethe
- KVRAF
- 2548 posts since 3 Dec, 2006
Thank you for the great Tips and Hints Marc,Teksonik wrote: ↑Tue Oct 15, 2024 9:41 am I've been having some health issues recently so I don't have the stamina to carry on drawn out running discussions but I will address the Osc Tabs issue. I've seen a handful of people over the years express the desire to see all three Oscs at once but I've never seen anyone do a mock up of how that would actually be accomplished, even people who would have the talent to do such a mock up (which I do not). I've done very crude mock ups of moving the Mod Matrix and Arp/Seq down to the bottom section which went nowhere and I can't even come up with a concept of an idea of how to get all three Oscs to display at once with each of the four different synthesis types. VA,FM,WT and Sample. I'm not even sure it would be possible with the current .ini file.
I'm not opposed to optional GUI workflows I just don't know if they would be possible on a technical level or practical on a functional level. Make the GUI larger and people will complain it's too large. Stuff as much as possible on one page and people will complain that it's too crowded. Make it tabbed and well, as we see here people will push back.
The more complex a synth is the more complex its workflow will be. How it's handled in other synths really doesn't apply since architectures vary wildly from one to the next. Take VPS Avenger for example, it is a tab fest and only one Osc can have visual focus at once. Want another Filter? No problem, just add one but then the filters become tabbed as well and so on. But again I don't know how it could technically be improved so I've just learned to use it and love it as is. Parawave Rapid shows all three Oscs of each layer at the same time but its Osc architecture is different and so on.
Third party skins are great but whoever makes them needs to commit to updating them any time the synth gets an update that adds new features and functions. I've lost track of the number of times I've had to update my simple color edit of the default skin but that's a good thing since it meant the synth was growing as a musical instrument.
So since these concerns about DUNE 3's workflow have been raised before going back many years and it still hasn't changed that would indicate it's not an easy or practical task to undertake. Who knows how man hours it would take when we make a feature request. Hours, days, weeks, months, who knows? I've always been of the opinion that those man hours would be better spent on features and functions that improve the range and/or quality of sounds a synth can make. Workflow can be learned and any perceived workflow imperfections adapted to and tolerated. New features can't be added by the end user. I know not everyone will share my opinion and that's fine.
I will leave you a tip on DUNE 3's Workflow that I've been using for many years to create the thousand plus patches I've made for it.
Instead of using Osc 2 in Voice (Layer) 1, I will use Osc 1 in Layer 2. That gives us the ability to have each Osc run through different filters with different ADSR settings, etc. We can Solo/Mute the layers which can't be done with individual Oscs on a single layer, we can copy/paste a layer to another (even from different instances of D3) which can't be done with individual Oscs. Yes that "limits" us to 8 Oscs which are enough to do some serious sounds and we can easily mix synthesis types (3xVA, 2xFM ,2xWT, 1x Sample) or any combination thereof. We can create templates for different combinations and if 8 Oscs aren't enough we can always reach for the other 16.
Yes only one Layer can be viewed at a time with my method and you'll still need to click tabs but the added flexibility makes it well worth the effort, at least to me.
The other tip I'll give is to express your wishes at the Synapse Audio forums as I'm not sure that Rich and Marcin frequent KVR these days so your concerns are more likely to be seen there.
Ok that's it for me, I'm spent for today. I'm not sure when I'll be back.......
I really hope that your health improves !!
-
- KVRian
- 903 posts since 30 Oct, 2003 from Pacific NW, USA
@Teksonik - sorry to hear that you’re going through a rough patch. I appreciate your contributions to this community and I sincerely hope that you overcome whatever it is that you’re facing. Please take good care of yourself mate!
Your ideas are practical, well-organized and logical. Since designing GUI’s isn’t something that I’ve ever tried before, I try to have some grace when a cool plug-in is released with a horrible interface.
I learn the workflow and any little quirks, then I make do with it and just concentrate on the music. With screen real estate being such a big factor though, I don’t know what kind of design that would be more practical in use for Dune 3 than a tabbed interface.
And as much as I’d love to see all of the oscillators at once to aid in complex patch design, I think Dune 3 was packaged brilliantly considering the extensive list of features. I can tell that a lot of time and effort went into getting all of those elements positioned for maximum performance and speed. It’s a fantastic synth and I happen to dig its GUI!
- KVRian
- 763 posts since 3 Nov, 2023
The gui changes won't happen, it's just wishful thinking
It's too far down the line to do a total rewite of gui code, and cost vs benefit is negligible (more likely negative) and probably not possible in some cases
I'm quite happy with how it is, but no harm in asking for changes
It's too far down the line to do a total rewite of gui code, and cost vs benefit is negligible (more likely negative) and probably not possible in some cases
I'm quite happy with how it is, but no harm in asking for changes
-
- KVRAF
- 3163 posts since 26 Mar, 2002 from london
Tabs are fine with me. It's either more visual noise and no extra clicks, or a quieter appearance with an extra click now and then.
Every day takes figuring out all over again how to f#ckin’ live.
- KVRAF
- 18750 posts since 16 Sep, 2001 from Las Vegas,USA
Thank you so much for your concern gentlemen. It really means a lot to me!
Anyway I'm feeling much better now. I turn 68 years old this month so at my age the next breath is never guaranteed.
But I'm going into old age kicking and fighting. I still lift weights and work out five days a week so hopefully I can fend off the grim reaper for quit some time into the future.
-------------
On the subject of DUNE 3'S GUI, Satyatunes sells an alternative skin called Glacier White that should appeal to the tastes of some. He keeps it updated whenever there is a change in D3 so you can use it with confidence going forward:
https://satyatunes.com/shop/glacier-white
You do not have the required permissions to view the files attached to this post.
None are so hopelessly enslaved as those who falsely believe they are free. Johann Wolfgang von Goethe