You can not select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
|
|
|
|
[STREAM]
|
|
|
|
|
codec_name=ac3
|
|
|
|
|
sample_fmt=fltp
|
|
|
|
|
channels=6
|
|
|
|
|
channel_layout=5.1(side)
|
|
|
|
|
[SIDE_DATA]
|
|
|
|
|
side_data_type=Audio Service Type
|
ffprobe: Rename Audio Service Type 'type' field to 'service_type'
677a030b26045acb50353d7954ae984ceefcd807 introduced more printable
side data types in ffprobe, however the Audio Service Type side data
'type' field that was introduced aliases an existing field of the same
name within the side data array, which can lead to JSON output like:
"side_data_list": [
{
"side_data_type": "Audio Service Type",
"type": 0
},
{
"side_data_type": "Stereo 3D",
"type": "side by side",
"inverted": 1
}
]
This, while technically valid JSON, is considered bad practice, since it
forces all downstream users to manually parse it and check all types;
it makes simple deserialization impossible. Worse, in som loosely
type languages, it can lead to silent bugs if exising code assumed
it was a different type.
As such, rename this second "type" field to "service_type".
Signed-off-by: Derek Buitenhuis <derek.buitenhuis@gmail.com>
3 years ago
|
|
|
service_type=0
|
|
|
|
|
[/SIDE_DATA]
|
|
|
|
|
[/STREAM]
|
