The big bug tier list
-
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.
8 Times more CPU consumption on Aida-X Neural Models · Issue #710 · christophhart/HISE
HISE exported plugin consumes 8 times more CPU than the Aida-X plugin, the same model is installed and there is nothing extra. This is obviously quite a lot. Forum post: https://forum.hise.audio/topic/11326/8-times-more-cpu-consumption-o...
GitHub (github.com)
-
Another critic one.
Effect Slot (HardcodedMasterFX) cannot open custom nodes with more than 2 channels · Issue #711 · christophhart/HISE
As the title says. Forum post: https://forum.hise.audio/topic/11005/using-2-and-multiple-channels-together-in-the-effect-slot?_=1743078046553
GitHub (github.com)
-
@Christoph-Hart Although it seems a good action on you behalf, I don’t really see the purpose of this thread. It’s like going back in the days where we were constantly asking for fixes in the forum and you said that if we want better chances to see them corrected, we have to open an issue on git. And that’s what we are doing, but they are often not treated, letting us in a state of despair… (yeah I know I’m just trying to draw a teardrop from you, Chris
)So in the end, is the only goal here to get a vote system?
I’m sure that the priorities can be easily seen from the issue list, and then taken in order until the « full » issue list is cleaned.I am not trying to print a bad feeling to this thread. It’s just that it’s already a pain sometimes to report issues that have already been reported multiple times (sometimes over a very ling period of time), as well report them in git, and finally see we have to do it again here.
Or maybe it’s just me and my laziness talking, and in no way I want to be demotivational or disheartening, I’d just like a bug report system we can really be relying on and trust, as a sustainable system
-
Guys this is not the final solution to the problem, it‘s just a way to find out for me at this point in the timeline which of the 100+ issues I should prioritize in order to remove blockers for the majority of people.
The proper way to report bugs is still the Github issue list.
-
@Orvillain I think @Christoph-Hart is simply being kind in opening it up for people who don't know the bug-reporting system, and also allowing for public commentary here on the forum.
-
@Christoph-Hart said in The big bug tier list:
The proper way to report bugs is still the Github issue list.
Reply
Genuinely, this was news to me. Oops.
-
@Christoph-Hart Shape FX shows no graph except for 'Curve':
Shape FX shows no graph except for 'Curve' · Issue #712 · christophhart/HISE
Except for the ‘Curve’ algorithm, the Shape FX module does not display a graph of the waveshaping function.
GitHub (github.com)
-
@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.MidiOverlayPanel bug in DAW project reload. · Issue #678 · christophhart/HISE
To reproduce the issue: the HISE project simply has to include a floating tile set to. 'MidiOverlayPanel'. Details: When loading the plugin in a blank project: the tile is correctly displayed. When loading a saved project in the DAW - wi...
GitHub (github.com)
Hurray Hurray! Here comes the Debugger ! 🥳
-
Server.downloadFile() doesn't follow redirects properly
Server.downloadFile() doesn't follow redirects properly · Issue #713 · christophhart/HISE
When I download a file from my WooCommerce site using Server.downloadFile() WooCommerce records it as two downloads having been used. If I download from the same URL via CURL (with the -L flag) or via my browser then it is correctly reco...
GitHub (github.com)
-
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
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!
