The big bug tier list

[DanH]

@Christoph-Hart HISE_NUM_STANDALONE_OUTPUTS Error // Channel Amount Mismatch on every start

HISE_NUM_STANDALONE_OUTPUTS Error // Channel Amount Mismatch on every start. · Issue #692 · christophhart/HISE

Issue snip:

GitHub (github.com)

This one has been driving me nuts

Appreciate it doesn't happen for everyone but I have to re-set my midi controller in the Hise settings every time I open Hise!

[aaronventure]

@DanH said in The big bug tier list:

but I have to re-set my midi controller in the Hise settings every time I open Hise!

this happens on crashes too, but I've been using this for a long time now and completely forgot that this is still actually an issue

https://forum.hise.audio//post/80689

defo not a long term solution but might help your sanity until it gets fixed. the fact that I can hardcode it like that with a few lines of code and it remains consistent through everything means it should not be that hard of a fix so we never ever have to go back and change it

There we go, I made an issue for this

[UX] HISE sometimes resets audio device and midi device settings · Issue #716 · christophhart/HISE

This happens on crashes and some other instances. I made a workaround here https://forum.hise.audio//post/80689 and forgot about this, but it is a major issue. HISE should never manually reset the selection of an audio device or a MIDI d...

GitHub (github.com)

[DanH]

@aaronventure applied the workaround - keyboard works (great) but error message still appears upon loading Hise.

[aaronventure]

@DanH yep, happens here occasionally as well

[d.healey]

Timestretch causing pops and white noise · Issue #718 · christophhart/HISE

I'm finding that enabling time stretching on a sampler is causing artefacts during playback, even with the ratio unchanged. Forum thread: https://forum.hise.audio/topic/11966/bug-timestretch-causing-pops-and-white-noise

GitHub (github.com)

[clevername27]

ScriptNode Clone Nodes don't compile. Verified with other developers.

[aaronventure]

Code-only UI declaration is broken because of this. This bug seems to have been around for at least 2.5 years!

[Engine] setZLevel() doesn't execute on init · Issue #731 · christophhart/HISE

const button = Content.addButton("btn", 0, 0); const panel = Content.addPanel("pnl", 0, 0); button.setZLevel("Front"); It has to be called with a delay so that it executes after init, because calling in during init does nothing. Also, ca...

GitHub (github.com)

[d.healey]

@aaronventure said in The big bug tier list:

Code-only UI declaration is broken because of this.

Declare your components in the order you want them to be at init.

[aaronventure]

@d-healey ah that's true, but that will forces a way of grouping components by place instead of functionality and messes with certain aspects of modularity. Also, you have to delete the entire component list every time you want to make a change, which means that you have to do the UI entirely in code (else you lose any property changes you put in by hand.

Kontakt had Z_LAYER since 2017.

[Christoph Hart]

@aaronventure don't want to derail this topic from its intentional purpose, but you can easily rebuild the component tree by clicking on the refresh button in the interface designer, this way you don't have to

do the UI entirely in code