Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

HLS doesn't work #3207

Closed
2 of 13 tasks
pikachu937 opened this issue Apr 8, 2024 · 1 comment
Closed
2 of 13 tasks

HLS doesn't work #3207

pikachu937 opened this issue Apr 8, 2024 · 1 comment

Comments

@pikachu937
Copy link

pikachu937 commented Apr 8, 2024

Which version are you using?

v1.6.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
  • Windows amd64 standard
  • Windows amd64 Docker (WSL backend)
  • macOS amd64 standard
  • macOS amd64 Docker
  • Other (LXC)

Describe the issue

When the function of saving hls segments to disk is enabled, it is not possible to open the hls stream in the browser (chrome/safari) or vlc player

Describe how to replicate the issue

  1. enable the HLS server in the configuration file and allow it to save segments in mpegts format to a folder.
  2. enable saving of published streams in the configuration file.
  3. start the server
  4. publish with rtsp any stream
  5. read HLS with any browsers

Did you attach the server logs?

yes / no
BAD - File recording function enabled + saving hls server files enabled mediamtx.log
BAD - File recording function is disabled + saving hls server files enabled mediamtx1.log
GOOD - File recording function is disabled + saving hls server files disabled mediamtx2.log
GOOD - File recording function enabled + saving hls server files disabled mediamtx3.log

Did you attach a network dump?

yes / no

@pikachu937 pikachu937 reopened this Apr 8, 2024
@pikachu937 pikachu937 changed the title HLS does n HLS doesn't work Apr 8, 2024
@aler9
Copy link
Member

aler9 commented May 24, 2024

i can confirm that this bug was present in v1.6.0, but after testing it seems to have been fixed with #3151 that is included since v1.7.0.

@aler9 aler9 closed this as completed May 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants