I know it doesn't have the silence. It will actually be really hard to find a file that would upload to the webpage given the 3MB max file size, which includes the APE tag. But good luck reproducing the errors and seeing what I have seen.
Then I will fail as adding APE tags does not do anythng to the payload part.
If the APE tags - as you think - are teh culprits for added silence, then this behaviour should be reproduceable. So adding APE tags to the already successfully attached file should modify it in the way that you described.
And? Does it?
If you have other files, you could share them after uploading them to a file hoster.
Here a screenshot of an audio editor of the original file (top) and the same file with APE tags - they look identical to me in respect to the audio part. At least there is no added silence.
I thnk the screenshots + the original file could show this. Did you see the screenshots? In any case that is what it did on my end. If you do want to split some of this later part of the thread away from the original post or two I understand. Go ahead, but it will need a title like "APE tags cause silence to be included on files, caution checking boxes you know nothing about in the tag MPEG menu". I am currently resizing my NYE mp3 playlist video which shows repeatedly that it had silences at the ends of songs over the 7:11:20 time of the (edited) video. I may upload it to archive website if you want to witness this factor. It is a long playlist of music showing lockscreen and sliding bar. I will include the original Who song Medac with the APE tag (above 3MB restriction of this site) on my Archive there.
You do not say what "it" is. Adding APE tags could not be "it". So what happened in the meantime? Which further processing steps are involved?
Adding ape tags is done by checking box that says ape tags under write is that right? (in toolbox, tags MPEG the checbox next to APE in the write section in the middle) change the original file by taking off the comment. change other factors like add album artist, and title. at the same time do add an APE tag. This will approximate what I did for 26000 songs which got APE tags and largely came up with anywhere from 10s to a few minutes added to lengths. That is all I did. No changes besides that.
uploaded in same way as the original file here a .txt.
Thank you.
I found that the next file has APE tags.
Here a screenshot of the original file and the latest from the audio editor:
The left shows the original file, the right section shows the file with APE tags.
The new file is reported in MP3diags to have an APE tag (which Mp3diags does not support but also does not treat as problematic data).
Both files are reported in MP3diags to have unsupported streams.
The original file:
The file with APE tags
And these unsupported streams may account for the silence that you found.
But that means that these files have been ripped in a way that corrupts the audio part - which would proove (again) that the files' problems originate outside MP3tag.
The file was originally ripped in iTunes. That's a whole lot of people who could easily experience problems just like I did. The Musicolet app warns people when they edit their tags. I know you don't really want to warn people in general but I think that you might add the warning when the box to write the APE tag is checked that it can cause issues and not to do it when it is unnecessary and unknown outcome.
Again I can see that you are vigilant about not accepting that this was caused by your program, however since there is not a pop up when the APE box is checked, and yet it was fairly easy for me to find, I would expect that some others at some point (for instance the 1 star reviewer on the Musicolet GPS from 2021 who was also having silence at the ends of his tracks), will also have this happen, while using your application. I appreciate that you are here for support of those of us, but since not everyone knows what the box does that writes the tags, or when it will take effect (presumably on save which you REFUSE to acknowledge that I have even asked about) you might want to add that warning box. Do what you want I really don't mind if you don't it's entirely on you.
There is nothing to acknowledge on the MP3tag side.
A warning about valid tags would be misleading.
A problem with different tag versions in a file only occurs, usually outside MP3tag, if the tag data gets out of sync esp. if not all tag versions get the same data. This happens often when gain data is written only into APE tag fields but no other fields get updated.
In your case it looks like you had those tags in sync as you read and wrote both - like the default setting suggest, which is the safe setting.
So, I stay with my statement that MP3tag has nothing to do with the silence in your files.
If I were you then I would invest the time and let MP3diags scan and repair my collection before I would change anything else.
Otherwise one would be stuck with the general data processing phenomenon: garbage in - garbage out. And at least the 2 files that you supplied have a questionable quality with unsupported streams.
@Dick_Harpees there is a very distinct difference in audio files between the audio streams and the header data. The headers are where data including the tag information resides. It does not matter what format these are in; id3v1, id3v2.x, or APE. Different users have their reasons for preference. But regardless of the tag format, they cannot directly influence a change to the audio streams.
If you have files that clearly show silence has been added to the beginning or end of any tracks within the actual audio stream, you would have to look at what other influence has been done to the file to have those silences show up. But it isn't from the tag info, and isn't from anything that mp3tag can do. Period.
Yes. User settings. MP3tag does that what the user tells MP3tag to do.
This discussion does not lead us anywhere as long as you are not willing to dig more into the technicalities.
There is objective proof delievered by other programs that something is wrong with your files and the impression
cannot be substantiated with these programs.
You continue to refuse to accept that tagging does not modify the audio - and "silence" is audio IMHO - and as long as that is your technical understanding I cannot do a lot against these alternative facts.
The discussion we have led so far points to a number of problems in the supplied files - it could well be that these are the odd ones out. But as you supplied them to support your statement that tagging causes your problems at least these two files do not give evidence for that allegation.
If you find other files that proove your point then these would be valuable assets to track down a bug. But as long as that is missing, you are simply hunting a mirage.
3 Likes
But you write the ape tags by default you said that in your previous posts. It is similar to the nationalist language warning I received from Florian. Don't really need to hear anymore. I am sure you have your reasons since you are at the advanced level of seeing garbage in files, however I don't experience any silence at all now that the APE tags the mp3tag program wrote (I could install it again and check the defaults) presumably when I saved it. At this point I am left with insults, obstinately withholding of information as regards to the behavior of the program, and a new level of testing that I would have to do to pursue your self substantiated level of avarice in regards to tagging. It is just a smidge more than I even needed setting out. I know all about the nationalist tendancies of your region of the world as I live in Poland myself. I have noticed, that crossing the border from Poland into Germany, one finds people with no fun on their hands. No surprize they are all worried about things in their audio files!!! 
I am sorry if
came across as a comment on the audio itself. I only referred to the findings in MP3diags which showed a lot of unsupported streams in the original file as well as the files with APE tags. This meant for me that the files had problems prior ot tagging and that these problems stayed the same after tagging.
That would be for me "garbage in - garbage out".
If you are not satisfied with the way MP3tag handles your files then, please, look around to find a program that suits you better. Nobody forces and forced you to use it.
But if you continue to use it, then, please, get deeper into the functions of the program and use them with a much better understanding of what you do with which function.
A good start would be to learn about APE tags e.g. by consulting Wikipedia:
and about the general structure of MP3 files which should also reveal that tags are apart from the payload data:
Enjoy.
Mp3tag doesn't write APEv2 tags to MP3 files by default.
I'm closing this topic now, as it continues to go in circles and repeatedly arrives at a personal level, discusses moderator actions, and generalizes certain behavior to nations and nationalities.
4 Likes