The big bug tier list
-
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!
-
@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)
-
@aaronventure applied the workaround - keyboard works (great) but error message still appears upon loading Hise.
-
@DanH yep, happens here occasionally as well
-
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)
-
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!
[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)
-
@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.
