getting separate url of video and audio after parse the master playlist file
I am getting separate url for audio and video after parse the master playlist so I am unable to play specific quality video with audio. Actually I wanted to implement manual bitrate control of video in player, for this purpose I parse the master playlist in order to get url of different bitrate video. I am getting the HLS file from Azure media service in which video is encoded with different bitrate.
Following shows that how my master playlist looks like:
specific quality video url only contains video fragment not audio. Suggest me how I can retrieve specific quality video with audio from Azure Media Service.
ios swift avplayer hls azure-media-services
add a comment |
I am getting separate url for audio and video after parse the master playlist so I am unable to play specific quality video with audio. Actually I wanted to implement manual bitrate control of video in player, for this purpose I parse the master playlist in order to get url of different bitrate video. I am getting the HLS file from Azure media service in which video is encoded with different bitrate.
Following shows that how my master playlist looks like:
specific quality video url only contains video fragment not audio. Suggest me how I can retrieve specific quality video with audio from Azure Media Service.
ios swift avplayer hls azure-media-services
add a comment |
I am getting separate url for audio and video after parse the master playlist so I am unable to play specific quality video with audio. Actually I wanted to implement manual bitrate control of video in player, for this purpose I parse the master playlist in order to get url of different bitrate video. I am getting the HLS file from Azure media service in which video is encoded with different bitrate.
Following shows that how my master playlist looks like:
specific quality video url only contains video fragment not audio. Suggest me how I can retrieve specific quality video with audio from Azure Media Service.
ios swift avplayer hls azure-media-services
I am getting separate url for audio and video after parse the master playlist so I am unable to play specific quality video with audio. Actually I wanted to implement manual bitrate control of video in player, for this purpose I parse the master playlist in order to get url of different bitrate video. I am getting the HLS file from Azure media service in which video is encoded with different bitrate.
Following shows that how my master playlist looks like:
specific quality video url only contains video fragment not audio. Suggest me how I can retrieve specific quality video with audio from Azure Media Service.
ios swift avplayer hls azure-media-services
ios swift avplayer hls azure-media-services
edited Nov 14 '18 at 20:31
naf123
asked Nov 14 '18 at 19:58
naf123naf123
2416
2416
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
That's correct - the current HLS specification requires that the tracks are not muxed together when used with fragmented MP4 segments or TS segments.
To get back a track with video and audio muxed together, you can request the very old version of the HLS spec which supported muxed audio and video TS segments. Just use the format=m3u8-aapl-v3 on the URL, and use the audioTrack to point to the specific audio track to mux if needed (optional)
/manifest(format=m3u8-aapl-v3,audioTrack=audio_1)
The other workflow is to submit an "subclipping" encoding job and just get back a normal Mp4 file with the audio and video muxed back together.
Be aware though that the industry has mostly moved on to the latest HLS and DASH specs which specify that all tracks are un-muxed (seperate audio and video tracks.) Most streaming players support the latest un-muxed CMAF style streams from HLS and DASH.
thanks for your response and I finally got the solution after searching a lot.One more thing I want to ask you that in future the format:format=m3u8-aapl-v3 would be depreciated?or in future would I not be able to get muxed audio and video together using format=m3u8-aapl-v3 ?
– naf123
Nov 15 '18 at 14:39
We will definitely keep support around for v3, that we can't easily deprecate as there are still a lot of legacy devices out there that support it. But you should be aware that Apple's plan is to move over to CMAF completely - which would be unmuxed Mp4 fragments per RFC 8216https://tools.ietf.org/html/rfc8216#section-3.3
– johndeu
Nov 15 '18 at 21:03
got it.........
– naf123
Nov 16 '18 at 21:42
add a comment |
Your Answer
StackExchange.ifUsing("editor", function ()
StackExchange.using("externalEditor", function ()
StackExchange.using("snippets", function ()
StackExchange.snippets.init();
);
);
, "code-snippets");
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "1"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53307902%2fgetting-separate-url-of-video-and-audio-after-parse-the-master-playlist-file%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
That's correct - the current HLS specification requires that the tracks are not muxed together when used with fragmented MP4 segments or TS segments.
To get back a track with video and audio muxed together, you can request the very old version of the HLS spec which supported muxed audio and video TS segments. Just use the format=m3u8-aapl-v3 on the URL, and use the audioTrack to point to the specific audio track to mux if needed (optional)
/manifest(format=m3u8-aapl-v3,audioTrack=audio_1)
The other workflow is to submit an "subclipping" encoding job and just get back a normal Mp4 file with the audio and video muxed back together.
Be aware though that the industry has mostly moved on to the latest HLS and DASH specs which specify that all tracks are un-muxed (seperate audio and video tracks.) Most streaming players support the latest un-muxed CMAF style streams from HLS and DASH.
thanks for your response and I finally got the solution after searching a lot.One more thing I want to ask you that in future the format:format=m3u8-aapl-v3 would be depreciated?or in future would I not be able to get muxed audio and video together using format=m3u8-aapl-v3 ?
– naf123
Nov 15 '18 at 14:39
We will definitely keep support around for v3, that we can't easily deprecate as there are still a lot of legacy devices out there that support it. But you should be aware that Apple's plan is to move over to CMAF completely - which would be unmuxed Mp4 fragments per RFC 8216https://tools.ietf.org/html/rfc8216#section-3.3
– johndeu
Nov 15 '18 at 21:03
got it.........
– naf123
Nov 16 '18 at 21:42
add a comment |
That's correct - the current HLS specification requires that the tracks are not muxed together when used with fragmented MP4 segments or TS segments.
To get back a track with video and audio muxed together, you can request the very old version of the HLS spec which supported muxed audio and video TS segments. Just use the format=m3u8-aapl-v3 on the URL, and use the audioTrack to point to the specific audio track to mux if needed (optional)
/manifest(format=m3u8-aapl-v3,audioTrack=audio_1)
The other workflow is to submit an "subclipping" encoding job and just get back a normal Mp4 file with the audio and video muxed back together.
Be aware though that the industry has mostly moved on to the latest HLS and DASH specs which specify that all tracks are un-muxed (seperate audio and video tracks.) Most streaming players support the latest un-muxed CMAF style streams from HLS and DASH.
thanks for your response and I finally got the solution after searching a lot.One more thing I want to ask you that in future the format:format=m3u8-aapl-v3 would be depreciated?or in future would I not be able to get muxed audio and video together using format=m3u8-aapl-v3 ?
– naf123
Nov 15 '18 at 14:39
We will definitely keep support around for v3, that we can't easily deprecate as there are still a lot of legacy devices out there that support it. But you should be aware that Apple's plan is to move over to CMAF completely - which would be unmuxed Mp4 fragments per RFC 8216https://tools.ietf.org/html/rfc8216#section-3.3
– johndeu
Nov 15 '18 at 21:03
got it.........
– naf123
Nov 16 '18 at 21:42
add a comment |
That's correct - the current HLS specification requires that the tracks are not muxed together when used with fragmented MP4 segments or TS segments.
To get back a track with video and audio muxed together, you can request the very old version of the HLS spec which supported muxed audio and video TS segments. Just use the format=m3u8-aapl-v3 on the URL, and use the audioTrack to point to the specific audio track to mux if needed (optional)
/manifest(format=m3u8-aapl-v3,audioTrack=audio_1)
The other workflow is to submit an "subclipping" encoding job and just get back a normal Mp4 file with the audio and video muxed back together.
Be aware though that the industry has mostly moved on to the latest HLS and DASH specs which specify that all tracks are un-muxed (seperate audio and video tracks.) Most streaming players support the latest un-muxed CMAF style streams from HLS and DASH.
That's correct - the current HLS specification requires that the tracks are not muxed together when used with fragmented MP4 segments or TS segments.
To get back a track with video and audio muxed together, you can request the very old version of the HLS spec which supported muxed audio and video TS segments. Just use the format=m3u8-aapl-v3 on the URL, and use the audioTrack to point to the specific audio track to mux if needed (optional)
/manifest(format=m3u8-aapl-v3,audioTrack=audio_1)
The other workflow is to submit an "subclipping" encoding job and just get back a normal Mp4 file with the audio and video muxed back together.
Be aware though that the industry has mostly moved on to the latest HLS and DASH specs which specify that all tracks are un-muxed (seperate audio and video tracks.) Most streaming players support the latest un-muxed CMAF style streams from HLS and DASH.
answered Nov 14 '18 at 20:35
johndeujohndeu
1,11667
1,11667
thanks for your response and I finally got the solution after searching a lot.One more thing I want to ask you that in future the format:format=m3u8-aapl-v3 would be depreciated?or in future would I not be able to get muxed audio and video together using format=m3u8-aapl-v3 ?
– naf123
Nov 15 '18 at 14:39
We will definitely keep support around for v3, that we can't easily deprecate as there are still a lot of legacy devices out there that support it. But you should be aware that Apple's plan is to move over to CMAF completely - which would be unmuxed Mp4 fragments per RFC 8216https://tools.ietf.org/html/rfc8216#section-3.3
– johndeu
Nov 15 '18 at 21:03
got it.........
– naf123
Nov 16 '18 at 21:42
add a comment |
thanks for your response and I finally got the solution after searching a lot.One more thing I want to ask you that in future the format:format=m3u8-aapl-v3 would be depreciated?or in future would I not be able to get muxed audio and video together using format=m3u8-aapl-v3 ?
– naf123
Nov 15 '18 at 14:39
We will definitely keep support around for v3, that we can't easily deprecate as there are still a lot of legacy devices out there that support it. But you should be aware that Apple's plan is to move over to CMAF completely - which would be unmuxed Mp4 fragments per RFC 8216https://tools.ietf.org/html/rfc8216#section-3.3
– johndeu
Nov 15 '18 at 21:03
got it.........
– naf123
Nov 16 '18 at 21:42
thanks for your response and I finally got the solution after searching a lot.One more thing I want to ask you that in future the format:format=m3u8-aapl-v3 would be depreciated?or in future would I not be able to get muxed audio and video together using format=m3u8-aapl-v3 ?
– naf123
Nov 15 '18 at 14:39
thanks for your response and I finally got the solution after searching a lot.One more thing I want to ask you that in future the format:format=m3u8-aapl-v3 would be depreciated?or in future would I not be able to get muxed audio and video together using format=m3u8-aapl-v3 ?
– naf123
Nov 15 '18 at 14:39
We will definitely keep support around for v3, that we can't easily deprecate as there are still a lot of legacy devices out there that support it. But you should be aware that Apple's plan is to move over to CMAF completely - which would be unmuxed Mp4 fragments per RFC 8216https://tools.ietf.org/html/rfc8216#section-3.3
– johndeu
Nov 15 '18 at 21:03
We will definitely keep support around for v3, that we can't easily deprecate as there are still a lot of legacy devices out there that support it. But you should be aware that Apple's plan is to move over to CMAF completely - which would be unmuxed Mp4 fragments per RFC 8216https://tools.ietf.org/html/rfc8216#section-3.3
– johndeu
Nov 15 '18 at 21:03
got it.........
– naf123
Nov 16 '18 at 21:42
got it.........
– naf123
Nov 16 '18 at 21:42
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53307902%2fgetting-separate-url-of-video-and-audio-after-parse-the-master-playlist-file%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown