2021-09-29, 17:12
I'm attempting to set up all my Kodi nodes to use my NAS (running TrueNAS, data shared via NFS) as a media source as well as MySQL server for the metadata.
Nearly everything is working perfectly, but I've run into one small issue I've been banging my head against for a while
When I go to Music -> Artists, after scraping metadata (default everything) I get:
I can navigate to albums, tracks, etc, and it will work as expected - displaying all the correct metadata.
The files are known and accessible and the tables appear to be populated correctly when viewed in dbeaver.
What I can't access is Artists, Roles -> *, Sources -> *. Everything else appears to function as normal.
This behavior is consistent on linux and Android clients (windows untested).
relevant kodi.log snippet:
Full kodi.log
The artist table has 2521 rows, running InnoDB with utf8. Kodi can handle full utf8, including Asian characters, right?
I've already dumped the database and repopulated - twice. This is an all day procedure and the problem doesn't occur until late in the scrape. I'd really like to solve this issue, but I'm not sure where to even start short of grabbing the source and stepping through in a debugger. I'm also looking to avoid editing tags to avoid having to resync my entire music library across multiple locations.
I'm hoping I'm just an idiot and am overlooking something obvious. If anyone has insight or more reasonable directions to point me in, I'd appreciate it.
Nearly everything is working perfectly, but I've run into one small issue I've been banging my head against for a while
When I go to Music -> Artists, after scraping metadata (default everything) I get:
I can navigate to albums, tracks, etc, and it will work as expected - displaying all the correct metadata.
The files are known and accessible and the tables appear to be populated correctly when viewed in dbeaver.
What I can't access is Artists, Roles -> *, Sources -> *. Everything else appears to function as normal.
This behavior is consistent on linux and Android clients (windows untested).
relevant kodi.log snippet:
Code:
2021-09-29 08:52:30.131 T:648628 ERROR <general>: SQL: Missing result set!
2021-09-29 08:52:30.131 T:648628 ERROR <general>: GetArtistsByWhere failed
2021-09-29 08:52:30.132 T:648628 ERROR <general>: GetDirectory - Error getting library://music/artists.xml/Full kodi.log
The artist table has 2521 rows, running InnoDB with utf8. Kodi can handle full utf8, including Asian characters, right?
I've already dumped the database and repopulated - twice. This is an all day procedure and the problem doesn't occur until late in the scrape. I'd really like to solve this issue, but I'm not sure where to even start short of grabbing the source and stepping through in a debugger. I'm also looking to avoid editing tags to avoid having to resync my entire music library across multiple locations.
I'm hoping I'm just an idiot and am overlooking something obvious. If anyone has insight or more reasonable directions to point me in, I'd appreciate it.
