Hello,
I am using the Perl module of ExifTool 8.77 to retrieve FLAC/Vorbis information from a .flac music file. I receive the error "Tag NOTES conflicts with internal ExifTool variable". ExifTool still handles everything OK just rather a nuisance. Just a heads up really. I searched on the forum but didn't find any similar posts.
Here is a stack trace:
#####
Tag NOTES conflicts with internal ExifTool variable
at C:/Perl/site/lib/Image/ExifTool.pm line 5707
Image::ExifTool::GetTagInfoList('HASH(0x29949fc)', 'NOTES') called at C:/Perl/site/lib/Image/ExifTool.pm line 5734
Image::ExifTool::GetTagInfo('Image::ExifTool=HASH(0x5eb684)', 'HASH(0x29949fc)', 'NOTES', 'SCALAR(0x299441c)') called at C:/Perl/site/lib/Image/ExifTool.pm line 5851
Image::ExifTool::HandleTag('Image::ExifTool=HASH(0x5eb684)', 'HASH(0x29949fc)', 'NOTES', 'Medieval CUE Splitter (www.medieval.it)', 'Index', 6, 'DataPt', 'SCALAR(0x298f2f4)', 'DataPos', ...) called at C:/Perl/site/lib/Image/ExifTool/Vorbis.pm line 160
Image::ExifTool::Vorbis::ProcessComments('Image::ExifTool=HASH(0x5eb684)', 'HASH(0x269aedc)', 'HASH(0x29949fc)') called at C:/Perl/site/lib/Image/ExifTool.pm line 5659
Image::ExifTool::ProcessDirectory('Image::ExifTool=HASH(0x5eb684)', 'HASH(0x269aedc)', 'HASH(0x29949fc)', undef) called at C:/Perl/site/lib/Image/ExifTool.pm line 5921
Image::ExifTool::HandleTag('Image::ExifTool=HASH(0x5eb684)', 'HASH(0x298d8d4)', 4, undef, 'DataPt', 'SCALAR(0x298f2f4)', 'DataPos', 1520) called at C:/Perl/site/lib/Image/ExifTool/FLAC.pm line 247
Image::ExifTool::FLAC::ProcessFLAC('Image::ExifTool=HASH(0x5eb684)', 'HASH(0x252c64c)') called at C:/Perl/site/lib/Image/ExifTool.pm line 1633
Image::ExifTool::ExtractInfo('Image::ExifTool=HASH(0x5eb684)', undef) called at C:/Perl/site/lib/Image/ExifTool.pm line 1290
######
On another note do you think there will be any write support for MP3/M4A/FLAC tags in the future?
Thanks for this report. This will be fixed in ExifTool 8.78.
About the write support: It isn't very likely that this will be added in the foreseeable future. I started adding ID3 write support a long while back but it was a real mess so it never got finished. The ID3 specification is very poor, and it is very frustrating to implement.
- Phil