u-he Hive 1.2 - free update - adds wavetables and more

[AnX]

we do have to take into account a devs vision for a product

ive been as gulity as anyone asking for x and y in various things, only to be told it "doesnt match my vision" or such like

very frustrating for sure, but you cant always get what you want

(good phrase that, might use it in a song...)

[pdxindy]

I have two, 61 key keyboard synthesizers each with the same type of 16 step sequencers and I program them, but I can't chain them in serial to have 32 steps as I'd like.

Use a dedicated step sequencer plugin... there are options with 32, 64 and even 128 steps. Plus capabilities like importing midi files, live recording of your own playing, polyphony, etc.

Despite disagreeing with Intrancer's other feature request's, I quite like the idea of a second page for the step sequencer. It's one of my favourite part's on the synth and I do feel that increasing it's range would expand the synth's capabilities without comprising it's workflow or character.

You are welcome to like whatever idea you want. In a theoretical sense, it's fine with me... however I really don't want more tabs added to Hive. Actually, I want less tabs. If there were going to be the option of a 32 step sequencer, then please make it part of a GUI redesign that allows it on one page. A bigger section would also allow the 2 WT panes to be on one tab as well.

The workflow enhancement of the two WT panes visible at once, plus seeing all the Mod Matrix slots at once would be more useful to me than any of the feature additions people are making.

[PieBerger]

I have two, 61 key keyboard synthesizers each with the same type of 16 step sequencers and I program them, but I can't chain them in serial to have 32 steps as I'd like.

Use a dedicated step sequencer plugin... there are options with 32, 64 and even 128 steps. Plus capabilities like importing midi files, live recording of your own playing, polyphony, etc.

Despite disagreeing with Intrancer's other feature request's, I quite like the idea of a second page for the step sequencer. It's one of my favourite part's on the synth and I do feel that increasing it's range would expand the synth's capabilities without comprising it's workflow or character.

You are welcome to like whatever idea you want. In a theoretical sense, it's fine with me... however I really don't want more tabs added to Hive. Actually, I want less tabs. If there were going to be the option of a 32 step sequencer, then please make it part of a GUI redesign that allows it on one page. A bigger section would also allow the 2 WT panes to be on one tab as well.

The workflow enhancement of the two WT panes visible at once, plus seeing all the Mod Matrix slots at once would be more useful to me than any of the feature additions people are making.

It's not a biggy for me and I would be equally happy with your suggestion of a single page workflow, as part of a GUI overhaul. All slots on a single page definitely gets my vote though and I would take that over a 32 step sequencer.

[vurt]

we do have to take into account a devs vision for a product

ive been as gulity as anyone asking for x and y in various things, only to be told it "doesnt match my vision" or such like

yup, nothing wrong with offering suggestions.
its learning to take no as an answer, that some people seem to have a problem with

very frustrating for sure, but you cant always get what you want

(good phrase that, might use it in a song...)

i can hear it now...

its very
its very
its very
frustrating for sure!

frustration!
frustration!
frustration, like a runaway train!

or something like that

[THE INTRANCER]

It's not a biggy for me and I would be equally happy with your suggestion of a single page workflow, as part of a GUI overhaul. All slots on a single page definitely gets my vote though and I would take that over a 32 step sequencer.

You can't add a 32 step sequencer yourself as that's at a coding level, and as for an overhaul of the GUI, you can do that yourself if you have the skills and knowledge to do so. In that essence, a 32 step sequencer would be more valuable in a productivity sense. Having all modulation slots available if that's what your referring to would just add more clutter to the GUI. In fact I've gone so far in my own GUI redesign of Hive to hide it all.

Redesign still in progress.

[PieBerger]

It's not a biggy for me and I would be equally happy with your suggestion of a single page workflow, as part of a GUI overhaul. All slots on a single page definitely gets my vote though and I would take that over a 32 step sequencer.

You can't add a 32 step sequencer yourself as that's at a coding level, and as for an overhaul of the GUI, you can do that yourself if you have the skills and knowledge to do so.

I don't understand. I didn't say anywhere in the above that I had intentions of rewriting the code to allow for a 32 step sequencer nor any suggestion that I might redesign the GUI myself... I just offered my support to the suggestion of it being a single page workflow instead of an additional tab, as I suggested in myself. A redesign of the GUI, either by u-he or a third party, would be required in order to accommodate this.

[Teksonik]

just that requests to make synth A more like synth B isn't always the way to go.

People normally don't ask for features "just because" that feature is found in another synth. They make the request because they find the feature useful.

For example I'd love to see Hive get Dual Arps like Dune because I really like playing Arps at different speeds,directions etc.

I don't want Dual Arps because Dune has them (or luSH101 which has 8 arps etc) it's because I like the feature and can imagine sounds in my head that I could create with Hive.

I don't want any of my synths to sound the same as the others because what is the point if they all sound the same but there are some common features I simply like and wish all my synths had.

Whether the developer thinks those features are useful or silly is beyond my control......

[Teksonik]

we do have to take into account a devs vision for a product

ive been as gulity as anyone asking for x and y in various things, only to be told it "doesnt match my vision" or such like

very frustrating for sure, but you cant always get what you want

All we can do is make the request and hope it's added to a future update. If it doesn't fit the developer's vision then there's nothing we can do. Life sucks get a helmet.

I'm pretty confident that my vision for Hive would not match U-He's vision but they are driving the bus so I just go along for the ride.

But I will say that "visions" don't pay the bills so at least keeping an open mind to new features requested by customers and/or potential customers is probably not the worst business model.

For the record I'm not making any official feature requests for Hive but if something gets added then it's just butter on the lobster tail.........

[pdxindy]

For the record I'm not making any official feature requests for Hive but if something gets added then it's just butter on the lobster tail.........

And if the butter is rancid, that would not be considered a positive addition...

[Teksonik]

Yes but if you trust the Chef you know the butter will be perfectly drawn.....

[pdxindy]

Fortunately, I trust the chef not to add the rancid ingredients being asked for

[Urs]

I don't want Dual Arps because Dune has them (or luSH101 which has 8 arps etc) it's because I like the feature and can imagine sounds in my head that I could create with Hive.

What is a "Dual Arp"? Do you mean step sequencers?

[Urs]

On the topic of tabbing etc... (and also for those who are not following the thread about page-less synths)

Showing all ModMatrix slots at once would communicate "difficult synth" to many people - I won't risk it. I'm slowly but surely leaning towards a dual approach like in Serum. I always wanted to make mod sources draggable directly, to set up ModMatrix slots on the fly. Now that we have support for mouse over events in our UI, we could even start visualizing/editing connections dynamically, right where the knobs for the target parameters are ("depth-on-target").

The reason for keeping FX, WTs and Arp/Seq in the hexagon is the ModMatrix. If drag'n'drop assignments can only be initiated from the ModMatrix, it's a matter of convenience to keep FX and Arp/Seq out of the bottom tabs. With direct drag'n'drop from mod sources there's a chance to change this. But...

... this idea conflicts with the enhancements we're adding to the ModMatrix. The upcoming redesign will unintrusively but very conveniently show the modifiers (curve, rectify...) for each matrix slot, and it'll make editing very comfortable (i.e. no excessive right-click menu diving). My gut feeling tells me that this will become a feature one doesn't want to miss. But I can not see any way to make this happen in any visualization/edits of modulations "on target". We have a lot of thinking and testing to do to see how we feel about it and our vision for Hive.

Anyway, it remains to be seen if any concept of direct dragging from mod source and editing depth-on-target is viable, just like I'm not sure if and how to visualize actual modulation on target. It may never happen, but what do I know. The main cause for the aforementioned redesign is to make the UI more pleasant to look at, and integrate the hinted at buchlaesque "playful modulators" aka "gamification of complex sound design".

[tony10000]

I don't want Dual Arps because Dune has them (or luSH101 which has 8 arps etc) it's because I like the feature and can imagine sounds in my head that I could create with Hive.

What is a "Dual Arp"? Do you mean step sequencers?

From Dune 3's web page:

"Two arpeggiator units instead of just one greatly increase the sound design capabilities of DUNE 3. The Arpeggiators can be programmed independently and support both classic Up/Down arps, as well as playing back different sequences or even MIDI files. Furthermore, new features like the Random mode or programmable Arp Hold make the arpeggiator more powerful than ever before!"

So, they are combination arpeggiators and step sequencers with MIDI file loading capabilities.

[Urs]

I don't want Dual Arps because Dune has them (or luSH101 which has 8 arps etc) it's because I like the feature and can imagine sounds in my head that I could create with Hive.

What is a "Dual Arp"? Do you mean step sequencers?

From Dune 3's web page:

"Two arpeggiator units instead of just one greatly increase the sound design capabilities of DUNE 3. The Arpeggiators can be programmed independently and support both classic Up/Down arps, as well as playing back different sequences or even MIDI files. Furthermore, new features like the Random mode or programmable Arp Hold make the arpeggiator more powerful than ever before!"

So, they are combination arpeggiators and step sequencers with MIDI file loading capabilities.

The advantage of multiple independent layers: Dual Arps! The curse of multiple layers: Can't reuse/route stuff from one layer in another.

The advantage of non-independent layers: Economy, yay! The curse of non-independet layers: No Dual Arps.

We can have left side and right side in Hive play independent sequences/arpeggios only if we

- do not allow routing Osc1/VCF1 into VCF2 and vice versa
- do not allow ModEnv1 to be used in Osc2/VCF2 and vice versa
- and put similar restrictions on LFOs etc.

Obviously, if things can play at different tempo or with different keys, you need to separate them. But one of the greatest things about Hive is everything being freely routable. This is what allows Hive to be very flexible with very few parts.

I have some vague ideas for algorithmic pitching though, but I would not necessarily squeeze those into a second arpeggiator/sequencer pair.

That said, you can of course already play different notes on left and right side using the sequencer, arpeggiator or any other modulation source with the ModMatrix and its funky new quantization modes.