The big bug tier list

[Lurch]

Clicking a draggablefilterpanel controlling a ParametricEQ within a panel that is disabled will hard crash HISE, and Cubase + Logic once the plugin is compiled. This is a real bummer as my latest plugin uses panels to display a series of effects which users can enable and disable, disabling the panel makes it visibly obvious the effect is off, but if a user was to click the panel they'd hard crash their DAW.

[David Healey]

@LozPetts said in The big bug tier list:

Clicking a draggablefilterpanel controlling a ParametricEQ within a panel that is disabled will hard crash HISE,

I'm pretty sure this bug has been around for a while. Place another panel over the EQ when it's disabled ;)

[HISEnberg]

@Dan-Korneff @ps Just got a report back that the automation system isn't working in Ableton properly. Thanks for sharing your insights.

[Dan Korneff]

Automation bug added here:

https://github.com/christophhart/HISE/issues/749

[Christoph Hart]

@Dan-Korneff I added a comment with a manual fix, please check whether this solves it (it works with my minimal test plugin here but I could use some help in verifying the fix for real world projects as this is a rather sensitive problem).

[Dan Korneff]

@Christoph-Hart excellent. I'll give it a try now.

[HISEnberg]

Not sure if I should post this here or on the Github but I did a pretty deep test on MacOS and everything is working quite smoothly for the automation fix. I tested all types (AU/VST/VST3/AAX) on ProTools, Ableton, Logic, & Bitwig and I haven't had any issues, strange CPU spikes or crashes. Mind you I only tested my janky EchoPlex-FX plugin so will still need to test both an instrument plugin and on Windows.

macOS M2
Sequoia 15.1.1

My hats off to you for the fix @Christoph-Hart !

Edit* I should have shown the automation lane but the sliders are being modulated by automations, not by my mouse!

[Chazrox]

@HISEnberg this looks awesome!!!

[HISEnberg]

@Chazrox haha thanks it was just a small project for a class, now it’s just for running tests!

[bendurso]

https://github.com/christophhart/HISE/issues/761

Wavetable Export – Residual Noise ignored
Preview applies residual noise correctly, but the exported HWT file bypasses it. All other settings are passed as expected.

[DanH]

@Christoph-Hart is the Notch filter display (in Scriptode) a fiddly fix?

[DanH]

@DanH said in The big bug tier list:

@Christoph-Hart

Scriptnode Notch Filter has the incorrect display graph (shows Bandpass) and neither it or the bandpass filter graph respond to Q value changes. Currently impossible to use either with an External Filter Slot on the user interface...

https://github.com/christophhart/HISE/issues/703

Is there any chance of having this remedied in the near future? Makes working with the notch filter a bit confusing

[It_Used]

This post is deleted!

[It_Used]

Envelopes in the scriptnode modulator - not recive Midi CC messages.

How recive midi cc events in scriptnode envelope mod? I has been add a Flex AHDSR, but this is no recive midi cc messages. i tried a more methods for a day, but i didnt take a resault.
Without scriptnode, build-in envelopes has recive midi cc messages...
i use it in sampler gain modulator, use it with sustain pedal, if i use midi_cc node - this is working, progress slider on this node - changed while i press/release my sustain pedal, but if i press pedal - any envelope do not apply sustain on sound.
https://github.com/christophhart/HISE/issues/782

[dannytaurus]

@Christoph-Hart Is there an order for this bug list? I'm happy to work on some and I'd like to do more useful stuff than little edge case stuff.

[David Healey]

@dannytaurus I repeat my annual-ish request for a proper bug/feature tracker :)

[dannytaurus]

@David-Healey And I echo that, but I feel like we already have all we need in GitHub.

If folks aren't going to GitHub to post, upvote and comment on issues, how could we get them to go anywhere else, like Mantis?

I'm going through the GitHub issues to see what I can fix but it would be a lot easier if those issues had snippets, comments and votes.

[David Healey]

@dannytaurus I find the github issues a bit messy, and only Christoph can add tags to issues so there is not really any options in terms of organisation. With a proper tracker the person making the report could add some categorisation to it (priority, severity, etc.) obviously people may misjudge these but it will at least give some indication.

It would also be good to have a voting system. Then we could sort the feature requests by most wanted, for example.

Also there are no issue templates on Christoph's repo - something I also requested - so there is no standardisation to the requests or reports. I think this would be a significant improvement. A good report should include the commit, preferably a snippet, a link to a forum post, OS version, standalone/plugin, etc. An issue template would mostly solve this.

[dannytaurus]

@DanH Fixed here https://github.com/christophhart/HISE/pull/809

[dannytaurus]

@David-Healey All those problems seem fairly easy to fix within GitHub issues.

Tags/Labels

Christoph could assign you, or other trusted members, the Triage role which allows adding and removing labels, apply milestones, mark duplicates, etc.

Triage: Recommended for contributors who need to proactively manage issues, discussions, and pull requests without write access

Voting

We can use emoji reactions for votes and sort by them in the UI.

or in the search bar: is:issue is:open sort:reactions-+1-desc

Issue Template

Adding an issue template is easy enough. Folks might not use it, either as intended or at all. But it's very simple to add it as a PR and have Christoph merge it.