Statistics

250,514 members
127,680 posts
  • New
    Regie
    Newcomer - Level 1
    2021-05-11
    How to have a good configuration between an HD96/24 and a DL251 ? When I try to connect both together, using the "patching/add new/autodetect" topic in the HD96, I have 2 DL251, both in "active - partial" status. When I use the I/O update manager in the Heritage, I can see that the DL251 is in "HD 0.18.0" version but I don't know what is this version ? When I try to update directly the DL with a PC and MIDAS-IO-Updater-v1to set-up the last firmware "PROXG3.4.6rel-9 " I have a "communication failed" message during the update and no possibility to know the firmware version in the DL. When I connect the DL to a mac with the IP adress, I can only see few information (see in the screenshot linked to this message). Is there someone who can help me to understand what is the problem and if its coming from the HD96 or from the DL251 ? Many thanks for the help
    View Attachment
    read more...
    0 70
    • Regie
      ChaseMcKnight Hi Regie,


      Firmware HD 0.18.0 is the correct version for the DL251 to work with the HD96. Are you connecting the two DL251s via the four local AES50 ports or from one of the Snake Ports / DN9680?

      What firmware version is the HD96 on?
      Do you have green lights at the DL251? How about at the HD's AES50 ports?
      Are you able to manually configure the DL251 ports in Patching? (instead of auto detect)

      On the HD, please verify settings in Preferences / Console Configuration / DSP Configuration:


      Clock Options set to Master

      SuperMac redundancy is turned OFF
      HyperMac redundancy is turned OFF

      On DL251, please verify:

      DL251 are on different IDs (1 & 2)
      DL251 front panel settings:
      Clock External

      Sample Rate 96kHz

      Control Mode 1

      If your settings are correct and are still unable to connect, please open a ticket so we can troubleshoot deeper.

      

Thanks,
      • May 11
  • New
    djsuperdock
    Newcomer - Level 1
    2021-02-10

    Here is my current setup with these components: 

    2 Behringer s16s daisy chained together, then connected to FOH x32 via the first s16's AES50-A port (2nd s16 is set to "out +8" mode).

    Playback laptop on stage using Klark Teknik DN9630 connected via ethernet to the open AES50-B port on the 2nd s16 unit.

    Routing at the x32 console has all inputs set to AES50-A. The first 24 inputs are set to AES50-A 1-24.

    Then, interestingly, to find the inputs coming from the Klark Teknik interface, the last 8 inputs are set to AES50-A 32-40. So AES50-A 25-32 are skipped over which is fine with our setup - all of our physical instruments can be connected to those first 24 inputs. 

    My question is this - I want to get more than 8 channels from the laptop to the x32. I figured that I could simply use the Aux-Ins on the console - by setting the aux-in to "user 1-6" and then defining those user inputs to AES50-A 41-46 (picking up where the other channels were coming in). But when do this AND set up my laptop to send more channels, I am not getting anything at FOH. 

    Any thoughts about what I could be doing wrong? 

     


    View Attachment
    read more...
    0 100
    • djsuperdock
      DavidKnighton Hello djsuperdock,
      Would you be able to upload your scene or provide a link to where we can download and take a peek at your routing setup first hand? I have too many questions to ask, and it would be easier to just glance at the routing. Then I could feasibly pinpoint your issue.
      • Feb 10
      • Klark Teknik DN9630 interface -- Behringer s16 -- Behringer x32 Ecosystem Question
        djsuperdock I'm not at my mixer now but just saved the scene I have on my x32 edit which I just used with the board earlier today. It should be attached to the discussion now.
        • Feb 10
      • Klark Teknik DN9630 interface -- Behringer s16 -- Behringer x32 Ecosystem Question
        DavidKnighton I checked your scene routing and you have but 1 channel from 41-48 assigned to the USER IN 1-8. Might I suggest a test. Assign AES50 41-48 to any bank of input channels and just make sure you're getting something. This will confirm or deny whether there is signal present on those channels. Then you can try a repatch the Aux inputs how you want.
        • Feb 11
    • djsuperdock
      GaryHiggins I think your main issue may be interconnection, the S16's don't transmit their xlr inputs via their B port, B ports of the S16 are fixed to deliver specific aes50 ch's from the FOH mixer. The 2 S16.s in turn would shift the 9630 upstream intended ch's by 32 such that whatever is meant to head to foh from the 9630 will show up as aes50a 33-48 at foh. If more than 16 ch's, they will exceed the 48 ch limit and be 'out of bounds' You probably need to connect the 9630 to it's own port on the mixer and rout any S16 inputs to it via aes50 from FOH. My 2 cents.
      • Feb 10
      • Klark Teknik DN9630 interface -- Behringer s16 -- Behringer x32 Ecosystem Question
        djsuperdock What you're saying about the 2 s16s bumping the interface up makes sense and is consistent with what I am experiencing. My first 8 inputs from the 9630 show up at AES50a 33-40. But then why wouldn't I simply be able to send more inputs to the 9630 and have them show up at AES50a 41-48?
        • Feb 10
      • Klark Teknik DN9630 interface -- Behringer s16 -- Behringer x32 Ecosystem Question
        GaryHiggins The next 8 outputs from the 9630 would show up as input ch’s aes50a 41-48 at foh. Inputs TO the 9630 would be via the foh mixer aes50a out 1-48 menu. To use the xlr inputs of the s16’s in this way you would need to send aes50a inputs 1-32 from the mixer via aes50a out 1-32 (aes50a out 1-32 must say aes50a 1-32 in groups of 8) by default it would now say out 1-8, out 9-16, out 1-8 and out 9-16 again.
        • Feb 10
      • Klark Teknik DN9630 interface -- Behringer s16 -- Behringer x32 Ecosystem Question
        GaryHiggins I still think you would be better off with a dedicated port for the 9630, no shifting of ch’s from it and more straightforward routing to it. Keeps your S16 outs more flexible too.
        • Feb 10
    • djsuperdock
      StephenEvans The S16s are not really meant to be a AES50 hub in the way you want to use them. It would be much better to connect to the AES50B port on the X32, you would be able to do much more flexible routing that way
      • Feb 11