Initialization of noise cancellation is blocking

[fidesit]

Which package/packages do you use?

• @stream-io/video-react-sdk
• @stream-io/video-react-native-sdk
• @stream-io/video-client

Describe the bug
Initializing noise cancellation takes 10+ seconds on MS Edge

To Reproduce

 private enableNoiseCancellation() {
    setTimeout(() => {
      this.ngZone.runOutsideAngular(() => {
        const isSupported = this.noiseCancellation.isSupported();
        (typeof isSupported === 'boolean' ? Promise.resolve(isSupported) : isSupported)
          .then(async (supported: boolean) => {
            if (supported) {
              await this.noiseCancellation.init();
              // provide the NoiseCancellation instance to the call and register the plugin
              await this.call.microphone.enableNoiseCancellation(this.noiseCancellation);
              logZoomDebug('stream: noise cancellation enabled');
            } else {
              logZoomDebug('stream: noise cancellation NOT supported');
            }
          })
      })
    })
  }

Expected behavior
I would expect the initialization of noise cancellation to be non-blocking, so I can continue loading my UI without having to wait.. now it blocks angular processing, causing UI update delays..

Version

"@stream-io/audio-filters-web": "^0.2.3",
"@stream-io/video-client": "^1.20.2",

Env:

Local , Angular 19

• Browser [e.g. chrome, safari]

MS Edge v136.0.3240.50

• OS: [e.g. iOS, linux...]

Windows 11

Additional context
See performance trace from MS Edge (attached)

Trace-20250509T095112.zip

[fidesit]

In Chrome it loads faster (<50ms)

[fidesit]

Perhaps related: another blocking task happens after the joining of the session, also in MS Edge..

Load time in Chrome is about 4-5 seconds until participants are shown, that sounds ok, wdyt?

Trace-20250509T102327.zip

[oliverlaz]

Hi @fidesit, thanks for reporting this. This isn't the expected behavior, as our NC module should initialize relatively fast.
We'll take a look at this and get back to you.

[oliverlaz]

Hi @fidesit, we don't see this issue on our side, and recently we've made a few improvements to our Noise Cancellation filters.
Can you try upgrading and see if things get better on your side, too?

[oliverlaz]

Hi @fidesit, I'm closing this issue due to inactivity.
Please feel free to reopen it case you still experience the described behavior.