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?
It looks similar, but I think it's a different concept.yellowmix wrote: Wed Mar 13, 2019 5:41 am Exciting! The shape sequencer looks like the "Flow LFO"s in Biotek. However, those in Biotek are performance controls and being able to sequence them in Hive 2 brings it to another level!
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.![]()
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.![]()
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.keel wrote: Wed Mar 13, 2019 10:24 am 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
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?![]()
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.keel wrote: Wed Mar 13, 2019 10:24 am 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
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?![]()
OH THE IRONY!Urs wrote: Wed Mar 13, 2019 10:58 amApparently Steinberg and others have not implemented VST3 properly in this one aspect
I'm just repeat what I get from some other dev who explained the issue to meEvilDragon wrote: Wed Mar 13, 2019 12:59 pmOH THE IRONY!Urs wrote: Wed Mar 13, 2019 10:58 amApparently Steinberg and others have not implemented VST3 properly in this one aspect![]()
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?![]()
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?![]()
![]()
It should, at least, be the name of the 2.0 default patch. : )
Submit: News, Plugins, Hosts & Apps | Advertise @ KVR | Developer Account | About KVR / Contact Us | Privacy Statement
© KVR Audio, Inc. 2000-2026