Uncaught Error: NOT_SUPPORTED_SAMPLE_RATE when using higher bitrate audio output devices and `noise-cancellation`

[hramos]

This issue can be reproduced using the Daily Prebuilt client.

Expected behavior

Ideally, higher bitrate output devices should be supported when background noise reduction is enabled. Alternatively, the error should be handled by Daily and surfaced as a documented error event. This would allow developers to handle the issue in custom Daily call clients.

Describe the bug (unexpected behavior)

If the selected output device is configured to use a higher bitrate (e.g. 24-bit 192.0 kHz), an uncaught error will be thrown if background noise reduction is enabled (the noise-cancellation audio processor input setting).

VM6985:4 Uncaught (in promise) Error: NOT_SUPPORTED_SAMPLE_RATE
    at E.createNoiseFilter (eval at <anonymous> (daily-esm.js:1:1), <anonymous>:4:2781999)
    at eval (eval at <anonymous> (daily-esm.js:1:1), <anonymous>:4:465406)
    at new Promise (<anonymous>)
    at e.eval (eval at <anonymous> (daily-esm.js:1:1), <anonymous>:4:465377)
    at Generator.next (<anonymous>)
    at e (eval at <anonymous> (daily-esm.js:1:1), <anonymous>:4:1451236)
    at n (eval at <anonymous> (daily-esm.js:1:1), <anonymous>:4:1451447)

Steps to reproduce

This issue has been reproduced on macOS Sequoia 15.2:

1. Open the Audio MIDI Setup utility, which is packaged with macOS.

2. Select an audio device which supports higher bitrates. In this particular case, we're using a Fosi Audio DAC-Q4 and a Reiyin DA-DD DAC. Both devices support higher bitrates, and setting up either one of them to use a higher bitrate will trigger the error.
   

3. Select 24-bit 192.0 kHz as the desired sample rate for the device.
   

4. Join a Daily test call, ideally using Daily Prebuilt as this will ensure the error is coming from the Daily library and not our own code (e.g. open your equivalent of https://foobar.daily.co/RMxyz123 in a browser, in this case we used Google Chrome)

5. For your audio output device, choose the audio device that you configured in step 3.

6. Click on "Reduce" to enable background noise reduction.

Observe the error in the console.

Screenshots

See above.

System information

• Device: M4 MacBook Pro
• OS, version: macOS Sequoia 15.2
• Browser, version: Google Chrome Version 131.0.6778.205

Additional context

Daily versions:

    "@daily-co/daily-js": "^0.74.0",
    "@daily-co/daily-react": "^0.22.0",

[nikkipelchat]

We were having this issue as well, I was told it should be fixed in v0.75. I haven't tested it yet.

I believe it is the third bullet point under Bug Fixes here: https://github.com/daily-co/daily-js/releases/tag/daily-js-2025-02-07-0.75.0

[mattieruth]

@nikkipelchat is right. We pushed a fix for this in the latest release. That said, we were unable to reproduce ourselves so the fix is optimistic based on external reports and logs. Please do test to make sure this is fixed. If I don't hear back in a week or two, I'll close this issue as fixed.

[mattieruth]

It's been two weeks. closing as fixed, but feel free to re-open if you end up discovering otherwise.

[mattieruth]

re-opening. The patch we pushed appears to be incomplete.

[myusuf3]

experiencing this as well.

[josheverett]

Currently seeing this on version 0.80.0.

[mattieruth]

This was supposed to be closed when 0.78.0 was released, as it contains the fix for this: https://github.com/daily-co/daily-js/releases/tag/daily-js-2025-04-18-0.78.0

Can you confirm that you are seeing an Uncaught Error and not just the error for NOT_SUPPORTED_SAMPLE_RATE? This issue was that the unsupported sample rate was not being handled properly, and not that it existed.

The NOT_SUPPORTED_SAMPLE_RATE error is expected on certain devices. Krisp only supports certain sample rates. With the latest fixes, we raise this error up dynamically through the non-fatal error of type audio-processor-error. Our advice is to listen for that event and suggest to the user to either turn off noise cancellation or switch to a different device.

[myusuf3]

We are getting this

[myusuf3]

OK Thanks @mattieruth the responsiveness. We will work around it.

[mattieruth]

ah!@myusuf3: that is expected and you will want to handle this error as I suggest above.

dailyCallClient.on('nonfatal-error', (e) => { if (e.type === 'audio-processor-error') { runWorkaround() } })

[mattieruth]

Note: If you want to go the route of just auto-turning off noise cancellation, we clear the input settings when this error occurs, so all that is needed is to turn the mic back on:

function runWorkaround() {
   informUserNoiseCancellationIsOff();
   dailyCallClient.setLocalAudio(true);
}

[mattieruth]

Closing this issue as I meant to do before :)