HISE Logo Forum
    • Categories
    • Register
    • Login

    The big bug tier list

    Scheduled Pinned Locked Moved Bug Reports
    72 Posts 20 Posters 24.5k Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • A
      aaronventure
      last edited by

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

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

      1 Reply Last reply Reply Quote 3
      • A
        aaronventure
        last edited by

        This is my #2. MIDI FX could use some love.

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

        1 Reply Last reply Reply Quote 3
        • LindonL
          Lindon @Christoph Hart
          last edited by Lindon

          @Christoph-Hart

          Ok here's the one about Channel Aftertouch not working correctly in all situations - to emphasise Channel aftertouch, not poly aftertouch...

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

          HISE Development for hire.
          www.channelrobot.com

          1 Reply Last reply Reply Quote 3
          • C
            clevername27 @Christoph Hart
            last edited by

            @Christoph-Hart

            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.

            1 Reply Last reply Reply Quote 2
            • C
              clevername27 @aaronventure
              last edited by clevername27

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

              1 Reply Last reply Reply Quote 0
              • C
                clevername27
                last edited by

                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.

                1 Reply Last reply Reply Quote 0
                • C
                  clevername27
                  last edited by clevername27

                  There is no functional SAVE command in HISE, and the menu items are confusing. (Workflows can have bugs.)

                  1 Reply Last reply Reply Quote 1
                  • C
                    clevername27 @Christoph Hart
                    last edited by

                    This post is deleted!
                    1 Reply Last reply Reply Quote 0
                    • C
                      clevername27 @Christoph Hart
                      last edited by clevername27

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

                      1 Reply Last reply Reply Quote 0
                      • C
                        clevername27 @Christoph Hart
                        last edited by

                        @Christoph-Hart Things working better > backwards compatibility. Reduce complexity. Don't introduce new API calls to get around other issues.

                        1 Reply Last reply Reply Quote 0
                        • OrvillainO
                          Orvillain
                          last edited by

                          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.

                          Musician - Instrument Designer - Sonic Architect - Creative Product Owner
                          Crafting sound at every level. From strings to signal paths, samples to systems.

                          C 1 Reply Last reply Reply Quote 0
                          • orangeO
                            orange
                            last edited by orange

                            A critical issue that prevents us from using the neural network node in a commercial plugin. My #1.

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

                            develop Branch / XCode 13.1
                            macOS Monterey / M1 Max

                            1 Reply Last reply Reply Quote 5
                            • orangeO
                              orange
                              last edited by orange

                              Another critic one.

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

                              develop Branch / XCode 13.1
                              macOS Monterey / M1 Max

                              1 Reply Last reply Reply Quote 5
                              • ustkU
                                ustk @Christoph Hart
                                last edited by

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

                                Hise made me an F5 dude, browser just suffers...

                                Christoph HartC 1 Reply Last reply Reply Quote 1
                                • Christoph HartC
                                  Christoph Hart @ustk
                                  last edited by

                                  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.

                                  OrvillainO Matt_SFM 2 Replies Last reply Reply Quote 6
                                  • C
                                    clevername27 @Orvillain
                                    last edited by

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

                                    1 Reply Last reply Reply Quote 1
                                    • OrvillainO
                                      Orvillain @Christoph Hart
                                      last edited by

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

                                      Musician - Instrument Designer - Sonic Architect - Creative Product Owner
                                      Crafting sound at every level. From strings to signal paths, samples to systems.

                                      1 Reply Last reply Reply Quote 0
                                      • C
                                        Consint @Christoph Hart
                                        last edited by Consint

                                        @Christoph-Hart Shape FX shows no graph except for 'Curve':

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

                                        1 Reply Last reply Reply Quote 0
                                        • Matt_SFM
                                          Matt_SF @Christoph Hart
                                          last edited by Matt_SF

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

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

                                          Hurray Hurray! Here comes the Debugger ! 🥳

                                          Develop branch
                                          Win10 & VS17 / Ventura & Xcode 14. 3

                                          1 Reply Last reply Reply Quote 6
                                          • d.healeyD
                                            d.healey
                                            last edited by

                                            Server.downloadFile() doesn't follow redirects properly

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

                                            Free HISE Bootcamp Full Course for beginners.
                                            YouTube Channel - Public HISE tutorials
                                            My Patreon - HISE tutorials

                                            1 Reply Last reply Reply Quote 3
                                            • First post
                                              Last post

                                            14

                                            Online

                                            2.0k

                                            Users

                                            12.7k

                                            Topics

                                            110.4k

                                            Posts