The big bug tier list
-
@Christoph-Hart Low priority for most I guess, but needed for me in my latest released plugin (sorry for being selfish
)
Wierd behaviour of the MidiOverlayPanel Floating Tile. I'm using it to drag'n'drop MIDI files into the DAW.https://github.com/christophhart/HISE/issues/678
Hurray Hurray! Here comes the Debugger ! 🥳
-
Server.downloadFile() doesn't follow redirects properly
-
This post is deleted! -
chanting Lets go Christoph! Lets GO!
Im sure all my bugs are covered here so im just sending some good energy! haha
@Christoph-Hart
-
@Christoph-Hart HISE_NUM_STANDALONE_OUTPUTS Error // Channel Amount Mismatch on every start
https://github.com/christophhart/HISE/issues/692
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!
-
@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
-
@aaronventure applied the workaround - keyboard works (great) but error message still appears upon loading Hise.
-
@DanH yep, happens here occasionally as well
-
-
ScriptNode Clone Nodes don't compile under some circumstances. Verified with other developers.
-
Code-only UI declaration is broken because of this. This bug seems to have been around for at least 2.5 years!
-
@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.
-
@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.
-
@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
-
This bug's been present for a while, but will likely become more noticeable as the new pitch_shift node is implemented.
-
@Christoph-Hart Two tick marks in a combobox popup. This has already been mentioned here somewhere. A screenshot and a snippet are in the GitHub issue.
-
-
Clones in ScriptNode don't work. I've posted three threads of examples which multiple devs have confirmed.
-
PluginParameters are not working anymore.
I assume since the new system there is a major bug that the plugin parameter is creating a loop reporting back the value which breaks automations in Ableton Live (i assume also major problem for other DAWS). As not everyone maybe tries if automations are still working when pushing an update I thought it's important to mention as it fully breaks automations.
Recreate: one slider - pluginParameter == true - compile and try to automate - live will instantly behave as if there was an interference. -
@ps Mmmm... That might be why I have a customer experiencing a bug, failing LogicPro validation... (though it works on some systems like mine)
