"error: NotReadableError: Could not start video source" when pushing by Android Pixel 4A5G of back camera with Chrome

[iesv]

Which version are you using?

v1.3.0

Which operating system are you using?

• Linux amd64 standard
• Linux amd64 Docker
• Linux arm64 standard
• Linux arm64 Docker
• Linux arm7 standard
• Linux arm7 Docker
• Linux arm6 standard
• Linux arm6 Docker
• [x ] Windows amd64 standard
• Windows amd64 Docker (WSL backend)
• macOS amd64 standard
• macOS amd64 Docker
• Other (please describe)

Describe the issue

when pushing by Android Pixel 4A5G of back camera with Chrome, it high probability dones't work.

Describe how to replicate the issue

1. start the server
2. publish with Android Chrome
3. read with OBS browers source

Did you attach the server logs?

no

Did you attach a network dump?

no

[aler9]

Hello, after doing some research it seems that that error is thrown when the camera is already in use. The server indeed requests the camera twice, the first call is performed in order to get all available codecs and devices, and the second call is performed in order to perform the streaming.

I've edited the code in order to stop the first camera request before starting the second one, please test this nightly release and let me know if it works (click on artifacts, binaries):

https://github.com/bluenviron/mediamtx/actions/runs/7234099772

[iesv]

YES! It works! Thank you aler9!
However, it cannot show 1920x1080 size in chrome. Moreover, is it possible to reduce the latency a bit?

MERRY CHRISTMAS!!! GOD BLESS YOU!

[aler9]

Thanks for providing the feedback and merry christmas to you too from Italy :)

Regarding the size issue, open another issue and provide details.

Regarding latency, the server doesn't introduce any latency, it just routes packets from an end to the other. Try to debug your streaming pipeline and to find the point in which latency is introduced. For instance, try to publish with a desktop browser and check whether latency is lower - it that is the case, it means that the problem lies in the smartphone, otherwise, the problem lies in something in the server side, and so on.

[github-actions]

This issue is mentioned in release v1.4.2 🚀
Check out the entire changelog by clicking here

[github-actions]

This issue is being locked automatically because it has been closed for more than 6 months.
Please open a new issue in case you encounter a similar problem.