Some ID3v1 taggers actually overwrote the last 128 bytes of the last frame with data. This means that we should check the last full frame to see if it contains an ID3v1 tag 128 bytes from its end.
Additionally, because the file could be a badly joined set of MP3 files, this 128 byte tag could be at the end of every frame, and they should all be checked.
Checking for ID3 tags at arbitrary loctations is unwise; both because it's slow an because the loose ID3v1 standard means at best we'd be relying on heuristics. But we might allow it as an option?
Some ID3v1 taggers actually overwrote the last 128 bytes of the last frame with data. This means that we should check the last full frame to see if it contains an ID3v1 tag 128 bytes from its end.
Additionally, because the file could be a badly joined set of MP3 files, this 128 byte tag could be at the end of every frame, and they should all be checked.
Checking for ID3 tags at arbitrary loctations is unwise; both because it's slow an because the loose ID3v1 standard means at best we'd be relying on heuristics. But we might allow it as an option?