I noticed that after modifying tags in foobar2000 that Open() would fail with the following error:
frame went over tag area
This was due to foobar2000 truncating the padding after the final frame and Open() was reading the audio data as the next frame size. The id == "" check should have caught this, but even though []byte{0, 0, 0, 0} will be printed as an empty string, it is not equivalent.
I noticed that after modifying tags in foobar2000 that
Open()
would fail with the following error:frame went over tag area
This was due to foobar2000 truncating the padding after the final frame andOpen()
was reading the audio data as the next frame size. Theid == ""
check should have caught this, but even though []byte{0, 0, 0, 0} will be printed as an empty string, it is not equivalent.