Tech Preview: Hive Wavetables

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

Post

Soooooo, first wave is a start cycle. next wave is the end cycle. you build a table using various algorithms, and then... "multiwaves."

lets talk about this. I'm assuming it splits your "table" into smaller sections that are stacked? It's mentioned that it's for the purposes of applying different velocities and what have you. It sounds pretty damn good. Took me seconds to find a timbre I wanted to play, although I'm getting a lot of artifacts (I'm assuming you know this). It really captures that early 90's vibe but, how do I address the layered sections? how do I go about assigning a seperate velocity to the 2nd "multiwave" for instance?

Post

oh, wait a minute. That must be happening in your little script. I see. It just hit me.

Post

Think of it as a 2D grid, it makes it easier to understand.

The wavetable position is the X axis, while the MultiTable position is the Y axis. So, if you have a Wavetable of 256 frames, and set the MultiTable count to 16, you'll get a 2D "grid" of 16*16 frames.
Now you can use the mod matrix to modulate the wavetable and MultiTable position however you want. You can also use the auto sweep feature to modulate the wavetable position in various ways, which can be quite handy.

Here is a somewhat convoluted script I wrote that basically generates a simple 2OP FM table where the wavetable position controls the FM index and the MultiTable position blends between different FM ratios:

Code: Select all

Info "A simple 2OP FM wavetable with independent controls for index and ratio. Set the MultiTable count to 4. Wavetable position controls the index and MultiTable position controls the ratio."

NumFrames=256

Wave start=0 end=63 "sin(2*pi*(phase+(sin(2*pi*phase)*(frame/16))))"
Wave start=64 end=127 "sin(2*pi*(phase+(sin(4*pi*phase)*((frame-64)/16))))"
Wave start=128 end=191 "sin(2*pi*(phase+(sin(8*pi*phase)*((frame-128)/16))))"
Wave start=192 end=255 "sin(2*pi*(phase+(sin(16*pi*phase)*((frame-192)/16))))"

Normalize base=each
Here is the script in action:
https://soundcloud.com/deltasign/hive-wavetable-test-06

During all of my extensive testing importing various samples, making wavetables and writing scripts, I have not encountered any unwanted artifacts, by the way. "Bad" wavetables won't behave well, of course.

Post

Well. I was just using the multi table function on example waves that came with the download, that would pop when they hit a start/end point. I was probably doing it wrong though. I'll play around with it some more. I don't know what I'm doing with these multiwaves yet.



EDIT: the options for these modulations are in the x/y section that you have to open up if anybody else has the same questions.

Post

All I want to know is if when this goes final it'll be a paid update or not.

(I hope not... please? :pray: I'm currently out of work so have lots of free time but not much money until that's resolved)

Post

longbongsilver wrote:All I want to know is if when this goes final it'll be a paid update or not.

(I hope not... please? :pray: I'm currently out of work so have lots of free time but not much money until that's resolved)
I'm guessing it's a Repro 5 style update: current customers are grandfathered in while Hive gets a price bump.

Post

I don't think there ever was a paid U-He update, if I remember correctly. I obviously don't know, but I strongly suspect this update will be free as well :)

Is it time to bombard U-He with feature requests yet, by the way? :hihi:
After messing around with Hive so much the last few days, there are two things I'd absolutely love to see in a possible future update:
  • A source selector similar to the ones on the filters, but after the filters.
  • New "filter" types. I'm not talking about more lowpass filters etc., but stuff like maybe a ring modulator, a decimator and, probably most importantly, a comb filter, because wavetables + comb filter = awesomeness.

Post

longbongsilver wrote:All I want to know is if when this goes final it'll be a paid update or not.

(I hope not... please? :pray: I'm currently out of work so have lots of free time but not much money until that's resolved)
Generally with u-he, if an update would be paid, it would have been mentioned already. My guess, and it is only a guess, is that it will be a free update.

Post

zvenx wrote:I think the new preset browser is incompatible with aliases and shortcuts.
I think it's because we switched from difficult-to-maintain code which was platform specific and full of hacks, to easy-to-maintain standard code which "just works" (Boost Filesystem, IRC). Unfortunately, it doesn't know anything about Shortcuts and Aliases, it only knows SymLinks - which I assume are a crossplatform standard as well!

Post

Sound Author wrote:Any chance of a "waterfall" waveform view in the foreseeable future?

Not at all a necessity. But it's just so fun to look at. :)
I don't really want to raise the impression that Hive is meant to be our new Serum. It isn't.

I am however contemplating to build flat spectrum/waterfall functionality right into the UI element which displays the waveform. It's tricky though, there might be too much jitter between the time bases, and I really don't want to stuff the data processing into the DSP part.

(looks like I have a thing for technical explanations this morning)

Post

Delta Sign wrote:I don't think there ever was a paid U-He update, if I remember correctly. I obviously don't know, but I strongly suspect this update will be free as well :)

Is it time to bombard U-He with feature requests yet, by the way? :hihi:
After messing around with Hive so much the last few days, there are two things I'd absolutely love to see in a possible future update:
  • A source selector similar to the ones on the filters, but after the filters.
  • New "filter" types. I'm not talking about more lowpass filters etc., but stuff like maybe a ring modulator, a decimator and, probably most importantly, a comb filter, because wavetables + comb filter = awesomeness.
Hehehe, bit early, really, but okay. (My stance: Do things step by step... turn this current functionality into Hive 1.2, see how it goes, then pick the most obvious improvement and add it in 1.3... if we do all at once)

What do you mean by "source selector ... after the filters"? A way to get the dry signal past the filters like Serum does? I'm not 100% sure that's necessary since Hive has 2 filters, and if you bypass one, the other one is still good to go, whereas Serum has just one filter, making this option a bit of a welcome goodie.

- U

Post

equinoxide wrote:
longbongsilver wrote:All I want to know is if when this goes final it'll be a paid update or not.

(I hope not... please? :pray: I'm currently out of work so have lots of free time but not much money until that's resolved)
I'm guessing it's a Repro 5 style update: current customers are grandfathered in while Hive gets a price bump.
My guess, too!

Post

Dasheesh wrote:"multiwaves."

lets talk about this. I'm assuming it splits your "table" into smaller sections that are stacked?
Let's get visual:

Here's a wavetable with 9 frames:

Code: Select all

[0] [1] [2] [3] [4] [5] [6] [7] [8] 
<-----------Wt Position----------->
The Wavetable Position parameter, going from 0-100, lets you scan through all frames from 0 to 8.

Now, let's set the number of MultiTables to 3 for the same Wavetable, and this happens:

Code: Select all

[0] [1] [2]     ^
[3] [4] [5] Multi Pos
[6] [7] [8]     v
<-Wt Pos-->
You get a stack of 3 x 3 tables. Now the Wavetable Position scans only 3 frames from left to right (columns). MultiTable Position scans in the second dimension (rows). So what you hear is a mix of up to 4 frames.

A few example settings for this 3x3 configuration:

WTPos=50, Multi=50: Frame 4
WTPos=25, Multi=100: 50% frame 6 + 50% frame 7
WTPos=75, Multi=25: 25% each of 1,2,4 and 5

Now, a wavetable with 4 frames, Multi set to 2 would give you 4 waveforms you can seamlessly crossfade, where the individual percentages sum up to 100%. Sounds familiar? This is essentially Vector Synthesis. But because we are also adding Macro Controls to Hive, we are tyring to avoid using typical Vector Synthesis terminology such as X-axis and Y-axis. This would cause confusion with the Macro pages.

(Ok, the Prophet VS had individual tuning for each waveform and this isn't the case here, but then Hive has multiple oscillators etc. to make up for that)

Post

pdxindy wrote:Playing around with the wavetables and tried a couple of the uhm scripts in the KS thread (thanks for those!)
Which thread is that?

EDIT: Forget it. I found it. It's the Karplus-Strong thread :) :tu:
Last edited by fmr on Tue Sep 18, 2018 10:40 am, edited 1 time in total.
Fernando (FMR)

Post


Post Reply

Return to “u-he”