HISE Logo Forum
    • Categories
    • Register
    • Login

    Audio inputs aren't working anymore

    Scheduled Pinned Locked Moved Bug Reports
    21 Posts 4 Posters 1.1k 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.
    • ustkU
      ustk
      last edited by ustk

      @Christoph-Hart Since I've pulled the last commits to my branch I cannot have audio inputs anymore.
      The culprit seems to be the - added audio & MIDI clip file drop to DAW timeline simulator commit.

      I still FORCE_INPUT_CHANNELS like before but nothing... (so it's not related to the USE_BACKEND flag that comes with that commit, which anyway is 1 obviously)

      So is it possible for the two friends to coexist? (audio IN and Timeline Simulator)

      Can't help pressing F5 in the forum...

      d.healeyD ustkU 2 Replies Last reply Reply Quote 0
      • d.healeyD
        d.healey @ustk
        last edited by

        @ustk Might be related to this - https://forum.hise.audio/topic/7055/fix-channel-resizing-in-hise-broke-my-routing

        Libre Wave - Freedom respecting instruments and effects
        My Patreon - HISE tutorials
        YouTube Channel - Public HISE tutorials

        ustkU 1 Reply Last reply Reply Quote 0
        • ustkU
          ustk @d.healey
          last edited by ustk

          @d-healey Well that's what I thought at first so I reverted this one but with no luck.
          It's the one before that causes my troubles (the input stream is back when reverted)...

          Two commits, two issues 😝

          Can't help pressing F5 in the forum...

          1 Reply Last reply Reply Quote 1
          • ustkU
            ustk
            last edited by

            @Christoph-Hart Have you had the time to analyse this issue, please?

            Can't help pressing F5 in the forum...

            1 Reply Last reply Reply Quote 0
            • ustkU
              ustk
              last edited by

              Bump bump

              Can't help pressing F5 in the forum...

              ustkU 1 Reply Last reply Reply Quote 0
              • ustkU
                ustk @ustk
                last edited by

                @Christoph-Hart Hmm... Nothing on this issue?

                Can't help pressing F5 in the forum...

                d.healeyD 1 Reply Last reply Reply Quote 0
                • d.healeyD
                  d.healey @ustk
                  last edited by

                  @ustk Have you figured out which commit caused the issue?

                  Libre Wave - Freedom respecting instruments and effects
                  My Patreon - HISE tutorials
                  YouTube Channel - Public HISE tutorials

                  ustkU 1 Reply Last reply Reply Quote 0
                  • ustkU
                    ustk @d.healey
                    last edited by

                    @d-healey In the first post ;)

                    Can't help pressing F5 in the forum...

                    DanHD 1 Reply Last reply Reply Quote 2
                    • DanHD
                      DanH @ustk
                      last edited by

                      @ustk did this ever get solved?

                      DHPlugins / DC Breaks | Artist / Producer / DJ / Developer
                      https://dhplugins.com/ | https://dcbreaks.com/
                      London, UK

                      ustkU 1 Reply Last reply Reply Quote 0
                      • ustkU
                        ustk @DanH
                        last edited by

                        @DanH I'm not sure actually, as I use my own Hise branch where I reverted the commit that was causing the issue...
                        And for whatever reason, I can have my branch running in Xcdode with no troubles while the develop branch always fires an assertion, but this might not be related to that reverted commit...

                        Can't help pressing F5 in the forum...

                        DanHD 1 Reply Last reply Reply Quote 0
                        • DanHD
                          DanH @ustk
                          last edited by

                          @ustk ah yes I remember you edited the source code to enable the inputs, is that right?

                          DHPlugins / DC Breaks | Artist / Producer / DJ / Developer
                          https://dhplugins.com/ | https://dcbreaks.com/
                          London, UK

                          ustkU 1 Reply Last reply Reply Quote 0
                          • ustkU
                            ustk @DanH
                            last edited by

                            @DanH Exactly

                            Can't help pressing F5 in the forum...

                            DanHD 1 Reply Last reply Reply Quote 0
                            • DanHD
                              DanH @ustk
                              last edited by

                              @ustk was it a simple edit?!

                              DHPlugins / DC Breaks | Artist / Producer / DJ / Developer
                              https://dhplugins.com/ | https://dcbreaks.com/
                              London, UK

                              ustkU 1 Reply Last reply Reply Quote 0
                              • ustkU
                                ustk @DanH
                                last edited by

                                @DanH we talked about it together here :)
                                https://forum.hise.audio/topic/6875/macos-microphone-access-issue

                                Can't help pressing F5 in the forum...

                                DanHD 1 Reply Last reply Reply Quote 0
                                • DanHD
                                  DanH @ustk
                                  last edited by

                                  @ustk haha! I thought I remembered something 😆

                                  13 files... that's a lot! If you're willing to share details let me know, no problems if not! :)

                                  DHPlugins / DC Breaks | Artist / Producer / DJ / Developer
                                  https://dhplugins.com/ | https://dcbreaks.com/
                                  London, UK

                                  1 Reply Last reply Reply Quote 0
                                  • ustkU
                                    ustk @ustk
                                    last edited by

                                    @Christoph-Hart

                                    @ustk said in Audio inputs aren't working anymore:

                                    @Christoph-Hart Since I've pulled the last commits to my branch I cannot have audio inputs anymore.
                                    The culprit seems to be the - added audio & MIDI clip file drop to DAW timeline simulator commit.

                                    I still FORCE_INPUT_CHANNELS like before but nothing... (so it's not related to the USE_BACKEND flag that comes with that commit, which anyway is 1 obviously)

                                    So is it possible for the two friends to coexist? (audio IN and Timeline Simulator)

                                    Would this be possible to have it fixed, please, Christoph?

                                    Can't help pressing F5 in the forum...

                                    1 Reply Last reply Reply Quote 0
                                    • ustkU
                                      ustk
                                      last edited by ustk

                                      @Christoph-Hart Found the culprit... Is it safe to do this?

                                      void BackendProcessor::processBlock(AudioSampleBuffer& buffer, MidiBuffer& midiMessages)
                                      {
                                      #if !HISE_BACKEND_AS_FX && !FORCE_INPUT_CHANNELS // <- Added the FORCE_INPUT_CHANNELS preprocessor def
                                      	buffer.clear();
                                      #endif
                                      

                                      If ok for you I'll push a request

                                      Can't help pressing F5 in the forum...

                                      1 Reply Last reply Reply Quote 0
                                      • ustkU
                                        ustk
                                        last edited by

                                        @Christoph-Hart Hmmm... Something else happened on top of everything. Somehow, the input is directly sent to the output internally.

                                        It's always been the case since I opened up the possibility of activating the inputs (and I think it's totally normal), but a muter in a container always solved this to keep the separation.

                                        Now even with a muter, the input is still leaking into the output and completely ruins my project. I wonder if this can be related to the recent channel fix/improvement you've made. Any idea how to solve this or at least where to look?

                                        Can't help pressing F5 in the forum...

                                        ustkU 1 Reply Last reply Reply Quote 0
                                        • ustkU
                                          ustk @ustk
                                          last edited by ustk

                                          @Christoph-Hart Seems that I found the culprit, but please I need your light to see if it's safe.

                                          I re-enabled the following lines that were removed by the commit https://github.com/christophhart/HISE/commit/799694e1f330fd82aa827a36b756ffa4e14d4d7d,
                                          but this time with an inverted preproc like in the screenshot (it was !FORCE_INPUT_CHANNELS)

                                          Screenshot 2023-05-05 at 19.28.42.png

                                          Without this fix and with the FORCE_INPUT_CHANNELS flag enabled, audio input is summed twice because I do this too to get the inputs working:
                                          (this explains why a muter just removed one part of the signal while the rest was still going through)

                                          
                                          void BackendProcessor::processBlock(AudioSampleBuffer& buffer, MidiBuffer& midiMessages)
                                          {
                                          #if !HISE_BACKEND_AS_FX && !FORCE_INPUT_CHANNELS // added !FORCE_INPUT_CHANNELS to keep inputs
                                          	buffer.clear();
                                          #endif
                                          

                                          Will this cause big problems?

                                          Can't help pressing F5 in the forum...

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

                                            @ustk yes this will mute any sound created in child containers which is why I pushed that commit.

                                            ustkU 1 Reply Last reply Reply Quote 0
                                            • First post
                                              Last post

                                            20

                                            Online

                                            1.7k

                                            Users

                                            11.8k

                                            Topics

                                            102.4k

                                            Posts