yeah wild isnt it? Him ALONE...
This is the problem for me:
"a internal JSON object for all widgets"
-- if this means that this JSON (which defines the UI) is now ONLY accessible via property lists then this is BAD BAD BAD.
I use a stand-alone code-generator for UI layout etc. that I then import into Kontakt (in the currently working product). I planned to port this across to write the JSON/UI part of products in HISE but if there's nowhere to import this "internal JSON" then this would be a big problem for me...
OK, well dont panic first we need to clear up whats happening:
"I try compile this * preset that doesn't work path I don't know what missing something :/"
-- what is "this * preset" ?
-- do you have a working version of HISE that you have compiled from GitHub source code?
-- have you tried to build a very very simple (just a sine wave generator) VST?
-- where did you put the VST libaries?
Oh yes, its a good thing, sorry if I gave the impression otherwise. It's just, as Dave says, it's very very early in the life cycle of HISE to see this sort of request.
Dave and I (amongst others here I'm sure) are Freelance Developers for "that other Kplatform", and as Dave was nearly as early on HISE as me, and he's done A LOT more work here than any one else, I think he's right - too soon I'm afraid - I suggest you wait until he (or I or someone else), has released a product (or two) and ask again.
Actually this might not be such a good idea, I think I'd want to (and do want to in Kontkat) define audio levels across maps/zones so something might be quiet on purpose. Of course if you mean examine everything in a map and normalise based on the loudest element then yeah sure fine, but if you mean normalise each zone -- bad bad bad.
Looks like your connection to Forum was lost, please wait while we try to reconnect.