Latest Builds (revision 3857) of nearly every u-he plugin (Public Beta 2)

[SLiC]

Is a single unified installer anywhere on the todo list?

what is wrong with the installer thats provided now?

Nothing, just that I have 13 of them to do.

I have to agree- chances are (as we are all U-HE fans here) that we have a lot of the plugins to update (I am on 10) Be great to have a page open where you 'tick' the products to install (U-HE Komplete and I am sure as demo's would install if you ticked them all that U-HE would sell even more stuff (once you try it....)

So a big +1 for a unified installer!

[Elektronisch]

I must say that loading times are really much faster, especially with Diva & Hive.

[provoc]

I'm not sure if I'm too happy with the plugin reverting to 16 samples latency in case it detects the host sending irregular buffers.

With Reaper this means increasing the latency to full buffer size, which is not cool for recording, at all. Especially with synths (seriously, why would 16 samples of latency be necessary for ACE, Bazille, Zebra, etc.?). And I'm not sure if there's a solution for this within Reaper. I notice the plugin reverting to 16 samples latency after a loop has been played once.

We're open to discuss this.

The main problem is that people won't make the connection between "horrible distortion" and having switched the latency off. So we did this new thing as quickly as we could. This (and the UI opening time) is the main reason we do a whole new round of public betas instead of taking it to a release candidate.

If there's another way that we can go, it needs to be absolutely fool proof, i.e. it must not spoil the experience of the not-so-technically-savvy user.

!BLOCK_LATENCY_OFF=YES not working for me with Tyrell N6 or Zebra/Zebralette in 32 bit Reaper 5.01. The previous version worked so wondering exactly what has changed? I can always disable/ignore the 16 samples PDC for live use but it was good to have the option to disable the latency completely.

Cheers,

provoc

[Urs]

!BLOCK_LATENCY_OFF=YES not working for me with Tyrell N6 or Zebra/Zebralette in 32 bit Reaper 5.01. The previous version worked so wondering exactly what has changed? I can always disable/ignore the 16 samples PDC for live use but it was good to have the option to disable the latency completely.

Yes, it interfered with the new "Base Latency" preference in the new preferences panel. You can switch it off in Zebra, but not in TyrellN6/Zebralette.

Hmmm... haven't thought of that. We'll bring it back once we do the panel in all of these plug-ins as well.

[EvilDragon]

So wait, $BLOCK_LATENCY_OFF is not the same thing as the option in the prefs panel? Confused.

[3ee]

DIVA rev3857

Dual VCO Eco pitch-range parameters are still too sensitive to mouse movements... is this intentional?

[Urs]

So wait, $BLOCK_LATENCY_OFF is not the same thing as the option in the prefs panel? Confused.

Sorry, where's my head today... (got confused when wondering what to call a tape emulation with linear phase)

We killed BLOCK_LATENCY_OFF from the default.h2p evaluation because its "YES" is the Base Latency's "Off" and its "NO" is the Base Latency's "On". Even our team got confused as to what's what and when is which what under which context. So we took it out completely, in favour of "Base Latency", which now unfortunately can't be switched off for plug-ins that have no prefs panel yet

[Urs]

DIVA rev3857

Dual VCO Eco pitch-range parameters are still too sensitive to mouse movements... is this intentional?

Not intentional, I guess it's just as it always was...?

Will throw it into our internal discussion...

[EvilDragon]

So wait, $BLOCK_LATENCY_OFF is not the same thing as the option in the prefs panel? Confused.

Sorry, where's my head today... (got confused when wondering what to call a tape emulation with linear phase)

I see what you did there.

We killed BLOCK_LATENCY_OFF from the default.h2p evaluation because its "YES" is the Base Latency's "Off" and its "NO" is the Base Latency's "On". Even our team got confused as to what's what and when is which what under which context. So we took it out completely, in favour of "Base Latency", which now unfortunately can't be switched off for plug-ins that have no prefs panel yet

Ah, it's like I though, then. But since you change this one thing in your framework, it applies to all plugins, even those which don't have the panel. So I assume all other plugins will need to get the panels sooner rather than later (not to mention Filterscape and MFM UI updates, eh?)?


EDIT: But wait, for the plugins that don't have prefs panel yet, couldn't I manually create Preferences.txt and it would be evaluated?

[Urs]

I see what you did there.

Yeah... closing threads is the ultimate weapon to have the last word.

Ah, it's like I though, then. But since you change this one thing in your framework, it applies to all plugins, even those which don't have the panel. So I assume all other plugins will need to get the panels sooner rather than later (not to mention Filterscape and MFM UI updates, eh?)?

Yep.

EDIT: But wait, for the plugins that don't have prefs panel yet, couldn't I manually create Preferences.txt and it would be evaluated?

I am not sure... it may indeed be possible, at least for the Base Latency.

If not, maybe we'll simply add this as an option.

[EvilDragon]

Tried it - setting Base Latency in the Preferences file WORKS even for plugins that don't have the prefs panel! Woohoo!

[Urs]

ta!

[hakey]

Diva 3857

A couple of my presets sound very different. I think it's related to LFO2 depth modulated by voicemap and running in sync with the arp.

The same presets have exhibited strange behaviour with previous builds - upon selecting the preset it was pot luck as to whether I'd get the correct sound that I'd originally programmed, or some weirdly different atonal version.

With this latest build they sound different again.

[Urs]

Diva 3857

A couple of my presets sound very different. I think it's related to LFO2 depth modulated by voicemap and running in sync with the arp.

The same presets have exhibited strange behaviour with previous builds - upon selecting the preset it was pot luck as to whether I'd get the correct sound that I'd originally programmed, or some weirdly different atonal version.

With this latest build they sound different again.

Hmmm, a lot of things have been changed, we hope for the better, e.g. no more missing first notes in the arp when looping.

If you could send 2-3 presets that are different to support at u-he we can check it out.

[provoc]

Tried it - setting Base Latency in the Preferences file WORKS even for plugins that don't have the prefs panel! Woohoo!

Thanks, working here too