You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
WAV: Constrain writer to stream length not file length
Previously, tags were simply written to the end of the file, but this would break files that have junk data appended.
This allows for files with appended junk data that falls outside of the stream length. This can be caused by buggy software misusing padding.
Copy file name to clipboardExpand all lines: CHANGELOG.md
+5Lines changed: 5 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -15,6 +15,11 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
15
15
* If a `free` atom claims to be larger than the remainder of the stream, parsing will simply stop. This will now only
16
16
be a `SizeMismatch` error in `Strict` mode. Invalid padding is a common issue in all tag formats due to buggy software,
17
17
so it's better to work around it by default rather than discard the entire stream as invalid.
18
+
***WAV**:
19
+
* When writing tags, the writer will be constrained to the stream size reported by the file, not by the file's actual length ([PR](https://github.com/Serial-ATA/lofty-rs/pull/517))
20
+
* Previously, tags were simply written to the end of the file, but this would break files that have junk data appended.
21
+
* This allows for files with appended junk data that falls outside of the stream length. This can be caused by buggy software
0 commit comments