Hive 1.2 - free update - adds wavetables and more

Official support for: u-he.com
Post Reply New Topic
RELATED
PRODUCTS
Hive 2$169.00Buy

Post

cytospur wrote: Fri Dec 21, 2018 10:03 pm What? She never stops! :hihi:
Boy you're telling me........ :phew: :P
None are so hopelessly enslaved as those who falsely believe they are free. Johann Wolfgang von Goethe

Post

Wow.........

Post

Just wanted to stop by and say thank you for the update. It's awesome!

Post

Finally had a chance to listen to Hive's update and holy cow! between the wavetables and the X/Y parameters, that's two major and long-requested features in one update! Hive's palette is muuuuch bigger now and can now totally handle those grimy digital styles like Dubstep. I can't wait to use it on my next track :D.

Post

It seems that manual XY assignment section (that the beta version had) was removed in this 1.2 stable ver.
Were there some serious problems and had to be removed, or you just concluded that the automatic/selectable XY fits more for HIVE's concept than to complicate UI with many knobs?

I mean, is it alright to re-add those manual assignments by customizing skins?
ImageMONA, the new skin for DIVA is released! | Follow me on Twitter.

Post

plugmon wrote: Mon Dec 24, 2018 5:06 amWere there some serious problems and had to be removed, or you just concluded that the automatic/selectable XY fits more for HIVE's concept than to complicate UI with many knobs?
I think it's the latter. Still, I'd love to see it added officially. Could be a button tucked away in the XY hexagon rather than sharing the tabs with keyboard/mod matrix...

Post

plugmon wrote: Mon Dec 24, 2018 5:06 am It seems that manual XY assignment section (that the beta version had) was removed in this 1.2 stable ver.
Were there some serious problems and had to be removed, or you just concluded that the automatic/selectable XY fits more for HIVE's concept than to complicate UI with many knobs?

I mean, is it alright to re-add those manual assignments by customizing skins?
It's two things:

We want to see how far we get with automatic assignments and the options available. We want to hear criticism/suggestions etc. to see if we can improve upon this "most comfortable" way. That's ebcause experience (Zebra2) tells us that people commonly can't be bothered setting up XYs, but they still like them when they're there.

Then, we have worked on a new layer selection method where the XYs/WTs would only be visible with the appropriate settings and pages. This has been deployed in the upcomming redesign. It should bring the custom assignments back, but it won't be in the user's face, i.e. fitting Hive's concept better.

Post

Urs,
Yep, that is me. I have rarely set up the XYs on my own, but they can come in handy when they are there.
You can hear my original music at this link: https://www.soundclick.com/artist/defau ... dID=224436

Post

Perhaps 4 always-available-on-the-GUI "macro knobs" could be a better way to do the same thing, while making it more user friendly. For instance, unless your in the perform page in Zebra2, or one of the XY pages, you may not even notice the X/Y's functionality. Same for Hive. It's in a tab in the Hexagon so it's not always available. Meanwhile, you've got some space to add macro knobs above the keys and below the ADSR's for example.

And really, the X/Y controls are simply standard MIDI CC's routed to macro knobs, just presented in an X/Y manner. This has some novelty if you're using a mouse or some kind of touch screen, but it also eats up more screen real estate and I doubt most of us have any kind of X/Y touch contoller we use with regularity. 4 macro knobs do the same things 2 X/Y's do in a fraction of the real estate. Plus when it comes to MIDI learn, having knobs on screen just increases the likelihood the X/Y's will get mapped. In Zebra2, I tend to not use the actual X/Y's and use the knobs instead because they're easier to fine tune and center, and not move two parameters at once when I'm only trying to change one. Using the X/Y's like that with a mouse is much clumsier experience.

So I realize it's kind of a semantic argument, since X/Y's are macro controllers, but maybe changing how they're displayed would have some benefit when it comes to adoption of the feature.

Post

Funkybot's Evil Twin wrote: Mon Dec 24, 2018 11:03 pm Perhaps 4 always-available-on-the-GUI "macro knobs" could be a better way to do the same thing, while making it more user friendly. For instance, unless your in the perform page in Zebra2, or one of the XY pages, you may not even notice the X/Y's functionality. Same for Hive. It's in a tab in the Hexagon so it's not always available. Meanwhile, you've got some space to add macro knobs above the keys and below the ADSR's for example.

And really, the X/Y controls are simply standard MIDI CC's routed to macro knobs, just presented in an X/Y manner. This has some novelty if you're using a mouse or some kind of touch screen, but it also eats up more screen real estate and I doubt most of us have any kind of X/Y touch contoller we use with regularity. 4 macro knobs do the same things 2 X/Y's do in a fraction of the real estate. Plus when it comes to MIDI learn, having knobs on screen just increases the likelihood the X/Y's will get mapped. In Zebra2, I tend to not use the actual X/Y's and use the knobs instead because they're easier to fine tune and center, and not move two parameters at once when I'm only trying to change one. Using the X/Y's like that with a mouse is much clumsier experience.

So I realize it's kind of a semantic argument, since X/Y's are macro controllers, but maybe changing how they're displayed would have some benefit when it comes to adoption of the feature.
Just use 4 macro knobs just like Serum and Spire do. That should be easy and provide quick access and functionality, especially if you can map more than one function to each knob.

Post

We're experimenting with macro knobs on the preset browser page, like I think Massive and FM-8 do.

Post

8 macro knobs would of course be better than 4, due to NKS - but 4 XY pads do exactly the same thing. 4 knobs is definitely not enough IMHO.

Post

XY: good for mouse
knobs: good for controllers

Post

Yep, but as long as you can assign X and Y to whatever CC it's all the same. And that's very much possible in your plugins, so both sides are satisfied :)


Merry Xmas, Urs - and to the rest of the crew!

Post

I'm not sure I follow you guys. Are you trying to implement macro-knobs as new kind of UI entities with their own modulation targets that would have to be assigned separately?

Post Reply

Return to “u-he”