u-he

Echoes in the Attic · Post by **Echoes in the Attic** » Mon Mar 24, 2014 3:22 am

I'm finding that all U-He synths show a generic unit value like unit 1.00, unit 2.00 etc. for any parameter which is a menu selection like a modulation source. Most synth plug-ins that expose their menus show the actual values for automation, but Zebra and Diva don't. See the Korg Monopoly example compared to Diva:

Is there any way this can be improved? It's a shame to not know what the values means for automation and even worse for hardware mapping that has a display like Novation keyboards, Ableton Push, Maschine, Nektar keyboards etc. where you can scroll the values of a menu. But it's impossible with "Unit" values.

thanks

Urs · Post by **Urs** » Mon Mar 24, 2014 10:11 am

Strange, I would consider that a bug. They are definitely supposed to show proper value strings.

I'll add that to our bug tracking system.

Echoes in the Attic · Post by **Echoes in the Attic** » Mon Mar 24, 2014 3:05 pm

Urs wrote:Strange, I would consider that a bug. They are definitely supposed to show proper value strings.

I'll add that to our bug tracking system.

I'm glad to hear you say that because I could swear that they didn't used to be like that!

cheers

moscom_electronics · Post by **moscom_electronics** » Mon Mar 24, 2014 3:23 pm

That was exactly the probem I reported a few weeks ago

It'd be so cool if this could be solved, as the Live configure tool would become very useful especially with Push in mind

Urs · Post by **Urs** » Mon Mar 24, 2014 3:32 pm

moscom_electronics wrote:That was exactly the probem I reported a few weeks ago It'd be so cool if this could be solved, as the Live configure tool would become very useful especially with Push in mind

Ah, okay, I might have misunderstood back then, or it's still in our bug tracking system.

Rob did a few tests this morning and found that it works, so maybe it's fixed already.

We're working passionately on a new "latest builds" release, hopefully for this week.

moscom_electronics · Post by **moscom_electronics** » Mon Mar 24, 2014 4:11 pm

No problem, I may have not be clear too. I had Push in mind hence it may have sounded obscure at the time.

Looking forward to playing with the new builds

Echoes in the Attic · Post by **Echoes in the Attic** » Mon Mar 24, 2014 6:36 pm

moscom_electronics wrote:No problem, I may have not be clear too. I had Push in mind hence it may have sounded obscure at the time.

These kinds of issues always cause confusion. The language is still a bit new to people and so communication is hard sometimes. People used to always talk about either midi or automation. Now that hardware devices are using parameters directly, as exposed for automation, people are starting to have think/talk about it for more than just automation, and more with regards to hardware devices. I've honestly been bugging devs for years about how they expose parameters to the host because I've been using automap since it came out, but I've been in tiny minority.

So I am always massively relieved when something like this is acknowledged as an issue. By either other users or the dev! (hopefully both)

rod_zero · Post by **rod_zero** » Wed Sep 03, 2014 3:33 am

Related to this,

Urs,

How many parameters does Diva has? I am trying to make a comprensive DIva mapping for Push And I would like to know how many banks I need.

Also would be nice if you can share a list with us so I can check which ones I am still missing.

Thanks a lot!

taoyoyo · Post by **taoyoyo** » Mon Mar 16, 2015 6:43 pm

Just wanted to check in to see if this 'unit' bug is likely to be fixed in the near future?

(the latest builds all have this issue still, at least in Live 9).

Cheers,

Alan

u-he

KVR Audio

Menu parameters show generic "unit" for automation values