I do have a dodgy usb Midi controller that goes south on many occasions, requiring me to reboot.īut. I don’t think I’ve ever had this happen with my focusrite interface (firewire, not usb). I'm super disappointed, because it started happening, when my band all gathered up to record and wasted a lot of time to make it work. I'll appreciate if anyone can recommend a fix or better workaround. Worked fine when I installed ASIO4All, but it's less flexible for me.

I'm using an old Line6 Toneport UX1 interface and Reason 10.3d78 (latest) fails to load the driver despite reattaching the USB or rebooting the PC. Unfortunately, I didn't notice, when it started happening. As dirty as it made me feel to even install Fruity Loops for their ASIO, surprisingly it works pretty well, but it can screw up output to other programs and on a couple of occasions I seem to have to run Windows audio troubleshooter to reset things to get audio out of Media Player or browser. Incidentally, someone recently told me about a neat video recording trick of installing the FLStudio demo, then using the FLASIO as that will pass audio to screen recording software, e.g., OBS, for low(er) latency sound recording.

Usually just going into prefs, and simply selecting a different driver then reselecting the Focusrite ASIO seems to restart it. I probably just sneezed or looked at it funny and it decided it was as good a time as any to stop working. Not enough I can identify an actual repeatable scenario anyway. It doesn't happen often here-fortunately, at least not annoyingly so, yet-but it does happen. No idea if it's the Scarlett ASIO or a Reason or a Windows cock-up, but it affected 9.5 as well as 10. I've also got a Focusrite Scarlett, and indeed it does sometimes 'stop working'. After the error, if I immediately quit Reason, other applications on my system play audio using the Focusrite ASIO driver without any problems. After the error, I can select a different (inferior) audio driver in Preferences, and audio will play When I returned to the computer, the ASIO driver error message was on the screen. The second time the error occurred, I opened a session, loaded up several NNXTs with orchestral samples, then went away from the computer for a couple of hours, while Reason sat dormant. The ASIO error occurs after Reason has been in use for a prolonged period of time (over 2 hours) Lots of VSTs have been installed, the most recent being Europa and UVI Workstation The only new significant software installed in the last year is Reason 10.1

This system and audio configuration have been in use for 3+ years with no issues Focusrite Scarlett interface with Focusrite ASIO driver Has anyone experienced this? Here are some additional details: In the last few days I have twice encountered a message from Reason saying the ASIO driver has stopped working, and all audio stops playing. I've been using 10.1 for about a month now (previously on 9.5).

Asio interface driver