[FFmpeg-trac] #6617(ffprobe:new): ffprobe feature request: add RFC 6381 string to stream metadata
FFmpeg
trac at avcodec.org
Sat Aug 26 00:27:49 EEST 2017
#6617: ffprobe feature request: add RFC 6381 string to stream metadata
-------------------------------------+-------------------------------------
Reporter: Melatonin64 | Type:
Status: new | enhancement
Component: ffprobe | Priority: normal
Keywords: rfc6381 | Version:
Blocking: | unspecified
Analyzed by developer: 0 | Blocked By:
| Reproduced by developer: 0
-------------------------------------+-------------------------------------
RFC6381 defines a string representation for media files that also includes
codec specifics such as profile, level etc.
Examples include:
{{{
video/mp4; codecs="avc1.42E01E, mp4a.40.2"
video/3gpp2; codecs="mp4v.20.9, mp4a.E1"
}}}
These strings are required for working with media on the web.
Examples of JS APIs that require these include
[https://developer.mozilla.org/en-
US/docs/Web/API/MediaSource/addSourceBuffer addSourceBuffer] and
[https://developer.mozilla.org/en-
US/docs/Web/API/HTMLMediaElement/canPlayType canPlayType].
It would be extremely useful if a property would be added to stream's
metadata, with the full codec string as a value (i.e. '''avc1.4D401F''')
Another property could be added to the format object, with the full
content type string (i.e. '''video/mp4; codecs="avc1.640028,
mp4a.40.2"''')
Related links:
[https://tools.ietf.org/html/rfc6381]
[https://ffmpeg.org/pipermail/ffmpeg-user/2016-October/034078.html]
--
Ticket URL: <https://trac.ffmpeg.org/ticket/6617>
FFmpeg <https://ffmpeg.org>
FFmpeg issue tracker
More information about the FFmpeg-trac
mailing list