The big bug tier list
-
Not so funny one. Doesn't quite blow up here, the signal is below audible range, but the network just dies (no output) and HISE must be restarted.
-
Might finally be time for Melatonin to take over?
-
This is annoying for anyone who doesn't read the docs THOROUGHLY or read the forum properly, but the workaround is easy: simply enable the queue. Perhaps it should be enabled by default for mouse broadcasters that aren't realtime?
-
Not being able to set the mouse sensitivity property for the built in sliders for this long... So either be happy with the HISE speed on shift or go and make a panel, which gets fun if you need MIDI mapping and DAW automation.
-
-
-
Better check your text on all systems thoroughly!
There's a title that I used a font for, which I had to break into two separate graphics calls to manually adjust kerning that way.
-
This is probably my #1. Timers work, yes, but multiplying every single setColour call with them just to get fades... Not to mention the poor message thread...
-
This is my #2. MIDI FX could use some love.
-
Ok here's the one about Channel Aftertouch not working correctly in all situations - to emphasise Channel aftertouch, not poly aftertouch...
-
posts that get no upvote are deleted after some time so that we can ensure that it's only the heavy hitters in this topic.
Respectfully, I don't think that's an effective way to improve HISE. Certain issues are simply more important than others, regardless of anyone experiencing them. And self-selection bias reinforces existing issues. Just my $0.02.
-
@aaronventure said in The big bug tier list:
This is annoying for anyone who doesn't read the docs THOROUGHLY or read the forum properly, but the workaround is easy: simply enable the queue. Perhaps it should be enabled by default for mouse broadcasters that aren't realtime?
Not just this, but all the issues in HISE like this. Reliability and API Logic, first. Performance, second. The API should respond as it implies, and be generalised as such. I realise that HISE only works its magic because of many (very clever, and hard-fought) hand-optimisations, and doing the first has implications for the second that I do not know.
-
Breakpoints don't work. HISE can crash by enabling them. They don't need to be fixed, but if not, should be removed from the UI.
-
There is no functional SAVE command in HISE, and the menu items are confusing. (Workflows can have bugs.)
-
This post is deleted! -
@Christoph-Hart All caching, that can result in incorrect data, should be disablable with a single flag. (Also, "disablable" is not a word, but also not a HISE issue.)
-
@Christoph-Hart Things working better > backwards compatibility. Reduce complexity. Don't introduce new API calls to get around other issues.
-
I don't understand the purpose of this. Are there rules that aren't being followed in terms of reporting bugs here? I'd like to know if I reported something badly or not.
-
A critical issue that prevents us from using the neural network node in a commercial plugin. My #1.
-
Another critic one.
