Closed chandranorth closed 1 year ago
I can't reproduce this but experience suggests that when this doesn't work it's a bug in one of your Mopidy backends.
RompR uses the MPD interface to save and amend playlists, the other frontends you've tried probably use the HTTP interface. Some backends are not well-behaved and can cause errors because of this. If I had to guess which one it was, I'd bet it was Tidal but I have no evidence other than experience to support that.
Thanks for your response. Is there any other configuration required in the [mpd] section of mopidy.conf? At present I have:
[mpd] enabled = true max_connections = 30 connection_timeout = 600
Best regards,
Venkat Chandrasekhar
On Thursday, January 19, 2023, 03:45:53 PM CST, Mark Greenwood ***@***.***> wrote:
I can't reproduce this but experience suggests that when this doesn't work it's a bug in one of your Mopidy backends.
RompR uses the MPD interface to save and amend playlists, the other frontends you've tried probably use the HTTP interface. Some backends are not well-behaved and can cause errors because of this. If I had to guess which one it was, I'd bet it was Tidal but I have no evidence other than experience to support that.
— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: @.***>
That's all the config you need. This isn't a configuration problem, it's a badly-written-backend problem. You might get some debug information out of Mopidy if you run it in a terminal and then try to save a playlist from RompR, but like I say it works on my setup, with a different set of backends. I can't test Tidal but it's the only one of your backends that I've never used so it points to that as the culprit.
You are probably right. See the discussion on Tidal playlists: https://github.com/tehkillerbee/mopidy-tidal/issues/86
Thanks again,
Venkat
On Friday, January 20, 2023, 03:06:15 AM CST, Mark Greenwood ***@***.***> wrote:
That's all the config you need. This isn't a configuration problem, it's a badly-written-backend problem. You might get some debug information out of Mopidy if you run it in a terminal and then try to save a playlist from RompR, but like I say it works on my setup, with a different set of backends. I can't test Tidal but it's the only one of your backends that I've never used so it points to that as the culprit.
— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: @.***>
@chandranorth Just to understand your issue so we can try to replicate it.
You can add to the playlist through Mopidy Iris or similar - but not when using RompR?
Johannes,
Sorry for the delayed response. Unfortunately, I am now having a problem with the mopidy-tidal plugin, but that is a separate issue.
Yes, the problem was that I could add to playlists using Iris, but not when using Rompr.
I noticed that fatg3erman has opened the same issue on the github page of mopidy-tidal.
On Monday, April 10, 2023, 10:58:42 AM CDT, Johannes L ***@***.***> wrote:
@chandranorth Just to understand your issue so we can try to replicate it.
You can add to the playlist through Mopidy Iris or similar - but not when using RompR?
— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.Message ID: @.***>
I noticed that fatg3erman has opened the same issue on the github page of mopidy-tidal.
No, I did not do that. This isn't my bug, so can we stop reopening this please.
I am unable to save tracks to a new playlist, or to add tracks to an existing playlist. I can make new playlists and add to playlists using another mopidy web frontend, e.g., Mopidy Iris, and once created, these appear in Rompr. Perhaps a write permission error?
Attached is the debug information from Rompr. Please let me know if any other information is required.
Thanks again for a great piece of software!