The big bug tier list

[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.

[Lindon]

@dannytaurus said in The big bug tier list:

@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.

Well if you are looking for an important one that (I think) is pretty easy to diagnose and fix.....

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

[dannytaurus]

@Lindon Should be fixed here: https://github.com/christophhart/HISE/pull/810

Haven't tested with a real controller yet, but in the code the 128 and 129 CCs were flipped, which would cause weird behaviour.

[dannytaurus]

@DanH said:

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

Fixed with this PR: https://github.com/christophhart/HISE/pull/809

[David Healey]

@dannytaurus You're on fire!

[dannytaurus]

@aaronventure said in The big bug tier list:

Code-only UI declaration is broken because of this. This bug seems to have been around for at least 2.5 years!

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

Fixed here: https://github.com/christophhart/HISE/pull/811

[dannytaurus]

@David-Healey Best way to learn!

[DanH]

@dannytaurus working

[DanH]

@dannytaurus although in scriptnode it still seems to display the bandpass graph rather than the notch? Weird, in the UI FilterDisplay floating tile it works fine!

Perhaps I didn't pull it into my fork properly?

[dannytaurus]

@DanH Seems to be working here: