Releases: Zeugma440/atldotnet
Version 6.18
New
- General : New warning when reading a file illegally tagged with ID3v2 (e.g. MP4/M4A)
Track
: Support using inputStream
with a non-zero offset; make sureStream
position is reset to that initial offset when reusing it internally
Binaries are available from nuGet
Version 6.17
Changed
- ID3v2.2 : Mapping
Track.Description
to TT3 instead of TT1 - ID3v2.2 : Mapping
Track.Group
to TT1 - ID3v2.3-4 : Mapping
Track.Description
to TIT3 - General : Don't show any warning when trying to remove additional fields on tagging systems that don't support them (e.g.
AdditionalFields
on ID3v1)
Binaries are available from nuGet
Version 6.16
INTERFACE-BREAKING CHANGES
IMetaData.TrackNumber
is now string
type instead of ushort
. This will break your code is you're using low-level classes instead of Track
.
You can use ATL.Commons.Utils.ParseFirstIntegerPart
to safely retrieve the track number value as an integer.
NB : Using int.Parse
will fail when confronted to LP notation (e.g. "A1").
New
- New
Track.TrackNumberStr
field to manipulate track numbers as strings (useful for storing LP information, e.g. "A1")
NB1 : That field writes non-numeric values on tagging systems that support them technically, even if specs are against it (ID3v2)
NB2 : That field won't write non-numeric values on tagging systems that do not support them technically (e.g. MP4/M4A, ID3v1, SPC700)
Fixed
- MKA : Properly read files whose first Cluster doesn't start at Timestamp 0
- M3U : Fix wrong parsing of title/artist separator (
" - "
)
Technical
- Releases are now fully automated (thanks to @kitsumed) and now include symbols, deterministic build and compiler flags
Binaries are available from nuGet
Version 6.15
Changed
- Playlists : Write track metadata to playlist files even when defining files with their Path only
- XMP metadata : Anchor namespace declarations to RDF node instead of root node
Fixed
- M3U : Fix title formatting when reading from the playlist file
Binaries are available from nuGet
Version 6.14
Changed
- VorbisTag : Write multiple fields when there are multiple values (now for
AdditionalFields
too)
Fixed
- M4A/MP4 : Improve duration detection for fragmented MP4s
- M4A/MP4 : Don't write chapter picture track if there are no chapter pictures to write
Binaries are available from nuGet
Version 6.13
INTERFACE_BREAKING CHANGES
Track.BPM
type is nowfloat?
instead ofint?
Changed
- Generic / BPM field : Can now read and write float values
- VorbisTag : All fields with multiple values are now persisted as multiple fields instead of one field with multiple values, as per specs
Fixed
- M4A / MP4 : Files with a
mdta
metadata handler type can now be read
Binaries are available from nuGet
Version 6.12
Changed
- WAV : Now defaults to ID3v2 and Native tagging when writing on a tagless file
- WAV / SMPL : Don't write explicit size for the sample size
Binaries are available from nuGet
Version 6.11
Fixed
- General : Better detection of AAC data (vs. MP1-MP3 data) when loading using a
Stream
- General : Don't format LRC timestamp with DDdHH:MM:SS
- MP4/M4A : Only insert the 1x1 bogus chapter picture on files where user-defined chapter pictures are actually present
Thanks a lot to @gnattu for his PR~
Binaries are available from nuGet
Version 6.10
New
Support for Speex audio
Fixed
MP3 : Better detection of "freeform" VBR files using Settings.MP3_parseExactDuration = true
Binaries are available from nuGet
Version 6.09
New
- VorbisTag : Add mapping for SortAlbumArtist and SortArtist fields
Changed
- General : Changed the default behaviour so that M4A/MP4, FLAC, OGG/OPUS, MKA and WMA write into their native tagging system alone upon writing on a metadata-free file (instead of using an APEtag or ID3v2 clutch)
- M4A/MP4 : Better support for fields with multiple values (see #290 for details)
Thanks to @gnattu for his contribution~
Binaries are available from nuGet