vmcosco 24 Posted January 16, 2017 Posted January 16, 2017 I routinely have issues refreshing album info via metadata manager. If I notice an album is missing info, I will go into metadata manager, click refresh and select replace all existing. I get the pop up saying refresh queued. I rarely get any new information populated. I tag all music with MB Picard. I have both MB and AudioDB enabled in settings for music albums. I have verified that the album(s) exists in AudioDB and have data in fields that are missing from Emby (AudioDB IDs, overview) etc. I have nfo files written to the artist and album folders. Thoughts on why I struggle with this so mightily?
Luke 42079 Posted January 16, 2017 Posted January 16, 2017 Have you enabled AudioDb for music albums? it is off by default.
vmcosco 24 Posted January 16, 2017 Author Posted January 16, 2017 Have you enabled AudioDb for music albums? it is off by default. Yes, it is enabled. I double and triple checked
Luke 42079 Posted January 16, 2017 Posted January 16, 2017 Then the best thing to do is refresh an album, then provide the information requested in how to report a problem. thanks !
vmcosco 24 Posted January 16, 2017 Author Posted January 16, 2017 Just attempted to refresh Gregory Porter - Liquid Spirit (http://theaudiodb.com/album/2232017). There was no change to the populated data in Emby as you can see in the attacheds screen capture. Below is the log excerpt. There is a lot of server info in the log that I would rather not share in a public forum. Let me know if you need more. 2017-01-16 08:58:07.8895 Info HttpServer: HTTP POST http://localhost:32200/emby/Items/25c05da49d02e9ae88b9186ae691e845/Refresh?Recursive=true&ImageRefreshMode=FullRefresh&MetadataRefreshMode=FullRefresh&ReplaceAllImages=false&ReplaceAllMetadata=true. UserAgent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:50.0) Gecko/20100101 Firefox/50.0 2017-01-16 08:58:07.9275 Info HttpServer: HTTP Response 204 to 127.0.0.1. Time: 38ms. http://localhost:32200/emby/Items/25c05da49d02e9ae88b9186ae691e845/Refresh?Recursive=true&ImageRefreshMode=FullRefresh&MetadataRefreshMode=FullRefresh&ReplaceAllImages=false&ReplaceAllMetadata=true 2017-01-16 08:58:27.0286 Info App: Emby.Kodi.SyncQueue: Starting Library Sync... 2017-01-16 08:58:27.0286 Info App: Emby.Kodi.SyncQueue: "LIBRARYSYNC" Added 0 items: 2017-01-16 08:58:27.0916 Info App: Emby.Kodi.SyncQueue: "LIBRARYSYNC" Updated 19 items: 25c05da49d02e9ae88b9186ae691e845,306ef29c54bb311ae0ae40570e5a0398,30097a4efe19410c04045e96e2776326,62f064a0b06ad9744baa188a841aaa8f,beb53e08b8c29421b241ce7e75c6e252,0eb372a8992a9bdeb6ea527806965491,83479e6bf63af26a8970a3174b4442c2,729cb8177e0ef2c80bf241df30b96bf1,3c1db71b7dcf0dd921e00b86311b41e4,80e951ac7a1caf01274e6eef16e1284b,6a7169f42cc32c01bb6c331e22b83c3e,ec446ea0a5ec0f8e3e8ccae17d1c1736,9259cdf289322cc22c2929cc8bed43be,8e5937ecfcc2b988f9f4c3bd7bc59356,ee644f4428bc66777caba51e695c3f47,c366e10cf800000806ce992d189b1327,c0be81994159f3da319e90f8b5aad488,37269e5d9280db8fa9239a197a20f7ea,c5737ec272a105bf69a61da9298ecc2a 2017-01-16 08:58:27.3236 Info App: Emby.Kodi.SyncQueue: "LIBRARYSYNC" Removed 0 items: 2017-01-16 08:58:27.3236 Info App: Emby.Kodi.SyncQueue: Finished Library Sync Taking 00:00:00.2950169 2017-01-16 08:58:28.0956 Info HttpServer: HTTP GET http://192.168.76.102:32200/emby/Users/6340ae8c29514358848d0efbc1c50182/Items?format=json&Fields=Path%2CGenres%2CSortName%2CStudios%2CWriter%2CProductionYear%2CTaglines%2CCommunityRating%2COfficialRating%2CCumulativeRunTimeTicks%2CMetascore%2CAirTime%2CDateCreated%2CMediaStreams%2CPeople%2COverview%2CCriticRating%2CCriticRatingSummary%2CEtag%2CShortOverview%2CProductionLocations%2CTags%2CProviderIds%2CParentId%2CRemoteTrailers%2CSpecialEpisodeNumbers%2CMediaSources%2CVoteCount&Ids=306ef29c54bb311ae0ae40570e5a0398%2C30097a4efe19410c04045e96e2776326%2C62f064a0b06ad9744baa188a841aaa8f%2Cbeb53e08b8c29421b241ce7e75c6e252%2C0eb372a8992a9bdeb6ea527806965491%2C83479e6bf63af26a8970a3174b4442c2%2C729cb8177e0ef2c80bf241df30b96bf1%2C3c1db71b7dcf0dd921e00b86311b41e4%2C80e951ac7a1caf01274e6eef16e1284b%2C6a7169f42cc32c01bb6c331e22b83c3e%2Cec446ea0a5ec0f8e3e8ccae17d1c1736%2C9259cdf289322cc22c2929cc8bed43be%2C8e5937ecfcc2b988f9f4c3bd7bc59356%2Cee644f4428bc66777caba51e695c3f47%2Cc366e10cf800000806ce992d189b1327. UserAgent: 2017-01-16 08:58:28.1067 Info HttpServer: HTTP GET http://192.168.76.102:32200/emby/Users/6340ae8c29514358848d0efbc1c50182/Items?format=json&Fields=Path%2CGenres%2CSortName%2CStudios%2CWriter%2CProductionYear%2CTaglines%2CCommunityRating%2COfficialRating%2CCumulativeRunTimeTicks%2CMetascore%2CAirTime%2CDateCreated%2CMediaStreams%2CPeople%2COverview%2CCriticRating%2CCriticRatingSummary%2CEtag%2CShortOverview%2CProductionLocations%2CTags%2CProviderIds%2CParentId%2CRemoteTrailers%2CSpecialEpisodeNumbers%2CMediaSources%2CVoteCount&Ids=c0be81994159f3da319e90f8b5aad488%2C37269e5d9280db8fa9239a197a20f7ea%2Cc5737ec272a105bf69a61da9298ecc2a. UserAgent: 2017-01-16 08:58:28.1607 Info HttpServer: HTTP Response 200 to 192.168.76.101. Time: 54ms. http://192.168.76.102:32200/emby/Users/6340ae8c29514358848d0efbc1c50182/Items?format=json&Fields=Path%2CGenres%2CSortName%2CStudios%2CWriter%2CProductionYear%2CTaglines%2CCommunityRating%2COfficialRating%2CCumulativeRunTimeTicks%2CMetascore%2CAirTime%2CDateCreated%2CMediaStreams%2CPeople%2COverview%2CCriticRating%2CCriticRatingSummary%2CEtag%2CShortOverview%2CProductionLocations%2CTags%2CProviderIds%2CParentId%2CRemoteTrailers%2CSpecialEpisodeNumbers%2CMediaSources%2CVoteCount&Ids=c0be81994159f3da319e90f8b5aad488%2C37269e5d9280db8fa9239a197a20f7ea%2Cc5737ec272a105bf69a61da9298ecc2a 2017-01-16 08:58:28.2217 Info HttpServer: HTTP Response 200 to 192.168.76.101. Time: 126ms. http://192.168.76.102:32200/emby/Users/6340ae8c29514358848d0efbc1c50182/Items?format=json&Fields=Path%2CGenres%2CSortName%2CStudios%2CWriter%2CProductionYear%2CTaglines%2CCommunityRating%2COfficialRating%2CCumulativeRunTimeTicks%2CMetascore%2CAirTime%2CDateCreated%2CMediaStreams%2CPeople%2COverview%2CCriticRating%2CCriticRatingSummary%2CEtag%2CShortOverview%2CProductionLocations%2CTags%2CProviderIds%2CParentId%2CRemoteTrailers%2CSpecialEpisodeNumbers%2CMediaSources%2CVoteCount&Ids=306ef29c54bb311ae0ae40570e5a0398%2C30097a4efe19410c04045e96e2776326%2C62f064a0b06ad9744baa188a841aaa8f%2Cbeb53e08b8c29421b241ce7e75c6e252%2C0eb372a8992a9bdeb6ea527806965491%2C83479e6bf63af26a8970a3174b4442c2%2C729cb8177e0ef2c80bf241df30b96bf1%2C3c1db71b7dcf0dd921e00b86311b41e4%2C80e951ac7a1caf01274e6eef16e1284b%2C6a7169f42cc32c01bb6c331e22b83c3e%2Cec446ea0a5ec0f8e3e8ccae17d1c1736%2C9259cdf289322cc22c2929cc8bed43be%2C8e5937ecfcc2b988f9f4c3bd7bc59356%2Cee644f4428bc66777caba51e695c3f47%2Cc366e10cf800000806ce992d189b1327 2017-01-16 08:58:51.7460 Info HttpServer: HTTP GET http://192.168.76.102:32200/emby/Users/6340ae8c29514358848d0efbc1c50182/Items?format=json&Fields=Path%2CGenres%2CSortName%2CStudios%2CWriter%2CProductionYear%2CTaglines%2CCommunityRating%2COfficialRating%2CCumulativeRunTimeTicks%2CMetascore%2CAirTime%2CDateCreated%2CMediaStreams%2CPeople%2COverview%2CCriticRating%2CCriticRatingSummary%2CEtag%2CShortOverview%2CProductionLocations%2CTags%2CProviderIds%2CParentId%2CRemoteTrailers%2CSpecialEpisodeNumbers%2CMediaSources%2CVoteCount&Ids=25c05da49d02e9ae88b9186ae691e845. UserAgent: 2017-01-16 08:58:51.7530 Info HttpServer: HTTP Response 200 to 192.168.76.101. Time: 7ms. http://192.168.76.102:32200/emby/Users/6340ae8c29514358848d0efbc1c50182/Items?format=json&Fields=Path%2CGenres%2CSortName%2CStudios%2CWriter%2CProductionYear%2CTaglines%2CCommunityRating%2COfficialRating%2CCumulativeRunTimeTicks%2CMetascore%2CAirTime%2CDateCreated%2CMediaStreams%2CPeople%2COverview%2CCriticRating%2CCriticRatingSummary%2CEtag%2CShortOverview%2CProductionLocations%2CTags%2CProviderIds%2CParentId%2CRemoteTrailers%2CSpecialEpisodeNumbers%2CMediaSources%2CVoteCount&Ids=25c05da49d02e9ae88b9186ae691e845 2017-01-16 08:58:52.0070 Info HttpServer: HTTP GET http://192.168.76.102:32200/emby/Emby.Kodi.SyncQueue/GetServerDateTime?format=json. UserAgent: 2017-01-16 08:58:52.0070 Info App: Emby.Kodi.SyncQueue: Server Time Requested... 2017-01-16 08:58:52.0070 Info HttpServer: HTTP Response 200 to 192.168.76.101. Time: 1ms. http://192.168.76.102:32200/emby/Emby.Kodi.SyncQueue/GetServerDateTime?format=json 2017-01-16 08:58:57.1093 Info HttpServer: HTTP SUBSCRIBE http://192.168.76.102:32200/dlna/8a37317e62e54bc3a84dd79dc729cf56/connectionmanager/events. UserAgent: UPnP/1.0 DLNADOC/1.50 Kodi 2017-01-16 08:58:57.1093 Info HttpServer: HTTP Response 200 to 192.168.76.101. Time: 1ms. http://192.168.76.102:32200/dlna/8a37317e62e54bc3a84dd79dc729cf56/connectionmanager/events 2017-01-16 08:58:57.1093 Info HttpServer: HTTP SUBSCRIBE http://192.168.76.102:32200/dlna/8a37317e62e54bc3a84dd79dc729cf56/contentdirectory/events. UserAgent: UPnP/1.0 DLNADOC/1.50 Kodi 2017-01-16 08:58:57.1093 Info HttpServer: HTTP Response 200 to 192.168.76.101. Time: 0ms. http://192.168.76.102:32200/dlna/8a37317e62e54bc3a84dd79dc729cf56/contentdirectory/events 2017-01-16 09:00:57.3397 Info HttpServer: HTTP GET http://localhost:32200/emby/Items/f0f790a18f122bc3a33f75c577d24ac1/MetadataEditor. UserAgent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:50.0) Gecko/20100101 Firefox/50.0 2017-01-16 09:00:57.3397 Info HttpServer: HTTP GET http://localhost:32200/emby/Users/6340ae8c29514358848d0efbc1c50182/Items/f0f790a18f122bc3a33f75c577d24ac1. UserAgent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:50.0) Gecko/20100101 Firefox/50.0 2017-01-16 09:00:57.3709 Info HttpServer: HTTP Response 200 to 127.0.0.1. Time: 31ms. http://localhost:32200/emby/Items/f0f790a18f122bc3a33f75c577d24ac1/MetadataEditor 2017-01-16 09:00:57.4957 Info HttpServer: HTTP Response 200 to 127.0.0.1. Time: 156ms. http://localhost:32200/emby/Users/6340ae8c29514358848d0efbc1c50182/Items/f0f790a18f122bc3a33f75c577d24ac1 2017-01-16 09:00:59.6642 Info HttpServer: HTTP GET http://localhost:32200/emby/Users/6340ae8c29514358848d0efbc1c50182/Items/25c05da49d02e9ae88b9186ae691e845. UserAgent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:50.0) Gecko/20100101 Firefox/50.0 2017-01-16 09:00:59.6642 Info HttpServer: HTTP Response 200 to 127.0.0.1. Time: 0ms. http://localhost:32200/emby/Users/6340ae8c29514358848d0efbc1c50182/Items/25c05da49d02e9ae88b9186ae691e845 2017-01-16 09:00:59.6798 Info HttpServer: HTTP GET http://localhost:32200/emby/Items/25c05da49d02e9ae88b9186ae691e845/MetadataEditor. UserAgent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:50.0) Gecko/20100101 Firefox/50.0 2017-01-16 09:00:59.6798 Info HttpServer: HTTP Response 200 to 127.0.0.1. Time: 0ms. http://localhost:32200/emby/Items/25c05da49d02e9ae88b9186ae691e845/MetadataEditor
Luke 42079 Posted January 16, 2017 Posted January 16, 2017 Please attach the complete Emby Server log. thanks !
Happy2Play 9780 Posted January 16, 2017 Posted January 16, 2017 (edited) There is a lot of server info in the log that I would rather not share in a public forum. Let me know if you need more. You can also PM the log to Luke if you don't want to post the log here. What is your Music folder structure? Edited January 16, 2017 by Happy2Play
vmcosco 24 Posted January 16, 2017 Author Posted January 16, 2017 Please attach the complete Emby Server log. thanks ! I PMed it to you. Thanks You can also PM the log to Luke if you don't want to post the log here. What is your Music folder structure? Music/Artist/Album/Track.mp3 .nfo and artwork files in Artist folder and Album folder. Tags embedded with Picard
Luke 42079 Posted January 21, 2017 Posted January 21, 2017 @@vmcosco, can you enable debug logging, repeat the test, and then send me that log? to enable debug logging, go in the server dashboard -> help, enable debug logging, then restart the server. thanks !
vmcosco 24 Posted January 23, 2017 Author Posted January 23, 2017 @@vmcosco, can you enable debug logging, repeat the test, and then send me that log? to enable debug logging, go in the server dashboard -> help, enable debug logging, then restart the server. thanks ! Just sent you the debug-enabled log. Thanks for taking a look at it.
Luke 42079 Posted January 23, 2017 Posted January 23, 2017 So what's the problem exactly? AudioDb is down right now. It looks like that's why you're not getting album overview text.
vmcosco 24 Posted January 23, 2017 Author Posted January 23, 2017 It is the the AudioDB data that is not populating. I do see that it is down now, but this has been the issue for some time. I have not been able to refresh the album info when, at the same time, I am able to access the album on AudioDB. Guess I should wait for AudioDB to be back up and then I will re-run the refresh and send a debug log then
Luke 42079 Posted January 23, 2017 Posted January 23, 2017 Yea i don't know how long it has been down so we can't really say much for sure right now. We will just have to wait or find another source at some point.
Happy2Play 9780 Posted January 23, 2017 Posted January 23, 2017 Welcome to TheAudioDB.com! IMPORTANT UPDATE: Unfortunately we've reached the limit our bandwidth this month after unprecedented demand on our API We're busy making improvements behind the scenes and hope to be back as soon as possible. The site will return on Feb 1st or earlier if possible. Feel free to donate, however small to keep us going in the mean time...
vmcosco 24 Posted February 3, 2017 Author Posted February 3, 2017 While it appears that artist refresh is now working, regrettably, I am still not able to get album metadata to refresh. Tried with two separate albums and all data that would come from AudioDB is still blank.
Luke 42079 Posted February 3, 2017 Posted February 3, 2017 While it appears that artist refresh is now working, regrettably, I am still not able to get album metadata to refresh. Tried with two separate albums and all data that would come from AudioDB is still blank. Best thing to do is see post #4, thanks !
vmcosco 24 Posted February 4, 2017 Author Posted February 4, 2017 Just attempted to refresh Gregory Porter - Liquid Spirit (http://theaudiodb.com/album/2232017). There was no change to the populated data in Emby. The only info present is the original info from the tags populated by Musicbrainz Picard. No AudioDB info is being added. I PMed you the complete debug log.
Luke 42079 Posted February 7, 2017 Posted February 7, 2017 What's in this file? C:\Users\Vic\AppData\Roaming\Emby-Server\cache\audiodb-album\eb676be9-13af-42b0-9ad2-b066d3313462\album.json
vmcosco 24 Posted February 7, 2017 Author Posted February 7, 2017 What's in this file? C:\Users\Vic\AppData\Roaming\Emby-Server\cache\audiodb-album\eb676be9-13af-42b0-9ad2-b066d3313462\album.json I opened the file with Notepad++ and there was just one line: {"album":null}
Luke 42079 Posted February 7, 2017 Posted February 7, 2017 try deleting that file then refreshing again.
vmcosco 24 Posted February 7, 2017 Author Posted February 7, 2017 try deleting that file then refreshing again. I deleted the folder and file. Refreshed the album and still nothing from AudioDB the folder and file were recreated with the same contents. I then tried deleting the file and folder again, deleted the album.nfo, restarted Emby and then refreshed the album and got the same result. Below is my log from when I did the refresh 2017-02-07 14:01:07.3757 Info HttpServer: HTTP Response 204 to 74.121.144.4. Time: 27ms. http://my.net:32200/emby/Items/25c05da49d02e9ae88b9186ae691e845/Refresh?Recursive=true&ImageRefreshMode=FullRefresh&MetadataRefreshMode=FullRefresh&ReplaceAllImages=false&ReplaceAllMetadata=true 2017-02-07 14:01:07.5277 Debug App: Running MusicBrainzAlbumProvider for \\Serv01\Music\Music01\Gregory Porter\Liquid Spirit 2017-02-07 14:01:07.5277 Debug App: Running AudioDbAlbumProvider for \\Serv01\Music\Music01\Gregory Porter\Liquid Spirit 2017-02-07 14:01:07.5407 Info HttpClient: HttpClientManager GET: http://www.theaudiodb.com/api/v1/json/49jhsf8248yfahka89724011/album-mb.php?i=eb676be9-13af-42b0-9ad2-b066d3313462 2017-02-07 14:01:07.8248 Debug JsonSerializer: Deserializing file C:\Users\Vic\AppData\Roaming\Emby-Server\cache\audiodb-album\eb676be9-13af-42b0-9ad2-b066d3313462\album.json 2017-02-07 14:01:07.8248 Debug App: AudioDbAlbumProvider returned no metadata for \\CoscoServ01\Music\Music01\Gregory Porter\Liquid Spirit 2017-02-07 14:01:07.8438 Debug App: Running AlbumNfoProvider for \\Serv01\Music\Music01\Gregory Porter\Liquid Spirit 2017-02-07 14:01:07.8538 Debug App: AlbumNfoProvider returned no metadata for \\Serv01\Music\Music01\Gregory Porter\Liquid Spirit 2017-02-07 14:01:07.9068 Debug XmlSerializer: Deserializing file C:\Users\Vic\AppData\Roaming\Emby-Server\config\xbmcmetadata.xml 2017-02-07 14:01:07.9178 Debug ProviderManager: Saving \\Serv01\Music\Music01\Gregory Porter\Liquid Spirit to Nfo.
Luke 42079 Posted February 7, 2017 Posted February 7, 2017 Ok, have you investigated this at all? because you can actually easily find the answer on your own just by looking at your music brainz id's and comparing them to information on audiodb. Unfortunately the data on music brainz is to blame. There are multiple release group id's on music brainz for this album: https://musicbrainz.org/release-group/aff0cc3e-68fa-4326-9080-c64412315076 https://musicbrainz.org/release-group/eb676be9-13af-42b0-9ad2-b066d3313462 If you look at the bottom of the audiodb page, you can check the musicbrainz link to see which one they have in their database: http://www.theaudiodb.com/album/2232017 It just so happens that the release group id in your emby database does not match the one that audiodb is using. So fix that, refresh again and that should fill in your information. This may lead you to ask, why does Emby have the wrong one in your database? None of them are wrong. That's just what the music brainz search api is giving us.
vmcosco 24 Posted February 7, 2017 Author Posted February 7, 2017 I looked into everything I can think of but, admittedly, I did not check that the MB release group listed on the AudioDB page matched up. That did not occur to me. I would not have expected that Emby would have relied on them matching up. Good to know. Thanks. I appreciate the guidance and apologize for making this more complex than it was.
Luke 42079 Posted February 7, 2017 Posted February 7, 2017 Your wording suggests you view the ties to musicbrianz id as a shortcoming but that is really not the case. imagine the opposite scenario, user has tagged audio with picard to fill in musicbrainz id's, but we ignore it and do an audiodb search by name. Imagine all of the "not working" reports we would receive due to the audiodb search api not returning the expected results. It is the same way with a tv show or a movie, for example, if you have an Imdb Id in your metadata then of course we are going to use it.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now