I realise that 160K of music tracks is a lot, but when i added these to mp3tag, several hundred of them only had the filename populated, all other tags were empty, however as i click on a filename the TAG fields are instantly populated, not helpful as I'm looking for albums where the album TAG is missing, any thoughts please, could break it up into smaller numbers of tracks, but hope thats not the only answer, hoped for a refresh button which would populate empty TAG fields thanks
See the documentation on keyboard shortcuts:
Maybe it's just me, but wouldn't it have been so much easier to tell me which shortcut I need, if in fact this will resolve my problem
I assume CTRL B is the one I need.....am I correct,
Thanks
Does it do what you want?
I don't know yet, as I'm working on some other music tracks, don't think I can have 2 copies of MP3tag open at the same time, be good if I could.
I had thought I'd lost tons of tag info for hundreds of my music tracks, very odd that clicking on the filename caused the TAG fields to populate, could that be a bug ![]()
With so few details about the circumstances and the environment it could be anything, couldn't it?
See here for a guideline how to post a good support query:
esp. the part about screenshots, what you have done so far and what you have done to check the files for errors.
How can I show a screenshot of something that doesn't happen
Ok
Here goes
I load up my 160K MP3 tracks into mp3tag
When I sort by the album tag, hundreds of them gave zero tag information except the file name.
Then I left click on one of the filenames, any one of them, immediately all the TAG fields are populated, for THAT TRACK ONLY i e. Artist, title, album, album artist track etc etc.
If I then lift click on the next filename the same thing happens, also if I click Down on the keyboard moving slowly through the tracks, as I pass a track it populated all tag fields as above. Can't explain it any clearer, sorry, assume it's a bug, but then who am I to say ![]()
![]()
![]()
The files do not have errors if I load up a dozen or so albums all is perfect, guess it's the quantity that trips this bug.
Which version are you running? 32-bit or 64-bit?
64 bit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Think that's enough characters lol
Then
should be managed without problems.
But it doesn't manage it, never loaded such a high number before, always been perfect up to now, see if florien can shed some light on this issue
I believe you are looking for the refresh function using the F5 key.
160k tracks is a lot, but not more than many other users here have reported using in the past. The 64-bit version should handle that. Are you using the library feature for faster loading?
Options>Library>[Enable]
This will speed up initial loading for the defined main library folder location. Otherwise perhaps your system is taking some time to process these 160k files before they can be fully displayed?
I don't think the phenomenon you describe has anything to do with loading too many files. Before the 64-bit version of Mp3tag was available, I would always run out of memory if I didn't split my library during loading and only loaded parts of it. But that never manifested itself in this way. Rather, it was simply not possible to load the full amount of files. I can now load far more files than you mentioned without such problems.
However, it must be said that the memory requirement depends not only on the number of files but also on the library usage and the memory requirements of the tags. For me, the average size of embedded covers per file is 160 KB at most. And since the memory requirements of the covers largely determine the size of the metadata portion, since the few bytes for the text portion hardly add any more memory, it does make a difference whether you use extremely high-resolution images with memory requirements in the gigabyte range, and several of them at once. I don't get more than 3 GB of memory usage for Mp3tag in the Task Manager when all files are loaded.
You haven't said much about:
- which version of Mp3tag you're using
- what type of drive the files are stored on (network drive, local hard drive, etc.)
- if you use the library option of Mp3tag for all loaded directories and the location of the library
Your description could be interpreted to mean that this problem doesn't occur immediately after the files have been loaded, but only after sorting, and that only a few hundred are affected. Is that so?
It occurs immediately and yes only a few hundred files affected
Using latest mp3tag to an externally usb 3 HDD and everything is default thanks
What other recent changes were made to your system or library prior to seeing this? You have been on the forum for a long time and very active for the past few months and this didn't come up in any of those threads.
You did post a similar problem in 2013 that popped up after using a separate program to change the gains. But you didn't mention if you had resolved this or not back then.
Could be to do with mp3gai.
Wil turn off as suggested in previous post in settings, maybe that's the reason, but didn't affect all tracks although all have had MP3 gain applied
Thanks
Unfortunately, you still haven't said whether you use the Library feature in Mp3tag. The most obvious cause of the phenomenon is related to this and occurs when the library and tags in the files get out of sync.
This can happen when tags are edited outside of Mp3tag and the editing software doesn't update the modification date. It can also happen when using Mp3tag if the setting to retain the modification date is selected and more than one installation of Mp3tag is used. By this, I don't mean multiple instances at the same time (which isn't possible), but rather multiple portable installations or one standard installation and one portable installation.
The reason:
When the Library is enabled, when loading existing entries in the Library, Mp3tag primarily reads the tags from the library, not from the files. Only for newly added files and files with a changed date are the tags read from the files and the library updated. If the library already knows the file without tags, it won't notice that tags have been added in the meantime, without even noticing, since not even the date has changed.
The consequence is that these tags only appear in the display after loading when they are selected or otherwise refreshed.
Additional note:
The worst thing you can do in such a case is to simply save files that don't display any content in MP3tag due to the circumstances described. They will then be saved exactly as they appear – with no or incorrect content (from the library), and they are gone forever.
So could I turn the library featute off to prevent this from happening I am happy to accept lower speeds for populating tag data fields
Thanks
The Library feature isn't necessarily the problem and, in my opinion, shouldn't be disabled in the long run. I wrote that because it might explain the phenomenon you've noticed. Ultimately, only you can say whether that applies to your case. If so, you've edited tags externally or worked with multiple installations of Mp3tag and didn't let the software change the modification date. In my opinion, you should never do the latter.
You don't have to navigate to each file individually to display its metadata again. You can also select all affected files together and press CTRL-t. In that case, the data will be read from the tags.
You can easily determine whether parts of the Library are currently out of sync by disabling the Library function in Mp3tag, restarting Mp3tag, and reloading the files. If the problem then goes away, then my suspicion is correct. Unless, of course, you've already brought everything back into sync, in which case this test would be meaningless.
Thank you for such a helpful reply
The library is in fact turned off, have turned off reading some data in case that's an issue, will try again later by address Ng all 160K tracks but ctrlT is good to know
Thanks again