@Cimarron 

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.

@Cimarron 

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

@Cimarron 

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.

Did you consider controlling the pair with a DCA?

Using a DCA to control a stereo input is a great idea and I’m using four of them for that purpose currently. We’ve got about 10 stereo sources we’d like to have on single faders. The console has enough inputs for all of our sources, just trying to get the most frequently used ones on the top fader layer. And trying to get my sound ops used to a console that is not our analog 32 channel Verona!  Thanks for the input!

While playing around with the great options that everyone has been suggesting, I stumbled upon another possibility (provided you aren't concerned with keeping stereo separation on a particular input). This solution could also work as a kind of internal router, and works around the "routing in banks of eight only" limitation by allowing the placement of any single input on any fader. 

Here's the theory (I have't actually tried it yet). Physically patch a cable between an available Aux Output and an XLR input in the 1-16 range (to put it on the first fader bank). Now you can internally route any one of your inputs to that Aux, and it will be available on that first bank's fader. Be sure to send that input prefader and pre-mute, then mute the actual input, so it does not feed the Main output from there. You'll now have full control of that input on the fader you chose, without having to change fader banks to get to it. You could send a stereo pair to that Aux and control it with that single fader (it will be summed mono of course), without burning a DCA or two top bank faders. 

In our TV studio, we have to occasionally use different sources for different shows, and the mix can be unpredicatable, so having 1 or 2 "route-able" inputs can be really useful to keep the frequently used faders for that show on the top page/bank. We've got a lot of possible inputs from audio clip playback devices, graphics SFX, in-studio guest mics, phone callers, Skype guests and satellite guests, so it's not possible to keep them all on the first fader bank, and the mixer's installation makes it impractical to physically repatch before each show. I can save a scene for each possible scenario and just load the correct one once I know where all my sources are coming from for a particular show. 

Thanks for all the great advice everyone, and I hope this idea can work for someone who might have been struggling with a similar issue (if it actually works and does not create some kind of audio black hole). 

---

@drice wrote:

While playing around with the great options that everyone has been suggesting, I stumbled upon another possibility (provided you aren't concerned with keeping stereo separation on a particular input). This solution could also work as a kind of internal router, and works around the "routing in banks of eight only" limitation by allowing the placement of any single input on any fader. 

Here's the theory (I have't actually tried it yet). Physically patch a cable between an available Aux Output and an XLR input in the 1-16 range (to put it on the first fader bank). Now you can internally route any one of your inputs to that Aux, and it will be available on that first bank's fader. Be sure to send that input prefader and pre-mute, then mute the actual input, so it does not feed the Main output from there. You'll now have full control of that input on the fader you chose, without having to change fader banks to get to it. You could send a stereo pair to that Aux and control it with that single fader (it will be summed mono of course), without burning a DCA or two top bank faders. 

In our TV studio, we have to occasionally use different sources for different shows, and the mix can be unpredicatable, so having 1 or 2 "route-able" inputs can be really useful to keep the frequently used faders for that show on the top page/bank. We've got a lot of possible inputs from audio clip playback devices, graphics SFX, in-studio guest mics, phone callers, Skype guests and satellite guests, so it's not possible to keep them all on the first fader bank, and the mixer's installation makes it impractical to physically repatch before each show. I can save a scene for each possible scenario and just load the correct one once I know where all my sources are coming from for a particular show. 

Thanks for all the great advice everyone, and I hope this idea can work for someone who might have been struggling with a similar issue (if it actually works and does not create some kind of audio black hole). 

 

---

I am not understanding what this will give you unless you are talking about using a Mix Bus to mearge each pair of inputs.

Merging (summing) the stereo inputs to one fader is one possible use, the other is that this allows me to internally route any one of my inputs to the top bank of faders. Sure, I could do this by simply connecting that device to an input that already appears on the top layer, but the connections on the back of our mixer are not easily accessible, and depending on what sources we are using for a show, I might want to quickly place something on a top level fader that does not usually appear there. Some other mixers allow you to do this on an single input basis, but the M32 locks you into routing inputs to faders in banks of eight.