taglib questions - 2.3.0
Uwe Dippel
udippel at gmail.com
Wed Jul 8 23:09:12 BST 2026
Okay, for the continuation of the question earlier, I was informed that the
message in question "does not come from taglib directly, but taglib's call
isValid() says that the file does not seem to be correctly structured".
Since I have carried those files over years, if not decades, and this
affects several dozens of video files (okay, I carry 4000), currently it
looks like an item popping up only recently.
And while these files play properly in VLC and dragon, btw., without
peculiarities, show no warnings in mediainfo, only in ffprobe lead to lines
like
[mov,mp4,m4a,3gp,3g2,mj2 @ 0x55c91f525840] st: 0 edit list: 1 Missing key
frame while searching for timestamp: 512
[mov,mp4,m4a,3gp,3g2,mj2 @ 0x55c91f525840] st: 0 edit list 1 Cannot find an
index entry before timestamp: 512.
.
Conceded, ffprobe and mediainfo do need more time to run on these files.
Though I never saw that message earlier. I don't know enough about
containers respectively coders to confirm the timestamp 512 as limit.
Looking forward to understand what is happening here,
Kind regards,
Uwe
On Sat, 4 Jul 2026 at 20:51, Uwe Dippel <udippel at gmail.com> wrote:
> No worries!
> Thanks a bunch for the information!
>
> Uwe
>
>
> On Sat, 4 Jul 2026 at 07:36, Urs Fleisch <urs.fleisch at gmail.com> wrote:
>
>> 2. Similar, with the version of taglib as in the subject, taglib informs
>>> about "TagLibHandler [...] does not appear to be a valid xyz file".
>>> This occurs for several dozen video files of different format; and had
>>> never been seen earlier.
>>> Using ffprobe, all those that I checked (they play perfectly well,
>>> despite the message), all indicate some "Cannot find an index entry
>>> before timestamp: 512", never observed earlier.
>>>
>>
>>
>>> Would you care to comment on my second question, about the seemingly new
>>> limit of 512 at searching index data not observed earlier?
>>> I am aware that it is not a bug, though I'd like to know if it stems
>>> from changes within taglib or the calling routine?
>>>
>>
>> Sorry for my late response, I was on vacation for a week. The message
>> "Cannot find an index entry before timestamp" is unrelated to TagLib. If I
>> search for it on GitHub, it looks like it is contained in
>> libavformat/mov.c, which is part of FFmpeg.
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/taglib-devel/attachments/20260709/9c3cb145/attachment.htm>
More information about the taglib-devel
mailing list