Hive Wavetable starter pack

[Elektronisch]

Because as previously stated, Hive does sound different in FL then in other DAWs in certain case

Yes, we know. And we have tried to figure out what's causing this, but if a developer can not find the cause in two weeks, he might not find it in a year. This is where we have to compromise and say "ok, there's a bug, there's a workaround, we need to let it go for the time being until we can revisit it again, maybe for next update".

Ah ok, figures, i have been reminding those problems with Hive from time to time in IL forum

[surreal]

how do we load single cycle waveforms into Hive and how dow we load Galbanum and Adventurekids wavetables into Hive? Cant we just load User Zebra Osc into Hive?

[surreal]

Urs?

[EvilDragon]

You cannot load Zebra oscillators into Hive, they're not compatible.

Single-cycle waveforms work just fine. Load them like any other WAV file. In Hive.data folder you have a new folder called Wavetables, place your single-cycles here and off you go.

[hakey]

how do we load single cycle waveforms into Hive

Stick them in: u-he/Hive.data/Waveforms

I put mine in a sub folder marked User within Waveforms.

Not overly impressed with the AKS stuff - there's an awful lot there, but it's very mixed.

[AnX]

Because as previously stated, Hive does sound different in FL then in other DAWs in certain case

Yes, we know. And we have tried to figure out what's causing this, but if a developer can not find the cause in two weeks, he might not find it in a year. This is where we have to compromise and say "ok, there's a bug, there's a workaround, we need to let it go for the time being until we can revisit it again, maybe for next update".

is it a Fruity bug or a uhe bug?

[Urs]

is it a Fruity bug or a uhe bug?

Probably ours. Just not traceable. A crash would be easy to find, some random synchronisation issue, not so much.

[tony10000]

Because as previously stated, Hive does sound different in FL then in other DAWs in certain case

Yes, we know. And we have tried to figure out what's causing this, but if a developer can not find the cause in two weeks, he might not find it in a year. This is where we have to compromise and say "ok, there's a bug, there's a workaround, we need to let it go for the time being until we can revisit it again, maybe for next update".

Is that related to this issue?

https://forum.image-line.com/viewtopic.php?t=162496

Just as an FYI, FL has problems with certain plugins and changing to “fixed sized buffers” usually fixes it.

See:

viewtopic.php?t=490542