Latest Builds (revision 3819) of nearly every u-he plugin

[u-he-michael]

Diva rev 3819, Win7, 32bit plugin, FL Studio 12

for example, take the Dual osc and adjust osc1 pitch to notice it goes lower than 32" (by one extra octave)
this is valid for osc2 also but it's a bit more strange since the detune knob is involved as it jumps...

if this is too vague, please ask questions to clarify "bug" , sorry if it was mentioned before.

PS I also get those line-glitches but I guess they are only there when using a different size than 100%

We'll look into the OSC range issue. Any other parameters behaving odd as well? Yes, the GUI glitches occur only on GUI sizes≠100%, and on Windows.

[3ee]

^ So far, only the pitch range switches ...and the detune knobs in the extra low-pitch-range context.

Another thing I've just noticed: The Dual VCO ECO's pitch ranges are like twice as sensitive to mouse movement than the other oscs.

[yl0506]

Hello,

I have a problem in Logic 10.2 in osx 10.10.5 since I update zebra to rev 3819, it is very very slow to show its window... I try with differents themes, but it's always the same...

Is there someone else with that problem ?

[ThrashJazzAssassin]

Zebra 2.7.2, Reaper 5.01, Win 8.1

Knobs are sometimes drawn over bottom menus when scale is ≠ 100%

[u-he-michael]

It should be easy but could you please provide some reproduction steps?

[Elektronisch]

When the plugin is updated and I load project that had previous version used those have the setting "Base Latency" as 16 samples and it distorts the sound. I need to set it "off" and back to "16 samples" to get rid of the distortion. Other way is to set it "off" and set FL Studio vst wrapper settings to "use fixed size buffers" and "process maximum size buffers" to get clean sound, this way though my latency compensation is broken. So there is some bug in this version because it thinks that the latency setting is set to "off" though it says that it set to "16 samples"

Ok, we're looking into this. There might be a bug, if you have to switch it off and on again.

We'll also make all explanations a bit more clear, and we'll display a short message if the software glitches because of it. That should help us debug this and also fix the issue for people who accidentally set it to off

I can confirm that this happens, aswel this happens with Zebra 2.

EDIT: Same with Hive

This aswel happens with Presswerk and Satin.

[u-he-michael]

When the plugin is updated and I load project that had previous version used those have the setting "Base Latency" as 16 samples and it distorts the sound. I need to set it "off" and back to "16 samples" to get rid of the distortion. Other way is to set it "off" and set FL Studio vst wrapper settings to "use fixed size buffers" and "process maximum size buffers" to get clean sound, this way though my latency compensation is broken. So there is some bug in this version because it thinks that the latency setting is set to "off" though it says that it set to "16 samples"

Ok, we're looking into this. There might be a bug, if you have to switch it off and on again.

We'll also make all explanations a bit more clear, and we'll display a short message if the software glitches because of it. That should help us debug this and also fix the issue for people who accidentally set it to off

I can confirm that this happens, aswel this happens with Zebra 2.

EDIT: Same with Hive

This aswel happens with Presswerk and Satin.

yes sure. we'll provide a fix for the next round.

[Elektronisch]

Good to hear!

Is it possible to expect the fix within few days ?

[Dip200]

Thanks for the update. Looks like you fixed a bug I reported some time ago in Uhbik

[Elektronisch]

I dont know if this should is normal how it looks, but when setting Presswerk to less then 100 size, Uhe logo letters edges become "rougher"?

[EvilDragon]

Those are resizing artifacts likely.

[Elektronisch]

Those are resizing artifacts likely.

It is likely. Same with Satin. Im using resized Hive, Diva to 90% aswel, but logo on them dont feel so jaggy like on Presswerk and Satin

[rheinlandhippie]

Hi @u-he,

some little issues with the unbelievable BAZILLE from my side (System Environment see below):

1. Initial Situation: a) Load/Activate a Step-Sequencer Patch from the Patch Browser b) Play any note on the Master Keyboard/Midi Controller c) Change to the System View

Result: You will see no movement (little lights) of the programmed steps even though you can hear every step correctly (most important!). After pressing any note on the Keyboard again the step display works perfectly.

No heavy bug indeed but a little bit curious.

2. Moving the wires leads to some graphical GUI artefacts that clear away after spotting everything to its place (after releasing the mouse button).

3. That’s nothing important to fix I guess: There is obviously a funny “Sense-Typo” in the Manual - have a look to „now and again“ on sides 15 and 51 (You mean „now and then“ actually, correct?)

- Side 15, Oscillators/Pitch/Tune
- Side 51, General Tricks/Keeping it clean #1 (Many thanks indeed to u-he for the tricks)

- - -

Best from Cologne to Berlin
Wolfram


[MAIN SYSTEM: i7-Workhorse with 16 GB RAM, Windows 10 Professional, Cubase 8 PRO, RME Fireface UCX, Neumann KH-120 A (small but excellent), Standard LCD-Monitor with a 1920 x 1020 Pixel resolution]

[Urs]

1. Initial Situation: a) Load/Activate a Step-Sequencer Patch from the Patch Browser b) Play any note on the Master Keyboard/Midi Controller c) Change to the System View

Result: You will see no movement (little lights) of the programmed steps even though you can hear every step correctly (most important!). After pressing any note on the Keyboard again the step display works perfectly.

Fixed! - Will be posted here in about a week or so.

2. Moving the wires leads to some graphical GUI artefacts that clear away after spotting everything to its place (after releasing the mouse button).

Yep, has been reported, is on our todo list for next week too!

3. That’s nothing important to fix I guess: There is obviously a funny “Sense-Typo” in the Manual - have a look to „now and again“ on sides 15 and 51 (You mean „now and then“ actually, correct?)

Will consult our native English speakers

[Howard]

http://idioms.thefreedictionary.com/every+now+and+again