Optimizing Video Initialization on Settings Screen

[SanjayBikhchandani]

• [ ] I have verified that the issue occurs with the latest twilio-video.js release and is not marked as a known issue in the CHANGELOG.md.
• [ ] I reviewed the Common Issues and open GitHub issues and verified that this report represents a potentially new issue.
• [ ] I verified that the Quickstart application works in my environment.
• [ ] I am not sharing any Personally Identifiable Information (PII) or sensitive account information (API keys, credentials, etc.) when reporting this issue.

Code to reproduce the issue:

Video.createLocalTracks(localTrackConstraints)

Issue

I would like to understand the factors behind the Audio/Video initialization process. Are there any dependencies on the user's device, network connectivity, or any other elements that might affect the initialization time? We have noticed that some users experience minimal delay, while others encounter longer delays on settings screen which comes before the Join Screen.

I would like to explore potential optimizations to reduce the initialization time and ensure a smoother user experience. If possible, could you provide guidance or suggestions on how we can enhance this aspect of the system?

Software versions:

• [ ] Browser(s): Chrome & Safari
• [ ] Operating System: Windows & MacOS
• [ ] twilio-video.js: 2.27.0
• [ ] Third-party libraries (e.g., Angular, React, etc.): React

[manjeshbhargav]

Hi @SanjayBikhchandani ,

Sorry for the late response. What do you mean by initialization time? Is it the time between calling createLocalTracks() and actually resolving the returned Promise? If that is the case, then delays can be caused if the user takes time to give media permissions to your application. Please let me know if I have understood your problem correctly.

[vbabenko]

We notice something similar. We see that some part of users wait for 10-15 sec to resolve the promise (Note: permissions were granted). Maybe the issue is related to the hardware or system security, or something else... But unfortunately, we cannot reliably identify it

[SanjayBikhchandani]

@manjeshbhargav

We've found out that it actually happens because of the Krisp Noise Cancellation plug-in where sometimes it takes more time (sometimes it takes around 1 Minute) for its model to load.