Latest Updates (Revision 3898) for 11 u-he products - now available!

[embass]

I use Reaper 5 (64bit) and Diva (vst 2 64bit). When you loop segment in Reaper and midi notes coincidence with the begining of the loop these midi notes dont play properly.

That's strange because we debugged this ad nauseam. Would you mind sending us a Reaper project to support at u-he dot com?

I found whats causing this behavior.. I had "Flush effects when looping" enabled in Reapers preferences. I have also noticed that plate reverb doesn't flush properly when you render. I get reverb tail from last playback, you have to use long reverb decay in order to notice it...

[AbsynthDave]

Uhbik 1.3.1 uses a buffer of 16 Samples latency again. It was usually enough to put a modded preset called "default" into the preset folders, but the new updates seem to remove that option. In Zebra, ACE and Bazille I can deactivate the buffer in that new settings menu. That new menu however is not with the new Uhbiks. Can we either get the modded preset method back or get the new menu to the Uhbiks?

P.S.: same for Zebralette, ZRev ...

[Chapelle]

---

[Sampleconstruct]

In the Dark Horse skin we're also missing the Prefill-knob for the combfilter, or is it hidden behind the GUI maybe?

My bad, Prefill is now labeled Noise.

[AbsynthDave]

Uhbik 1.3.1 uses a buffer of 16 Samples latency again. It was usually enough to put a modded preset called "default" into the preset folders, but the new updates seem to remove that option. In Zebra, ACE and Bazille I can deactivate the buffer in that new settings menu. That new menu however is not with the new Uhbiks. Can we either get the modded preset method back or get the new menu to the Uhbiks?

P.S.: same for Zebralette, ZRev ...

Until these plugins get the configuration menu you can disable the latency by editing the preferences files:

For example for Uhbik-A the preferences file is in [...]\Uhbik.data\Support\com.u-he.Uhbik-A.Preferences (on Windows, not sure where it is on OSX)

Open the file in a text editor and replace the line

Code: Select all

value='AudioPrefs:BaseLatencyBuffer16:YES'

with

Code: Select all

value='AudioPrefs:BaseLatencyBuffer16:NO'

I haven't tested it for all plugins, but it should work.

Thank you, it works fine for Uhbik and Zebras FX versions. Is something like this possible for Satin and Presswerk?

[Chapelle]

---

[hakey]

Diva:

In preset view I see either 19 presets per column or, if there are more than 4 columns with a scroll bar, 18 presets per column. I'm sure that I used to be able to see 20 per column. Have I imagined that?

[Sampleconstruct]

In the Dark Horse skin we're also missing the Prefill-knob for the combfilter, or is it hidden behind the GUI maybe?

My bad, Prefill is now labeled Noise.

But: in the modulator targets it is still named Prefill, so this can cause confusion when using the Black Horse skin.

[Urs]

Diva:

In preset view I see either 19 presets per column or, if there are more than 4 columns with a scroll bar, 18 presets per column. I'm sure that I used to be able to see 20 per column. Have I imagined that?

The UI was redesigned pretty much from scratch… There wasn't a requirement to keep the rows per column exactly the same as the original setting was done by gut feeling

[Urs]

In the Dark Horse skin we're also missing the Prefill-knob for the combfilter, or is it hidden behind the GUI maybe?

My bad, Prefill is now labeled Noise.

But: in the modulator targets it is still named Prefill, so this can cause confusion when using the Black Horse skin.

Well spotted again. We changed a lot of parameter names over the years which hasn't always trancended all themes.

[nortle]

I wonder that modulation targets are not midi mappable as well as sequencer off, play etc.

In Diva that works fine. I never understood why many synth programmer make 90 - 95 % of their parameters available for midi mapping but always left a small amount to make sure you never have full control.

[hakey]

The UI was redesigned pretty much from scratch… There wasn't a requirement to keep the rows per column exactly the same as the original setting was done by gut feeling

I can live with that.

Unrelated: I'm getting stray white lines after closing drop down menus in Diva (3898, Win XP, Live 8 ).

[Urs]

I wonder that modulation targets are not midi mappable as well as sequencer off, play etc.

In Diva that works fine. I never understood why many synth programmer make 90 - 95 % of their parameters available for midi mapping but always left a small amount to make sure you never have full control.

Developers have to weigh benefits against disadvantages of features all the time.

Some parameters can be automated without a hitch. Some parameters can't. Automation of some parameters can have destructive side effects. Some parameters simply can't be automated at all.

We distinguish between 4 kinds of parameters in respect of automation and MIDI Learn:

a) Parameters that are simply automatable in a musical context, without restriction. Filter cutoff, gains values.

b) Parameters that can't be automated because they're not "just numbers". That's for instance the order of effects in Hive and their individual on/off status.

c) Parameters that can be automated for editing (sound design) but should not be automated, say, in a song project. As an example, this would be filter types, waveforms or pretty much anything that has a drop down list. We might extend whatever is in a drop down list in future updates and that would break existing automation in all plug-in formats except AAX and AU. I.e. if you automate Hive's waveform in a song and we add new waveforms, your song might sound different.

In addition, c) applies to all parameters that cause audible artifacts such as clicking, drop outs or similar. Which is also usually stuff found in drop down lists, inclduing modulation assigments or on/off switches.

d) Parameters that are "dangerous" to automate. Those are parameters that incurr so much change in the underlying process that we'd either need to safe guard with too much effort, or which to safe guard would cost excessive resources. Or, these parameters might simply involve a logic that could cause unwanted side effects if changed through anything else but UI interaction.

#----

The Sequencer on/off parameter for instance might erase the current sequence if MIDI Learned to a hardware knob. I'm not sure anymore. It was discussed a few times but I decided that if we give that to users, we'd end up with dozens of support emails from upset users.

There ModMatrix targets are not distinguished by a numerical value (such as 7, 11 or 5672), they are based on literal strings, such as "Osc1:Tune". Those don't map to a continuous list of values, i.e. most possible values would not be valid targets, say if that value was the parameter ID. Also, there is a manifold more of ModMatrix targets than there are individual values sent by MIDI controllers, even at 14 bit. They furthermore invoke quite some change underneath. I deem changing them by host automation - e.g. possibly thousands of times per second as opposed to once per mouse click - dangerous enough to keep them out, at any case.

I hope this answers the question...

[steveuk42]

I seem to be getting crashes in cubase 8 when using the new updated version of Zebra. I keep getting zebra console error now. Cubase crashes if I try and shut the project or cuabse down. Is this a known bug and will it be sorted soon ?

[Urs]

I seem to be getting crashes in cubase 8 when using the new updated version of Zebra. I keep getting zebra console error now. Cubase crashes if I try and shut the project or cuabse down. Is this a known bug and will it be sorted soon ?

That sounds like you have two version installed, or the old .dll didn't get overwritten maybe. Afaik the old version may crash with the updated GUI.

In any case, please contact support at u-he dot com, the guys can sort it out!