Hive 2 is coming!
-
- KVRist
- 99 posts since 1 Jul, 2018
[quote=Grizzellda post_id=7341155 time=1552438392 user_id=352033]
How is this any different from what you could achieve using a modular system, either software or hardware?
[i]Providing that system could do wavetables[/i].
[/quote]
polyphony?
How is this any different from what you could achieve using a modular system, either software or hardware?
[i]Providing that system could do wavetables[/i].
[/quote]
polyphony?
- u-he
- 28063 posts since 8 Aug, 2002 from Berlin
It looks similar, but I think it's a different concept.
Biotek has 8 LFOs with 8 "SubLFOs" each. That's 64. So you'd sit there and edit 64 LFO settings in order to use it to its full potential. It's certainly powerful, but man, doesn't it explain why even in Zebra we only ever put 4 of each?
Hive's shape thing has 8 envelope segments in total. Just those 8 you see. Those are shared by the 4 sequences set up below it. It's a mindbogglingly simple concept. It kind of puzzles me that I have not seen this before. Surely, someone must have had that idea before me - would love to check it out!
When you click a segment, a larger version of it appears in the hexagon. There you can set the shape (saw/square/triangle) the maximum and minimum level, the curvature and the number of ratchets. Latter smoothly fades in multiple versions of the same basic shape in an IMHO very useful pattern.
What's furthermore different to Biotek's Flow LFO, there you can scan through the settings by about any modulation source, if I understand it correctly. I have not added any way to scan through Hive's shapes from an external modulation source. I'm sure this will be the next feature request. But I'll be reluctant to do that because it uses a lot less CPU when moving forward at a constant pace.
-
- KVRAF
- 2023 posts since 23 May, 2012 from London
Also simplicity. Hive is an otherwise straight forward synth to understand and program, that we're getting a taste of some of the deeper and more generative tools of modular, in such a simple and streamlined synth is awesome imo.robbmonn wrote: ↑Wed Mar 13, 2019 5:53 ampolyphony?Grizzellda wrote: ↑Wed Mar 13, 2019 12:53 am How is this any different from what you could achieve using a modular system, either software or hardware?
Providing that system could do wavetables.
Always Read the Manual!
- u-he
- 28063 posts since 8 Aug, 2002 from Berlin
In a modular system you'd get to connect anything to anything. Hive on the other hand has a strict distinction between modulation and audio signals. For instance, you can not route an audio signal into the envelope followers (Func1/2) to extract a modulation signal. You can't sync an envelope to an audio oscillator, or use an oscillator as an LFO.Grizzellda wrote: ↑Wed Mar 13, 2019 12:53 am How is this any different from what you could achieve using a modular system, either software or hardware?
Providing that system could do wavetables.
But. I think the main reason I always thought Hive was underrated was the power of its ModMatrix. If you know the Hive Science soundsets by Kevin Schröder and Howard Scarr, they are full of "sounds Hive can't do". But then you check out what they did in the ModMatrix and it go oi, didn't think about that.
I think with the revised interface and the added options Hive will go far into modular territory.
But I can also think of a gazillion ways to make playable and "musically useful" patches sound more alive and expressive than they would without.
- KVRAF
- 7624 posts since 21 Dec, 2002 from MD USA
I been kicking myself for selling HIVE, i know I will buy it back before too long.
my music: http://www.alexcooperusa.com
"It's hard to be humble, when you're as great as I am." Muhammad Ali
"It's hard to be humble, when you're as great as I am." Muhammad Ali
-
- KVRian
- 892 posts since 27 Oct, 2004 from Inside the kick drum
Will there be modulation "moves" like Serum has? You modulate some knob and it will move in visually, just like in Serum and Pigments and so on. I find it useful
PS. I tested latest Bitwig 2.5 demo, and I found out that if I have uhe synths playing and then I open the synth, the sounds from the synth stops right away. I need to stop and press play again to get the sound back. Bug on uhe synths or in Bitwig?
PS. I tested latest Bitwig 2.5 demo, and I found out that if I have uhe synths playing and then I open the synth, the sounds from the synth stops right away. I need to stop and press play again to get the sound back. Bug on uhe synths or in Bitwig?
- u-he
- 28063 posts since 8 Aug, 2002 from Berlin
That's what I call "balls in orbit". I might give it a try, but the schedule is quite tight. If we do this, it would certainly be an option one can switch on or off.
The problem with these things is, you can't really make out fast modulations. But it's those fast modulations most of the time which you will want to track down. That's why we're adding the Insights module. It shows you the past seconds or so of a bunch of modulations and when you hear something unexpected you can freeze the scope and zoom in to where it happened.
This currently works for any modulation source, but I will try to make it happen for ModMatrix slots as well, such that you can track individual parameter movements. I'm not sure if I get that baked for 2.0 though, it may have to wait for a later date.
It's an issue with our VST3 versions IIRC. Apparently Steinberg and others have not implemented VST3 properly in this one aspect, so this bug never occurred to us. Bitwig is going to offer a workaround in the next update and we will continue to fix this with future updates.PS. I tested latest Bitwig 2.5 demo, and I found out that if I have uhe synths playing and then I open the synth, the sounds from the synth stops right away. I need to stop and press play again to get the sound back. Bug on uhe synths or in Bitwig?
-
- KVRian
- 1236 posts since 8 Jan, 2012 from frankfurt, Germany
I think visible modulation is the success of massive, serum, avenger and now also pigments. An option to switch on / off would be nice.Urs wrote: ↑Wed Mar 13, 2019 10:58 amThat's what I call "balls in orbit". I might give it a try, but the schedule is quite tight. If we do this, it would certainly be an option one can switch on or off.
The problem with these things is, you can't really make out fast modulations. But it's those fast modulations most of the time which you will want to track down. That's why we're adding the Insights module. It shows you the past seconds or so of a bunch of modulations and when you hear something unexpected you can freeze the scope and zoom in to where it happened.
This currently works for any modulation source, but I will try to make it happen for ModMatrix slots as well, such that you can track individual parameter movements. I'm not sure if I get that baked for 2.0 though, it may have to wait for a later date.
It's an issue with our VST3 versions IIRC. Apparently Steinberg and others have not implemented VST3 properly in this one aspect, so this bug never occurred to us. Bitwig is going to offer a workaround in the next update and we will continue to fix this with future updates.PS. I tested latest Bitwig 2.5 demo, and I found out that if I have uhe synths playing and then I open the synth, the sounds from the synth stops right away. I need to stop and press play again to get the sound back. Bug on uhe synths or in Bitwig?
When i demonstrated last weekend a friend some basic synths he understood nothing about how an envelope or a lfo is working, then I showed him pigments and he was finaly able to undestand what is going on.
- KVRAF
- 23102 posts since 7 Jan, 2009 from Croatia
- u-he
- 28063 posts since 8 Aug, 2002 from Berlin
I'm just repeat what I get from some other dev who explained the issue to me
-
- KVRian
- 892 posts since 27 Oct, 2004 from Inside the kick drum
Hmm.. I am using only VST 2.4 plugins, so I don't knowUrs wrote: ↑Wed Mar 13, 2019 10:58 amIt's an issue with our VST3 versions IIRC. Apparently Steinberg and others have not implemented VST3 properly in this one aspect, so this bug never occurred to us. Bitwig is going to offer a workaround in the next update and we will continue to fix this with future updates.PS. I tested latest Bitwig 2.5 demo, and I found out that if I have uhe synths playing and then I open the synth, the sounds from the synth stops right away. I need to stop and press play again to get the sound back. Bug on uhe synths or in Bitwig?
-
- addled muppet weed
- 105849 posts since 26 Jan, 2003 from through the looking glass
- u-he
- 28063 posts since 8 Aug, 2002 from Berlin
Might still be the same issue.keel wrote: ↑Wed Mar 13, 2019 3:10 pmHmm.. I am using only VST 2.4 plugins, so I don't knowUrs wrote: ↑Wed Mar 13, 2019 10:58 amIt's an issue with our VST3 versions IIRC. Apparently Steinberg and others have not implemented VST3 properly in this one aspect, so this bug never occurred to us. Bitwig is going to offer a workaround in the next update and we will continue to fix this with future updates.PS. I tested latest Bitwig 2.5 demo, and I found out that if I have uhe synths playing and then I open the synth, the sounds from the synth stops right away. I need to stop and press play again to get the sound back. Bug on uhe synths or in Bitwig?
-
neverbeeninariot neverbeeninariot https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=350084
- KVRian
- 912 posts since 3 Feb, 2015 from UK
It should, at least, be the name of the 2.0 default patch. : )
-
- KVRian
- 678 posts since 15 Feb, 2012 from France