Hive 1.2.1 maintenance update RC rev. 8256

[Urs]

It's a bit weird, I will install Hive on another computer and see if the same thing happens.
Anyways, I have started a support case via the U-he support webform instead. I really should stop hijacking threads like this.

This is the right place! We need to know if we can release it, but any suspicion that we can't needs to be looked into.

[drzhnn]

Did you guys change something in how path separator symbol works, when using Import command in UHM? Before this version I was able to use both "\" and "/" separators. But now only "/" works.

I'm on Windows.

[Urs]

Did you guys change something in how path separator symbol works, when using Import command in UHM? Before this version I was able to use both "\" and "/" separators. But now only "/" works.

Shouldn't have changed, it should always have been just / since the official 1.2.0

\ got really problematic as it was swallowed on Mac/Linux.

[Urs]

Oh, actually...

maybe yes

\ is now used for escape sequences \" \' \n \t when formatting info stuff... hence probably also unescaped in file paths...

[drzhnn]

Hive_120_8115_Win - "\" works.
Hive_121_RC_8256_Win - "\" doesn't work.

Not complaining, just reporting

[Urs]

Yes, that's very likely the fix for "no apostrophe in Info text". I added escaping to the parser.

Try \\ and see how it goes. I might have made the escape character escapable

[drzhnn]

Checked. "\\" works fine here. But I'll probably stick with the "/", just in case

[Urs]

But I'll probably stick with the "/", just in case

Please do

[Funkybot's Evil Twin]

I'm using the VST2 in Cubase10.0.10 in Windows 10 and every now and then (seems pretty random) if I've got the WT osc visibile in the hexagon, with one of the Auto modes enabled to cycle through the WT (e.g. Loop <-->), the waveform display will just randomly freeze at times until the next note is triggered.

It's about as minor a bug as you can get since it's a cosmetic thing and triggering another note resolves it, but figured I'd report it anyway. Don't recall if it happened in a prior build, but don't remember seeing it before. Haven't tried other DAWs yet.

Also, I could never figure out why prior experiments with uhms didn't work (even when copying and pasting) and it turns out it was the damn " character. For instance, copying and pasting from the examples in the Wavetables User Guide to Notepad or Notepad++ in Windows resulted in errors when loading the .uhm files. The new "Error on line X" message, along with this thread, helped track them down. So when I went in and manually typed over the quotation marks, everything worked as expected. Not sure if there's anything that can be done with those characters in the User Guide itself to make copy/paste work, but if not, maybe mention some of these common pitfalls with characters in the guide to say something like, "Warning: if you find that your scripts are erroring on load and everything looks fine, or your getting errors with scripts copied and pasted from this document, try overwriting the following characters in your text editor..." or something to that effect.

[tasmaniandevil]

I'm using the VST2 in Cubase10.0.10 in Windows 10 and every now and then (seems pretty random) if I've got the WT osc visibile in the hexagon, with one of the Auto modes enabled to cycle through the WT (e.g. Loop <-->), the waveform display will just randomly freeze at times until the next note is triggered.

The visualization of the wavetable will always show the last note you triggered.
So if you hit note A, keep it held, it shows note A. Then hit note B, and it will show the visualization for note B. If you continue to hold note A, but release note B, then the visualization will stop when the release phase of note B is over, although you still hear the sound of note A.

[Funkybot's Evil Twin]

I'm using the VST2 in Cubase10.0.10 in Windows 10 and every now and then (seems pretty random) if I've got the WT osc visibile in the hexagon, with one of the Auto modes enabled to cycle through the WT (e.g. Loop <-->), the waveform display will just randomly freeze at times until the next note is triggered.

The visualization of the wavetable will always show the last note you triggered.
So if you hit note A, keep it held, it shows note A. Then hit note B, and it will show the visualization for note B. If you continue to hold note A, but release note B, then the visualization will stop when the release phase of note B is over, although you still hear the sound of note A.

That makes sense in explaining exactly what I was seeing. Thanks!

[Mastrcode]

Hi!
I noticed a problem that happens sometimes when using wavetables. If i load own made wavetables, then sometimes there are crackles in lower notes when playing it with auto mode or modulating the position with a lfo or envelope. It's not with all own made wavetables, but some do. I also tried them with other Wavetable VST's to check if it is a problem with the wave file. But in all other VST's they work fine without crackles. They always have 2048 samples per frame. And it also doesn't matter how much frames they have or what interpolation mode i use in Hive.

Thanks!

[Urs]

Hi!
I noticed a problem that happens sometimes when using wavetables. If i load own made wavetables, then sometimes there are crackles in lower notes when playing it with auto mode or modulating the position with a lfo or envelope. It's not with all own made wavetables, but some do. I also tried them with other Wavetable VST's to check if it is a problem with the wave file. But in all other VST's they work fine without crackles. They always have 2048 samples per frame. And it also doesn't matter how much frames they have or what interpolation mode i use in Hive.

Thanks!

Hi,

I cannot quite figure out what you mean. It would be great to have an example wavetable and preset which shows these crackles, maybe also a quick mp3.

Thanks,

- Urs

[joris.roling]

I have a problem in Bitwig (v2.5 beta 7) that the VST2 of Hive stopped working (the VST3 does actually work). So now I'm back on v1.2.

Anyone sees this?

- J*

[Urs]

I have a problem in Bitwig (v2.5 beta 7) that the VST2 of Hive stopped working (the VST3 does actually work). So now I'm back on v1.2.

Anyone sees this?

- J*

There's a problem with VST3, but Bitwig are working on a solution for the final 2.5

I do not know anything about the VST2 and Bitwig.