Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Bug with offsets/length for description in custom tags (and possibly its data)

See original GitHub issue

This bug is probably related to what others have already reported, but I wanted to give an additional example. The offsets to where description resides seem to be calculated wrongly or using wrong encoding (?).

For example, a hex dump of a MP3 file containing custom Serato (a DJ software) ID3 frames - a small hex dump sample:

tagsbug

However, when parsed all of these ends up mangled for description etc. It’s not consistent either so I guess the offset/length is read from the wrong position - but this is just an initial guess.

The output ends up something like this:

[
  { id: 'TXXX:SERATO_PLAYCOUNT', value: '1' },
  {
    id: 'GEOB',
    value: {
      type: 'application/octet-stream',
      filename: '',
      description: 'erato Overview',    // Should be "Serato Overview", skipping 1 char
      data: <Buffer 65 72 61 74 6f ...  ---8X--- cut for brev.
    }
  },
  {
    id: 'GEOB',
    value: {
      type: 'application/octet-stream',
      filename: '',
      description: '',         // should have been "Serato Analysis", none...
      data: <Buffer 65 72 61 74 ...  ---8X--- cut for brev.
    }
  },
  {
    id: 'GEOB',
    value: {
      type: 'application/octet-stream',
      filename: '',
      description: 'erato Au',   //  "Serato Autotags", skipping one, length wrong
      data: <Buffer 65 72 61 74 ...   ---8X--- cut for brev.
    }
  },
  {
    id: 'GEOB',
    value: {
      type: 'application/octet-stream',
      filename: '',
      description: 'erato Markers_',   // "Serato Markers_", skipping one
      ...   ---8X--- etc.