Yes, it could. However, I see this process as a collaboration between developer and sound designer: The dev creates a limited (by necessity) tool with fantastic sound and efficient control interface. The sound designer is then free to use the full breadth of their creativity, filtered through each synth as it has been presented by its developer. The choices made in the design of each instrument are what make it unique and give it a workFLOW, instead of a workFLOOD.Fritze wrote:This could be achieved with an option in the detune law drop down list that says something with the meaning of "switch with engine", which could be the default. The other entries in the list could be the various detune laws.Infinite5ths wrote:A few engine options (each with a detune law, filter, and envelope pre-selected with a certain sound in mind) may actually save the average user from wasted time and confusion.
Best of both worlds: Easy mode if you keep the default and more control if you want to have it.
Hive preview (April 1 update)
-
- KVRist
- 322 posts since 19 Sep, 2005 from Los Angeles, CA
-
- Banned
- 10196 posts since 12 Mar, 2012 from the Bavarian Alps to my feet and the globe around my head
What about making 2 layers or views - one with a simple view for the beginners, and an "advanced view" with more options for the experts? That wouldn't destroy the easy-to-use character of Hive...
-
- KVRist
- 322 posts since 19 Sep, 2005 from Los Angeles, CA
-
- KVRAF
- 26963 posts since 3 Feb, 2005 from in the wilds
The pressure from users to have everything is huge... I like that Hive is limited and hope it does not get too much feature creep. Just having options is itself a burden... knowing that they are there a distraction.
I really like that each engine is different and hope that the individual aspects are not dissected into options. Let each engine be unique and let there be combinations that are not possible. That is just fine.
I really like that each engine is different and hope that the individual aspects are not dissected into options. Let each engine be unique and let there be combinations that are not possible. That is just fine.
-
- KVRAF
- 26963 posts since 3 Feb, 2005 from in the wilds
-
- KVRAF
- 1888 posts since 13 Aug, 2011 from Berlin
So you agree with me? I'm not sure if I got your point.Infinite5ths wrote:Yes, it could. However, I see this process as a collaboration between developer and sound designer: The dev creates a limited (by necessity) tool with fantastic sound and efficient control interface. The sound designer is then free to use the full breadth of their creativity, filtered through each synth as it has been presented by its developer. The choices made in the design of each instrument are what make it unique and give it a workFLOW, instead of a workFLOOD.
-
- KVRist
- 322 posts since 19 Sep, 2005 from Los Angeles, CA
I vote that the engine selection UI stays as-is. This limitation moves the creative process ahead -- pick an engine and go. If Urs adds hidden options under the hood, fine; but the streamlined design is superb. Options to tweak the engine to death simply mean it's harder to 'know the knobs' - they respond differently with every permutation of engine settings.Fritze wrote:So you agree with me? I'm not sure if I got your point.
Last edited by Infinite5ths on Fri Dec 26, 2014 12:31 am, edited 3 times in total.
-
- Banned
- 10196 posts since 12 Mar, 2012 from the Bavarian Alps to my feet and the globe around my head
Noooooooooo, not everything! It's not HiveMaster!pdxindy wrote:The pressure from users to have everything is huge...
Only a few more features...
-
- KVRist
- 322 posts since 19 Sep, 2005 from Los Angeles, CA
My sole feature request to date: 2 more target slots/knobs in each Mod Matrix 'cell'
HIVE responds well to modulating multiple targets with the same source, double-hitting targets, and modulating modulators. I often use multiple matrix cells with the same source, to hit 3 or 4 targets.
Even so, it's already so easy to copy one cell to another and then tweak new targets...do I really even need 4 slots/cell?
I also thought about asking if we could have the Mod Matrix depth knobs available as targets for other matrix slots (similar to the FabFilter plugins UI). But then it gets more tricky to see at a glance what's going where; and adjusting anything is complicated, because so many mods are tied into each other.
EDIT: Oddly enough I just found either a bug or what appears to be a way to modulate mod depths via other slots.
1) Click on any mod depth knob
2) Immediately right- (or control-) click on a target slot
On my copy of HIVE, the resulting menu shows the previously clicked depth knob as the very top item. When I choose it, the target slot reads something like MM2: Depth1
Unfortunately, it doesn't work - nothing happens at the target when I route modulation this way.
Is this a known feature I overlooked or a GUI anomaly ?
HIVE responds well to modulating multiple targets with the same source, double-hitting targets, and modulating modulators. I often use multiple matrix cells with the same source, to hit 3 or 4 targets.
Even so, it's already so easy to copy one cell to another and then tweak new targets...do I really even need 4 slots/cell?
I also thought about asking if we could have the Mod Matrix depth knobs available as targets for other matrix slots (similar to the FabFilter plugins UI). But then it gets more tricky to see at a glance what's going where; and adjusting anything is complicated, because so many mods are tied into each other.
EDIT: Oddly enough I just found either a bug or what appears to be a way to modulate mod depths via other slots.
1) Click on any mod depth knob
2) Immediately right- (or control-) click on a target slot
On my copy of HIVE, the resulting menu shows the previously clicked depth knob as the very top item. When I choose it, the target slot reads something like MM2: Depth1
Unfortunately, it doesn't work - nothing happens at the target when I route modulation this way.
Is this a known feature I overlooked or a GUI anomaly ?
Last edited by Infinite5ths on Fri Dec 26, 2014 2:31 am, edited 6 times in total.
-
- KVRAF
- 4075 posts since 28 Jan, 2011 from MEXICO
Arent there other options for those who want moar? Like Zebra?
I a like that each synth is it's own thing. Hive is simple fun and its fine.
I a like that each synth is it's own thing. Hive is simple fun and its fine.
dedication to flying
-
- KVRist
- 322 posts since 19 Sep, 2005 from Los Angeles, CA
Another sound - weird synth thing: I call it Skwerp
http://www.i5pmusic.com/sound/presets/u ... %20MFD.h2p
http://www.i5pmusic.com/sound/presets/u ... %20MFD.h2p
-
- KVRAF
- 4141 posts since 11 Aug, 2006 from Texas
You're quite welcome, I hope you enjoy them.zvenx wrote:Thank you very much for collecting these, editing them and all the contributors.
Yep:zvenx wrote:Who is AusDisciple aka David O'Connor. Is he a kvrite?
http://www.kvraudio.com/forum/memberlis ... e&u=313921
-
- KVRist
- 31 posts since 29 Oct, 2014
you´ve put that stupid 303 patch in there but not the imo pretty usefull amp2rel?Here's the link again for those that don't want to go through pages of posts:
http://u-he.com/PatchLib/presets/hive/KVR-Hive_Beta.zip
.
why that? the name? I ve variatiions called willi too.. Here it is again in 3 variations
i dont think that i like that the fx section on/off is not stored with the patch
You do not have the required permissions to view the files attached to this post.
Last edited by 3phase on Fri Dec 26, 2014 6:52 am, edited 1 time in total.
-
- KVRAF
- 4141 posts since 11 Aug, 2006 from Texas
Well, there were about 40 pages to go through and I do make mistakes. I'll fix it in the next upload.3phase wrote:you´ve put that stupid 303 patch in there but not the imo pretty usefull amp2rel?
why that? the name? I ve variatiions called willi too.. Here it is again in 3 variations