Can ffmpeg support creating DASH “availabilityStartTime” with milliseconds?
I'm currently trying to use FFMpeg to capture my webcam , output it to dash and stream it live.
I noticed that the "availabilityStartTime" parameter created in the MPD file is without the milliseconds part.
availabilityStartTime="2018-12-31T14:47:13Z"
I noticed that the ffmpeg library use "get_utc_date_time_insec" to fill the availabilityStartTime in the MPD file.
Is there a way for ffmpeg to fill the availabilityStartTime with complete timestamp?
Thank you
ffmpeg mpeg-dash dash
asked Dec 31 '18 at 15:08
Shachar LevyShachar Levy
1
|
show 1 more comment
I'm currently trying to use FFMpeg to capture my webcam , output it to dash and stream it live.
I noticed that the "availabilityStartTime" parameter created in the MPD file is without the milliseconds part.
availabilityStartTime="2018-12-31T14:47:13Z"
I noticed that the ffmpeg library use "get_utc_date_time_insec" to fill the availabilityStartTime in the MPD file.
Is there a way for ffmpeg to fill the availabilityStartTime with complete timestamp?
Thank you
ffmpeg mpeg-dash dash
asked Dec 31 '18 at 15:08
Shachar LevyShachar Levy
1
1
Not implemented, but it could be added to the code. But why would you need such precision here?
– slhck
Dec 31 '18 at 15:43
ffmpeg is using ISO-8601 format for date time. Although not specified anywhere in the DASH spec (ISO 23009), all examples use the 8601 format. So it's unlikely that this would be changed.
– Gyan
Dec 31 '18 at 16:23
We need this information to be as precised as possible as we count on the availabilityStartTime for synchronization between two live streams.
– Shachar Levy
Jan 1 at 9:15
@Gyan DASH uses XML'sxs:dateTimefor timing, which can use millisecond precision. But it's unlikely that this is needed in practice.
– slhck
Jan 1 at 12:25
@slhck I agree with you , however we do have a case where the extra milliseconds data is important for us. If the Dash spec does not conflict with the ffmpeg implementation (meaning that the complete timestamp can be used) , why not adding it?
– Shachar Levy
Jan 1 at 12:37
|
show 1 more comment
I'm currently trying to use FFMpeg to capture my webcam , output it to dash and stream it live.
I noticed that the "availabilityStartTime" parameter created in the MPD file is without the milliseconds part.
availabilityStartTime="2018-12-31T14:47:13Z"
I noticed that the ffmpeg library use "get_utc_date_time_insec" to fill the availabilityStartTime in the MPD file.
Is there a way for ffmpeg to fill the availabilityStartTime with complete timestamp?
Thank you
ffmpeg mpeg-dash dash
asked Dec 31 '18 at 15:08
Shachar LevyShachar Levy
1
I'm currently trying to use FFMpeg to capture my webcam , output it to dash and stream it live.
I noticed that the "availabilityStartTime" parameter created in the MPD file is without the milliseconds part.
availabilityStartTime="2018-12-31T14:47:13Z"
I noticed that the ffmpeg library use "get_utc_date_time_insec" to fill the availabilityStartTime in the MPD file.
Is there a way for ffmpeg to fill the availabilityStartTime with complete timestamp?
Thank you
ffmpeg mpeg-dash dash
ffmpeg mpeg-dash dash
asked Dec 31 '18 at 15:08
Shachar LevyShachar Levy
1
asked Dec 31 '18 at 15:08
Shachar LevyShachar Levy
1
asked Dec 31 '18 at 15:08
Shachar LevyShachar Levy
1
asked Dec 31 '18 at 15:08
Shachar LevyShachar Levy
1
asked Dec 31 '18 at 15:08
Shachar LevyShachar Levy
1
1
1
Not implemented, but it could be added to the code. But why would you need such precision here?
– slhck
Dec 31 '18 at 15:43
ffmpeg is using ISO-8601 format for date time. Although not specified anywhere in the DASH spec (ISO 23009), all examples use the 8601 format. So it's unlikely that this would be changed.
– Gyan
Dec 31 '18 at 16:23
We need this information to be as precised as possible as we count on the availabilityStartTime for synchronization between two live streams.
– Shachar Levy
Jan 1 at 9:15
@Gyan DASH uses XML'sxs:dateTimefor timing, which can use millisecond precision. But it's unlikely that this is needed in practice.
– slhck
Jan 1 at 12:25
@slhck I agree with you , however we do have a case where the extra milliseconds data is important for us. If the Dash spec does not conflict with the ffmpeg implementation (meaning that the complete timestamp can be used) , why not adding it?
– Shachar Levy
Jan 1 at 12:37
|
show 1 more comment
1
Not implemented, but it could be added to the code. But why would you need such precision here?
– slhck
Dec 31 '18 at 15:43
ffmpeg is using ISO-8601 format for date time. Although not specified anywhere in the DASH spec (ISO 23009), all examples use the 8601 format. So it's unlikely that this would be changed.
– Gyan
Dec 31 '18 at 16:23
We need this information to be as precised as possible as we count on the availabilityStartTime for synchronization between two live streams.
– Shachar Levy
Jan 1 at 9:15
@Gyan DASH uses XML'sxs:dateTimefor timing, which can use millisecond precision. But it's unlikely that this is needed in practice.
– slhck
Jan 1 at 12:25
@slhck I agree with you , however we do have a case where the extra milliseconds data is important for us. If the Dash spec does not conflict with the ffmpeg implementation (meaning that the complete timestamp can be used) , why not adding it?
– Shachar Levy
Jan 1 at 12:37
1
1
Not implemented, but it could be added to the code. But why would you need such precision here?
– slhck
Dec 31 '18 at 15:43
Not implemented, but it could be added to the code. But why would you need such precision here?
– slhck
Dec 31 '18 at 15:43
ffmpeg is using ISO-8601 format for date time. Although not specified anywhere in the DASH spec (ISO 23009), all examples use the 8601 format. So it's unlikely that this would be changed.
– Gyan
Dec 31 '18 at 16:23
ffmpeg is using ISO-8601 format for date time. Although not specified anywhere in the DASH spec (ISO 23009), all examples use the 8601 format. So it's unlikely that this would be changed.
– Gyan
Dec 31 '18 at 16:23
We need this information to be as precised as possible as we count on the availabilityStartTime for synchronization between two live streams.
– Shachar Levy
Jan 1 at 9:15
We need this information to be as precised as possible as we count on the availabilityStartTime for synchronization between two live streams.
– Shachar Levy
Jan 1 at 9:15
@Gyan DASH uses XML's
xs:dateTime for timing, which can use millisecond precision. But it's unlikely that this is needed in practice.– slhck
Jan 1 at 12:25
@Gyan DASH uses XML's
xs:dateTime for timing, which can use millisecond precision. But it's unlikely that this is needed in practice.– slhck
Jan 1 at 12:25
@slhck I agree with you , however we do have a case where the extra milliseconds data is important for us. If the Dash spec does not conflict with the ffmpeg implementation (meaning that the complete timestamp can be used) , why not adding it?
– Shachar Levy
Jan 1 at 12:37
@slhck I agree with you , however we do have a case where the extra milliseconds data is important for us. If the Dash spec does not conflict with the ffmpeg implementation (meaning that the complete timestamp can be used) , why not adding it?
– Shachar Levy
Jan 1 at 12:37
|
show 1 more comment
0
active
oldest
votes
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
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%2fsuperuser.com%2fquestions%2f1389284%2fcan-ffmpeg-support-creating-dash-availabilitystarttime-with-milliseconds%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Super User!
- 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%2fsuperuser.com%2fquestions%2f1389284%2fcan-ffmpeg-support-creating-dash-availabilitystarttime-with-milliseconds%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
1
Not implemented, but it could be added to the code. But why would you need such precision here?
– slhck
Dec 31 '18 at 15:43
ffmpeg is using ISO-8601 format for date time. Although not specified anywhere in the DASH spec (ISO 23009), all examples use the 8601 format. So it's unlikely that this would be changed.
– Gyan
Dec 31 '18 at 16:23
We need this information to be as precised as possible as we count on the availabilityStartTime for synchronization between two live streams.
– Shachar Levy
Jan 1 at 9:15
@Gyan DASH uses XML's
xs:dateTimefor timing, which can use millisecond precision. But it's unlikely that this is needed in practice.– slhck
Jan 1 at 12:25
@slhck I agree with you , however we do have a case where the extra milliseconds data is important for us. If the Dash spec does not conflict with the ffmpeg implementation (meaning that the complete timestamp can be used) , why not adding it?
– Shachar Levy
Jan 1 at 12:37