• New
    TomCosaert
    Newcomer - Level 1
    2020-11-18

    Hey! I have a Midas MR18 digital mixer (similar to the Behringer XR18) and want to connect from its (balanced XLR, mono) AUX outputs to the (unbalanced TRS, stereo) AUX inputs of a Behringer HA6000 headphone amplifier.

    Depending on the number of participants (mix-minus feeds for each), I would like to support the following two scenarios:

    1. stereo (L/R) headphone monitoring up to 4 people (Midas MR18 limit)
    2. mono (R+R) headphone monitoring up to 6 people (Behringer HA6000 limit)

    To be sure not to damage anything, I'd rather not start experimenting with different cables. Therefore, I have two questions (and a follow-up question, depending on the answer of the 2nd question):

    Question 1: Would a 2x XLR female to TRS male cable (wired as illustrated below) work for stereo (L/R) headphone monitoring (scenario 1), connecting (paired) MR18 AUX outputs to single AUX inputs of the HA6000?

    This would accomodate 3 headphones (AUX outputs only), or even 4 headphones (if I use the MR18 Main L/R outputs as well), to enjoy stereo monitoring.

    Question 2: Would the same cable also work for mono (R+R) headphone monitoring (scenario 2), when simply not connecting one of the XLR ends and pressing the "MONO R" button on the HA6000, or is leaving the ring (or tip) signal of the TRS cable "floating" like this a really bad idea?

    This would accomodate 6 headphones to be able to monitor in mono (mirrored).

    Question 2b: In case using the same cable for scenario 2 is not recommended (see above, question 2), would an XLR female to TS male cable be advised?

    Thanks a lot for any help with this! I've been searching the internet for hours already, but could not find any definitive answers to these questions. It seems not a straightforward thing, wanting to connect the MR18 to a HA6000, or similar device with unbalanced stereo inputs.

    Note: I currently also own the Behringer AMP800 (which has balanced inputs and allows the use of regular XLR to TRS cables) but I want more connectivity options. Unfortunately, it seems headphone amps with more balanced inputs are not that common.

    read more...
    0 195
    • TomCosaert
      RexBeckett Hi Tom, your cable wiring is correct for dual XLR-F to TRS stereo. This should also work for mono if the HA6000 is switched appropriately.
      • November 18, 2020
      • Midas MR18 AUX Outputs to Behringer HA6000 AUX Inputs
        TomCosaert Thanks for the confirmation. Greatly appreciated!
        • 1
        • ·
        • November 18, 2020
  • filo1465
    Newcomer - Level 1
    2020-09-25

    I have a Pro 2/DL231 issue.

    The system setup is: FoH Pro2 and a monitor Pro 2. The FoH P2 is connected to the AES50 A X port and the Monitor board is connected via the AES50 B X port.

    The Problem: I just did a firmware update on the entire system and it all updated without a problem. However, the monitor board is having issues with the DLs. Please see the attached picture.  It is still passing audio even with this issue but the red status light is keeping me up at night knowing this system has to be used in two days...  

    Maybe the firmware changed some DL Settings? 

    Thanks!

     
    read more...
    0 54
    • filo1465
      Nigel67 Hi Adam. i think that I replied to you on one of the Forums that you posted on. It looks as though you have set up the DL231 to be controlled on the A mic amps, however if you look at the unconfigured they appear to be set up for the B mic amps. If your FOH is working correctly, then it could be a setting on the Mon console. As a quick check, if you go to the Home - Preferences - General page on your console, and at the top of the page in the middle will be your Microphone A or B option. Select B and see if the DL231 then go green. If they do, then the setting was incorrect. If they stay red, then get back to me and we can look further into the problem.
      • September 27, 2020
      • Pro 2 & DL231 Update caused connection issue
        Nigel67 After an update, everything will reset itself to default and the default is the Mic A control.
        • September 27, 2020
      • Pro 2 & DL231 Update caused connection issue
        DavidKnighton I believe this gentleman submitted a CARE ticket and we came to the conclusion that his monitor desk was set to Mic A Inputs. Switched to B inputs and all is well once more
        • 1
        • ·
        • September 28, 2020
      • Pro 2 & DL231 Update caused connection issue
        Nigel67 I made a mistake in one of the last sentences. Doesn't read correctly. But yes, that is what the diagnostics are showing.
        • September 29, 2020
  • ChayoDosis
    Newcomer - Level 1
    2020-09-19
    0 27
    • ChayoDosis
      GaryHiggins I assume you want suggestions to resolve this? I would download the latest M32 firmware file again, extract it. Delete the present version from your usb stick and copy the newly extracted firmware file on to the usb drive. Try to load it again. Your current file might be corrupted. Also try a different usb drive if that fails.
      • September 20, 2020
  • Midas
    Newcomer - Level 1
    2020-07-27

    We're back on Facebook! Like and follow our page here. :)

    read more...
    1 42
  • Midas
    Newcomer - Level 1
    2020-07-01
    We've done some upgrades so you can have a better browsing experience. Visit https://www.midasconsoles.com/ now.
    0 44
  • BillFleming
    Contributor - Level 2
    2020-04-27

    20200425_153809.jpgCH17-32 mapped to A01-A16CH17-32 mapped to A01-A16Ch1-16 mapped to A17-A32Ch1-16 mapped to A17-A32

     

    Good evening, We recently expanded our stage inputs by adding a 2nd DL16 so we now have two DL16s daisychained to the M32. When we were using just one DL16, its stage inputs were identified on the M32 as A17-32, however after adding the new DL16 to the end of the chain the inputs from the first box were shifted up to A1-16 and the new box is now assigned A17-32 (see pics). Is there a way through routing perhaps to have the original box appear as A17-32 and the new box to appear as A1-16? I looked into switching the routing by switching Inputs 1-16 to AES50 A1-16 and Inputs 17-32 to AES50 A17-32 on the Home screen (see pic) but managed to generate some major low frequency feedback (muted the main fader afterwards ), however the Inputs were no longer numbered sequentially as they are in the attached pics, which resulted in all inputs just displaying the letter A instead (which seems right to me). But after hearing the feedback I decided against testing it as I was there by myself so wanted to confirm that I was doing this the right way before locking down the configuration and blowing up our monitors. Thoughts?

    20200425_153809.jpg
    read more...
    0 122
    • BillFleming
      DaveMorrison


      @BillFleming wrote:


      But after hearing the feedback I decided against testing it as I was there by myself so wanted to confirm that I was doing this the right way before locking down the configuration and blowing up our monitors. Thoughts?





      Check the new system at 1/10 of the performance volume?


      The A in the scribble strip refers to the AES50-A bus and the number is the channel number. If you want the original box to be A17-A32, then it needs to be second (after the new DL16). Old DL16 [A] --> [B] new DL16 [A] --> M32. The first DL16 in the chain is 1-16; the second, 17-32; the third 33-48.


      That will put the numbers in the right order, but doesn't explain how they were A17-32 in the first place. Did you replace a different box with the new one?


      If you want us to take a look at the your scene to look for feedback possibilities, you can upload your current scene. Also tell us which DL16 your monitors are connected to and it's switch position.


      Here are (older) instructions for saving/uploading a scene. https://behringerwiki.musictribe.com/index.php?title=Uploading_files_to_the_forum
      Upload by Choose File at the bottom of the window.

      • April 27, 2020
    • BillFleming
      GaryHiggins

      @BillFleming 


      In addition, double check the mode each one is set for. The first one should be in in mode 1 (no led's lit). The second one should be mode 2 (+8 led lit). This would be pertaining to outputs but that could be where the feedback problem was coming from based on where the xlr's outs were then connected. Setting them to the modes above would make by default, out 1-8 assignments come from  #1 and out 9-16 from #2. You can change that in your aes50 output routing if you want.


       


      Inputs if daisy chained as @DaveMorrison said, should be seen at the M32 by whichever DL is physically connected first to it, first would be seen as aes50 a 1-16, second would be aes50a 17-32. You can then of course rout those inputs into whatever input bank desired, so aes50 1-16 could be routed to mixer ch 17-32.

      • April 27, 2020
    • BillFleming
      DaveMorrison

      @BillFleming 


      The letter C is fot the Card (probably USB in your case).


      You can't change the number as it's simply the AES50 channel, but thats really not important. It's just an indicator of what source it comes from (and you can remap them per channels). If you really want A17 to be on channel 1, then make sure that box is second in the chain. On the Routing : Input page, Select AES50-A 17-24 to be bank one and AES50-A 25-32 to be bank two. It's just like you had in you pictures.

      • April 28, 2020
    • BillFleming
      BillFleming

      OK, still a little confused so I'll cut to the chase. Ultimately I want the first box connected to the M32 to be mapped to Inputs A17-A32 and the 2nd box connected to the first box to be mapped to inputs A01-16. You said "You can then of course rout those inputs into whatever input bank desired, so aes50 1-16 could be routed to mixer ch 17-32." which I take to mean that rerouting the way I was going about probably was working, the feedback most likely occurred because I had the mains up too high.


       


      In the meantime I found this pick online which illustrates what I was trying to say originally in that after rerouting the Inputs on the Home menu produces just a letter instead of the Input number - letter C in this pic and in my case the letter A. I take it that I'm going about this the right way, if not let me know if and where I messed up.


       


       


      MidasM32_ScribbleStrip.JPG


       


       


       


      Thanks!

      • April 28, 2020
  • PatrickGMaillot
    Valued Contributor - Level 2
    2020-03-15
    xrrapp.pngxrrtxt.pngCIDG.pngXlive2.0.jpg
     
    2.0 released!
     
    The two applications providing automation for X32 or M32 desks can now also be used for organizing your work files, your mix files for theater or musical performances by using X32 or M32 cues and their text/name as a help to sort or recognize them. Additionally, utilities are added to generate the list of cues to use/load to the desk, and to edit event files generated by the two applications.
     
    All available under the "Products" section of https://x32ram.com
    read more...
    0 57
  • PatrickGMaillot
    Valued Contributor - Level 2
    2019-11-29

    Does this sound familiar? Remember X32ReaperAutoMate? This is the same... with a twist. Same functionalities, including loop control for X-Live and external device support (such as external jog/shuttle/buttons USB devices) Soon available at www.x32ram.comX32LiveAutoMate.jpg

    read more...
    0 147
    • PatrickGMaillot
      PatrickGMaillot Just release the following video: https://youtu.be/xG_onRMkZPk It shows mixing using X32XLiveAutoMate. The resulting automation files will be used by a pro audio engineer in Taiwan to mix, using REAPER this time. The goal is to show compatibility between the X-Live and Reaper versions of the program. Go to https//x32ram.com for X32ReaperAutomat and soon to be released X32XLiveAutoMate
      • November 30, 2019
    • PatrickGMaillot
      PatrickGMaillot Here's the reply from my friend MJ in Taiwan, whom I sent my files to; He was kind enough to send me a small video of his test of the X32XLiveAutoMate Mix files being used with X32ReaperAutoMate, enabling additions or corrections to the Mix made with one platform with the other. Great flexibility. https://youtu.be/lHLDlLrcDKQ
      • December 4, 2019
    • PatrickGMaillot
      PatrickGMaillot News: X32ReaperAutoMate, X32X-LiveAutoMate: Two very powerful automation packages for the X32 or M32 now available at https://X32ram.com, as separate packages or as a bundle with a special deal valid until Dec. 31st! -Patrick
      • December 7, 2019
    • PatrickGMaillot
      PatrickGMaillot X-Live can play loops!!! Watch X32XLiveAutoMate playing X-Live Loops (audio as well as automation): https://youtu.be/TTfEFHptKrU
      • December 8, 2019
  • MikeDrennan
    Contributor - Level 3
    2019-11-18

    Ca someone tell me how to order replacement screws for for attachment of the plastic side panels to the chassis of the M32R?  I think they are T15 torx.  One appears to be about 17mm from head to toe, and the other about 12mm.

    6BFAE8B1-ECB7-422C-8D79-A171F4DC75F6.jpeg

     

    A9E84DF8-E7D9-4EC3-8017-3BFF6819AD28.jpeg

     

    read more...
    0 73
    • MikeDrennan
      LucasLettmann

      i think the easiest and cheapest way would be to go to your local screw/metal dealer and purchase some of these (only cent per piece in packs of 1000)

      • November 23, 2019
  • RayMontreal
    Contributor - Level 2
    2019-11-11

    Hi everyone,

    I hope this video helps to explain my problem, struggling to find the right words in english

     

    https://vimeo.com/372529561 

     

    got a MIdas MR18, I'm trying to use it in Ableton via TouchOSC, to control faders and mute buttons

    Now I'm on a Mac and I tried Osculator, I got everything to work except, for the life of me, I can't get any of my movements from ableton or the mixer to reflect on the TouchOSC.

    Ableton talks fine to the mixer, I just can’t figure out how to send it out to the iPad’s TouchOSC. ,

    My knowledge is limited on OSC and I can’t figure it out (I’m pretty good with technology in general).

    I made a map to kinda show my problem:  

     

    Screen Shot 2019-11-11 at 3.48.22 PM.pngScreen Shot 2019-11-11 at 7.04.25 PM.pngScreen Shot 2019-11-11 at 7.04.34 PM.png

    I need help. LOL

     

    Sorry for the poor English as I am French speaking in Montreal Canada,

     

    Thank you for taking the time to read this very long message!

    read more...
    0 251
    • RayMontreal
      KenMitchell

      Hi @RayMontreal , 


       


      Looks like a fun project.  I love the graphic with the orange arrow and the matching orange text explaining the problem.  Well done.   However, I suspect the problem is actually above it with the connection between the mixer and Osculator.   In order to get feedback back from the MR18, Osculator has to listen for those messages as well as periodically re-subscribe to updates.   A couple of years ago a developed a utility called XAirRemote to serve as a bridge between OSC clients (TouchOSC, Lemur, etc) and the XAir/MAir mixers.  I hadn't thought about it but Osculator should be able to be used as a client as well.  


       


      Here's a link to the utility: https://sites.google.com/site/xairutilities/XAirRemote-1_2-OSX.zip?attredirects=0&d=1


       


      In your setup, you'll want to set it up between Osculator and the MR18. 


       


      Let me know what questions you have about the setup. 


       


      Ken

      • November 11, 2019
    • RayMontreal
      RayMontreal

      Well, first of all a very big thank you for replying to my message!


      The MR18 is currently being kept alive with an OSC Message (/xremote) tied to the Beat, so as long as Ableton is playing, the MR18 is alive and also in Ableton, if I move a fader, it does reflect it on the MR-18,


      so that part works! it's just not also being sent to the iPad...


      I want to duplicate the backmapping in Osculator so that it sends it also to the iPad, I just don't know how to get Osculator "talking" to MR-18 AND iPad at the same time. that Ð (and L and 1-16 in Osculator) is super confusing to me and I don't know how to deal with it.


      Having Osculator in there is already a big move for me as I prefer having a very bare minimum of apps open during shows...


      will definitely try your app, thank you!


      but if it's job is to keep MR18 awake, I am already doing that in Osculator and that is working.


      Best,


       


      Ray


       

      • November 11, 2019
    • RayMontreal
      RayMontreal

      my ini file looks like this:


      1 0 0 1 0
      1 16 17 17 18 21 40 45 46 49 51 54 0
      <92.168.0.123>
      <192.168.0.105>
      <192.168.0.182>
      <8000>
      <8000>
      #EOF


      but the MR18 listens to 10024 not 10023 like the XR18, so I think it might be the reason I'm getting a tail like;


       


      OSC Controller at IP <192.168.0.105>, receives on port <8000>, sends to port <8000>


        Listening for OSC Controller on <192.168.0.182>:<8000>


        Flags: verbose: 1, delay: 0ms, Transport: 0, Master: 1, Sync: 0


        Map (min/max): Ch 1/16, Aux 17/17, FxR 18/21, Bus 40/45, FxS 46/49, DCA 51/54, Bus Offset 0


       


      *******************************************************************************************


        Start of Log data:


       


      ->X,    8 B: /info~~~


      XAirConnect: Error sending data to XAir


       


       


       

      • November 11, 2019
    • RayMontreal
      KenMitchell

      Hi Ray, 


       


      The XR18 also uses 10024. 10023 is what the X32 uses. 


       


      Remove the "<" and ">" from the IP addresses and ports in your ini file.  


       


      You've also got <92.168.0.123> which I suspect should be 192.168.0.123.


       


      Ken

      • November 11, 2019
    • RayMontreal
      RayMontreal

      correctly writing my ini file made your app work,


      your app now logs correctly but I dont know what that brings to the table,


      in the tail I see both ipad and mr18 messages show up in the log


      but when I start osculator, it says port 8000 already being used error.


       


      I will NOT give up, my brain is struggling, but there has got to be a way to make all this work! haha

      • November 11, 2019
Go to page