Hive2 feature request thread

[claudedefaren]

...

[PieBerger]

Fwiw, ANA2 has wavetable FM and it doesn't seem to affect cpu that strongly

The interpolation in Hive's wavetable engine is much more resource intensive, which is why it sounds so good and is smooth enough to do convincing DX-style FM with UHM scripts. To retain the same fidelity at audio rate would increase CPU usage 50-fold or so I remember Urs saying, when I brought this same topic up a while back.

Edit: CPU usage in Serum isn't too bad when FMing two wavetables but it does sound harsh to me and the scanning in general isn't quite as good and as much as I like to combine wavetable and FM synthesis, I'd rather u-he didn't compromise on the quality of the wavetable engine to make it possible. This is why I'm more supportive of FM between the VA waveforms only, as a reasonably compromise

[Urs]

It can be done "okay-ish quality" with oversampling. That would still be about twice or more CPU.

[PieBerger]

It can be done "okay-ish quality" with oversampling. That would still be about twice or more CPU.

[Freaqpeak]

Personally, it would be enough to have FM possibilities for the standard oscillators.
I wish I could make cooler Uhm scripts though. My math skills are pathetic and I can't translate what I have in mind into the scripting language. Would not mind an offline-editor for making uhm files, instead of FM.

[recursive one]

Personally, it would be enough to have FM possibilities for the standard oscillators.

Standard waveforms, you mean?

Yes, that woulld be indeed enough for most of my FM uses.

Adam Szabo's Viper has great sounding FM/PM with different alogithms that can be used with classic VA oscillators and wavetables. I's not very CPU intensive and sounds absolutely awesome even at extreme settings. And it's just one knob I'd love to see something like that in Hive, this might be just one more knob in the osc section, e.g. using the subosc as the FM source for the main osc, which would restict the choice of the modulator waveforms and, I guess, make it easier to avoid various harsh sounding artifacts.

That's basically the kind of FM i want (the final sound at 4:14)

I understand, it must be possible to use just a wavetable but the interesting part is when you modulate the FM amount, e.g. transform a clean saw into the FMed sound.

[wilx]

Something Urs said in response to my zebra 3 request for more intuitive visual feedback reminded me of a request for hive:

It would be a huge benefit, and hopefully a very easy addition, to have one of the zones (maybe the default zone) in Hive's scope be 'last touched parameter' or even mouse-over parameter, tooltip style.
So if I mouse over or click on env1, that instantly shows up in the scope. This would save so much time & seems a pretty intuitive use of the (excellent) scope.

[Urs]

That's an interesting thought, but that would only make sense with modulated parameters? Otherwise it'll pretty much be just straight lines...

It's not trivial though because parameters like cutoff and anything pitch-related are often composed out of multiple distinct parameters and/or direct modulation paths - the question is then, what exactly do you visualise - the parameter or the compound value it contributes to? Which is why the most sensible visualisation for the filter seemed the little mini-scope we added in 2.0.

That said, visualising the outcome of the ModMatrix is high up on my list and, if I can pull this up, it will show the movement of the actual parameter that's modulated. That is, it won't show any direct modulation assignments such as pitchbend or key tracking.

[Alex_Longard]

Hello Urs,
add please tooltips for buttons and menus.
How it's work you can see in Tone2 plugins.
I find ctooltipsupport class in vstgui v3.6, and not know where this in vst3 framework which you use.

[wilx]

That's an interesting thought, but that would only make sense with modulated parameters? Otherwise it'll pretty much be just straight lines...

True, but lots of stuff like LFOs and Envelopes are useful to see even if they're not (yet) modulating or modulated. And a scope showing a straight line can still be useful to determine that something is inactive.

Which is why the most sensible visualisation for the filter seemed the little mini-scope we added in 2.0.

Yeah, I really like the scope as it is. I'd suggest the 'active/last touched parameter' as an extra option rather than a replacement.

[EvilDragon]

I find ctooltipsupport class in vstgui v3.6, and not know where this in vst3 framework which you use.

u-he uses their own homebrew UI framework.

[plugmon]

Now I heavily use wavetables in Hive and have 2 requests related to it.

(1)Browser for wavetables
Just like microtunings, it would be great if wavetable selector had a small popup browser -- There'd be some button like a folder icon next to dropdown triangle so that user can choose between menu(=close after selection) or browser(=stay open after selection).

(2)Wavetable information in h2p
Currently the information of which wavetables a preset is using seems to be stored as binary. So when I want to batch-change wavetable setting (e.g. when changing extension from .uhm to .wav), I have to edit each preset one by one. If it were stored as plain text, I can batch-replace using some text editor.

Not a big deal at all and I can live with what it is now, just wishes.

[Urs]

Now I heavily use wavetables in Hive and have 2 requests related to it.

(1)Browser for wavetables
Just like microtunings, it would be great if wavetable selector had a small popup browser -- There'd be some button like a folder icon next to dropdown triangle so that user can choose between menu(=close after selection) or browser(=stay open after selection).

I think we're a tiny bit reluctant here since our browser has become so big. We would like to avoid that people expect tagging and stuff... but yeah, a more comprehensive way to browse wavetables would be nice.

(2)Wavetable information in h2p
Currently the information of which wavetables a preset is using seems to be stored as binary. So when I want to batch-change wavetable setting (e.g. when changing extension from .uhm to .wav), I have to edit each preset one by one. If it were stored as plain text, I can batch-replace using some text editor.

That's almost certainly going to happen. We'll probably add some kind of "related files" section.

[plugmon]

(2)Wavetable information in h2p
Currently the information of which wavetables a preset is using seems to be stored as binary. So when I want to batch-change wavetable setting (e.g. when changing extension from .uhm to .wav), I have to edit each preset one by one. If it were stored as plain text, I can batch-replace using some text editor.

That's almost certainly going to happen. We'll probably add some kind of "related files" section.

That's nice to hear! And I understand about browser. On hearing that I instantly thought "oh, tagging for wavetables must be epic. I want that!". We cannot stop asking you for features

[wilx]

On visualisation and the scope - I've been playing around with a few synths recently, and Cypher 2 does a very similar thing to my suggestion. It shows the results of changes you make as you alter modulations - cleverly snaps to show whatever you're currently working on - including all the transMod sources.

Very intuitive. It also does 'modulation rings' in a very effective, non-distracting way similar to Equator 2, Alchemy, Serum etc. Vital does this quite well but it's a little too contrasty/obvious for my taste.

I think the new Equator 2 is probably the best balance of this - it's not flashy, but all of the visual stuff is implemented in a really sensible and practical way.