![]() ![]() I'm happy to send someone an actual mp3 file to test or anything else I can do to help, but at this point I've exhausted what I can do on my own.On some level I understand all the trouble MB is currently having (including server resources, search server, bugs, etc). I do see a ton of google results regarding ffprobe incorrectly reading multiple artist tags, but most of them are older and I can't tell for sure if it's an unresolved issue or not. I've noticed there is some sort of app called Jellyfish that uses ffprobe and there are a lot of users reporting the same issue over there, so I suspect the problem is with ffprobe itself. I've tried clearing all tags (verified with both mp3tag extended tags, picard & tagcanner) then re-scrapped the tags, but the problem remains. Literally tagging or music collection app shows the same tags with multiple artist with multiple artists displaying correctly, except for ffprobe. ![]() At this point I've spent at least 30+ hours on this issue, using every piece of music tagging software I can get my hands. I'm a decade+ Emby premium user and really really don't want to move to start over somewhere else, but my music collection is important to me. ![]() Hi it possible for me to give an additional donation in exchange for some dedicated help on the music issue as it relates to ffprobe and Artist in Emby? If that's not appropriate, I understand and will just move on to something else. For this test I create the mp3s myself so that I could have control over exactly which tags were being added so I don't understand why Artist is showing a single value. The main difference between the two tracks tags, as far as I can tell, is that correctly displayed track has all three performers in Artists tag.Ī non-Emby question that I now have is why ffprobe is only showing a single value in the Artist tag despite every mp3 tagging software that I've tried (Mp3tag, MusicBee, TagScanner, MediaMonkey) all showing multiple Artists in that tag. You can see that both the correct and incorrect tracks show only "Russ" as the Artist. The results from ffprobe seem to support that something is off with the tags themselves or at least with how ffprobe is reading the tags. Then if you take that and run it from a command prompt, you can see what ffprobe got from the track. You can try refreshing the metadata on the track, then the server log will show the ffprobe command line that was used to probe it for media info. And that multiple artists separated by is the correct format to use in the tags? I'll go through the process again, just to be 100% sure and report back.Īssuming what I'm saying is true, am I correct is saying that Emby should only look at the tags and then use the Artist tag to populate the Artist info in Emby metadata. I then added the tags, exactly as you see them in the screenshots. So for these files, I wanted to make sure everything was clean so I created 2 copies and then used 3 different tag softwares to ensure that all tags had been removed (TagScanner, Mp3Tag & MusicBrainz Picard). You'll want to use tag writing software that writes to all versions of id3 tags. You could run that from a command prompt to see what ffprobe picks up.īottom line, it's not tagged how you think it is. Then the server log will have the ffprobe command line. ![]() Try refreshing the metadata on the track. it could also be that its' just tagged with Russ. It could be that ffprobe did not pick up any artist tag, and so the server took the value from album artist and applied it to artist. Right so because the Artist is the same as the album artist, that's why you're not seeing it. ![]()
0 Comments
Leave a Reply. |