@DanH no it figures it out using advanced AI technology:
numWavetables = fileLength / cycleLength.
@DanH no it figures it out using advanced AI technology:
numWavetables = fileLength / cycleLength.
The open source framework for sample based instruments - - allow CSS & scripted LAF within same component · christophhart/HISE@e459f0b
GitHub (github.com)
Long overdue, but it seems that this was really holding people back from CSS...
These are the rules:
Combobox with scripted draw function & CSS styled popupmenu:
const var laf = Content.createLocalLookAndFeel();
// Combobox is styled by a function
laf.registerFunction("drawComboBox", function(g, obj)
{
g.setColour(obj.bgColour);
g.fillRect(obj.area);
g.setFont("Comic Sans MS", 21);
g.setColour(Colours.blue);
g.drawAlignedText(obj.text, obj.area, "centred");
});
// Popup menu is styled by CSS
laf.setInlineStyleSheet("
.popup
{
background: #333;
}
.popup-item
{
background: transparent;
color: #999;
padding: 10px;
}
.popup-item:hover
{
background: rgba(255,255,255, 0.2);
}
.popup-item:active
{
color: white;
font-weight: bold;
}
");
Content.getComponent("ComboBox1").setLocalLookAndFeel(laf);
so how do you want to merge them? Is Alice 31 or 30?
I would refrain from a recursive logic, looks like you have a fixed depth hierarchy that you can just handcode.
don't use the velocity stacking (I think I've removed those). If you don't need to resample acousting material and already have power of two sized wavetables, just load in a sample that has all the wavetables stitched together, and use the resample mode. Ideally you can pass in the cycle length so the chances of the algorithm messing that up is smaller.
At some point we have to address that problem, I notice more and more posts just pasting the rubbish GPT output which dilutes the prestine information set available here in the forum.
Regarding the problem at hand, a single look at one of the many snippets / code examples from a good source should solve that problem, tuck inline
before the function definition and pass it into the call.
@ustk nope once compiled they are a blackbox.
You don‘t need to compile nodes it just makes them faster especially when doing complex stuff and if you need to access them through the API then it‘s definitely a case of leaving them in the interpreted state.
@Oli-Ullmann use the button text as the key in a JSON object with the display string as value then you don‘t need to branch at all.
Also it's not stored as plain text, but as compressed zstd blob, but that won't stop the criminal masterminds of this world.