I am using a Midas 32R. Input 9 seems to be the only working channel when I plug in an SM58. The other working channels are wireless recivers programmed into Inputs 1 and 2.
We have a problem with our Midas Pro2C. When saving a scene in a show file, the channel fader settings are not saved. The faders of the VCA groups, for example, are saved. I.e. If the fader of a channel is up in scene 1, then pulled down to safe a second scene, the channel fader is not raised again when scene 1 is recalles (this works with the VCA faders). The strange thing, however, when the safe scene is recalled, the channels are not reset, the POP groups and VCA groups already ... Recall and Score Scope is clean ... What are we doing wrong
I have an M32C with a DL32 with a split snake always connected in the rack. I had my vocalist over to play back the last gig to enhance his sounds of his IEM's because he just bought new molds. We all run in stereo and It's weird, I all of a sudden can't get Bus 3 to respond to fader moves. I moved him to Bus 11 and it works fine. Fader moves appear on screen but audibly makes no difference in Bus 3. Can someone please review my attached scene to see what is possibly wrong?
We use this setup for FOH with our IEMS and also when a venue has their own PA system we use this rack with our split snake just for IEMS only. Should I have a different scene for each use case? Meaning a differnt pre/post settings?
If anyone sees anything else I should be doing on this scene to improve our experience it would be greatly appreciated.
Thanks,
Danny K
Hi there,
With remote work and assistance becoming the norm in today's COVID-19 climate, our need and reliance on remote apps is ever increasing. I've noticed an issue when using the M32-Edit software with the Midas M32 desk, that after some time, the software either loses connection with the desk and it requires reconnecting, or no longer is able to synchronise properly. In order to resolve the issue and regain full control, the desk needs to be restarted.
I have attempted closing the software and reconnecting, but synchronisation only gets to 90%. Exactly 90% every time. This happens on computers connected both locally and remotely.
I have also noticed that after some time, the desk starts dropping pings and this is the same time connection issues with the app start. The desk also has a Dante card installed, and there doesn't appear to be any issues with connection to that.
The issue happens with both the Mac and Windows version, so appears to be an issue with the desk. The desk is running the latest version of firmwate - 4.02. M32-Edit version is V4.1 .
Does anyone else have this issue, or able to assist with resolving the issue? Any assistance would be appreciated.
Kind regards,
Hello,
I noticed that a snippet won't consider "main stereo" affectation on channels, even with all parameters in the snippets menu selected.
That'would be great help to be able to have this feature activated.
(FW4.04)
Guillaume
HERITAGE-D Series
bit.ly/Midas-HERITAGE-D-Series
Live Digital Console Centres, Stage Boxes with Multiple Microphone Preamplifiers and Accessories
The Midas HERITAGE-D Series Digital Mixers and I/O Interfaces are designed to serve our Tour Sound and Installed Sound Customers.
From: $37,500
#Midas #HD9624CCIP #HD9624CCTP #HERITAGEDSeries #Mixers #Digital
Hello all,
I just received my M32 mixer, and it came with a DN32-Live card to interface to my DAW. It seems that this may be the place I might request suggestions on what I might need to do to make that work. If not, and you can suggest a proper place to ask, I would appreciate that.
So, in general I found some directions for installing the drivers and such for the DN32-USB, which may be part of my issue (or not), though I didn't appreciate that there was a distinction at the time. I followed the directions to upgrade the M32's firmware to 4.02, and that seemed to complete fine, the M32 is working from what I can tell (I've not tried every option - by far, of course) and sounds great through the mains.
I then installed the ASIO-Driver v4.59 onto my DAW computer. I can see the DN32-LIVE in the Device Manager under Sound, video and game controllers. However looking at the Properties, the Device status says that "This device cannot start [Code 10]". I've tried computer restarting/power cycling (several times), using different USB ports, trying a different USB cable, to no avail.
Also, and probably no surprise here, I've tried the DN32USBAudioDfu.exe, which it appears is intended to update firmware on the DN32-LIVE itself, which pops up a "DN32-USB Firmware Upgrade" window, but it says "No device found. Please plug in the device you want to upgrade".
In my frustration I even dug out an old Macbook Pro and tried plugging into that (it was suggested that no driver installation would be needed for the Mac - though I wouldn't want to use that computer as my DAW), and that instantly just crashed my Mac upon plugin, and if I powered it up with the DN32 plugged in via USB, it also crashed while trying to boot. So, some research about that seemed to suggest that my Macbook Pro had "Snow Leopard" on it, which does crash like that, but upgrading to Lion (I think it was - next version up), would make it work. I haven't yet tried to do the upgrade, since thats not my preferred system for this. But at least it indicates that some computer can detect and react (by crashing) to the fact that my DN32 is attached - and given the OS installed on that system, it even reacts the way that is expected (though not as desired).
So I guess the main point of this post is to solicit any suggestions or guidance that could get my M32-Live connected to my Computer (and then get the DAW to see it). Thanks for any help with this.
-- Greg
Hello Greg, welcome to the community.
First check that the option card is really a DN32-Live. It should have SD card slots as well as a USB connector. With the console power off, remove the card and reinsert - making sure it fits into the guides correctly.
With the console power on, check on Setup -> Card that the card is being recognized. Also check on Setup -> Global under Firmware that the card firmware is A12. If not, you will need to download the A12 firmware and install it.
With everything connected and on, open Windows Device Manager and display the DN32-Live device. Right-click and select Uninstall. Now disconnect the USB and reboot the PC. When you reconnect the USB, the device should be reinstalled - possibly without errors.
I think @RexBeckett has hit the main issue-the DN-32 Live latest firmware is required. Pretty sure you need A12 with mixer firmware 4.02. That can't be done via a computer but by a usb stick on the mixer itself. If mixer firmware version 4.02 is installed already you can try to update the card with the mixer ON by using setup/update/firmware (bottom left of the screen) and then it will let you scroll to the proper update file on the usb drive. If that fails or won't work properly you will have to do it with the mixer off. Make sure the A12 card firmware file is then the ONLY firmware at the root directory with the mixer off method. Other type mixer firmware can be in a folder on the drive but not at the root directory. Turn on the mixer while holding down the usb button, the card firmware should update. You can cofirm the card firmware on the setup page by reading the (very tiny) info given there.
I might suggest completely uninstalling the drivers and trying again.
Also perhaps worth a try is usb driver 4.38 which can be found if you check off show legacy versions in the list of available files.
EDIT: There are several known issues with Win7-documented in the pdf.
@GaryHigginsThanks for taking time to reply to my message.
As I mentioned in my reply to @RexBeckett it looks like the M32 (which has 4.02 firmware) sees the DN32 card, and is reporting a firmware version of A12. So, I would assume I could move beyond the firmware installation (or re-installation), or would you think that might still be a potental step to take?
It seems a reasonable step to try deleting the DN32 driver in Windows Add/Remove programs (after first removing the device again from the device manager), and then reinstalling it. I've seen stranger things happen.
Failing that I may look into the 4.38 driver. Thanks for that information. And I'll look for the .pdf you refered to.
Thanks again,
-- Greg
It sounds as though the console is happy with the DN32-Live card and the card is running the latest firmware. I cannot say whether it is worth buying a suitable driver to reseat the card only that it has sometimes fixed problems. It has also been known for reinstallation of the card firmware to apparently fix problems. I've seen it on my own console and cannot explain it. Sometimes there can be a sequence of steps that fix a problem and we don't always identify the actual cause.
There can be several reasons why a USB device cannot start. Common ones are defective USB cables, using a USB 3 port instead of a USB 2.0 one, connecting through a USB hub, incorrect drivers or that the device has a fault. I think you have already tried different cables and ports. It would certainly be worth following Gary's advice to reinstall the driver and, if necessary, trying an older version of the driver.
My son brought his macbook down and we connected the USB from the DN32-LIVE to that and he pulled up Logic and it saw the interface and could specify any of the 32 channels as the input device for a channel. So, it seems pretty apparent that the issue is with my computer.
I had purchased myself the appropriate screwdriver and removed the DN32-LIVE, and re-installed it. Just to give that a chance, and overall good to have the screwdriver. No change.
I went to try the older 4.38 driver, and in the folder with the driver there is a PDF file TUSBAudio_KnownIssues_v4.38.0.pdf which I looked into and see a section "10.3 AllSignersEqual Group Policy breaks Driver Installation". Reading about this it sounds like the issue I'm having. If this is set to OFF somehow (thrugh Group Policy Editor or something), Windows will not actually install the driver although the driver setup finishes successfully. When it finds the DN32 on the USB port it installs a built in driver "for the respective device which possibly fails to start". I had noticed that the device manager page that described the DN32 device did say something about a "Microsoft" driver, but I thought that might have been a result of the other issue I'd had to address to even try to install the driver, which involved installing a Windows Update KB3033929 to resolve. This was apparently due to an issue that the driver wasn't signed (or incorrectly signed or something).
So, I wanted to check on the setting, but apparently the Windows 7 Home Premium edition on my computer is too lame to have gpedit.msc to start from the run menu (or another thing I saw mentioned gpupdate.msc from an administrator command prompt), which are the tools that are to be used for "Enterprise" versions of Win7, and it did mention that they wouldn't be there if you had Home Premium. But it didn't mention how to check, or what to do if you do have Home Premium (which I do).
This sounds like exactly what I'm encountering, If anyone knows about Group Policies on Home Premium (does it even have them?), or perhaps an alternate approach to installing the driver (manually copying some files into place and possibly making a registry entry or such)? Or perhaps this might already have been resolved, if I only knew where to look or what to search for.
So I have a very new MR18. Haven't done anything to it really; connected over the built in LAN a few times and that's about all. I recently got a UniFi access point, thinking I could run that off the built in DHCP server, that the MR is supposed to have, without any external router or anything. After a bunch of trying with different switches and stuff, I wasn't able to make any connection. I tried networking the unit directly from the MR to my Surface Book, and the network diagnostic error is that there's no IP lease when the unit is both on DHCP and DHCP server. I don't know how to establish a hardwired network connection because of this, and furthermore I don't know where to go with the wireless solution. All help is appreciated. Thanks.
Hello,
I've posted previously about having an issue with seeing the channel names broadcasted to the DP48 while using an SD8 with the Behringer X32 Compact. The community has helped with understanding the AES50 A & B streams. However, I still need help from the community to answer this question.
Should the DP48 see the broadcasted channel names when connected to an SD series digital snake or should I be using the S or DL series digital snakes?
What I've experienced is that the DP48 does not see the broadcasted channel name but does get the same channel setup and audio from the AES50 A side the snake box is setup on. When the DP48 is directly connected to a separate AES50 port on the mixer and NOT through the SD snake box, all the channel names are received including real-time name changes. I've experienced this on the X32 Compact and WING mixers using the SD8 and SD16 stage boxes.
Tribal help is greatly appreciated.
Hello, Talkback activation isn't saved with scene memory on M32R, that would be great if we could activate that feature.
Regards,
Guillaume
Look out for a email with your unique access code and details on how to join.
We look forward to seeing you soon!
Look out for more session announcements soon on our social media channels and at www.musictribe.com
EN
ES
ZH
ID
JA
FR
DE
.
All Categories
Cables and Connectors
Microphones
Mixers
Personal Monitors
Effects and Signal Processors
New
Recently Updated
Popular
Unanswered
Solved
Discussions
Videos
Photos
Files
