INTERACT FORUM
More => Old Versions => JRiver Media Center 29 for Windows => Topic started by: hoyt on February 21, 2022, 12:17:49 pm
-
This has been going on for a long time and I never posted about it, but it's particularly annoying. I have a client open and I import new music onto my server. The new album shows on my client, so I find it and hit play. Nothing happens. Then I look on the server and there's a popup that says "Playback Failed: The database entries for the selected files are missing and invalid." I can find the same album on the server and play it, which works fine, or I can close the client, reopen and it plays just fine.
-
Are these files moving in the meantime?
-
No. They get saved to a network path, then imported into MC.
-
I just tried to replicate this with a new recording and logging turned on. Of course it didn't happen, but then I realized I was playing back to the client in my test. Normally I sit at my desk and play to a DLNA zone on my server (from my client). I'll give that a shot again tomorrow because I would say this commonly happens. It's not a rare occurrence when something goes weird, it's every new album/ recording that I import when the client is open and I try to direct playback from the client to the DLNA zone on the server.
-
I replicated this at my desk and I think the fact that I'm playing to a server zone may be a cause. Here's the workflow:
1) Client is up and running on Mac, zone is set to There: rpi01 (a DLNA renderer).
2) New tracks get imported into the server via MCWS calls (not sure this matters, but I'm not using auto-import, I'm using a python script that finds new files and pushing them into MCWS with /Library/Import)
3) I see the new track on the client and hit play so that it should go to There: rpi01. The client does nothing, on the server I see the "database entries" popup.
Filename on the client looks correct (it's a windows path on the server). I can find the same file on the server and send it to the DLNA zone without an issue. I'm happy to provide log files.
-
I'm still experiencing this and wanted to bump this thread back up. I've determined that I don't need to restart MC on my client, but instead I can disconnect/ reconnect to the server.