Avid Pro Audio Community

Avid Pro Audio Community (http://duc.avid.com/index.php)
-   003, Mbox 2, Digi 002, original Mbox, Digi 001 (Win) (http://duc.avid.com/forumdisplay.php?f=17)
-   -   003 issue with 48KHz, w10 and Sonarworks (http://duc.avid.com/showthread.php?t=411281)

AudioSpine 07-25-2020 06:24 AM

003 issue with 48KHz, w10 and Sonarworks
 
Hi, I have an issue with my digidesign 003 interface and windows 10. For some reason, it cannot put out 48 KHz on my w10 desktop. If I open Pro Tools project on my computer, it says:

"The current playback engine does not support a sample rate of 48 KHz"

If I choose to use an other output device on my w10 (for example, my samsung screen with built in speakers) I can open a Pro Tools project in 48KHz with no problem for some reason.:confused:

The problem I have now is that I started using sonarworks to calibrate my monitors that I work on. The problem with that is that I must use sonarworks as an output on my W10 to work for that, but in that case I cannot work on 48KHz.

albee1952 07-29-2020 11:13 AM

Re: 003 issue with 48KHz, w10 and Sonarworks
 
Let me clear up all of this for you:

#1-With all Windows systems, you need to go into Settings>Sound make sure that Windows is NOT using the 003 as its "Default Playback Device". That will free up the 003 to be under Pro Tools control for sample rate.(most likely Windows is controlling the sample rate at the moment)

#2-the Sonarworks analysis MUST be run at 44.1K only. Once its run and has calculated the correction curve, the plugin inside PT will work at all sample rates.

#3-Many people have had bad luck running the analysis on 002/003 interfaces. In other cases, I don't know the reason. In my own case, after lots of back-and-forth with Sonarworks, they insisted that my clock(internal to the 003) had enough drift that made it unusable. I borrowed a Behringer interface from a friend and was able to run the analysis without any issue at all. Was my clock messed up? Tough to know for sure, but using another interface solved that issue. And FWIW, my 003R failed completely about a month later(now running a Presonus Studio 1810c).

#4-the only way I know of to try the 003 one more time is: create or open any session at 44.1K(that will set the 003 clock to 44.1), Close the session and immediately open the Sonarworks analysis program. If it runs thru the process, that's all you need to get a calibration curve. If it still stalls out, borrow any interface for an afternoon, install the proper Windows 10 driver, run the Sonarworks program(saving the calibration curve) and then you can return the interface(you may as well leave the driver installed in case you want to repeat the process at a later date).

#5-in case you were not aware of this, the room correction is ONLY for listening/mixing. When you are ready to bounce the final mix, BYPASS the Sonarworks plugin. This is true of any of these plugin-based processes(like IK Multimedia ARC).


All times are GMT -7. The time now is 06:54 PM.

Powered by: vBulletin, Copyright ©2000 - 2008, Jelsoft Enterprises Limited. Forum Hosted By: URLJet.com