Frequently having our Gen 3 2i2 Scarletts stop sending out audio to mixer. They still will bring audio into the PC. Output setting in Windows never changes. USB unplug and plugging in fixes it. Never have issues with the same units on Mac. Any ideas why?

4:33Next up is from Daniel Patridge in Rochester, Minnesota. Frequently having our Gen 3 2i2 folks write, Scarlett, stop sending audio out to the mixer. They still will bring audio into the PC. Output setting in Windows never changes. USB unplug and plugging in fixes it. Never have issues with the same units on Mac. Any ideas why? What's your thought, Alexander? It's interesting. When I first read this question, somehow I missed the last part of it because to me it sounded like maybe there was a hardware failure going on.

5:04But if the same exact piece of hardware works flawlessly on another computer with a different operating system, that tells me there is something software-related there. So first thing that I would do is with these Scarlett's – now you mentioned this is a third gen. So there's one generation behind. They have done firmware updates on these devices. One thing I would probably do is

5:30install the latest version of Focusrite Control. Make sure the latest firmware is installed and also through Focusrite Control perform a factory reset of that device. If you're still having the issues, I'm assuming you're still using the same USB cable. So if you're taking that exact same piece of hardware to another computer using the same exact USB cable and it's working fine, it's probably

5:51Probably software related. I hate to say it, but you may spend less time just biting the bullet and also reinstalling Windows. And also, if you have another Windows computer, try testing it there and see if it still has the same issue. Mickey? Yeah, a couple of things. I'm curious, like, if this issue occurs after a computer has perhaps gone to sleep. different computers different motherboards treat USB peripherals differently or even different

6:20USB controllers within the same motherboard treat USB peripherals differently when the machine goes to sleep my suggestion if this is the case production machines just never never ever put them let them go to sleep just let them keep them on keep them running use them as appliances that's what you would typically do with production systems. Another thing after that with Windows, there is a functionality within Windows,

6:50and I believe this is the default setting within Windows, which is it allows applications to take exclusive control of an audio device. device. So perhaps when you find that you're not able to output from an application to the Scarlett, maybe some other application has exclusive control or exclusive access to that Scarlett and unplugging and replugging restarts that or something. So you should

7:23disable that functionality within Windows with every single audio device that you have, be it the physical audio interface or like a virtual audio interface like Dante Virtual Soundcard or if you use VB audio cables, disable that exclusive functionality within that device. Another thing is if you have the Focusrite control software, with that you can judge whether the error is happening within the software slash Windows side or if it's happening

7:56happening at the Scarlett side. If you see the audio meters bouncing, but you're not hearing it coming out, then it's something within the Scarlett. But if you're not seeing any movement in the meters, then it's probably something in the software, just a troubleshooting step. Courtney? One thing I looked at is, there's a multi-channel audio interface. It probably requires the ASIO drivers. And sometimes, you know,