id3v2 frameId RGAD causes failure to read tags about node-taglib-sharp

[benrr101]

Hi @digimezzo, thanks for the report and the investigation. I think this is actually a duplicate of #85 and you were really close to pinpointing what I think is the issue. A while back to improve the memory requirements for ID3v2 and unify the identifiers to make converting between ID3v2 versions easier, I went to a static list of identifiers from the ID3v2 docs. When reading the frames, the frame identifier is converted to a string and used as the index into the static list. Since RGAD is a non-standard identifier, pulling it up from the static list returns undefined.

Rather than allow that to throw later on, it should be creating an on-the-fly identifier and the frame factory should treat it as an UnknownFrame. I have a proposed solution for this but was waiting for the #85 reporter to test it out. Can you try out this beta version and see if it resolves the issue? If so, I can publish it as a hotfix in a couple days https://www.npmjs.com/package/node-taglib-sharp/v/5.2.1-fixid3v2nonstandardframes.1

[digimezzo]

@benrr101 I tried the beta version and it fixes the Argument null: id was not provided error. Thank you for the fix.

[benrr101]

@digimezzo, thanks for testing! I just published the v5.2.2 release that contains the fix https://www.npmjs.com/package/node-taglib-sharp/v/5.2.2

Interestingly, the RGAD frame isn't totally non-standard, it's a legacy ReplayGain frame format. As such, I think it'd be useful to add support for reading it and optionally writing it. However, I'll close this one and track that issue on another issue.

[stuartambient]

I have a proposed solution for this but was waiting for the #85 reporter to test it out.

Sorry @benrr101 never got to testing.