Hello,
I don't know if this is a bug or just a limitation of the program or my system. I am running windows 10 (Up to date).
I am using the latest version (3.08) of MP3TAG and am having a problem with a simple action I have created. (Format value "COMMENT":$left(%albumartist%,1)%albumartist%) The action works fine on small quantities of MP3 files, say 100 or less, however, if I select a larger quantity say over 200 The action runs until it hits around 120 to 125 files and then hangs. I then have to terminate the program using Task Manager and sometimes force a reboot.
If the action runs in general and only refuses to run on some files, then I would assume that it is something local.
Either the treated files are corrupted to some extent (which you would have to really check and not just say that they are ok - also, being playable does not mean that the tag data is ok. There are some links to programs to check the files in the FAQs)
And then there is the possibilty that other programs notice that some change is on the way and try to find out what that is and block the files. So you would have to find out whether this is the case and which program that might be.
Thanks for getting back to me.
I believe that all the files are OK. It only seems to hang on large selections of files. If I select 100 or less there is no problem. If I select a large quantity it hangs. Once I reboot and repopulate the list I can tell exactly where it has stopped. When I select the next file to be processed it does the action so I doubt it is the file.
Is it possible that it is a buffering issue or a memory space issue?
I have 8192MB memory, 3852MB cached. I am using a 1TB drive with 653GB free space.
I have tried running the program alone, no other user apps running. Also started as administrator with same results. Unfortunately windows 10 runs so much stuff in the background it is hard to determine if one of them could be the problem. Any other suggestions? I have over 7K tracks to do and don't want to have to do that in small blocks.
MP3tag is a 32bit application so it uses no more than 4GB of Memeory.
Again: unless you rule out all the local influences - and these are foremost problematic files and simultaneous access - it is virutally impossible to guess any further.
Esp. if you have interrupted the process forcefully the state of the files is questionable.
So, please, run a check on all the files.
Hi, I bow to your expertise. I can not believe that over 10% of my files had errors. I ran MP3Val on the entire library and that was the result. Most were garbage at the end of the file but a few were VBR without VBR headers. Would you have any idea as to why this could happen. I am very careful when manipulating the files. I use MP3TAG exclusively to build the tags and to name the file and build the folders for the files. I use Audacity to edit them if there is too much dead space or if there are multiple tracks in the one file.
Anyway thank you very much for the assist.
Thank you.
Now that you have become suspicious as to what might have happened to the files - could you also run Mp3diags? Not all checkers find (and possibly correct) all the errors.
After MP3diags has loaded and analyzed all the files, it is a good practice to use the yellow filter and move one of the found problems from the right column to the left and see which files have to be treated.
Some "errors" like low quality or missing cover are no real errors. Others, like bad or unknown streams should be corrected.
Hard to say - sometimes Audacity messes things up when used as tagger.
I think the only way out is to regularly check the collection with the checking tools, or, if not the whole collection, then at least the new files.
I've replied to this as the problem is similar. I recently started to add new ripped files to my collection 1 CD at a time. As suggested earlier I now rip, MP3Val and MP3Diag each group of files and correct as required before loading them into MP3Tag. The problem I am now having is that MP3Tag hangs each time I try to do anything. What I am doing is renaming the files to contain all the tags I have. I then run actions to manipulate various tags to get the information formatted the way I want. Once that is successful I rename the files to the format I need using the tags.
Are there any other tools you can suggest to help correct the file errors?
If these are freshly ripped tracks from CD, I would have to think they should be considered intact and therefore not need to be evaluated by any programs for errors. Have you tried to do the operations you would like to do on any of these rips without using MP3Val or MP3Diag?
The files are all from commercial CD collection. I use AudioGrabber to do the rip. I have used this software for a goo many years without problems. I tried reinstalling Audiograbber and MP3Tag but that made no difference. This morning I installed the 2 programs, Audiograbber and MP3Tag, on my laptop and loaded the files that were causing the failure on my desktop and everything went as it should. I was able to manipulate all the files without error. I also did a rip of a CD and then opened the files in the MP3Tag tool and there were no problems. I now suspect there is a problem on my desktop but am unsure as to what it could be. I'm thinking it may be the MP3 encoder. I'm trying to find out what versions are being used by Audiograbber and MP3Tag.
Yes, Normally I have had no problems using Audiograbber and then MP3Tag. If you check the earlier posts from Aug 2021, I had a similar problem but that was on files I had not ripped but were from MP3 CDs I got from a friend. Once those were repaired by MP3Val and MP3Diag everything went OK. This current problem is something new. I'm hoping someone here has suggestions as to how to go about fixing this without having to start all over with a windows 10 reinstall and reloading all my software.
And it looks like general file access.
So you would have to check the usual like access rights, ownership.
And it is something that you have to investigate locally as no one can find out the differences in configurations between your laptop and desktop.
I'm not sure I understand how access rights would cause this as the problem does not seem to be on every file. Last night I ripped a CD and opened the MP3s in MP3Tag. I tried doing a change Tag to Filename and it hung. I then did it to one file at a time and it all worked. When I tried to save the changes the program hung again.
Besides I have not made any changes to access, ownership, on the desktop so don't see why it should suddenly be an issue. I have experienced a number of Microsoft windows updates over the last month or so, as well as some new version releases of some software. I'm leaning more towards some conflict in the MP3 encoder. I'm just not sure where to start or how to proceed with a repair.
Doesn't all this look like a genuine Windows problem?
MP3tag is only the messenger.
So I would check the Windows pages and find out if there are any reports.
The intermittent problems then look also like old causes like anti-virus programs, indexers that also look into the folders that contain the currently modified files.
Check this forum for "Defender":
Problem solved!
It was definitely a windows problem. I uninstalled all the programs associated with MP3 file including the Lame files. I then ran the windows Media Creation Tool keeping all my files and apps. I then installed Audiograbber and ran several disks through it. Then I installed MP3Tag and tried to manipulate the MP3s. It worked like a charm and a lot faster. I think this is something I might do once a year as it seems to have removed some garbage that was slowing down my machine in general.
Just wanted to add an additional comment. I now believe that the problem is not windows. I think the issue is between Audiograbber and MP3Tag and the culprit is Audiograbber. I noticed that Audiograbber is now installing its own Lame drivers which it never did before.
When I do a complete uninstall of Audiograbber the problem goes away. I am now using a different ripper and have no problems.
The 2020 Edition of Audiograbber 1.83 offers integrated MP3 functionality (no additional installation of the previous MP3 plugin is required anymore).
and
Since Audiograbber 1.83 (2020 Edition) it is no longer necessary to install and configure an MP3 encoder by yourself.
From the setup screen of the mentioned plugin:
This plugin adds the MP3 encoder LAME 3.99 to Audiograbber, which allows Audiograbber to create high quality MP3 files. The LAME encoder is downloaded from the web during installation, so please make sure you have a valid internet connection.
I can not believe that over 10% of my files had errors. I ran MP3Val on the entire library and that was the result. Most were garbage at the end of the file but a few were VBR without VBR headers. Would you have any idea as to why this could happen. I am very careful when manipulating the files. I use MP3TAG exclusively to build the tags and to name the file and build the folders for the files. I use Audacity to edit them if there is too much dead space or if there are multiple tracks in the one file.