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

hlsDirectory parameter - Hls directory doesn't created per stream in 1.6.0 when it worked properly in 1.5.1 #3135

Closed
12 tasks
EvgIL74 opened this issue Mar 12, 2024 · 4 comments · Fixed by #3151
Closed
12 tasks
Labels
bug Something isn't working hls

Comments

@EvgIL74
Copy link

EvgIL74 commented Mar 12, 2024

Which version are you using?

v1.6.0
v1.5.1

Which operating system are you using?

  • [x ] 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 (please describe)

Describe the issue

Description
Ask to create ts files on disk instead of in memory by add directory in hlsDirectory in yml file.
The server doesn't create directory path and not created ts files on disk.
It was properly in 1.5.1 and stopped work in 1.6.0.

Describe how to replicate the issue

Ask to create ts files on disk instead of in memory by add directory in hlsDirectory in yml file.
The server doesn't create directory path and not created ts files on disk.

Did you attach the server logs?

no

Did you attach a network dump?

no

@tschettervictor
Copy link

Same issue here.

@aler9
Copy link
Member

aler9 commented Mar 19, 2024

Thanks for reporting the issue, this is fixed by #3150 and #3151

Copy link
Contributor

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

Copy link
Contributor

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.

@github-actions github-actions bot locked and limited conversation to collaborators Oct 18, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Something isn't working hls
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants