Hive 2.X Feature Requests

[EvilDragon]

Good example there with filter cutoff. In Surge, it's also in semitones, internally stored as offset from middle A, MIDI note 69. But we do display it in Hz (and show the nearest 12-TET note value alongside.



(We also support octave offsets to resolve the eternal C3/C4/C5 is middle C debate. )

And yep, I'm fully aware that the mode-scaled parameters (LFO timebase, etc) are a problem in the u-he framework for this sort of feature. That's definitely a tricky matter to resolve.

Thanks for detailed writeup on the rest, though! I really appreciate it. I'd say that just having real-world units display would be a great start. Text input is an eventual bonus but not a must, as far as I'm concerned (although it certainly benefits the user).

(BTW, when you say "it might take a while", which timescale are we talking about? Less or more than one idle() loop cycle?)

[Urs]

I think you should also show the actual linear numerical value like we do.

[Urs]

"it might take a while"

Development time. Designing a concept that works. Removing competing attempts from previous developers. Not breaking anything. Adding the new concept to hundreds if not thousands of parameter descriptions in the DSP part, including sometimes having to measure the actual values.

Years, really.

[EvilDragon]

Ah, dev time, not execution time in the codebase (doh, haha!). Noted.

I think you should also show the actual linear numerical value like we do.

Ha, we'll see. Maybe just the MIDI note number, yeah. But then, some parameters have wider range than the MIDI note number range, including going down to 0.5 Hz in a comb filter based effect (which is roughly C negative 6 octave, if C3 is middle C )! I feel this might confuse the user rather than actually help.

[Urs]

Exceeding the realm of MIDI Note Numbers has never been an issue for me. Some of our filter cutoffs go to 150 or so.

[EvilDragon]

Yeah true, I don't have a problem with >127, but with <0 Weird, I know.

[Urs]

Just do it!