The currently playing song could not be found in the database. The database may not be populated. #264
Comments
|
Full log provided here from start containers |
|
Thanks for giving Cadence a try! I was able to reproduce your error by intentionally adding a song with incomplete metadata to my music directory, and then by having Liquidsoap select it. Here's the log: ... The UI: And my (garbage) metadata, as read by mp3tag: Note that I intentionally left artist and title blank - If you leave all fields blank the song won't be listed in the database at all, so it wouldn't appear in search results (I'm not sure what exactly the required subset is, it's driven externally to this project). Cadence uses the artist, title, and album art from the metadata tags in the currently playing song to populate both the database and the UI. I suspect that the files you have in your music directory do not have these tags set properly, and that causes the blank entries in the song library on the UI. That then means that the automatic setting of the listen URL gets broken - Cadence fetches that from Icecast along with the currently playing song, but it checks if the title or artist are empty and discards the response if so. Therefore, when the currently playing song lacks that metadata, Cadence is unable to update its tracking of the current state of Icecast, including the URL, even if it has never done so before. Thus, the UI gets no mountpoint back, which means it cannot then connect to the stream server. I don't know if/how we'll want to fix the latter issue (allow Cadence to update the host info even if there's no info on the currently playing song, or at least if it does not currently have host info) - That's up to @kenellorando. But, the workaround to that issue, and the fix for the broken song library display, is to go through and update the metadata tags on the songs in your library to make sure they at least have the artist and title set correctly. For that, you can use Mp3tag on Windows, or on Linux you may either prefer a GUI like EasyTAG, or to simply run |
kenellorando
added a commit
that referenced
this issue
Aug 6, 2024
I noticed we never allow overriding of the log level from Info, even though we do log at lower levels. This provides a mechanism to fix this - I thought it might be potentially helpful in debugging population errors (as #264 might be). This partially depends on, and therefore has some similar diffs to, #266. Default output:  With level=Debug (and the ideal Cadence dev music folder):  Commandline that sets Debug: 
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hello!
Check your app and stuck with the similar issue from this
#262
What i see in cadence docker log:
for now my stream on
http://stream.igratelyfm.ru/
but UI is not working properly
http://igratelyfm.ru/
What could be the reason?
The text was updated successfully, but these errors were encountered: