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

Issue with fragment Command When Init Segment is .m4s #979

Open
capuajuan opened this issue Mar 18, 2025 · 0 comments
Open

Issue with fragment Command When Init Segment is .m4s #979

capuajuan opened this issue Mar 18, 2025 · 0 comments

Comments

@capuajuan
Copy link

Problem Description

I encountered an issue when using the fragment command with a DASH init segment that has the .m4s extension. Although DASH allows the init segment to be an .m4s file like the other segments, this init segment contains an ftyp box, meaning it behaves like an MP4 file.

Currently, the fragment command does not recognize this type of init segment as valid. However, adding .m4s to the list of allowed extensions resolves the issue.

Steps to Reproduce

  1. Use the c2patool fragment command with an init segment in .m4s format that contains an ftyp box.
  2. Observe that an error occurs, indicating the file is invalid.
  3. Add .m4s to the list of allowed extensions.
  4. Retry the command and confirm that it now processes correctly.
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

1 participant