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

[thetechnobear]

the difference between MPE and multi chnnel Midi support.

MPE is a bit more elaborate in that it requires a +/- 48 semitones pitchbend range, it can define a number of active MIDI channels and it has a "master channel" whose pitchbend and control changes propagate to all other channels. It's not a big difference, but some of those things are very particular and wouldn't work with our stuff right now.

Great to hear you have MPE on your radar still...

one thought, whilst the MPE is still in draft, Madrona Labs have released Aalto with current draft and Linnstrument, Eigenharp, Soundplane and Continuum (in beta), all support the current draft... also Bitwig has added it too. (seaboard status unknown)
so whilst it is evolving, the draft is already supported pretty well.
(though as a developer I can appreciate the do it 'once' approach too)

anyway, a couple of small (perhaps intermediate) requests.
- is it possible to extend range to +/- 48 semitones, independently of MPE?
- could there be a way we can save 'locks' as defaults e.g. Id like to permanently lock PB to +/- 48 (currently I need to do this each time I create an instance)

sidenote: the one thing that stops us using MPE mode with u-he plugins (albeit without the PB range support), is that CC74 is not available. perhaps if CC74 and CC11 were used as 'expression' then we could still use MPE mode. this would be really very useful to us
(you could add a new 'timbre' outlet instead, but Im guessing UI changes are more work)

[Urs]

Ah, yes... CC74...

There's no quick fix for any of this. We need to tackle a few other issues first. The +/-48 semitones pitchenbend range is the easiest thing to do, but locking that beyond instance is not an option right now.

MPE mode (switched via CC127 IIRC) will automatically set all these things - 74 mapped to expression, range set to 48 etc. That's why I wouldn't want to implement anything right now that might seem like an intermediate solution.

Our current multi channel MIDI support has been a mighty step for us, but we still need to validate and refine some of the concepts. For instance, there's no rule as to how a "single trigger" envelope/LFO/whatsoever should behave in MPE or elsewhere, i.e. per channel or globally. Time will tell as more people adopt this and as input increases.

[Beamboom]

Any plans in the horizon for a Linux build of these?

[Urs]

Any plans in the horizon for a Linux build of these?

We'll ask abique to get into it once all issues are resolved. This way he doesn't have to do things several times.

[hyperconnectedspace]

looks sweet!

[Wanterkeelt]

Urs, do you plan to also offer a multi-installer in the future ? I own all of your plugins, and updating to 3819 will require launching 12 installers. Fabfilter, Melda Production and PSP Audioware have very practical multi-installers, which make that quite easy. Any plans ?
Of course thanks for the continuous work

[Urs]

Urs, do you plan to also offer a multi-installer in the future ? I own all of your plugins, and updating to 3819 will require launching 12 installers. Fabfilter, Melda Production and PSP Audioware have very practical multi-installers, which make that quite easy. Any plans ?

Yes, but we haven't had time and energy to do that yet. Mostly concentrating on this update, and hopefully it's the last one that requires individual installs.

[az82]

The new ACE skin, scaled 140% is gorgeous. You have an awesome designer there. Can't wait for the new Zebra 2 skin

[az82]

Here's what it seems to be a bug (manifests in previous versions as well): When browsing presets in Logic Pro X, if there are less than 2-3 seconds before switching to the next preset, the name is not updated in the wrapper's preset menu, title bar nor in tracks's title. Happens in all plugins.

[Beamboom]

We'll ask abique to get into it once all issues are resolved. This way he doesn't have to do things several times.

Alright, makes sense. Thanks!

[u-he-michael]

Here's what it seems to be a bug (manifests in previous versions as well): When browsing presets in Logic Pro X, if there are less than 2-3 seconds before switching to the next preset, the name is not updated in the wrapper's preset menu, title bar nor in tracks's title. Happens in all plugins.

yes, we gonna look into it. thanks

[u-he-michael]

Hey there,

just a little reminder regarding: TESTING

We need your input!

This is likely the easiest and quickest way to reveal issues:

1.
Sound-designers: Go through your patches and verify, that they sound as they should
Producers: Load many (old) projects and verify, that they sound as they should

You can also, simple as that, play the synths live, while flipping through presets.
Please make sure, to cover all voice-modes, etc., including ARP/SEQ and Glide.

2.
Please check, that all MIDI CC's & modulation sources/targets work 100% - as they should.

Thanks!

Michael | QA
u-he.com

[u-he-michael]

Here's what it seems to be a bug (manifests in previous versions as well): When browsing presets in Logic Pro X, if there are less than 2-3 seconds before switching to the next preset, the name is not updated in the wrapper's preset menu, title bar nor in tracks's title. Happens in all plugins.

yes, we gonna look into it. thanks

I'll report this to Apple, as it happens also with plugins from other manufacturers.

[WolfKay]

In Logic Pro X, the value displayed in the Default Value box of the Configuration page is always 100%, even if another value had been chosen earlier.

(The size is OK though.)

[u-he-michael]

In Logic Pro X, the value displayed in the Default Value box of the Configuration page is always 100%, even if another value had been chosen earlier.

(The size is OK though.)

which plugin? could you send a screenshot please?