HISE Logo Forum
    • Categories
    • Register
    • Login

    Snex node - Change the error message when a soundcard isn't found

    Scheduled Pinned Locked Moved Feature Requests
    4 Posts 3 Posters 317 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.
    • O
      Orvillain
      last edited by

      a6187b89-2b93-4b1c-adca-9c6043086d78-image.png

      So I spent a bit of time chasing my tail because of this. I left my code in a working state last night at about 2am (lol!) and came to it this evening, and was so confused why the node wouldn't compile.

      The error message is super super non-useful to be honest. I thought it was to do with the node, but it isn't. It's to do with my soundcard not being active.

      I would suggest a better error message. Something like:
      "Output channels not found. Node cannot pass audio. Check your audio interface settings."

      Because - call me stupid idiot boy from a village - I had no idea this was in reference to my audio interface. I thought something had gone wrong with the node specifically.

      A 1 Reply Last reply Reply Quote 0
      • A
        aaronventure @Orvillain
        last edited by

        @Orvillain depends on how the error is checked for and if no interface is an error in the first place. HISE is pretty loose with restoring interface selections, remembering preferences about this, as well as about midi devices, and it all resets on a crash.

        Luckily, you can hardcode the whole logic, including fallbacks, right into your script. https://forum.hise.audio/topic/9722/tip-hardcode-your-dev-environment-audio-setup

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

          Yes the SNEX nodes are particularly pedantic when it comes to channel configurations (because it will compile the code for each channel that is requested).

          How can I recreate this issue? I'm not sure how it could end up with a channel count of zero, as this is usually set by the surrounding script FX which should not depend on the audio driver configuration.

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

            @Christoph-Hart said in Snex node - Change the error message when a soundcard isn't found:

            Yes the SNEX nodes are particularly pedantic when it comes to channel configurations (because it will compile the code for each channel that is requested).

            How can I recreate this issue? I'm not sure how it could end up with a channel count of zero, as this is usually set by the surrounding script FX which should not depend on the audio driver configuration.

            I've been having some issues with my Presonus Quantum. Every other boot of my system, the card will not connect. I didn't notice the big bright red light on the front of it, telling me it couldn't connect to the OS.

            I started HISE, and noticed the SNEX node like in the screenshot. So I would assume connecting HISE to an audio interface, and then pulling the connection on it, would probably reproduce the issue.

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

            38

            Online

            1.7k

            Users

            11.7k

            Topics

            102.2k

            Posts