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
Is it possible to use variables, such as $vod_clip_id in the vod_hls_segment_file_name_prefix and vod_dash_fragment_file_name_prefix directives.
Our use case is as follows:
A video player requests a video from a URL formatted as {vod_set_id}/master.m3u8 or {vod_set_id}/manifest.mpd
The nginx-vod-module then queries our API to retrieve a mapping response based on the vod_set_id
The API returns a mapping response containing the vod_set_id along with sequences where each sequence has its own vod_sequence_id and corresponding video/audio MP4 file.
The nginx-vod-module uses the response from the API to create the m3u8/mpd file and returns it to the video player.
In our backend, users can change the video or audio MP4 file, which updates the vod_sequence_id in the API response.
We have deployed the nginx-vod-module behind a CDN, which caches the TS/M4S segments. When the scenario described above occurs, we would like to update the segments by altering the segment names using a variable, such as vod_sequence_id
The text was updated successfully, but these errors were encountered:
nonth
changed the title
Using Variables in vod_hls_segment_file_name_prefix and vod_dash_fragment_file_name_prefix
Using variables in vod_hls_segment_file_name_prefix and vod_dash_fragment_file_name_prefix
Aug 30, 2024
This is not supported.
The common solution to the caching issue you described is to change the path of the URL instead. For example, you can use a URL like - http://domain/video/{id}/version/{ver}/master.m3u8. If you change the version, the manifest and all segments get a new URL, and bypass the CDN cache.
Thanks for your answer.
Unfortunately, the user can’t change the URL of the master playlist (m3u8/mpd) since it’s already being used on their website/app. Is there any way to change the URLs for the sub-playlists (m3u8) or the segment files (TS/M4S) instead?
You can solve it with HTTP redirection - have the master URL used by the website/app redirect to the nginx-vod-module master URL (cached on the CDN). Then, when you want to publish a new version, you just change the redirection to point a new URL, that has a new version, and therefore bypasses the CDN cache.
Is it possible to use variables, such as
$vod_clip_id
in thevod_hls_segment_file_name_prefix
andvod_dash_fragment_file_name_prefix
directives.Our use case is as follows:
{vod_set_id}/master.m3u8
or{vod_set_id}/manifest.mpd
vod_set_id
vod_set_id
along with sequences where each sequence has its ownvod_sequence_id
and corresponding video/audio MP4 file.vod_sequence_id
in the API response.We have deployed the nginx-vod-module behind a CDN, which caches the TS/M4S segments. When the scenario described above occurs, we would like to update the segments by altering the segment names using a variable, such as
vod_sequence_id
The text was updated successfully, but these errors were encountered: