Midas

Midas

Brand

Midas

259,806 members
138,224 posts
  • New
    busychild1
    Newcomer - Level 1
    2021-07-27

    Still trying to get a stock check on a M32.........................5 email have gone unanswered, several "cases closed" without any documentation to support closing it or even speaking with me............

    I know the audio world is a mess for you folks as well. Set an example and start following up.............

    read more...
    0 46
  • New
    Unkle1
    Contributor - Level 2
    2021-07-25

    I am having issues with my auxes 3-16 coming on after I set up the board mix 1 and 2 come on with no issues ,this is the pro 1 console any help will be truly appreciated thanks.

    0 44
    • Unkle1
      DavidKnighton Hell Unkle1,
      Not sure I understand your meaning. Do you mean the auxes are not unmuting? Or you're unable to turn the auxes ON for each individual channel? I don't suppose you submitted a support inquiry for this have you? If so, may I have the case number?
      • Jul 26
    • Unkle1
      Unkle1

      To make things a little clearer,my auxes 3-16 do not come on from when I patch them in from the back of console,I do not use a Stagebox, previous owner used Stageboxes, so I was informed to try resetting to default settings ( case# 474216-T9P4V )thanks,

      • Jul 26
  • New
    DwayneAasberg
    Super Contributor - Level 1
    2021-07-25

    Hello all.

    At first I thought this problem was a product of deploying V4.3 onto a new Win10 box.  I have now upgraded M32-Edit from 4.2 to 4.3 on an established PC and this new problem has been repeated.

    Specifically.  In v4.2, when clicking Save or Load the Windows explorer window would open to the last folder accessed by this application.  Now in v4.3 clicking Save or Load causes the Windows explorer window to open to the root User default folder location - very time.  This forces the user to click-dive to find the appropriate folder to load or save.  When you come back to load or save again, you need to repeat the exercise.  VERY FRUSTRATING!

    Now that I've proven this is an M32-Edit problem, and not a Windows problem, I need to drop this directly on MG and ask that when you offer new features (sarcasm intended), don't make others inoperable.  AND - PLEASE RESTORE WINDOWS EXPLORER FOLDER MEMORY.

    Thank you.  Dwayne A.

    read more...
    0 45
    • DwayneAasberg
      DavidKnighton Hell Dwayne,
      Thank you for the feedback. I will try to recreate this issue and bring it up to our software team for evaluation.
      • Jul 26
  • New
    MadsHyldahl
    Newcomer - Level 1
    2021-07-24

    Im trying to test some midi commands for muting mute groups over midi. As i dont have the M32 at home i'm trying to test everything in the edit software. But i cant get m32 edit to responde to anything.

     

    im following this sheet

    https://community.musictribe.com/pages/kba?articleId=b675dad0-fb77-ea11-a811-000d3ac693d8&brand=Midas

     

    i'm sending from ableton live to "network session" cc80 on channel 2 to turne ON/OFF mute group 1, but it does not work.

    i have also tried with a midi foot controller, but m32 edit i not responding to anything.

     

    so does midi only work if i have the console ? 

     

     

    read more...
    0 53
    • MadsHyldahl
      Paul_Vannatto The M32-Edit is a client app that requires the OSC server that is built into the M32. Midi commands received by the M32 is converted to the OSC equivalent and changes the appropriate setting. When that happens, the M32 senses the changes and adjusts its screens accordingly. Therefore you need an M32 or X32 connected to both the M32-Edit and the computer (with Ableton).
      • Jul 24
  • New
    mikerosen
    Newcomer - Level 1
    2021-07-20

    Hey,

    One of the channels on my Midas Venice F24 makes some ruffling noises sometimes when there is nothing connected to the input on that channel. Would appreciate it if anyone could help me with this!

     

    Thanks :)

    read more...
    0 47
    • mikerosen
      Dale_M This sounds like one of the op amps on that channel has failed, assuming you have tried a known good cable and mic from a neighbouring channel then it is likely to be faulty and require a repair, for assistance in this matter please go to the support tab above and select Service as your ticket type to inquire on a non warranty repair.
      • Jul 21
  • New
    zendrummer84
    Newcomer - Level 1
    2021-07-20

    Hey! im new to posting here but i just need a quick anwser to a question. Ive submitted 2 care tickets now in relation to aquiring Parts to repair a M32R i have. I cant seem to get anyone on the care team to email me back and when i check my ticket status it just says "Problem Solved" but no real anwsers have been given. Working with tech support trying to accomplish repairs is turning out to be very frustrating and im just reaching out to see if anyone might have any suggestions. I literally just need to order a new PSU haha thats it. 

    read more...
    0 51
    • zendrummer84
      ChrisEdwards1 Hi zendrummer84, are these the case you are referring to? CAS-454657-J3B7R0, CAS-459761-V4S3R0. If so i can see responses have been sent out on both with no further follow-up, a response was sent on 25/05/2021 for CAS-454657-J3B7R0 and 10/06/2021 for CAS-459761-V4S3R0.

      It may be possible that the responses are routing to your spam/junk folder as we have seen this happen in the past, do you happen to have a second email address at all? If so I will pass this along to my colleagues and have them reach out to you again including the second email.
      • Jul 20
  • New
    GregWarren
    Contributor - Level 3
    2021-07-19

    I have 6 DP48s and they've been rock solid until last Sunday when we used them. I had some completely drop all signal coming into them. It seemed like 1 worked and the rest dropped out. They eventually reconnected but that's a no-go when you're using a click track. Suggestions?

     

    My signal chain: Midas M32>AES50B>DP48>DP48>DP48>DP48>DP48>DP48

    read more...
    0 51
    • GregWarren
      GregWarren I did some digging around and found that my firmware was woefully behind on the dp48s. It was 1.5 and I updated to 2.2. My 2 DL16s were 2.4 and I update to 2.5 and my Midas M32 is 4.02 so I think we're good there. I will have practice Wednesday and update if I have more signal loss.
      • Jul 19
    • GregWarren
      Paul_Vannatto Hey Greg, are you using proper AES50 cable (shielded with ethercon ends)?
      • Jul 19
      • Dropout on DP48
        GregWarren I'm running shielded cable but it's not ethercon.
        • Jul 20
    • GregWarren
      Paul_Vannatto Hey Greg, Brian Wynn proved to us (back in 2013) that the ethercon ends are very important in shielding the cable from ESD (electrostatic discharge) which results in AES50 dropouts. So if you have low humidity, this may be the source to your dropouts.
      • Jul 21
  • New
    BerndVanPraet
    Contributor - Level 2
    2021-07-19

    Hi,

     

    Is there a way to change where the VU-metering picks of in the audio chain ?

    0 61
    • BerndVanPraet
      ChaseMcKnight Hi @BerndVanPraet if you navigate to the Metering preferences ( Preferences / DSP Configuration / Metering) you have the option of changing output channel meters between Pre Fader & Post Fader.
      • Jul 19
    • BerndVanPraet
      BerndVanPraet

      ok, the question I got from a tech was, the meters above the faders, are this showing PRE fader, after the whole chain of ' gain - dyn - eq - insert.

      • Jul 19
    • BerndVanPraet
      ChaseMcKnight Hi @BerndVanPraet , the surface meters above the faders default to Pre Fader for Input Channels and Post Fader for Output Channels. Yes, that's correct; it’s metering the signal post-processing but pre fader.
      • Jul 19
  • New
    msteel
    Newcomer - Level 1
    2021-07-14

    We have an M32 (full size, original non-live, still running v3.11) installed in a venue for over a year now.  One of the uses of the space is a classroom, in which case the system operates unattended.  In the past few weeks there have been a handful of times I have discovered the console not passing audio.  Visually, everything looks fine and the screen, buttons, and LEDs are responsive.  But no audio.  Notably, when I recalled a snapshot to make sure settings were correct, the console rebooted.  After that audio was working as intended.

    This behavior began recently and is relatively frequent - every couple of days or more often.  Of course it is possible that the console has failed in some way, but I'm not yet convinced of that.  I'm not aware of any power problems in that location either, although this particular system is not on a UPS.

    A significant change that coincides fairly well with the beginning of this behavior is related to some automation I have implemented using OSC commands over the network.  A recent feature change had the automation system continually setting some scribble strip colors and channel mutes twice a second.  Probably about 14 OSC commands per second altogether.  In some ways this feels like a lot of traffic, but it really doesn't seem excessive compared to something like real time meter updates or fader moves on an iPad app.  All the same, I am wondering if it is  somehow too much data to send and is crashing something in the console.

    I've read all the release notes I've found in case there was a known issue my automation could be triggering, and nothing seemed to stick out.  But updating to the latest firmware might still be a good idea, I suppose.

    In the mean time I've retooled my automation to reduce the frequency of the parameter updates.  I will see if that seems to make a difference.

     

     

    read more...
    0 56
    • msteel
      Paul_Vannatto Hi Matthew, what app are you using to send the OSC commands remotely? Are the OSC commands properly formatted (4 byte aligned, big endian, etc.)? The reason I ask is that during my early development of Live Toolbox, I would frequently send incorrectly formatted commands that would generate an error on the console which would result it a freeze until either I cleared the error or rebooted the console. Patrick has this well documented in his X32 OSC Protocol document (page 11) found here:
      https://drive.google.com/file/d/1Snbwx3m6us6L1qeP1_pD6s8hbJpIpD0a/view
      • Jul 14
      • M32 stops passing audio, possible connection to OSC
        msteel I have seen that error dialog before, but am not getting it now. My automation system is based on Node Red which in turn is based on node.js and javascript. The commands are generated from Javascript strings and include padding characters. They work as intended (i.e. the desired effect is seen on the surface) and do not generate an error dialog. The system is powered on 24/7, though, and since the problem showed up about the same time as my changes I was suspicious about the long term effects of continuous commands. You know, maybe my changes were revealing a memory leak or buffer issue that wouldn't show up on a system that was power cycled more frequently.
        • Jul 14
    • msteel
      Paul_Vannatto I would suggest that you update the firmware to the latest version (4.06). Make sure that you backup your scenes, snippets, etc. (export the show will back those up) as well as the library presets. Also make note of the settings on the first 4 screens of the Setup. Firmware 4.x now provides the ability to backup everything.
      • Jul 14
    • msteel
      msteel I updated the firmware on this console to 4.06 a while back and a few days ago the issue happened again. As a result I did some testing. Since the M32 is installed and in daily use my ability to test on it is limited. However, I also have an X32 producer at my disposal and decided to set it up as a test bed. Here is what I have found out:

      * This issue has now been observed on M32 v3.11, M32 v4.06, and X32 Producer v4.06. This means it is not limited to one version of firmware, and happens on both Midas and Behringer versions of the console.
      * The original automation was sending 7 OSC commands 1-2 times per second. The console would hang every few days.
      * Reducing the number of commands to 7 commands every 5 seconds or so greatly reduced the frequency of the console locking up. Maybe a few weeks?
      * In my test setup I sent 10 commands approximately 100 times a second. Under these circumstances I can make the console crash after about 15 minutes. Being able to reproduce the issue relatively quickly has allowed me to gather additional data.
      * When the console crashes, the message "Checkpoint: target.cpp: 93" appears at the bottom of the screen. At this point the console no longer sends audio to any outputs and the meters are frozen at the last level. Additionally, OSC commands no longer have any effect. However, the surface user interface including mute buttons, LEDs, and screen all appear to respond normally.
      * After the console has crashed, recalling a scene causes the message, "Checkpoint: target.cpp: 86" to appear briefly before the console reboots.
      * To measure if the exact number of OSC commands is always the same, I included in each burst a command to set the name of channel 1 to the number of bursts sent so far. This way when the console crashes I can tell exactly how many bursts of messages have been sent. This number is not exactly the same but appears to be fairly consistent and somewhere around 100,000 bursts (1 million OSC commands) at the time of a crash.
      • Nov 10
    • msteel
      Paul_Vannatto Thanks for the detailed write up. The developers are aware of the issue and will be fixed in the next firmware release.
      • Nov 12
  • New
    BrotherBruce
    Newcomer - Level 1
    2021-07-12

    The text on M32 User Manual p22 does not seem to follow the image shown of the Dyn page in the user interface.

    Specifically, I'm interested in the function of the Mix (0-100%) knob shown. I cannot find where it is described. I'm guessing it will implement parallel compression by adjusting the wet/dry ratio, but am confounded by the lack of description. When set to 100% does that mean there is no dry signal passed?

    Is there another source of info on this product? I'm familiar with digital consoles in general, but each implementation is different and I cannot find the detail I'm seeking in many areas. I've read through all the M32 threads in this forum, downloaded all the documentation and searched in vain for a help file or more specific information. I really don't want to burden this board with continual questions about control function, location and detail, considering most of the questions here are of a more advanced nature.

    Thanks in advance for your helpful replies.

     

    read more...
    0 113
    • BrotherBruce
      Paul_Vannatto Yes that is correct. 100% mix results in 100% wet signal (0% dry). The reason the user manual does not describe it is because the manual is based on firmware 2.0 and the mix function was added in a later firmware update to provide functionality primarily for parallel compression application.
      • Jul 12
Go to page