-
Notifications
You must be signed in to change notification settings - Fork 519
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
Organize output files for hls+dash #2769
Comments
You need to use the segment template for that, e.g. I did a few updates on master to handle this use case: templates are now relative to variant playlist for HLS, and you can use templating in playlist names:
will generate |
And what if there are more than one audio or video track? |
I mean, it is not working for me in that case. I have several audio and video tracks, somewhere like the organization that bento4 does is what I'd like to achieve: a folder per track and inside each folder the corresponding index.m3u8 in the case of HLS.
|
You don't need to use |
Is it what you expect? |
It's not quite the same. I would like to first have a folder on what type of track it is. /live.m3u8 >> Main index Video tracks and files Audio tracks and files Have I explained my self correctly? |
I came to a good approach, however when trying to use it with Drm the problem is that |
The stream type is stored as GF_PROP_PID_ORIG_STREAM_TYPE but using |
Using latest master, use |
@jeanlf Why does GPAC limit the properties it resolves? I understand we may need to add identifiers, but why remove some? And why rename some (which makes it harder to remember)? |
it does not, see http://wiki.gpac.io/Filters/filters_general/#url-templating But we have aliases for a few properties, as documented in above link. |
… original types - cf gpac#2769
Is there any way to organize better the output files for an hls+dash packing?
![image](https://private-user-images.githubusercontent.com/19694461/308951960-79a6f932-06f3-4fad-b346-34f0e2b6c9c7.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MTkxNDQ5ODcsIm5iZiI6MTcxOTE0NDY4NywicGF0aCI6Ii8xOTY5NDQ2MS8zMDg5NTE5NjAtNzlhNmY5MzItMDZmMy00ZmFkLWIzNDYtMzRmMGUyYjZjOWM3LnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNDA2MjMlMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjQwNjIzVDEyMTEyN1omWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTg1YzFhZjg4Y2ZkYWEyOGQyZGE2NTllZTM5YTVlMDZjYWI1N2FhNWFmZTUwMzU3ZDhiMzQ2MjYzN2QzNDYxYmQmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0JmFjdG9yX2lkPTAma2V5X2lkPTAmcmVwb19pZD0wIn0.PuVzcJpXakx-iapQyjTqX6CCTUIMng9kvS5LYODvmKQ)
The output by default is a little bit messy:
Wouldn't it better to have a folder per track, and inside each folder the m3u8 of that track, and the main index.m3u8 and index.mpd in the root folder?
The text was updated successfully, but these errors were encountered: