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

[fmr]

And now I can't even open the script anymore. Hive doesn't recognize it, although it is there.

It was created with "Wordpad" (using TXT format), and was working before

I tested to create a duplicate of the example "Morph Two Waves" and it worked

[Urs]

Interpolate start=0 end=255 Type=Morph1

The scripting engine itself is dumb. It doesn't keep track of your intentions.

You need to interpolate between each segment, like this:

Interpolate start=0 end=21 Type=Morph1
Interpolate start=21 end=40 Type=Morph1
... and so on

[Urs]

And now I can't even open the script anymore. Hive doesn't recognize it, although it is there.

It was created with "Wordpad" (using TXT format), and was working before

I tested to create a duplicate of the example "Morph Two Waves" and it worked

That's a last minute bug we missed - when the script can't be parsed, it'll post the "can't find..." message. When you click ok it should have more detail (e.g. line number of the error) in the info field.

Hope to fix this soon

[fmr]

And now I can't even open the script anymore. Hive doesn't recognize it, although it is there.

It was created with "Wordpad" (using TXT format), and was working before

I tested to create a duplicate of the example "Morph Two Waves" and it worked

That's a last minute bug we missed - when the script can't be parsed, it'll post the "can't find..." message. When you click ok it should have more detail (e.g. line number of the error) in the info field.

Hope to fix this soon

Thanks Urs. I located the mistake already (it was a dumb instruction I wrote, to try to make the script work . But I think that a more detailed error message will help a lot, indeed.

[fmr]

Interpolate start=0 end=255 Type=Morph1

The scripting engine itself is dumb. It doesn't keep track of your intentions.

You need to interpolate between each segment, like this:

Interpolate start=0 end=21 Type=Morph1
Interpolate start=21 end=40 Type=Morph1
... and so on

OK, Now I think I got it.

Another thing. It seems that, for Hive to recognize the different waves inside a wavetable, we have to insert silence between each wave. The first wavetable I created (the one I uploaded) doesn't have that silence, and Hive doesn't seem to be able to extract individual waves from it. I created another wavetable with silence between each wave (I expanded it from the original 14 gframes to 28 frames), and now Hive can correctly locate each wave.

[Urs]

Someone on Facebook wrote the other day, paraphrasing: "Serum eats them all for breakfast", meaning Hive and other synths. I answered "not in terms of wavetable interpolation quality, CPU usage, workflow, preset management, formula parsing, modulation routing".They are different synths. Hive doesn't do this, Serum doesn't do that.

Now I´m curious - which would be an area where you´d call Serum either "currently better than Hive, we need to improve on this" or "well done in Serum, but not a feature we want to add/expand upon"?

Serum has an excellent editor, loads of filter types, a lot of modulation feedback and very nice LFO shaping tools. Neither of which we find to be a "must have" for Hive.

We will figure out *some* modulation feedback sooner or later, but the editors in particular, as good as they are, would contradict our claim that Hive is a streamlined synth aka "less is more".

The real question is, from what point does complex modulation become so arbitrary that the means to get there become arbitrary as well? From what point does it not matter anymore whether a curve has been sculpted by sophisticated tools, or a randomizer? Likewise, how much of a crazy modulation pattern has been consciously envisioned by the sound designer and how much was just "a bit of drawing here and let's try that slope there"? - I recommend watching a few sound design videos on Youtube. There's interesting conclusions to be had, even if they will always be ambiguous.

These questions are complementary to our original concept for Hive, from whence we wanted to see how much we can leave away - but still be able to recreate all common sounds. There wasn't any factory sound in Sylenth1 (4 oscillators, two pages) which we couldn't almost identically do in Hive (2 oscillators + 2 subs, one page).

So my interest fro Hive's future is to create an extremely minimal set of controls which let you achieve the same complexity, density and broad palette of sounds that e.g. Serum excells at, without the need to spend hours in sophisticated editors. The results don't need to be exactly the same, so long as they're equally as useful, musical and interesting.

[Urs]

Interpolate start=0 end=255 Type=Morph1

The scripting engine itself is dumb. It doesn't keep track of your intentions.

You need to interpolate between each segment, like this:

Interpolate start=0 end=21 Type=Morph1
Interpolate start=21 end=40 Type=Morph1
... and so on

OK, Now I think I got it.

Another thing. It seems that, for Hive to recognize the different waves inside a wavetable, we have to insert silence between each wave. The first wavetable I created (the one I uploaded) doesn't have that silence, and Hive doesn't seem to be able to extract individual waves from it. I created another wavetable with silence between each wave (I expanded it from the original 14 gframes to 28 frames), and now Hive can correctly locate each wave.

I would have to look at this (but won't be able to before end of next week). Is it by chance a wavetable which has less than 2048 samples per cycle? - In that case you still need to add -WT256 whtsoever to its name.

[fmr]

I would have to look at this (but won't be able to before end of next week). Is it by chance a wavetable which has less than 2048 samples per cycle? - In that case you still need to add -WT256 whtsoever to its name.

No, it was created in Serum, with 2048 samples per cycle. Anyway, I will perform more tests, now that I understood the script mechanics.

Another thing, for you to check when you have the chance. Hive doesn't export the WAV wavetables in the correct format. If I load them directly in Serum, I get very strange results.

For them to work, I have to perform an "Import" function in Serum, using the "via fixed frame size" option. I select 2048 frame size, and then Serum correctly reads the wavetable. I don't understand why does this happen, because Serum should be able to read the wavetable directly, right?

[Urs]

For them to work, I have to perform an "Import" function in Serum, using the "via fixed frame size" option. I select 2048 frame size, and then Serum correctly reads the wavetable. I don't understand why does this happen, because Serum should be able to read the wavetable directly, right?

A wavetable saved be Serum contains a special chunk which apparently includes some kind of identification scheme.

We don't (can't?) write this into the files, so you need to import instead, or add a text file (see Serum manual).

Do wavetables exported from something else "just load" in Serum?

[fmr]

A wavetable saved be Serum contains a special chunk which apparently includes some kind of identification scheme.

We don't (can't?) write this into the files, so you need to import instead, or add a text file (see Serum manual).

Do wavetables exported from something else "just load" in Serum?

The wavetables created in Audio-Term using the Serum format "just load" directly in Serum. I don't have to do anything. I will test with Icarus.

[THE INTRANCER]

When I saw wavetables being introduced into Hive, I had expected that it would simply be a case of drag and drop of a wave file onto the hex display... Simple and straight forward..the way Hive is supposed to be.

[pdxindy]

Interpolate start=0 end=255 Type=Morph1

The scripting engine itself is dumb. It doesn't keep track of your intentions.

You need to interpolate between each segment, like this:

Interpolate start=0 end=21 Type=Morph1
Interpolate start=21 end=40 Type=Morph1
... and so on

OK, Now I think I got it.

Another thing. It seems that, for Hive to recognize the different waves inside a wavetable, we have to insert silence between each wave. The first wavetable I created (the one I uploaded) doesn't have that silence, and Hive doesn't seem to be able to extract individual waves from it. I created another wavetable with silence between each wave (I expanded it from the original 14 gframes to 28 frames), and now Hive can correctly locate each wave.

With your wavetable of 14 frames... you were calling them 1-14... I think it should be 0-13

[fmr]

With your wavetable of 14 frames... you were calling them 1-14... I think it should be 0-13

Hmm... Maybe you're right. Will test that (although I managed to get the script to work with the new wavetable created with the inserted silent waves). Thanks

EDIT: And you nailed it absolutely right. It was the numbering that was causing the problem. Now, the mystery is solved, and I can use any wavetable to extract the waveforms, without any other editing. Once again, thanks

[knowix]

When I saw wavetables being introduced into Hive, I had expected that it would simply be a case of drag and drop of a wave file onto the hex display... Simple and straight forward..the way Hive is supposed to be.

Except is that actually straightforward? How was the wavetable generated in the first place?

[Funkybot's Evil Twin]

I came across a bunch of waveedit wavetables, all are 256 sample waves with 64 frames per table. Thinking about going through the effort of converting these via the script thinking that after I did it once, it's very easy to just change the name of the import file, and use find and replace to change the interpolation modes for the remaining wavetables.

I'm assuming the benefit of doing it this way is smoother interpolation as 64 frames essentially become 256 frames. Figure it will be a good, but highly tedious, way to dip my toes in.