u-he

lsasso · Post by **lsasso** » Thu Oct 02, 2014 11:57 pm

Has anyone found a way to make Bazille always instantiate in Multicore and HQ mode?

3ee · Post by **3ee** » Fri Oct 03, 2014 1:35 am

In FL Studio, the full plugin state is saved when adding to plugin picker.

lsasso · Post by **lsasso** » Fri Oct 03, 2014 3:18 am

Thanks. I'm working in Live and that doesn't seem to be the case—it always loads with Multicore off and HQ on.

NadirToZenith · Post by **NadirToZenith** » Fri Oct 03, 2014 6:15 am

lsasso wrote:live
loads with multicore off
hq on

hello, lsasso,

saving (with the required settings set) a template might help in any workstation, then loading the template instead of initiating, loading, the plug-in gets back the saved settings.

all the best...

aMUSEd · Post by **aMUSEd** » Fri Oct 03, 2014 6:50 am

Or saving it as a rack.

Anyone who has NI Kore 2 can also use my Kore template which is set to Multicore by default

Nielzie · Post by **Nielzie** » Fri Oct 03, 2014 7:45 am

Multicore is not a global option like in ACE, but saved within the preset, right? I'd love to have it as a global option though.

HQ mode I can understand that it's bound to a preset, because it effects the sound of that preset.

aMUSEd · Post by **aMUSEd** » Fri Oct 03, 2014 7:49 am

Nielzie wrote:Multicore is not a global option like in ACE, but saved within the preset, right? I'd love to have it as a global option though.

HQ mode I can understand that it's bound to a preset, because it effects the sound of that preset.

No Multicore is global, but just not retained between sessions (as with Diva and ACE) - but you can use the host to save some sort of template or preset/rack in most hosts (certainly Kore, Tracktion, Live offer this).

HQ is per preset - but you can lock it

lsasso · Post by **lsasso** » Fri Oct 03, 2014 1:34 pm

Yes, saving it as a rack is the thing in Live, I should have thought of that

.

I agree, it would be nice if the default were 'on' or if it were a preference setting.

Urs · Post by **Urs** » Fri Oct 03, 2014 2:34 pm

(we'll be working on it)

BBFG# · Post by **BBFG#** » Fri Oct 03, 2014 6:03 pm

It's been related to me that in the DAW (if it uses multi-core support) that it is best to leave it off in the plugin itself.
I'll assume this to be true here until U-He tells me otherwise?

aMUSEd · Post by **aMUSEd** » Fri Oct 03, 2014 6:06 pm

BBFG# wrote:It's been related to me that in the DAW (if it uses multi-core support) that it is best to leave it off in the plugin itself.
I'll assume this to be true here until U-He tells me otherwise?

I would add even if the host does multicore well there's probably not going to be much benefit unless you are using more than one instance. On the other hand if there is just one instance there's probably no harm in turning it on - it certainly makes a difference on my i7 regardless of the host's capabilities.

pdxindy · Post by **pdxindy** » Fri Oct 03, 2014 6:53 pm

BBFG# wrote:It's been related to me that in the DAW (if it uses multi-core support) that it is best to leave it off in the plugin itself.
I'll assume this to be true here until U-He tells me otherwise?

I use it all the time on a multi-core daw... no problems here

lsasso · Post by **lsasso** » Fri Oct 03, 2014 7:10 pm

It seems to make a difference here. In a Live set with a single track holding Bazille running the Local patch 'TUC Pudding Trampoline 2 minor' (converted to 6 voices as suggested), a single note registers 38% on Live's CPU meter with Bazille Multicore off and 16% with it on. (Live's Multicore support is turned on.)

I have no idea whether this is an accurate test

.

Urs · Post by **Urs** » Fri Oct 03, 2014 10:50 pm

lsasso wrote:It seems to make a difference here. In a Live set with a single track holding Bazille running the Local patch 'TUC Pudding Trampoline 2 minor' (converted to 6 voices as suggested), a single note registers 38% on Live's CPU meter with Bazille Multicore off and 16% with it on. (Live's Multicore support is turned on.)

I have no idea whether this is an accurate test .

Well, hehe, it may still take 38%, but it's only 16% on the core that Live assigns to it, and 22% are being forked out to other cores.