-
Notifications
You must be signed in to change notification settings - Fork 587
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ID3 Tags not being written #1271
Comments
@Kolokial Why did you close it? Was it solved? A mistake? |
Unfortunately not. I've opted for a complete re-install to see if my installation was corrupt. If I get the same problem then I shall re-open this with the relevant information. |
So, after a re-install I still have the same problem. I imagine it's something to do with my environment, but I can't for the life of me figure it out. Can anyone suggest where or what I can begin to test/tinker with? |
Could you increase logging level to a maximum? You should get an error. In my case, I have:
on a song for which it fails. It also seems to be failing on OGG files. Concerning the two clicks needed to open the panel, it seems to be always needed, even with |
So, with
But the song information in front of me does not update at all. The song title before editing is displayed as "07 Water", and I go to remove the number so it is just "Water". Not sure if I am reading the above incorrectly, but shouldn't this |
Yes, the order of the info in the Could you confirm the two clicks behavior does not depend on Could you also try another music? (MP3 from a different source ideally) Could you also send me the MP3 files you are using, so that I could try to reproduce? (my email address is on my profile page). Thanks |
Thanks @Phyks for responding. My apologies, the two clicks on the edit window are irrelevant, it seems that two clicks are required the first time on page load. I never noticed this because I was always navigating to another page, so always experienced two clicks. Once the first two clicks are made to bring up the pane, it is one click to edit anything else on the same page. I tried the same process again on a different song, 'Voices', by 'Disturbed'.
I have also just emailed you both mp3s from kolokial@icloud.com. |
Thanks. The issue seems to be with this condition which is not satisfied. I also saw the same issue with some OGG files. I created a separate issue for the double click issue. |
The parsed structure from getID3 looks like:
Notice the I see two issues here:
I do not know enough about ID3v3 tags. Maybe @Afterster or @Niols would have ideas. |
I have news... I wondered if it was my environment or the MP3, it may be something to do with the MP3 specifically. I decided to edit a track that already had the correct name, track number, album and artist. I chose 'Here We Are' by 'Breaking Benjamin' and updated the title to 'Here We Are1' and ran an update. This time the title change stuck.
Not sure how I would parse the mp3 to get the ID3 tag structure as above. |
Some things:
Which at least I have some clues to debug.
would do the trick.
I saw your file was encoded by iTunes (it is written in one of the id3 tags field), so I guess the error is coming from this. In particular, the first point looks a lot like the "invalid frame" we are getting and the error above. Still, this should be handled by getID3 and I am not sure why he did not do it. I will try to investigate further on this in the upcoming days. P.S.: @Afterster do you have an idea about why the condition is present in this file? I do not get the point of checking the presence of id3v2. I may have missed something, but if a file does not have any tags, we could still write some, no? |
Actually, I think I got most of the error. See this commit in getID3 which seems to be fixing the exact issue we are encountering here. @Kolokial if you have some time, I think you can try to run a Else, I will have a deeper look at it tomorrow and see if it solves everything :) EDIT: Correct command is |
I updated to latest Quick summary on this issue:
I will try to fix them. |
After having looked into it, the specific issue about @Kolokial file is that it has deeply invalid idv3 tags structure. I opened an issue on getID3 to see how we can deal with it. I think Ampache should clean up files whenever imported into the catalog, or something like this. For those interested, I set up a branch to work on a PR on this on my fork: https://github.com/Phyks/ampache/tree/issue_1271. It does not do much at the moment, just giving more logging for errors and fixing the first issue encountered because of iTunes invalid frame. |
@Phyks thanks for looking at this issue. I've run an update on composer and pulled the most recent version of Ampache (3.8.3-develop) however the issue persists, I can only assume this is a problem with my MP3s. Is there perhaps something I can run on the MP3s to reset them entirely? |
I did not expect the To solve the whole issue, one would have to tackle this issue. I am waiting for an update from the maintainer and may try to handle it, at least for the precise issue which arises here. In the meantime, if I remember well, I managed to get your files working by resaving the id3 tags with VLC. I do not know much about id3 tags edition software, I guess you may be able to force rewrite them with either vlc, ffmpeg or any such software. Quick search on Google (for Linux) gave me http://www.linux.org/threads/tool-for-repairing-mp3-id3-tags.3274/, https://unix.stackexchange.com/questions/39185/command-line-tool-to-remove-selected-tags-from-mp3-files and https://superuser.com/questions/327410/is-there-a-tool-that-can-detect-and-if-possible-fix-glitches-in-mp3-files that you may find interesting. |
Closing due to inactivity (and age), reopen if this is still relevant in latest version |
Settings
Please see attached config file
My music path is /serve/music
The permissions are currently set to 777 as I've been trying to figure out what the problem is, but am new to Ampache and haven't been able to find much by googling.
I should add that although I opted for the clients above, I'm currently only using Web. I thought during install that I might need/want them later on.
Description
I set write_id3 to true, and then went to edit a song to update it. However when I do, the changes do not seem to appear. The song still has the same information previously. Yet when I disable write_id3 Ampache appears to allow the tags to be updated, but when I update the catalog, everything reverts to how it was originally.
So, the logs below are basically me going to find a song by Breaking Benjamin called Water. The song is in the correct folder, and I am able to find it by searching "Saturate", the album name.
When write_id3 is set to false I have to click the "Edit" button twice in order for the "Song edit" pane to appear. Once it does, I then proceed to update the track name from "07 Water" to "Water", change the artist from "Unknown (Orphaned)" to "Breaking Benjamin" from the drop down, and change the album from "Unknown (Orphaned)" to "Saturate" and add the track number "7". Then hit save and the pane closes. The track updates with the information I just submitted. However, when I later on update the catalog in the "Show Catalog" section, I find all the information I've given the track has now reverted to what it was originally.
Whereas, when write_id3 is set to true, I only have to click the "Edit" button once in order for the "Song edit" pane to appear, I then repeat the process above and click save, but this time the information does not update nor does it change once I run an update on the catalog.
Logs
The text was updated successfully, but these errors were encountered: