Created attachment 129181 [details] screenshot and test file SUMMARY STEPS TO REPRODUCE Open the "test.mp3" attached file OBSERVED RESULT ID3 tags not read with version 3.8.3, OK on version v 3.6.2 EXPECTED RESULT SOFTWARE/OS VERSIONS macOS: Mojave ADDITIONAL INFORMATION See screenshot attached
This seem to be a one shot random bug. After reporting it, I've tried again and everything was OK on both versions... Don't waste your time on this. My apologies and thank you for the GREAT software :)
Well... I's still occurring randomly on v3.8.3 ... Annoying :( I will take a try to other versions.
I tried to reproduce this both on Linux and on macOS, but the tags are always read. Is it possible that the file is locked by another application - a behavior which I would rather expect from Windows? For MP3 files with ID3v2.3.0 tags, you have the option of using two libraries: TagLib (the default) or id3lib. You could try to switch to the other library in the Plugins tab of the preferences (and restart Kid3 afterwards). A more advanced examination would involve monitoring Kid3 using dtruss or a similar tool and check what exactly is going on. This should also reveal errors occurring when accessing the file.
Urs, if you set the status to NEEDSINFO, please clarify which information you need from the reporter to further investigate the issue. Our janitor will watch those bugs and regularily ask the reporter to add the missing information.
Sorry, Christoph, I thought that it would be clear that I need the following information: - Does the observed result occur with both TagLib and id3lib or only one of these libraries? - dtruss output of file access when the observed result happens.
(In reply to Urs Fleisch from comment #3) > I tried to reproduce this both on Linux and on macOS, but the tags are > always read. Is it possible that the file is locked by another application - > a behavior which I would rather expect from Windows? > > For MP3 files with ID3v2.3.0 tags, you have the option of using two > libraries: TagLib (the default) or id3lib. You could try to switch to the > other library in the Plugins tab of the preferences (and restart Kid3 > afterwards). > > A more advanced examination would involve monitoring Kid3 using dtruss or a > similar tool and check what exactly is going on. This should also reveal > errors occurring when accessing the file. Hello Urs, Today no way to reproduce the issue... As soon as it occurs I will take a try by following your instructions.