u-he

zvenx · Post by **zvenx** » Mon Sep 21, 2015 1:57 pm

Hi, you are changing it the wrong place. It is in the new panel preferences you should be changing it.
Rsp

Urs · Post by **Urs** » Mon Sep 21, 2015 2:29 pm

lucassantana wrote:The default Zebra GUI size seems to be stuck at 110%.....I changed it to 170% and clicked "make default".

Sounds like you're using a 3rd party skin w/o the preferences panel. The "make default" command only ever worked for the skin/theme, not for the size. We left it in for themes that haven't been updated with the preferences panel yet (well, that'll be pretty much all 3rd party ones for a while)

Urs · Post by **Urs** » Mon Sep 21, 2015 6:08 pm

hakey wrote:
Urs wrote:If you could send 2-3 presets that are different to support at u-he we can check it out.
okay, sent

Those were a tough nut, I pretty much got some grey hair over one of these presets today, haven't studied the other one yet

After a mind numbing armada of tests for VoiceMap, Stacking, Arp and the likes it turned out that multiple differences are based on actual bugfixes.

First off, the LFO Single Trigger option now works Arpeggiator-wide. You press a bunch of notes, the LFO will be triggered once but it won't be retriggered for each arpeggiated note, only for the first one pressed on the keyboard. This fix was done for Hive, we didn't even know it was broken in Diva. The current behaviour is the one that is supposed to happen.

Secondly the single triggered LFO that you hear will naturally be the one of the voice that's processed first. That may be a pretty random race if multicore is switched on. Thus, depending on thread scheduling and all that, any voice can be the one that provides the single trigger LFO for all voices to follow. Obviously, the probability as to which voice this might be has changed from build 2165 to 3857. Thus, if a VoiceMap modulator is used to control a single trigger LFO, it's pretty random.

I see two chances to fix this. Firstly we can recommend to use voice specific LFOs (i.e. not "single triggered") if per-voice modulations are desired. Secondly we can change the behaviour of the LFO so that each LFO for each voice gets calculated even is single trigger is set. This will cost a tad more CPU and time for us. I tend to latter, but I have to figure out how much is involved.

I'll sleep over it, feedback is welcome

Cheers,

- Urs

lucassantana · Post by **lucassantana** » Mon Sep 21, 2015 9:08 pm

Aah I see! Then perhaps I'll have to 'renovate' my current 3rd party skin based on the latest 'default' skin I guess...anyways, will do.
thanks alot.

Unread postby zvenx; Mon Sep 21, 2015 5:57 am
Re: Latest Builds (revision 3857) of nearly every u-he plugin (Public Beta 2)
Hi, you are changing it the wrong place. It is in the new panel preferences you should be changing it.
Rsp

by Urs; Mon Sep 21, 2015 6:29 am
Re: Latest Builds (revision 3857) of nearly every u-he plugin (Public Beta 2)

lucassantana wrote:
The default Zebra GUI size seems to be stuck at 110%.....I changed it to 170% and clicked "make default".

Sounds like you're using a 3rd party skin w/o the preferences panel. The "make default" command only ever worked for the skin/theme, not for the size. We left it in for themes that haven't been updated with the preferences panel yet (well, that'll be pretty much all 3rd party ones for a while)

hakey · Post by **hakey** » Tue Sep 22, 2015 7:50 am

Urs wrote:
hakey wrote:
Urs wrote:If you could send 2-3 presets that are different to support at u-he we can check it out.
okay, sent
Those were a tough nut, I pretty much got some grey hair over one of these presets today

Sorry.

Thanks for the explanation - that all makes sense. I'd favour calculating the LFO per voice, but the problem is fairly esoteric, so whatever you decide.

I think we discussed non-random initial voice triggering before? That's something I'd like (for quasi-sequencing effects) but not likely to happen, iirc.

And don't worry about that other preset. It's another example of the same issue.

Urs · Post by **Urs** » Tue Sep 22, 2015 8:12 am

Ok, thanks

I think a quick solution for your resets would be setting LFOs to "gate" trigger maybe.

On the issue, making single trigger LFOs evaluate per voice will be possible only for amplitude modulation, but not for LFO rate. It would be devil's kitchen and if we give users one option but not the other… it might be even more confusing.

I have thougth about it last night and I think I might have a solution. Instead I would like to try to ensure voice processing order from oldest to latest in multicore mode. This should at least make any case reproducible. I think there might even be some room for a performance improvement if some concepts of our multicore support changed a bit.

Will see what I can cook up today.

- U

hakey · Post by **hakey** » Tue Sep 22, 2015 8:49 am

Urs wrote:I think a quick solution for your resets would be setting LFOs to "gate" trigger maybe.

Don't worry about it, they're no great loss. They were just the chance result of experiments using the Arp and single triggered LFO's modulating Osc pitch to get melodic/harmonic sequences. Not sure how I'd come to assign Voice Map to LFO amplitude.

lucassantana · Post by **lucassantana** » Tue Sep 22, 2015 12:23 pm

update:

ok I've removed all 3rd party skins, uninstalled and re-installed latest build with just the default skins.

used Panel Preferences to set default skin size to 170% or whatever....re-opened vst. Still the same problem...it's at 100%. Default skin.

the monitor screen's kind of far away from my eyes so I need a larger skin size to work...but i can't keep resizing everytime I open up an instance of the vst. Doesn't seem like anyone else is having this problem though...arrgh

Urs · Post by **Urs** » Tue Sep 22, 2015 12:27 pm

lucassantana wrote:update:

ok I've removed all 3rd party skins, uninstalled and re-installed latest build with just the default skins.

used Panel Preferences to set default skin size to 170% or whatever....re-opened vst. Still the same problem...it's at 100%. Default skin.

the monitor screen's kind of far away from my eyes so I need a larger skin size to work...but i can't keep resizing everytime I open up an instance of the vst. Doesn't seem like anyone else is having this problem though...arrgh

What revision number is printed on the XY page? - Maybe you have an older installation?

lucassantana · Post by **lucassantana** » Tue Sep 22, 2015 7:44 pm

Urs wrote:
lucassantana wrote:update:

ok I've removed all 3rd party skins, uninstalled and re-installed latest build with just the default skins.

used Panel Preferences to set default skin size to 170% or whatever....re-opened vst. Still the same problem...it's at 100%. Default skin.

the monitor screen's kind of far away from my eyes so I need a larger skin size to work...but i can't keep resizing everytime I open up an instance of the vst. Doesn't seem like anyone else is having this problem though...arrgh
What revision number is printed on the XY page? - Maybe you have an older installation?

It says Rev 3857...

Urs · Post by **Urs** » Tue Sep 22, 2015 8:18 pm

Hmmm, in that case I'm not sure what to recommend. The stuff usually works. Maybe contact support at u-he dot com and see what they suggest.

My last straw would be, what does the preferences file in the support folder say?

lucassantana · Post by **lucassantana** » Wed Sep 23, 2015 7:44 am

Urs wrote:Hmmm, in that case I'm not sure what to recommend. The stuff usually works. Maybe contact support at u-he dot com and see what they suggest.

My last straw would be, what does the preferences file in the support folder say?

Alritey. I'll contact support from the main site.

Well the preference file currently states:

V_PROPERTY name='Author' id='0' value='u-he'
V_PROPERTY name='Preference' id='0' value='AllViews:DefaultSkin:Original'
V_PROPERTY name='Preference' id='0' value='AllViews:Text Antialiasing:YES'
V_PROPERTY name='Preference' id='0' value='AllViews:KeyControl:NO'
V_PROPERTY name='Preference' id='0' value='AllViews:DefaultUISize:150%'
V_PROPERTY name='Preference' id='0' value='All:MouseWheel Raster:YES'
V_PROPERTY name='Preference' id='0' value='AllViews:Graphics Gamma:neutral'
V_PROPERTY name='Preference' id='0' value='AudioPrefs:SmoothMidiCtrls:LIGHT'
V_PROPERTY name='Preference' id='0' value='AudioPrefs:BaseLatencyBuffer16:YES'

Viktor [TUC] · Post by **Viktor [TUC]** » Wed Sep 23, 2015 8:59 am

Hi everyone,
on the off chance that everyone who *applied* reads this:
Those of you that were interested in translating one of our manuals into German and never received my reply, feel free to write to me again at Support. I've sent replies out to everyone two weeks ago, but most of you have never gotten back to me, and I know some never got my emails strangely. Maybe also check your spam folders.
So if you're still interested in translating one of our manuals into German in exchange for a license of choice, let me know and write to me at Support.

Thank you, guys!

Viktor

lucassantana · Post by **lucassantana** » Wed Sep 23, 2015 12:55 pm

Eureka! (meh)

looks like Cubase was the culprit here and I was too dull to figure this one out. Thanks Viktor and Urs, the GUI default size issue is now settled. Cubase's feature allows one to set any perimeter of any VST as "default preset". Used it and now it's perfect.

Danke!

lucassantana wrote:
Urs wrote:Hmmm, in that case I'm not sure what to recommend. The stuff usually works. Maybe contact support at u-he dot com and see what they suggest.

My last straw would be, what does the preferences file in the support folder say?
Alritey. I'll contact support from the main site.

Well the preference file currently states:

V_PROPERTY name='Author' id='0' value='u-he'
V_PROPERTY name='Preference' id='0' value='AllViews:DefaultSkin:Original'
V_PROPERTY name='Preference' id='0' value='AllViews:Text Antialiasing:YES'
V_PROPERTY name='Preference' id='0' value='AllViews:KeyControl:NO'
V_PROPERTY name='Preference' id='0' value='AllViews:DefaultUISize:150%'
V_PROPERTY name='Preference' id='0' value='All:MouseWheel Raster:YES'
V_PROPERTY name='Preference' id='0' value='AllViews:Graphics Gamma:neutral'
V_PROPERTY name='Preference' id='0' value='AudioPrefs:SmoothMidiCtrls:LIGHT'
V_PROPERTY name='Preference' id='0' value='AudioPrefs:BaseLatencyBuffer16:YES'

rod_zero · Post by **rod_zero** » Wed Sep 23, 2015 5:23 pm

rod_zero wrote:Glitches while activating multi core support on an i5 760 are expected right?

Any comment on this?