You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
ios and mac safari native mode does not support llhls very well.
there will be a long latency 10s+ delay on ios device and mac safari native mode
sometimes the video freezed and did not recover
start mtx with following configuration. set
hlsEncryption: yes
hlsServerKey: server.key
hlsServerCert: server.crt
hlsVariant: lowLatency
hlsSegmentCount: 7
hlsSegmentDuration: 6s
hlsPartDuration: 1000ms mediamtx.yml.zip
use obs to send rtmp stream , configuration as follow.
GOP: 6s
tune:zerolatency
url: rtmp://localhost:1935/live/abc
use mac chrome to play https://localhost:8888/live/abc/ , latency is about 3.5s
use ios safari to play https://localhost:8888/live/abc/ , we will see a very long latency 10s+
use mac safari play stream.m3u8 directly https://localhost:8888/live/abc/index.m3u8 we will see a very long latency 10s+
both ios and mac safari will get freezed sometimes.
we have seen the network through web console that small segement part.mp4 are downloaded.
we have dig into the issue and find something:
check the images above
part2856.mp4 is preload in the first m3u8
but in the second m3u8 it is gone.
and browser report part2856.mp4 404 error
this may cause the video freeze on ios or native safari.
ios or native safari always download several seg.mp4 before part.mp4 and push it into play buffer, that cause latency very long.
how to resolve above 2 issues?
Did you attach the server logs?
no, it is easy to replicate
Did you attach a network dump?
no, it is easy to replicate
The text was updated successfully, but these errors were encountered:
Hello, thank you very much for reporting and debugging this bug, i found out that when hlsSegmentDuration is an exact multiple of hlsPartDuration, and IDR frames are sent out at an interval equal to hlsSegmentDuration, there are gaps in parts IDs that causes the URL in EXT-X-PRELOAD-HINT to return 404.
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.
Related Topic #2288
Which version are you using?
v1.0.3
Which operating system are you using?
Describe the issue
ios and mac safari native mode does not support llhls very well.
there will be a long latency 10s+ delay on ios device and mac safari native mode
sometimes the video freezed and did not recover
Describe how to replicate the issue
build mtx
follow https://github.com/bluenviron/mediamtx#compatibility-with-apple-devices to generate hlsServerKey and hlsServerCert
openssl genrsa -out server.key 2048
openssl req -new -x509 -sha256 -key server.key -out server.crt -days 3650
start mtx with following configuration. set
hlsEncryption: yes
hlsServerKey: server.key
hlsServerCert: server.crt
hlsVariant: lowLatency
hlsSegmentCount: 7
hlsSegmentDuration: 6s
hlsPartDuration: 1000ms
mediamtx.yml.zip
use obs to send rtmp stream , configuration as follow.
GOP: 6s
tune:zerolatency
url: rtmp://localhost:1935/live/abc
use ios safari to play https://localhost:8888/live/abc/ , we will see a very long latency 10s+
use mac safari play stream.m3u8 directly https://localhost:8888/live/abc/index.m3u8 we will see a very long latency 10s+
both ios and mac safari will get freezed sometimes.
we have seen the network through web console that small segement part.mp4 are downloaded.
we have dig into the issue and find something:
check the images above
part2856.mp4 is preload in the first m3u8
but in the second m3u8 it is gone.
and browser report part2856.mp4 404 error
this may cause the video freeze on ios or native safari.
ios or native safari always download several seg.mp4 before part.mp4 and push it into play buffer, that cause latency very long.
how to resolve above 2 issues?
Did you attach the server logs?
no, it is easy to replicate
Did you attach a network dump?
no, it is easy to replicate
The text was updated successfully, but these errors were encountered: