u-he

mutantdog · Post by **mutantdog** » Sat Dec 01, 2018 1:37 pm

Is there a rough ETA on when v1.2 will be ready for release?

I seem to recall the original Hive beta being something a christmas present, is this looking like the case again?

Urs · Post by **Urs** » Sat Dec 01, 2018 3:06 pm

mutantdog wrote: Sat Dec 01, 2018 1:37 pm Is there a rough ETA on when v1.2 will be ready for release?

I seem to recall the original Hive beta being something a christmas present, is this looking like the case again?

We're working like mad on a mid December release. Kinda crazy atm with the spring reverb being brought to beta in parallel.

mutantdog · Post by **mutantdog** » Sat Dec 01, 2018 7:57 pm

You will be spoiling us for chrimbo then.

benmcc84 · Post by **benmcc84** » Sun Dec 02, 2018 12:58 pm

Hey Urs, did you manage to fix the voice handling issue where quantised chords that contained over 4 notes caused Hive to produce a weird flam sound rather than having all notes triggered on point?

EvilDragon · Post by **EvilDragon** » Sun Dec 02, 2018 1:07 pm

I just tried an 8 voice chord everything triggered on the grid, no flam whatsoever.

benmcc84 · Post by **benmcc84** » Sun Dec 02, 2018 1:34 pm

Great, thanks for checking!

AdvancedFollower · Post by **AdvancedFollower** » Mon Dec 10, 2018 8:21 am

Sorry if this has been asked before, but are there any plans for a "free flowing", shared LFO that isn't tempo synced?
It seems if you use "Single" mode, the phase of the LFO is free flowing as long as you hold at least one MIDI note, but restarts when notes are released. If you use "Sync" mode, the LFO is shared and free flowing, but this limits your rate options to time divisions (as expected).

Sometimes I just want to apply the same modulation to all voices, without tempo sync, but this doesn't work if the phase of the LFO keeps resetting when you release all notes. In fact, that makes the synth almost paraphonic, as the LFO feels more like a monophonic envelope generator than an LFO

I think the options should be split so you have separate independent switches for re-triggering, Shared/Polyphonic LFO's and Tempo Sync

Urs · Post by **Urs** » Mon Dec 10, 2018 8:51 am

AdvancedFollower wrote: Mon Dec 10, 2018 8:21 amIf you use "Sync" mode, the LFO is shared and free flowing, but this limits your rate options to time divisions (as expected).

Your expectation must have overridden your perception

You can still use tempo independent time bases in sync mode, e.g "1 sec". It takes the time passed since song start as reference rather than bars and measures.

tony10000 · Post by **tony10000** » Mon Dec 10, 2018 9:13 am

Urs wrote: Sat Dec 01, 2018 3:06 pm
mutantdog wrote: Sat Dec 01, 2018 1:37 pm Is there a rough ETA on when v1.2 will be ready for release?

I seem to recall the original Hive beta being something a christmas present, is this looking like the case again?
We're working like mad on a mid December release. Kinda crazy atm with the spring reverb being brought to beta in parallel.

Great news!

AdvancedFollower · Post by **AdvancedFollower** » Mon Dec 10, 2018 4:37 pm

Urs wrote: Mon Dec 10, 2018 8:51 am
AdvancedFollower wrote: Mon Dec 10, 2018 8:21 amIf you use "Sync" mode, the LFO is shared and free flowing, but this limits your rate options to time divisions (as expected).
Your expectation must have overridden your perception

You can still use tempo independent time bases in sync mode, e.g "1 sec". It takes the time passed since song start as reference rather than bars and measures.

Yeah, I guess I a$$umed the rate knob stopped having an effect when selecting sync and a time division, but it seems to work more like an offset than an actual rate control. A bit idiosyncratic but that works for me

Urs · Post by **Urs** » Mon Dec 10, 2018 5:01 pm

I might release this topic into the realm of standard topics, because Hive 1.2 is imminent...

viewtopic.php?f=31&t=516302

THE INTRANCER · Post by **THE INTRANCER** » Mon Dec 10, 2018 8:36 pm

Is it possible to have the older version installed and new the version installed in a new separate folder, just like another separate plugin ? Or are we tied to the single hive.dll and .data folder for everything related to Hive ? For example would renaming the Hive(x64).dll to Hive1(x64).dll and Hive.data to Hive.data1 allow that ? My guess is that if it was possible, one would need to reference
that within the script inside the .data folder.

In essence, allowing you to have two instances of different versions of Hive installed in the DAW you are running ?

Urs · Post by **Urs** » Mon Dec 10, 2018 9:35 pm

THE INTRANCER wrote: Mon Dec 10, 2018 8:36 pm Is it possible to have the older version installed and new the version installed in a new separate folder, just like another separate plugin ? Or are we tied to the single hive.dll and .data folder for everything related to Hive ? For example would renaming the Hive(x64).dll to Hive1(x64).dll and Hive.data to Hive.data1 allow that ? My guess is that if it was possible, one would need to reference
that within the script inside the .data folder.

In essence, allowing you to have two instances of different versions of Hive installed in the DAW you are running ?

I would highly recommend not to. If it's about the skin you did, you can put it in the themes folder and use it with the new version.

THE INTRANCER · Post by **THE INTRANCER** » Mon Dec 10, 2018 9:54 pm

Urs wrote: Mon Dec 10, 2018 9:35 pm
THE INTRANCER wrote: Mon Dec 10, 2018 8:36 pm Is it possible to have the older version installed and new the version installed in a new separate folder, just like another separate plugin ? Or are we tied to the single hive.dll and .data folder for everything related to Hive ? For example would renaming the Hive(x64).dll to Hive1(x64).dll and Hive.data to Hive.data1 allow that ? My guess is that if it was possible, one would need to reference
that within the script inside the .data folder.

In essence, allowing you to have two instances of different versions of Hive installed in the DAW you are running ?
I would highly recommend not to. If it's about the skin you did, you can put it in the themes folder and use it with the new version.

Yeah..., I thought I'd ask before I jumped into trying it, and seeing what you're view on it would be in whether it would be a safe and viable thing to do. The reason I asked was because there was many things I had changed colour wise in the script of the older version to make things more visible than they were previously. Light blue text wouldn't look right on an orange background for example. I figure I'll need to copy over the hexadecimal colour values from the script over to the new script to make it look right.

Also, I take that, it's only the original blue GUI which has been updated to accommodate the wavetable stuff and not also the Honeycomb as well ? It's the Honeycomb version in which the GUI mod I did is based from.

Cheers.

Funkybot's Evil Twin · Mon Dec 10, 2018 10:21 pm

Did you create your skin in the same location as the default theme? If so, you'll want to move that into the Support\Themes folder before you install the new one. I'd probably make a second backup somewhere else too.

Best practice for creating a U-he skin:

1. Start by creating a new folder for your skin in [plugin name].data\Support\Themes\[your skin name]
2. Copy over any relevant scripts from the default theme that you plan on using (make sure to keep the folder structure the same, so scripts go in Scripts, panes in Panes)
3. Copy over any .png's from the default theme you plan on modifying (you don't need to copy over stuff you're not changing)

That will ensure that you can update your U-he products going forward without breaking anything, and always switch back to the default skin as needed.

u-he

KVR Audio

Hive 1.1 latest build - revision 7485