• garypegb
    Contributor - Level 2
    2019-05-29

    Is the Heritage-D a real thing?

     

    IMG_0259.JPG

    read more...
    0 1,910
  • MikeEsonic
    Contributor - Level 2
    2019-11-14

    Hi.

    Just updated to the new FW on M32. The faders now move much slower when changing layers.. Is that part of the new software update?

    0 1,094
    • MikeEsonic
      GaryHiggins

      @MikeEsonic It is part of the update. See second to last line below.


        new features:


        - point to point user routing, 4 input and 6 output banks (32 in / 48 out)


        - DP48/HUB4 remote configuration support


        - DP48 setup page with preset library


        - send pan optionally follows LR pan function


        - full backup export/restore function


        - new keyboard with channel name suggestions/history and keyboard layouts


        - X32Core/M32C: Export Show function


        - M32/M32R: V.1 Fader option (forces update of faderboards, requires reboot)


        - option for coloured RTA bars


       

      • November 14, 2019
    • MikeEsonic
      nicholi

      "M32/M32R: V.1 Fader option (forces update of faderboards, requires reboot)"


      This is not very clear.  So are we supported to enable this setting?  What exactly is its functuon whether enabled or disabaled?

      • November 14, 2019
    • MikeEsonic
      GaryHiggins

      @nicholi I think the word option here is meant more like 'feature'...not really a user option or choice, in other words updating the faders for the Midas boards is part of the update period, it comes with the package, no matter...BUT this is only my opinion. I had the same experience and saw no option to update or not update the faders.  

      • November 14, 2019
    • MikeEsonic
      nicholi

      Hi Gary,


      Hmm.  I am not at the board now but under System there is an option to enable or dsable the "feature".  The mixer will reboot.  It does not change change the fader speed howwever from what I can tell.  So I am trying to figure out if it should be enable or not and what is the benefit.  I guess the questions should be.  What is V.1 Fader? What versions of the boards does this affect M32 with black buttons or rubber?

      • November 14, 2019
    • MikeEsonic
      MikeEsonic

      @nicholi Yes I did the same thing. I enabled V.1 Fader option and I thought it would change the speed but it did not. Still trying to figure out what it does, and if you can change the back to original speed. Also, I’m thinking they changed the speed to save the motors so they last longer. 

      • November 15, 2019
  • danhennings
    Contributor - Level 1
    2019-11-13

    I have an RMA for an M32. Have any of you found a shipping box for your console, and if so, where?

    0 1,015
  • GaryHiggins
    Superhero - Level 1
    2019-12-10

    This is originally from another post but I started a new one because I am wondering if other M32 owners have a similar experience with firmware 4.01. Specific to me, this is an M32R. Anyone else tried this yet and had a similar experience?

     

    The back story is with version 4.0 the fader speed on M32's was reduced/smoothed out, it was (and apparantly still is) a permanent change. With this newer firmware 4.01 there is a "fast fader" checkbox that reboots the mixer and was intended to return the faders back to the 'fast' version.

     

    Well there seems to be a BIG bug or something with the new M32 fader speed! I loaded up 4.01 and went right to the config page/fast fader checkbox area to see if I could get my mixer fader speed back the way it was prior to updating to V4. I confirmed I wanted that 'fast fader' option and....it reboots....and it did change BUT It is WAY different than before. Now the faders "snap" in to place (kind of like it used to) but there is this very worrisome fader motor "after spin" sound (more than just sound) that occurs. (a digital mixer's version of grinding gears) I can tell you 100% this never existed before. I went right back to the (since 4.0) slower fader version and that sound (and whatever process this was) went away! Not ready for prime time I think!

    I am tempted to try it once more to see if maybe it was just a quirky firmware update and I may do so later in the day. 

    EDIT: I just tried the fast fader reboot again with the same results. I am told this is normal and expected however it's a normal I can't live with. I will again say that noise was never there for me before this. I can live with the slower version so there it will stay. 

     

    read more...
    2 902
    • GaryHiggins
      KevinMaxwell

      I will be setting up a system this afternoon for an event this weekend and we will be using one of the M32s (still on V3.07 of the firmware) for this. I will try and pay attention to the fader behavior and report back later today. 

      • December 10, 2019
    • GaryHiggins
      GaryHiggins

      @KevinMaxwell Well, I finally located firmware version 3.07 myself and when I loaded it up, my nice, snappy and essentially noise free faders returned!! Yippy! NOW the question is if I reload 4.01 from here if it will return them to this fast version when I do so. At least I know how to get them back to what was my normal now. 3.08 did not, 3.11 did not. And I now know I am not crazy (well sort of know) I wil also report back.


       


      EDIT: Loading 4.01 again puts the faders at the slower, smoother speed and the fast fader option makes them fast again but with losts of extraneous "after" noise NOT like version 3.07 at all. I made some short videos of all 3 and when I figure HOW to post them, I will.

      • December 10, 2019
    • GaryHiggins
      KevinMaxwell

      I listened very carefully and on the M32 I was setting up (that has V3.07 on it) there was no weird noises like you were experiencing with the console running 4.01 and the faders set to fast. I agree with you that it sounds like there is a bug in the 4.01 fast fader firmware.

      • December 10, 2019
    • GaryHiggins
      GaryHiggins

      @KevinMaxwell Thanks Kevin, my experience exactly. I can't seem to upload my little videos so I'm trying to post them via dropbox link instead. These show the differences quite clearly (though video is NOT my thing). Hope they will be up soon.

      • December 10, 2019
    • GaryHiggins
      GaryHiggins

       


      @KevinMaxwell or anyone else interested: Video 3 is the "new" fast fader version Again the news for anyone wanting the faders back the way they used to be prior to firmware 4.0 or 4.01 Load version 3.7 (it's still availble if you choose to include the archived version in search on the Midas page) In my case it brought back the fader speed to what it was the day I bought it. BUT 4.01 puts them right back to slow or (noisy) fast. I am choosing to use the slower faders and stay on 4.01 due to its awsomeness in other areas and until such time as the old fast and noisefree version returns. And.....just like the recent US Congressional hearings, The gentleman recognizes himself as to the solution


       


      https://www.dropbox.com/sh/5ru6bwfno5fcg5k/AAA9ugBcV-Se8L7YtteR35uYa?dl=0


       


      EDIT2: I re-loaded firmware 3.7 to see what fader version it is that runs across the bottom of the screen-it appears to be fader version r/R .12 or r/R 1.2 


       


      EDIT: As an aside I noticed in this process of loading different firmware versions that if you use the console global setup page (bottom left) for updating firmware, you can have several firmware files at the root directory at once, and pick which one to load. I always made sure there was only 1 in the past as that was the specifried way to do it. FWIW

      • December 10, 2019
  • RikRayner
    Contributor - Level 3
    2019-06-10

    Hi Guys,

    I'm looking to move up from my XR18 to either an X32 rack or a Midas M32C and the simple question is are the Behringer SD8/SD16 stageboxes compatible with the M32C or do I have to get the Midas DL stageboxes?

    Thanks in advance

    Rik

    read more...
    0 693
    • RikRayner
      Paul_Vannatto

      Hi Rik @RikRayner,


      Yes the SD8 and SD16 will work with the M32C. But you don't gain much of the "Midas" touch that way. The M32C has the identical DSP engine as the X32 models. The difference is in the Midas preamps and outputs, which in the case of the M32C would be in the stagebox(s). You would be far better ahead to get an X32 Rack with an SD8 (or 2) or an SD16 IMO.


       

      • June 10, 2019
    • RikRayner
      RikRayner

      Hi Paul,


      thanks for the confirmation.  I'm attracted by the ultra-compact form factor of the M32C and the ability to expand the array of inputs available, using both the DL and SD series stageboxes.  I can definitely see the use of an SD8 for a stagefront stagebox for monitor wedge and L/R outputs plus vocal mic inputs.  Just a shame that there is no Midas equivalent of the SD8

      • June 10, 2019
    • RikRayner
      Paul_Vannatto


      @RikRayner wrote:


      I'm attracted by the ultra-compact form factor of the M32C and the ability to expand the array of inputs available, using both the DL and SD series stageboxes.  I can definitely see the use of an SD8 for a stagefront stagebox for monitor wedge and L/R outputs plus vocal mic inputs.  Just a shame that there is no Midas equivalent of the SD8





      Yes its also a shame that they discontinued the X32 Core (the Behringer equivalent of the M32C). But to me the real shame is that they didn't produce a Midas equivalent to the X32 Rack. The reason is that there is a significant difference with the Midas Pro preamps and outputs (over the Behringer Midas designed).


       


      Yes there is a space advantage of the 1U form factor, but at the expense of the flexibility of the inputs/outputs. As you probably know, I use a dual X32 Rack with and SD8 and SD18 setup. A couple of years ago (this Aug) I was setting up for a Chicago tribute band when we got hit with 4 downpours during setup/soundcheck. I had the SD16 at the back of the stage to handle the drums and backline and it got a bit wet (due to the horizontal driving rain). The results was that it was showing signals where there was nothing plugged in. Their sound engineer shared his concern and I quickly wheeled one of the Racks to the back of the stage, configured it as an S16, repatched - and we were back in business in about 10 minutes. The other Rack was used as the main mixer, situated at one end of the stage and took care of the MC wireless mics and and opening act (since we were using all 24 inputs of the stageboxes for the main act). If I had a choice between an M32C and X32 Rack, I'd still choose the Rack.


       

      • June 10, 2019
    • RikRayner
      RikRayner

      Hi Paul,


      I can see that by taking the X32 rack I have a backup option of hardwiring into the desk in the event of a stagebox failure.  We've never exceeded the 16 inputs on the XR18 so a pair of SD8s would handle everything connectivity-wise, plus give me the flexibity of stage positioning and additional inputs if the need arises, albeit not as conveniently connected.  Perhgaps that SD16 might be a good option ??

      • June 10, 2019
    • RikRayner
      Paul_Vannatto


      @RikRayner wrote:


      We've never exceeded the 16 inputs on the XR18 so a pair of SD8s would handle everything connectivity-wise, plus give me the flexibity of stage positioning and additional inputs if the need arises, albeit not as conveniently connected.  Perhgaps that SD16 might be a good option ??





      You've never exceeded because you didn't have a choice  Just wait...


       


      If I had only a choice between an SD16 or 2 SD8's, I'd choose the 2 SD8's. It gives you 8 more outputs, plus it gives more flexibility of positioning at stage front/back or left/right, reducing the cable spaghetti.

      • June 10, 2019
  • 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 568
    • 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
  • 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 559
    • 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
  • 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 557
    • 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
  • 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 552
    • 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
  • 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 495
    • 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
Go to page