-
Notifications
You must be signed in to change notification settings - Fork 115
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
v18/Leia: Music > Song browsing is broken (songs and album details not listed) in Chorus2 #327
Comments
I am having problems with this too. I am willing to try and help resolve it, but I need guidance setting up the build environment. Anybody? |
Hi All, I know this is an issue and is very high on my priority list. As the API has changed between 17 & 18 I need to update any pending PRs and do a final release for 17, then fork a version for 18 where dev/fixes can be applied to Leia only Will likely have 2 new branches going forward, something like... |
Sounds great, thanks! What can we do to help? |
Should be all fixed now :) |
Thanks! How do we install this? My failed attempt is described here: https://forum.kodi.tv/showthread.php?tid=333520&pid=2754879#pid2754879 |
|
Linux machine. I just tried it again. Rebooted. Help > About Chorus still says 2.4.4. |
@mrobe the latest kodi nightlies already come with chorus 2.4.5 included, so just install a recent nightly - the issue is fixed |
Thanks! Got it sorted. The very stubborn Safari cache was throwing me off. Now wondering about this: #331 |
Tested with the latest v18 nightly (alpha2)
Via Kodi GUI, I am able to browse my Music collection with no issues (by Genre, Album, Songs etc) and play it back.
Via the Web Interface (Chorus2), Albums and Genres are listed as usual, as well as artists. However, when clicking in any album (which would normally display), no songs are displayed.
Forum discussion thread with details, including debug logs: https://forum.kodi.tv/showthread.php?tid=333140
I reported this initially in the Music team but they diagnosed immediately that the problem is with Chorus2 using an outdated JSON API.
Sample error triggered by Chorus2 when I try to browse the contents of an album:
The text was updated successfully, but these errors were encountered: