Hive 1.1 latest build - revision 7485

[robosax]

great ideas ! thanks guys

[Benjamin923]

Is the update going to come with some new presets showcasing the edgy sounds of the new features and waveforms? Very excited for this, Urs!

[Howard]

Sure

[spunkmuffin]

That audio example does sound edgy, angry even. Howard will you be making a Neuro EDM banger to show off the new presets?

[snigelx]

Never knew Hive would get this much of an update. What I'm reading back there sounds intriguing. Wavetable(-ish) functionality would be lovely addition. The synth is damn near perfect as-is with the exception of a couple not-completely-necessary things like dedicated LFO delay (could be due to me not being an advanced enough patcher to get the workaround but like I said, I'll get by). It's super quick and efficient to get a whopping variety of patches out of this thing to get work done. It's probably one of the most intuitive and efficient design tools I've run into for producing electronic music sounds. I've recommended it a couple times to folks IRL who were interested in starting to program. That said, of course I'll be waiting with bells on for any new functionality. If i find it to be overwhelm then I'll just continue using it the way I normally do. I've even started to use Hive much more often than Zebra2 and Diva because of lightning fast patching efficiency. It's just a well-thought out synth with some 'hidden' functionality gems that are not typically found elsewhere. (Also nearing completion on a 5-star review for it which I'll be putting up in a few days. This will be my first synth review, but I just love it that much.)

[Urs]

Hehe, thank you!

No worries, the new stuff will not clutter the interface in any way. The macro controls (4 x XY or 8 knobs with automatic setup for existing presets) will be more visible (one hexagon tab, one more bottom tab working same as ModMatrix) than the new waveform stuff (current plan: One hexagon tab per oscillator, available only when the waveform is set to the respective entry).

[snigelx]

Hehe, thank you!

No worries, the new stuff will not clutter the interface in any way. The macro controls (4 x XY or 8 knobs with automatic setup for existing presets) will be more visible (one hexagon tab, one more bottom tab working same as ModMatrix) than the new waveform stuff (current plan: One hexagon tab per oscillator, available only when the waveform is set to the respective entry).

Sounds perfectly -ignorable- if need be, Urs. ...And positively wonderful, if and when I need to get my distraction on. The clean engine has the linear ENV's if I recall correctly, but are you guys planning some other trickery for linear or break-point type modulators, besides LFO1 and 2 and the clean engine ENV's, for use with those wave(tables)?

[Urs]

I haven't implemented it yet, but I think there'll be a simple "auto-scan" function.

Atm I'm wrapping up the engine which let's one script the whole wave-thing. There are a couple of ideas I want to check out later, while parts of the team can work on waveforms.

That said, we'll soon focus on whether or not we'll have a vector thing in it, maybe at a later date. With it come the competing concepts of 2D-envelopes vs. the macro controls we have already added. But if we don't add the vector thing, we might have a chance to add multistage envelopes later - after the rewrite for Z3 is done. Those however might go against the concept of simplicity in Hive. Decisions, decisions ahead.

[EvilDragon]

I'd totally love it if we had a Custom engine in Hive, where we can mix&match elements from all 3 engines that are already there...

[snigelx]

I haven't implemented it yet, but I think there'll be a simple "auto-scan" function.

Ah. I think I grasp you. AND this plays nicely with Hive's "simplicity" (Less is More ancient principle) factor.

Atm I'm wrapping up the engine which let's one script the whole wave-thing. There are a couple of ideas I want to check out later, while parts of the team can work on waveforms.

I see, so this will be a 4th Engine so-to-speak. Intrigue is building, if I grasp what you are saying.

That said, we'll soon focus on whether or not we'll have a vector thing in it, maybe at a later date. With it come the competing concepts of 2D-envelopes vs. the macro controls we have already added.

I trust the vast patching experience you have, as a resource at U-he HQ, will be able to help decide the course of action to take.

But if we don't add the vector thing, we might have a chance to add multistage envelopes later - after the rewrite for Z3 is done. Those however might go against the concept of simplicity in Hive. Decisions, decisions ahead.

I leave you with a thought. There is something very ancient that 'seems' to be lost of us in modern times. That is the value of simplicity. To be more complex, simplicity is not all that "simple" of a principle. In this case, and many others, it begets efficiency. There is a sensitive balance b/t what is simple and what is complex. The thought I leave you with is this. What is the purpose of this synthesizer. Is it a tool of experimentation or is it a tool for music producing. If memory serves, "Zebra" is the laboratory of all these tools. At any rate, as I stated earlier, in my stupid humble opinion (despite my innre nagging endless desire for more, which i often try to stifle), the Hive synthesizer is one of the best BALANCED synths on the market (esp. if people will familiarize themselves with the user manual and (yes) videos available). With that I say very best wishes with whatever course the team and yourself decide to take. I am very excited for the future, no matter what form it takes.

Edit: I should add that I meant simplicity as it relates to moderation.

[snigelx]

I'd totally love it if we had a Custom engine in Hive, where we can mix&match elements from all 3 engines that are already there...

U-he has a synth that fit that bill already, no? In Zebra2 you can twist and patch all kinds of filters and envs and general architecture in "new" or "uncommon" ways. Also that jurassic beast of a synth DIVA allows one to mix match Magical modules... just wonderful things happen. Hive is more a get-work-done-swiss-army-knife type of synth. But if that was easy for U-he to implement then sure thing. Just tuck it away somewhere and put a lock on it so I can't get in.. HA

Would be kinda funny to have features 'available' or 'unlocked' only after a certain criteria were met, such as a certain number of user patches using 'certain' combinations of modules were saved... (the actual successful implementation of which would be nigh on impossible however)

[Urs]

I see, so this will be a 4th Engine so-to-speak. Intrigue is building, if I grasp what you are saying.

Oopsie, sorry, no... ambiguous wording.

I wasn't talking about the three synth engines in Hive - I was talking about finalising the scripting engine I mentioned before. It's a means to create new waveforms beyond just loading a .wav file. It uses a formula parser much like the one in Serum, but it adds script-based editing capability to it.

I have previously also talked about an exciting innovation which might consume too much CPU. The scripting engine makes use of that innovation and "bakes" its effect into the sound. It therefore is a vehicle to make that innovation usable in Hive, without taking up any further CPU. Again, this is all hidden from Hive's user interface. Those people who wish to deal with it (sound designers...) can do so, and it will be well documented.

But yes, I totally get the concept of simplicity.

[snigelx]

I see, so this will be a 4th Engine so-to-speak. Intrigue is building, if I grasp what you are saying.

Oopsie, sorry, no... ambiguous wording. I wasn't talking about the three synth engines in Hive - I was talking about finalising the scripting engine I mentioned before.

Got it. Thx for the clarification.

It's a means to create new waveforms beyond just loading a .wav file. It uses a formula parser much like the one in Serum, but it adds script-based editing capability to it.

Intriguing. I can maintain my general lack of desire to demo Serum in this case.

I have previously also talked about an exciting innovation which might consume too much CPU. The scripting engine makes use of that innovation and "bakes" its effect into the sound. It therefore is a vehicle to make that innovation usable in Hive, without taking up any further CPU. Again,

THAT was a major concern for me right there. Thanks for mentioning that. I must admit I do most of my work still using 32-bit architecture on a 'music' laptop running a 2.5ghz processor. I get by, as it is... even with Repro (but that is the limit I can painfully see, and only if I do massive amounts of bouncing)

this is all hidden from Hive's user interface. Those people who wish to deal with it (sound designers...) can do so, and it will be well documented. But yes, I totally get the concept of simplicity.

Oh don't get me wrong... I'm also very much a sound designer/and general tinker-er... but I got this beautifully weird vintage modular Zebra thing, which is happily grazing on the sidelines for the moment, for heavy sound design. Like I say, in the end I'm excited for whatever you guys add. I've good faith in your quality implementations. in my coming review I state that it's not necessarily that some of these features are exclusive to Hive (some ARE), yet it is the WAY they are implemented that makes Hive "special". So I trust ya

[Urs]

Ok, probably the most unexpected thing you've heard all day, but I had some fun dabbling with DX-style FM Synthesis while testing the script engine.

https://www.u-he.com/Urs/HiveDXPiano.mp3

[Delta Sign]

That's indeed unexpected, but it sounds very sexy