I keep obtaining an error blog post that says "Pro tools can not initialize the focusrite usb 2.0 audio driver. Please make sure that the machine has to be configured correctly."

It worked fine because that a couple of days and also then this begin happening. I've tried uninstalling and reinstalling everything and also checking my laptop settings. I'm to run it on home windows 10 and it's Protools 11. I've done a many research however still nothing has been helpful. I'm hoping someone will understand where to walk next~ Thanks


5 comments
share
save
hide
report
60% Upvoted
Log in or authorize up to leave a comment
Log InSign Up
Sort by: best


*

level 1
· 3y · edited 3y
professional
I had lots of problems with mine pro40 not playing round with ProTools under home windows 10. Opening sessions of various sample rates would break it every time. Could not initialize.

You are watching: Pro tools could not initialize the focusrite

Make a new session at the sample rate you need. That will kick start the unit. Climate you can go ago to the conference you actually want, and it will work for a while. When it division again, make another brand-new session climate switch back.


2
Reply
Share
ReportSave
level 1
· 3y · edited 3y

Switching sample prices and/or little bit depths is your issue. Here's the solution I come up with:

label sessions or session folders v their sample rate and bit depth.

when transforming sample rates, an initial open the Focusrite ASIO manage panel and switch the there.

if an altering bit depths, open the windows audio controls, and collection it.

stop and restart windows audio solutions (via a batch script)

open session.

I'll attach the batch script here when i can get to mine computer.

EDIT: On step #3, come navigate to this in home windows 10, right-click the speak on the taskbar, click 'Sounds', hit the Playback tab, right-click the Focusrite device, climate hit the advanced tab. Alternatives are under 'Default Format'.


2
Reply
Share
ReportSave
level 2
· 3y

Here's a dough to a batch script. Just put it right into Notepad, and save it through a '.bat' extension. Double-click, push yes when it asks for admin, and it will perform the rest.

https://pastebin.com/GJGQb83p


2
Reply
Share
ReportSave
level 2
· 3y
professional

Oh yes, I'd forgotten about the negative handling in between the WDM and ASIO leading to conflicts. Honestly, I'd thought an extremely highly the focusrite prior to I owned one of their interfaces - ns love my producer load - however won't be buying anything rather from them. I've had such a better experience under RME


2
Reply
Share
ReportSave
level 1
· 3y
professional

I've had actually ENDLESS troubles with mine Scarlett 2i4 on home windows 10. But mostly with FL studio, only tiny issues with Pro Tools.

See more: Girl Talk This Is The Remix, This Is The Remix By Girl Talk

I've had actually varying degrees of success through installing the Beta drivers, for this reason I'd start there. If that doesn't help, every couple of months I have to update every my outdated chauffeurs for every little thing to find the one niggling tiny one that's causing some interference. Yet I found a comfortable open resource utility to more or much less automate the process.


1
Reply
Share
ReportSave
r/protools
***/r/ProTools***Your residence for whatever Pro Tools. Anyone is welcome, from market veterans to bedroom engineers. Be sure to check out our wiki pages for an ext information regarding Pro Tools; links, shortcuts, FAQs, Guides, Tutorials, PlugIns and more.* PlugIns* Tracks* Automation* Editing* Mixing* Music* through / virtual Instruments
29.3k

Members


40

Online


Created Mar 15, 2010
Join
*
*
*
*

*

Top articles june 18th 2018Top posts of june, 2018Top write-ups 2018
helpneurosoup.org coinsneurosoup.org premiumneurosoup.org gifts
aboutcareerspressadvertiseblogTermsContent policyPrivacy policyMod policy
Back to Top