Statistics

254,455 members
132,142 posts
  • hollywood
    Contributor - Level 3
    2020-03-25

    I just purchased a used Midas DL16...

    I have a Mac, how would i go about updating the firmware on the DL16?

     

    Secondly, when i hold down the Config button, and power up the unit; It does NOT display the current firmware version....is there a different way to do this?

    read more...
    0 765
    • hollywood
      GaryHiggins

      @hollywood 


      Hello, you need a pc to update, you will not see the firmware version unless connected to the pc via the usb connection.


       


       





      Update Process:



      1. Download and unpack the latest updater zip file from midasconsoles.com on your Windows PC


      2. Connect the DL16 USB port to your PC using a standard USB cable (type A -- type B)


      3. Hold the CONFIG button depressed while switching the DL16 on


      4. The DL16 display will show the current firmware version on its display


      5. Make sure you have started your Windows session with Administrator access, then start the updater executable


      6. The terminal window will inform you about the update progress. Wait approximately 1 min until it shows completed.


      7. Disconnect the USB link and switch the DL16 power off / on


      8. If you wish, you may check if the update has successfully been loaded by holding the CONFIG button while power cycling the DL16, again.


      9. Note, that the display will only show the firmware version while being connected via USB.






       

      • March 25, 2020
  • DavidC3Av
    Contributor - Level 2
    2019-08-24

    Could someone pls advise about whether it is possible to connect Behringer P16 to DL153. We have MIDAS M32R and DL153 stage box. P16 works fine off the mixer desk M32 Ultranet port, but the DL153 manual is silent about whether the DL153 Ethernet Control can send Ultranet. Is this possible or are we going to have to run a separate RJ44/Cat5 cable from the M32 to the stage for Ultranet? If DL153 cannot run Ultranet, what is the cheapest alternative to running an additional Cat5 cable to provide Ultranet connectivity on stage? Thanks in advance, David. 

    read more...
    0 718
    • DavidC3Av
      DaveMorrison

      Hi @DavidC3Av 


      No. Ultranet is neither AES50 or Ethernet. The DL153 doesn't have ultranet capability. The Midas DL 32 & 16 and Behringer S32, S16, SD16, SD8 all can do ultranet because they have the proper chipsets. Channels 33-48 on the AES50 bus are then routed by the stageboxes to the ultranet ports. Theoretically it might be possible to send signal to a SD8 and then daisy-chain to the DL153. Maybe someone on the forum has done it.

      • August 24, 2019
    • DavidC3Av
      DavidC3Av

      Thank you Dave, much appreciated. Looks like an elegant solution, and low enough cost to order and give it a shot next Sunday. Do you think it might be possible to daisy chain the SD8 after the DL153? Ie. even though DL153 doesn’t have Ultranet chipset that it is likely to faithfully pass on whatever protocol is happening on the AES50 for the SD8 to put out the Ultranet? Thanks again.

      • August 24, 2019
    • DavidC3Av
      GaryHiggins

      @DavidC3Av AFAIK you can't daisy chain any of the midas "blue" series stageboxes. The second aes50 port on those is redundant meaning if one fails the other will keep working when connected to a Midas Pro series mixer. It's not an in/thru type line. When using with the X32/M32 series mixers, it can be used on one aes50 port and nothing can be daisy chained beyond it on that line, In that regard they become somewhat limited. However your SD8/16/32's can be used on the other remaining X32 aes50  port and daisy chained normally up to the 48 ch limit.

      • August 24, 2019
    • DavidC3Av
      DavidC3Av @GaryHiggins thank you. Would inserting the SD8 before the DL153 on that AES50 work?
      • August 24, 2019
    • DavidC3Av
      GaryHiggins

      It may, I am not sure, I would wonder how/if the S/SD boxes can pass forward the ch's of the DL153 box properly to the mixer due to the ch shift they normally impose and implement with regard to each other. You might not achieve proper sync. I might guess no but it's just a guess. @ChaseMcKnight would be the guy here who would know for sure.


       


      @RexBeckettsorry did not see your post before writting my response...


       

      • August 24, 2019
  • ChasHands
    Contributor - Level 2
    2019-09-11
    My setup:
     
    32 inputs of mic and DI into Midas DL32 Stage Box running through the Behringer Cat5 standard 50m reel to the console.  There are no secondary consoles in play.
     
    I choose AES-50A 1-8, 9-16, 17-24, 25-32 as my input sources for the four input banks.  Everything functions as expected.
     
    I connect the KT DN32 USB card to a Mac laptop running a current OS and a current version of ProTools to record, and I also hope to playback as a virtual soundcheck.
     
    FYI - I also record USB flash drive copies of the LR mix each night (recording pre-LR dynamics and pre-LR EQ) so I am only capturing the sounds of the channel processing and mix blends, and I can also use those as general speaker tuning reference material at a new venue, however I would like to be able to work on individual channel sounds.
     
    My expectation of the KT USB card would be that it is capturing raw channel signals, “post" head amp gain (in this case DL32 head amps), and “pre" any console processing (HPF, Polarity, EQ, dynamics, inserts, etc).
    Is that correct?
     
    My expectation after I successfully captured a 32 track ProTools file - which I did - is that I could have a channel by channel virtual soundcheck from the Pro Tools playback, and work on fine tuning channel processing as if the player was playing in front of me.
    Is that correct?
     
    I setup ProTools to recognize the DN32 as the master interface and clock source.  In ProTools, I selected the DN32 as the input device, assigned Input 1 to Channel 1, etc... up to assigning Channel 32 to Input 32, and successfully recorded a 32 channel session from the live event.
     
    Subsequently, in ProTools, I selected the DN32 as the output device, and I assigned Ch 1 to Output 1, etc…. up to assigning Channel 32 to Output 32.
     
    On the M32 Routing Page, on the Inputs tab, I selected Card 1-8, Card 9-16, Card 17-24, Card 25-32 as my input sources for the four input banks.
     
    I’m expecting each channel to see an individual ProTools track associated with that channel - hopefully, coming in through a Trim knob set to “0” so that the channel sees the input at the identical gain that it would have been from the DL32 Stage Box with the original gain of “X” dB dialed in.
    Is that correct?
     
    I’m not seeing any audio except on Channel 1 which is totally overloaded.
     
    Do I have a Midas / KT issue, or perhaps a ProTools issue?
     
    This seems very simple, but I'm not getting the expected result.  Comments?
    read more...
    0 695
    • ChasHands
      garyh

      On the inputs page you want either local or aes50a ch’s, not card. Local for whatever m32 ch’s used and aes50a for whatever DL32 chi’s you are using. That’s when the record section (at the bottom of the inputs page in m32-edit) is set active and recording, when playback is active then you want card ch’s. You set that by selecting play at that same location. Also in card out set that to whatever inputs you used as well, that is whatever ch’s you want sent to your card to record. 

      • September 11, 2019
    • ChasHands
      ChasHands

      Well - obviously my earlier reply just dissappeared into the ether...



       


      Your suggestions seem to be more oriented to using the M32 and DN32 USB card in a studio context, and exploring the abilities of the M32 as a DAW control surface.


       



      I am not trying to go back and forth between recording and playback as if it was a recording session.  I am not trying to control the DAW.  I am also not running additional control software on a laptop (the M32Edit software?)  I am just trying to acquire 32 channels of previously recorded soundcheck material to fine tune console channel sounds at a subsequent venue. 


       


      I am under the impresssion that I can playback DAW tracks as soundcheck material during a live concert setup without necessarily putting the M32 into "DAW Control" mode.  Is that correct?




       


      Perhaps I have misunderstood...


       


      You say "On the inputs page you want either local or aes50a ch’s, not card..." How would selecting my stage box or my local inputs access the playback of audio from my DAW?


       


      To restate the details of my first post, I am initially sourcing audio from my stage box via AES50A, and routing that into a 32 track ProTools session successfully.  That was accomplished by setting M32 inputs to the appropriate AES50A banks 1-8, 9-16, 17-24, 25-32, and then by using the ProTools Playback engine setup to locate and select the KT DN32 card as the master interface, and assigning inputs 1:1... 32:32  Recording happened with no problem.


       


      On playback, In ProTools, I  assigned each of 32 tracks of audio to the corresponding mono outputs (1:1... 32:32).  On the M32 inputs page I selected Card 1-8, 9-16, 17-24, 25-32 as my M32 channel1-32 sources.  This is where I have the problem.  I only get audio on Channel 1.


       


      I'm not sure how your suggestion applies to my situation or what I am trying to acomplish.


       


      Please elaborate.

      • September 12, 2019
    • ChasHands
      DaveMorrison

      @ChasHands 


      It looks like your setup is correct. This is the way it's supposed to work. Now it's troubleshooting time. Do you really have 32 channels on the USB? Is the M32 receiving all 32? Under the Setup > Card tab, Do you have 32 In/Outs selected? If you want to post your current scene file, we can take a look.

      • September 12, 2019
    • ChasHands
      ChasHands

      Well, thank you for confirming that this is something that should be possible, and that my general approach seems sound.


      That’s a good thought to look  at the Card set up page.  I was unaware of that page until I watched a Music Group webinar (with Justin? & John?) this morning. If I recall correctly, there are 4 options determining how many outputs and how many inputs.


       


      As my recording happened exactly as intended, I conclude I have 32 out.


       


      It seems like the input options were 32X32 and 32X8.


       


      Even if it were set to 32X8, why would I only see audio on channel 1?   I think I would see audio on channels 1 through 8.


       


      There is definitely audio evenly distributed on every on every track  of the recording.


      I will be on site tomorrow, and be able to check some things and get some scene files at that time. The console is living onsite for a 10 week show.  It is possible I have an output configuration wrong in ProTools but I have also been working through that process this week, and believe I did it correctly.

      • September 12, 2019
  • Trusound
    Contributor - Level 2
    2019-10-03

    As i am trying to do the recent firmware update, i am experiencing heavy malfunction.
    After finishing the procedure, BOTH consoles do not boot up, but remain in the linux text screen asking for
    MC -1 login:

    Creating a ticket for service support seems to be an impossible task also.
    Has somebody got an idea, how to resolve this very unpleasant limbo?

    Thanks in advance, Andi

    read more...
    0 646
    • Trusound
      Trusound

      For instance: Is there such a thing like a bootloader, that i can use on my usb stick to reboot the console?

      • October 3, 2019
    • Trusound
      ChaseMcKnight

      Hi @Trusound 

      Are you turning the consoles on while the USB drive is still connected? If so, take out the USB drive and boot. If this isn't the case -- what firmware were the Pro1 & Pro2 on before updating? Do you currently have a support ticket submitted? 

      • October 3, 2019
    • Trusound
      zigson


      @Trusound wrote:


      As i am trying to do the recent firmware update, i am experiencing heavy malfunction.
      After finishing the procedure, BOTH consoles do not boot up, but remain in the linux text screen asking for
      MC -1 login:
      For instance: Is there such a thing like a bootloader, that i can use on my usb stick to reboot the console?





      Hello Andi.... yes there is...


      this same thing happened to me once, and I was quite in panic... (the reason was simple and stupid : after the update the console reboots by itself after you quit the updater (push the button "quit" and wait !!.!!). I was too busy and did not wait this reboot and after shut down  the console it never wanted to boot up again (same problem at yours !!)


      fortunately we have a very responsif  "Midas-Support-Service" here in France and they  helped me to fix the thing within a couple of hours.


      The thing to do - contact your support-service (distributor, importer, etc) - call them on the phone instead of sending mail or creating tickets...; they will provide you a bootable system called "MidasRecoverySystem.zip" (which goes on an USB-Stick and you boot from this stick) - than install a brandnew (or older system); re-boot the console and upgrade again to the latest Firmware....


      if you can't find this particular USB-bootable-system at your retailer/repair/support-service, I can (maybe) provide you one of these.....; just let me know....




      Midas-Support wrote :

      You will need a good quality USB stick containing a FAT32 (Windows) partition with at least 8 GB available. For safety, this should be a separate stick to that used during normal updates, and should be clearly marked.

      Step 1 – Download the right zipped file for your console

      Step 2 – Un-zip the file to the root of the USB stick, the un-zipped file that lives on the root of the USB stick will be called “MIDASRecoverySystem” 


      Step 3 – Insert the USB stick into a port on the failed board; ensure no other USB sticks are connected

      
Step 4 – Power on the console

      
Step 5 – Wait several minutes; the Updater application will display the current stage of the recovery process

      Step 6 – In case of Pro3/6/9, if a licence file was successfully backed up, it will be restored to the console after the new image has been installed; if licence backup failed, the console will need relicensing

      Step 7 – When prompted, by a green message saying it is now safe to shut down the console, perform a hard power down, remove the usb stick and start the console up.

      Step 8 – Once the console has booted, the stick may be reinserted for restoring show files and presets libraries using the GUI's File Manager

      Step 9 - Care should be taken to not leave the recovery stick in the console when rebooting, or the recovery process will be repeated

      Step 10 - Log files will remain on USB stick and can be used to diagnose the original fault
PLEASE SEND THE LOG FILE THAT IS CREATED, TO OUR CARE DEPARTMENT TO DIAGNOSE THE FAILURE REASON

      (in the “MIDASRecoverySystem” root = logfile”) – You can cut and paste this into a mail to [email protected]





       

      • October 3, 2019
    • Trusound
      zigson


      @Trusound wrote:


      As i am trying to do the recent firmware update, i am experiencing heavy malfunction.
      After finishing the procedure, BOTH consoles do not boot up, but remain in the linux text screen asking for
      MC -1 login:


      .........For instance: Is there such a thing like a bootloader, that i can use on my usb stick to reboot the console?





      Hello Andi.... yes there is...


      this same thing happened to me once, and I was quite in panic... (the reason was, in my case, simple and stupid : after the update the console reboots by itself after you quit the updater (push the button "quit" and wait !!.!!). I was too busy and did not wait this reboot and after shut down the console it never wanted to boot up again (same problem as yours !!)


      fortunately we have a very responsif "Midas-Support-Service" here in France and they helped me to fix the thing within a couple of hours.


      The thing to do - contact your support-service (distributor, importer, etc) - call them on the phone instead of sending mail or creating tickets...; they will provide you a bootable system called "MidasRecoverySystem.zip" (which goes on an USB-Stick and you boot from this stick) - than install a brandnew (or older system); re-boot the console and upgrade again to the latest Firmware....


      if you can't find this particular USB-bootable-system at your retailer/repair/support-service, I can (maybe) provide you one of these.....; just let me know....










      Midas-Support wrote :

      You will need a good quality USB stick containing a FAT32 (Windows) partition with at least 8 GB available. For safety, this should be a separate stick to that used during normal updates, and should be clearly marked.

      Step 1 – Download the right zipped file for your console

      Step 2 – Un-zip the file to the root of the USB stick, the un-zipped file that lives on the root of the USB stick will be called “MIDASRecoverySystem” 


      Step 3 – Insert the USB stick into a port on the failed board; ensure no other USB sticks are connected

      
Step 4 – Power on the console

      
Step 5 – Wait several minutes; the Updater application will display the current stage of the recovery process

      Step 6 – In case of Pro3/6/9, if a licence file was successfully backed up, it will be restored to the console after the new image has been installed; if licence backup failed, the console will need relicensing

      Step 7 – When prompted, by a green message saying it is now safe to shut down the console, perform a hard power down, remove the usb stick and start the console up.

      Step 8 – Once the console has booted, the stick may be reinserted for restoring show files and presets libraries using the GUI's File Manager

      Step 9 - Care should be taken to not leave the recovery stick in the console when rebooting, or the recovery process will be repeated

      Step 10 - Log files will remain on USB stick and can be used to diagnose the original fault

      
PLEASE SEND THE LOG FILE THAT IS CREATED, TO OUR CARE DEPARTMENT TO DIAGNOSE THE FAILURE REASON (in the “MIDASRecoverySystem” root = logfile”)


       





       

      • October 3, 2019
    • Trusound
      Trusound

      Hi Zigson,


      thank you much for your help. I recently got in touch with a midas man here in germany. He sent me a recovery file, that contained the folowing file:
      DL2G3.4.4rel-14.image
      Therefore our PRO1 Console now thinks, she's a PRO2. In accordance she does not recognize her DSP within the network.


      So now i am searching for DL1G3.4.4rel-14.image. Can You help?
      Thanks again, Andi

      • October 4, 2019
  • MarkNorgren
    Contributor - Level 3
    2020-01-22

    I see that there is a new Firmware out for the X/M32 series.  NICE!  My question pertains to why MIdas lists the dates of the updates for the boards and not the stage boxes?  I also have the DL32 and the Firmware for it is listed as 1.7, but NO date.  I remember updating a year or two ago and I'm thinking there is nothing new since then?  Just wish Midas would list a date along the side of the Download so I new if there was something new?  

    Is there anyway to check the Stagebox to see what Firmware it is running?

    read more...
    0 637
    • MarkNorgren
      GaryHiggins

      1.7 is the latest. I believe as part of the update, only while connected to your pc, the current firmware will display.

      • January 22, 2020
    • MarkNorgren
      MarkNorgren

      Thanks Gary!


       


      It would be nice if Midas would put the Firmware date next to the download so we would know.  Easy to check on the board, not so easy on the stagebox!

      • January 22, 2020
    • MarkNorgren
      GaryHiggins

      @MarkNorgrenI may have told you wrong-but there is an easier way. Holding the mute button in while powering up disables the fan with firmware 1.7...so if that doesn't happen it's not on 1.7...and yes, I agree a release date would be nice! Seems easy enough to add. Or some other easily accessible way to tell.

      • January 22, 2020
    • MarkNorgren
      MarkNorgren

      I remember updating when we moved to V3.0, so my guess is that was 1.7?  Just update the board to V4.02 and things went well!


      Game on!

      • January 22, 2020
    • MarkNorgren
      GaryHiggins

      @MarkNorgren Looks like it was from Feb 2016


       


      Capture.PNG

      • January 22, 2020
  • KingBurton
    Contributor - Level 2
    2017-08-12
    Hi everybody.

    Current
    Using electronic drum kit. Only L & R output so we pan hard L/R with low sounds one sire high sounds other.

    Goal
    But drum processor does have midi out. Is there a way to separate each drum to discreet channel through midi at DL16 to M32.

    If yes, how do I make that happen? Asking for three churches.

    Cheers.
    King
    read more...
    0 624
    • KingBurton
      KevinMaxwell

      King Burton;129333 wrote:

      Hi everybody.



      Current

      Using electronic drum kit. Only L & R output so we pan hard L/R with low sounds one sire high sounds other.



      Goal

      But drum processor does have midi out. Is there a way to separate each drum to discreet channel through midi at DL16 to M32.



      If yes, how do I make that happen? Asking for three churches.



      Cheers.

      King




      I think you will find that the Midi outs on the Drums are control outputs. If you wanted to hit a drum and have it bring up or down a fader on the console then that might sort of work. But the Midi out is not a way to get the different drum sounds out of the drums to the mixer.
      • August 12, 2017
  • DaveMorrison
    Rock Star - Level 2
    2019-11-08

    At the current time, M-32 edit v4.0 is available to download. However the link to the Mac version is wrong (3.2). I'm guessing the firmware will follow very soon???

    0 603
    • DaveMorrison
      DaveMorrison

      Wow! This is gonna take a minute to digest.


      User In and User Out are cool. Now I wanna rebuild my whole setup.


      @Paul_Vannatto  It seems that Output 1-16, Ultranet, and Aux In are still the only way to add a Mixbus to any outputs. Does that mean we (potentially) have a triple staged output system? For example. Mixbus 1 > Output 12 > User Out 48> AES50-B 48 (and/or AES50-A 8)?


      I suppose all this new power will lead to some serious thinking. How do we explain it to new users?

      • November 8, 2019
    • DaveMorrison
      KenMitchell

      @DaveMorrison  - I've got a headache reading what you just wrote.   I wish I had the time to write a graphical routing tool that allowed scene editing and saving.   This new firmware is going to require a lot of pencil and paper sketches.  Fire up the scanner. 


       


      Ken

      • November 8, 2019
    • DaveMorrison
      CraigFowler

      Saw some of this on Reddit a couple of weeks ago.


       


      It looks like using the User IO we can move away from the blocks of 8 a bit, especially wrt inputs.  It looks like we can get source signals from anywhere outside the DSP using the UserIn tab, and not be restricted by the blocks of 8.  2 local preamps (not necessarily in the same block of 8, in fact not even next to each other) + 1 card in + another local preamp + 1 aux socket + 2 remote preamps + another card in, all in 1 block of input signals is now possible, without needing to burn other input blocks, or get creative with the AuxIn Remap, or re-assign channel sources.  Yay.  Also, the internal TB mic and ExtTB preamp are both available as separate sources; so no more burning a bus to get TB to a channel.  Then once we've "staged" the UserIn tab, we can apply those userIn blocks to the input tab.  Alternatively, if we're happy with the blocks of 8 as is, we can route inputs normally, ignoring the UserIn tab alltogether.


       


      This makes a lot of my previous posts redundant. 


       


      Re outputs, it looks like we can just do the normal stage to block then assign block to output as per usual, however the UserOut tab can be used for things like passthrough without relying on blocks of 8, similar to input blocks, but can also be used to mix and match DSP signals staged in the out1-16\aux out\ultranet tabs in too, in pretty much any order, ie in the one block-of-8, you can get the signal from output5 in the out1-16 tab (eg bus5, post fader) appearing next to the signal from output15 on the ultranet tab (eg DirOut ch15, In\LC,) appearing next to a tap straight off a remote preamp from a stagebox connected to AES50A, then a signal from a cardin (eg a click track, no need to assign the click to a channel,) then the signal from a preamp from a stagebox connected to AES50B.


       


      Basically we've almost hit routing nirvana (though IMO the app could use some workflow tweaks.)

      • November 8, 2019
    • DaveMorrison
      KenMitchell

      @CraigFowler  - you guys scare the heck out of me.  I feel like I'm on an amusement ride and my head is spinning and I'm just about to... <deleted>


       


      Ken

      • November 8, 2019
    • DaveMorrison
      DaveMorrison

      When I saw that 4.0 (M32-Edit) was available, I had to look. Thankfully all the old ways seem to work. But the User In and User Out tab were mind numbing for a bit. I couldn't even understand the GUI for 10 or 15 minutes. It makes sense now.  

      • November 8, 2019
  • gtcode
    Contributor - Level 2
    2019-08-21

    We have an M32 AES50-B <-> X32 Core A <> X32 Core B <-> DL32 A

     

    Sync master is X32 Core

     

    We are not always getting sync on power up

     

    1) Is there a special power up sequence here? X32 Core first?

    2) Can they be arbitrarily power cycled (as long as the X32 core being the master is on)

     

    Maybe the X32 Core which I got used has a problem here?

    read more...
    0 555
    • gtcode
      Paul_Vannatto


      @gtcode wrote:


      We are not always getting sync on power up


      Anytime I get intermittent sync, it is usually due to a flakey AES50 cable.


      1) Is there a special power up sequence here? X32 Core first?


      I normally power up the master clock device first. But it seems to sync irrespective of the order.


      Maybe the X32 Core which I got used has a problem here?


      I would suspect a cable.





       

      • August 21, 2019
    • gtcode
      gtcode

      Thanks Paul


      We lost sync between X32Core+DL32.


      We powere cycled them both which fixed sync


      This caused M32+X32Core sync to be lost


      We reset M32, sync still lost


      We powered everything down then turned on X32Core+M32, waited for them to boot/sync, then turned on M32 and it worked finally.


       


      As per these steps, sync was lost on both cables at separate times


       


      If this is supposed to be robust on bootup at all times I'd suspect the X32 Core since sync was lost or not achieved on both AES ports of the X32 Core

      • August 21, 2019
    • gtcode
      gtcode

      By the way, we did not move or change any AES or other cables at all during this process.  Entirely related to reboots and the like.

      • August 21, 2019
    • gtcode
      gtcode

      Sorry no edit feature. We are using high quality AES50 cables here for both cables. Odds they are problematic is extremely low, and odds that both happened to fail is even lower. Sorry no edit feature on these posts my bad

      • August 21, 2019
    • gtcode
      Paul_Vannatto

      Have you tried to change the master to the M32?


      Are the AES50 cables shielded with ethercons on each end?


      Have you tried re-aligning the RJ45 connectors inside the ethercon ends (by loosening the stress nut, plugging the end into a jack, wiggling slightly, then tightening the nut)?

      • August 21, 2019
  • New
    althea1076
    Newcomer - Level 1
    2021-04-06

    Hi folks,

    I recently purchased an MR18, and my Macbook (M1 Chip) will not recognize the MR18 as an audio device.  An old 2015 macbook  recognized it no problem, so I think it has something to do with the new M1 architecture. 

    Is there plans to release a driver to make the MR18 class compliant with current Macs?  Or is there a workaround so I can record via my MR18 to my current gen Macbook?  Would really like to keep this thing 

    read more...
    0 550
    • althea1076
      Nigel67 Hi althea1076, all our USB USB audio / midi devices are fully UAC2.0 class compliant and do not require drivers under MAC OS and will continue to work under CoreAudio as before. You will need to take this up with Apple. However, we haven't received any complaints from other customers so this could be a set up issue rather than an incompatibility. Make sure the MR18 is running the latest software version.
      • Apr 6
    • althea1076
      Anacrousered I already mentioned this in the beginning of this year (CAS-422198-R6R0B2-CRM:0048100004722) ... Both Apple and you say the problem is on the other one's side ... I tried latest Midas version and updated macOS Big Sur to 11.4 in the hope something would have changed but no progression ... it's a pity because I like the MR18 but can't use it anymore as I can't regulate the volume
      • Jun 18
    • althea1076
      epeltzman

      I was having this same problem, driving myself crazy trying to get audio to send out of CoreAudio and through the M-Air interface running Big Sur 11.4. I did, however just fix it (I think). I reset my MR18 twice and am running 11.7firmware version. transferred it to another machine running the same OS, and got it working there. I transferred back to my work computer, transferred settings from the mixer to the pc, and now everything is working (for now)

      • Jul 20
  • collins
    Contributor - Level 1
    2019-06-06

    Correct usb driver for windows  10 64 and MR10 so I can record into Cubase 10 all the ones I have tryed dont work????

    0 549
Go to page