u-he

Urs · Post by **Urs** » Sat Jun 28, 2014 7:45 pm

thetechnobear wrote:"Continuous 14 bit" , not in the Ace or Bazille manual (or I couldn't find it), but the Diva and Zebra manual simply says 14 bit CC.

theres a couple of threads about it here:
http://www.kvraudio.com/forum/viewtopic ... &p=5120437
http://www.kvraudio.com/forum/viewtopic ... 26#5295926

Yeah, the switches define which kind of controller you're going to learn. One can mix any type for different knobs/parameters.

That said, once we get to develop a global preferences pane, there'll be a list of all assignments and a way to edit them. But this is another project that was planned about ten years ago and never really took off. Maybe now with the combined power of 3 developers + interns.

NothanUmber · Post by **NothanUmber** » Sat Jun 28, 2014 8:36 pm

thetechnobear wrote:"Continuous 14 bit" , not in the Ace or Bazille manual (or I couldn't find it), but the Diva and Zebra manual simply says 14 bit CC.

theres a couple of threads about it here:
http://www.kvraudio.com/forum/viewtopic ... &p=5120437
http://www.kvraudio.com/forum/viewtopic ... 26#5295926

Ok, thanks again!
Had a look at the Diva manual, there it is describing it as a feature for MIDI learn (binding a GUI knob to a MIDI event). Does 14bit MIDI also work for the (per voice) MIDI modulation inputs? (I can't hear a difference if I set EigenD and Bazille to 14bit vs both to 7 bit MIDI. For PianoTeq I have the impression that 14bit velocity+CCs makes a difference (the Eigenharp key outputs work with 10bits resolution, so theoretically at least a x8 increase in resolution should be possible for the entire finger-to-sound-generator chain). I never did a blind test though...)

P.S.: Mini Bug: The user guide is not copied over to the Bazille.data directory by the installer (as it is the case for all release version plugins).

dreammaka · Post by **dreammaka** » Sat Jun 28, 2014 10:53 pm

possible bug?

I was playing with the new build on my system (iMac i5) and switching between the original and the gearporn skin.
Somehow when I'm using the gearporn skin Bazille consumes 2~3 times the CPU compare to the original skin.

Urs · Post by **Urs** » Sat Jun 28, 2014 11:21 pm

dreammaka wrote:possible bug?

I was playing with the new build on my system (iMac i5) and switching between the original and the gearporn skin.
Somehow when I'm using the gearporn skin Bazille consumes 2~3 times the CPU compare to the original skin.

Possible UI optimisation problem. To make the gearporn skin work we need to render panels on top of the cables. This may cost more CPU and we'll need to investigate how to bring it down. It isn't called gearporn for no reason, I guess a fast CPU is paramount!

(there's a lot of room for optimisation though, we're just slowly enhancing the UI framework to do all these things)

pdxindy · Post by **pdxindy** » Sat Jun 28, 2014 11:45 pm

dreammaka wrote:possible bug?

I was playing with the new build on my system (iMac i5) and switching between the original and the gearporn skin.
Somehow when I'm using the gearporn skin Bazille consumes 2~3 times the CPU compare to the original skin.

They are the same here for me... (iMac i7 - 10.9.3)

aMUSEd · Post by **aMUSEd** » Sat Jun 28, 2014 11:52 pm

Me too (also Mac) - maybe this is a Win or graphics card thing?

samplemania · Post by **samplemania** » Sun Jun 29, 2014 12:08 am

I allready bought Bazille without hesitation. However I was today a little bit turned off when playing with the recent beta on my Macbook Pro with (2012) with an i7 quad core: The CPU use for some of the patch competition patches is really high

pdxindy · Post by **pdxindy** » Sun Jun 29, 2014 2:42 am

I love the gearporn skin... all the parameters on one page is great!

I wouldn't mind if the background panels were just slightly lighter...

note stealing is improved as is the aliasing on the tap maps

pdxindy · Post by **pdxindy** » Sun Jun 29, 2014 2:43 am

samplemania wrote:I allready bought Bazille without hesitation. However I was today a little bit turned off when playing with the recent beta on my Macbook Pro with (2012) with an i7 quad core: The CPU use for some of the patch competition patches is really high

Bazille uses some CPU... no doubt... I assume you had the multi-core option turned on.

AtomOfScent · Post by **AtomOfScent** » Sun Jun 29, 2014 3:40 am

Thanks a lot for the extra month. Gives a bit of time to finish up a few existing projects.

I'm looking forward to demoing the released version too. I'm not overly skilled with synthesis so it will be nice to evaluate it with Howard's patches to see what it's capable of.

The gearporn skin looks great btw, it's got that mad scientist vibe that always impresses the ladies...

a-type · Post by **a-type** » Sun Jun 29, 2014 5:23 am

GEARPORN SKIN. YES.

Urs · Post by **Urs** » Sun Jun 29, 2014 11:41 am

samplemania wrote:I allready bought Bazille without hesitation. However I was today a little bit turned off when playing with the recent beta on my Macbook Pro with (2012) with an i7 quad core: The CPU use for some of the patch competition patches is really high

Bazille's CPU load is usually constant for each voice, regardless of synthesis parameters. Therefore, if you experience high CPU load you might want to reduce the number of voices playing simultaneously, or distribute them among CPU cores. In general your options are

- try turning Multicore on (should work well on any i7 quad core)
- try reducing stacked voices
- try reducing the overall number of voices
- shorten release times, maybe check if a reverb works instead

I can't really promise any/much improvement on the cost of voices. Some CPU load however is related to the UI, and there we may squeeze quite some more out of it - at least, if some of the things we've planned pan out.

EvilDragon · Post by **EvilDragon** » Sun Jun 29, 2014 12:06 pm

Gearporn skin - f**king SPLENDID!

I noticed two tiny easy fixable niggles: the revision text ("Rev." or "R.") is not aligned with the revision number (both Original and GP), and longer preset names aren't centered vertically in the preset name area correctly. Screenshot:

Also not sure I like the fact that knob labels are baked into the background pane PNG... makes it harder to edit the skin

And - is there a way for Bazille to remember the thickness and opacity of the cables globally? I'd like a size between line and hair, too...

The bug with scope not remembering its mode is still there for now, too.

samplemania · Post by **samplemania** » Sun Jun 29, 2014 3:33 pm

Urs wrote: Bazille's CPU load is usually constant for each voice, regardless of synthesis parameters. Therefore, if you experience high CPU load you might want to reduce the number of voices playing simultaneously, or distribute them among CPU cores. In general your options are

- try turning Multicore on (should work well on any i7 quad core)
- try reducing stacked voices
- try reducing the overall number of voices
- shorten release times, maybe check if a reverb works instead

I can't really promise any/much improvement on the cost of voices. Some CPU load however is related to the UI, and there we may squeeze quite some more out of it - at least, if some of the things we've planned pan out.

Switching on Multicore made a big difference. Before that it went to +80%.

Tom Drinkwater · Post by **Tom Drinkwater** » Sun Jun 29, 2014 11:15 pm

fantastic steps forward in usability, the midi features and the resizing are great!

what about a colour hue knob for the gearporn skin, like the one that changes the lights colour in Diva.

will the multi channel controller features become standard on other uhe synths? that will be great with touchkeys. (not to mention the eigenharp if I ever get that going)

u-he

KVR Audio

Bazille rev2435