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
*Note (Same sample file as #315, can resend if needed)
Issue:
When saving the new metadata after calling Track.AdditionalFields.Clear() ATL does remove all of the fields (TXXX in this case) but also throw warnings in the console for each key name that read out as 'Field code [KEY-NAME-HERE] cannot be deleted because it has not been found on current TagData.'. LOCATION : 'C:\Users\<hidden>\AppData\Local\Temp\file.mp3'. Warning that does not make sense as all of the key where still deleted.
Sample code:
// Load the file in ATLTrackaudioTrack=newTrack("file.mp3");audioTrack.AdditionalFields?.Clear();boolwasNewMetadataApplyed=awaitaudioTrack.SaveAsync();// Warnings are reported here
*Require that the ATL loggers delegate is configured to see the warnings
The text was updated successfully, but these errors were encountered:
Thanks for your feedback. This is a specific issue that arises when ATL rewrites tagging systems that have a fixed set of fields and therefore do not support additional fields (in that case : ID3v1).
There's no actual problem; these messages shouldn't even show up.
File Type :
mp3
Format :
ID3v2
*Note (Same sample file as #315, can resend if needed)
Issue:
When saving the new metadata after calling
Track.AdditionalFields.Clear()
ATL does remove all of the fields (TXXX
in this case) but also throw warnings in the console for each key name that read out as'Field code [KEY-NAME-HERE] cannot be deleted because it has not been found on current TagData.'. LOCATION : 'C:\Users\<hidden>\AppData\Local\Temp\file.mp3'
. Warning that does not make sense as all of the key where still deleted.Sample code:
*Require that the ATL loggers delegate is configured to see the warnings
The text was updated successfully, but these errors were encountered: