Opened 5 years ago

Closed 8 months ago

#7217 closed defect (fixed)

ffprobe produces wrong XML; "data_hash" attribute sometimes in text

Reported by: Carl Reinke Owned by:
Priority: normal Component: ffprobe
Version: git-master Keywords:
Cc: Blocked By:
Blocking: Reproduced by developer: no
Analyzed by developer: no


The "data_hash" attribute is sometimes in the text instead of in the tag.

How to reproduce:

$ ffprobe -v 0 -print_format xml=xsd_strict=1 -show_packets -show_data_hash sha160 -noshow_private_data -read_intervals %+#1 kahvi048_pinza-thickline.ogg
<?xml version="1.0" encoding="UTF-8"?>
<ffprobe:ffprobe xmlns:xsi='' xmlns:ffprobe='' xsi:schemaLocation=' ffprobe.xsd'>
        <packet codec_type="audio" stream_index="0" pts="-128" pts_time="-0.002902" dts="-128" dts_time="-0.002902" duration="128" duration_time="0.002902" size="60" pos="4315" flags="K_">
                <side_data side_data_type="Metadata Update"/>
 data_hash="SHA160:5e0e1c526cd631e016e378bc99302e63ea40e381"        </packet>

File used is available here.

Change History (8)

comment:1 by Carl Eugen Hoyos, 5 years ago

Version: 3.2.4git-master

comment:2 by Balling, 4 years ago

Status: newopen

Yep... So where should it be? Like in <side_data data_hash="SHA160:5e0e1c526cd631e016e378bc99302e63ea40e381"> or where?

comment:3 by Carl Reinke, 4 years ago

According to the schema, it should be an attribute on the "packet" tag.

Last edited 4 years ago by Carl Reinke (previous) (diff)

comment:4 by Stefano Sabatini, 15 months ago

Cannot reproduce with latest master f7dd408d64013ae177c1f8d0e04418e5075db5bc.

Can you provide a sample reproducing this issue?

This or we should mark this as resolved.

comment:5 by Balling, 15 months ago

The file after redirect is here:

It still happens, data_hash="SHA160:5e0e1c526cd631e016e378bc99302e63ea40e381" should be in <packet codec_type="audio" data_hash="SHA160:5e0e1c526cd631e016e378bc99302e63ea40e381">

comment:6 by Stefano Sabatini, 14 months ago

Thanks for the sample, I was able to reproduce, patch sent to ML.

in reply to:  7 comment:8 by Stefano Sabatini, 8 months ago

Resolution: fixed
Status: openclosed
Note: See TracTickets for help on using tickets.