Laptop Soundcard Sample Rate Greyed-Out, Can't Change?

[taylor4814]

Pro Tools Studio 2022.12
Dell Inspiron laptop - 12th Gen Intel® Core™ i7-1255U
Audio Controller: Cirrus CS42L42 (Cirrus Logic High Definition Audio sound card)
Driver: Cirrus-Logic-High-Definition-Audio-Driver_78XG8_WIN_10.0.7.39_A01
Windows 11 Home
Version 22H2
OS build 22621.963
Feature Experience Pack 1000.22638.1000.0


I am hoping to successfully run Pro Tools on this laptop, and resolve this issue... any suggestions welcome...

The sound card sample rate dropdown menu is greyed out, and can't be changed... (it's set to 16 bit, 48000 Hz)

Pro Tools can select the Windows audio device, and can play a 16/48 session through the onboard speakers — but no other sample rates are available.

I've tried ASIO4ALL, and Pro Tools can select it, and other sample rates are available, but so far it's unable to access onboard speakers...

I've tried driver re-installs and most settings changes I can think of, with no luck yet...

[junkgear]

Pro Tools and Windows audio do not play well together. Your laptop sound device is being controlled by Windows, so whatever sample rate it is set to is what PT will be forced to use.

If you plan on doing any serious work in PT, it is strongly recommended to get an ASIO compliant external audio device. This way, the device will be exclusive to Pro Tools and you can freely set the sample rate as you wish.

[taylor4814]

Thanks- yes, typically that is how I have my main machines set up. On this laptop, I'm trying to see if a change is possible, as I've seen it's possible in some cases...

[sw rec]

Buy an interface. And make sure Windows isn’t using it as the default sound device.

[taylor4814]

Originally Posted by sw rec

Buy an interface. And make sure Windows isn’t using it as the default sound device.

Yes, that is my typical workflow...

[taylor4814]

I've tried ASIO4ALL, and Pro Tools can select it, and other sample rates are available, but so far it's unable to access onboard speakers...

< ✅ Solved > I reset ASIO4ALL to defaults, and that seems to have solved my issue, at least insofar as ASIO4ALL goes...