Emby and scanning music to library pt2

[misterkoat 6]

Normally what I do is, I get my music files from a streaming site and rip it with 100% correct tags. Music files have multiple artist tags and for consistency purposes, one usually keeps the main artist so that data sent to last fm for scrobbling across emby, kodi, spotify, deezer etc is similar. Previously i used to rip with all the artists and edit the files manually to leave the main artist only. no problems. Now, since I rip hundreds of songs at once, it's definitely a lot of work to edit each one of them manually and so i've set that the ripping software just keeps the main artist. 

From the Windows file explorer, this is how the files look. Pay attention to the marked areas  

From, say another audio app, which in this case is Groove Music this is how it looks

Totally consistent right?

However, this is Emby

Where did the extra tags come from? I've scoured the files extensively yet can't seem to find any attribute of the file that even contains the tags. 

This started happening when I changed the option to remove all other secondary artists and leave the main artist. Kindly help.

[PenkethBoy 2068]

open them in mp3Tag (use alt+T to see every tag) and you can see all the tags - audio progs dont always show all the tags

[Luke 42085]

Penkethboy is exactly right. I promise you'll find those values embedded within your audio files. The server isn't making them up or pulling them from any internet source.

[misterkoat 6]

I've seen them after opening using Mp3Tag.

However still, there's a problem. I honestly never knew that there was an mp3 field called artists, apart from contributing artists and album artist. It would be much simpler if emby stuck with the regular fields that audio players use to read audio tags. Even though I now know where the tags are coming from, editing all the files to remove that field is still alot of work.

These are the only options available in the ripping software and I've tried all of them to no sucess in removing the field.

Is this an issue that can be fixed in the next update?

And while at it, emby can't read "year" tag. Could it be because I use ID3v1 and ID3v2?

[PenkethBoy 2068]

the new way of reading music for emby - currently in beta- is fully tag driven

so they need to be correct and consistent

MP3Tag makes it easy to do this as you can edit as many files at once as you need

Also if you run the albums through the MusicBrainz Picard app it can help you correct your tags so things are correct rather than random if you just accept what you are given from where you get your media. For albums that dont exist in MusicBrainz then Mp3Tag is you best option.

Ripping software is fine - just then run the album through Picard to get consistent results

[misterkoat 6]

9 minutes ago, PenkethBoy said:

the new way of reading music for emby - currently in beta- is fully tag driven

so they need to be correct and consistent

MP3Tag makes it easy to do this as you can edit as many files at once as you need

Also if you run the albums through the MusicBrainz Picard app it can help you correct your tags so things are correct rather than random if you just accept what you are given from where you get your media. For albums that dont exist in MusicBrainz then Mp3Tag is you best option.

Ripping software is fine - just then run the album through Picard to get consistent results

Yeah. Not gonna do that but thanks for the suggestion.

[PenkethBoy 2068]

then you are going to have issues

[misterkoat 6]

2 minutes ago, PenkethBoy said:

then you are going to have issues

or not. I've decided to fix the issue from the software side so let's see how that plays out.