MEDIAINFO ALTERNATIVE SOFTWARE
What's the reason of their existence and why does some encoders/video editing software injecting these metadata into the file?Īccording to Mulvya's answer, running a simple stream-copy on the file can reset the timestamps! So long story short, I'd like to know what are these metadata used for? "Surprisingly", substracting the length and the delay gives me the correct duration.Īlso, it is really embarrassing that some encoder libraries count these delays towards the total length, but some of them doesn't! Seemingly there's no way to distinguish which length values are correct and which were incremented accordingly! and Delay or Delay_relative_to_video in Mediainfo's: mediainfo -full -output=XML /path/to/the/file/converter/master/194/194_video.flv
Stream #0:1: Audio: aac (LC), 44100 Hz, stereo, fltp Metadatacreator : Yet Another Metadata Injector for FLV - Version 1.4ĭuration: 00:01:44.77, start: 58.033000, bitrate: 984 kb/s There's a software videoconferencing solution wich produces these special files, and when our videoprocessing software examines these files, it gets longer duration values than the actual length of the content, thus storing wrong data into the database which causes more trouble in the postprocessing phase.įor example, we recorded a 46 second long video, which was detected as 104.7 seconds long.Īfter inspecting the file with FFmpeg and Mediainfo, it turned out that the original file had a so called "delay" value which can be seen as start time in FFmpeg's output: Input #0, flv, from '/path/to/the/file/converter/master/194/194_video.flv': Recently, I'm forced to fiddle with a nasty little problem with videos that have some special metadata attributes, namely "delay" or "delay_relative_to_video".
0 kommentar(er)
