Sorry to re-visit this thread, but I think it's the right place to post
this.
I recently did a full re-install of the OS on my server and re-deployed
LMS. Everything was great, except once again, my DSTM wasn't working.
Remembering that this happened before, and recalling it had something to
do with a plugin conflict, I was super careful to read all the
descriptions and look for any conflicts. I checked logs and nothing
jumped out. There was a comment:
Code:
--------------------
[22-02-11 18:41:20.7302]
Slim::Plugin::DontStopTheMusic::Plugin::onPlaylistChange (183) Found Sugarcube
active - I'm not going to interfere with it.
--------------------
But that didn't raise any alarms for me.
I looked at the SugarCube settings pages, the MusicIP pages and the DSTM
settings pages and nothing indicated conflicts or things to watch out
for between plugins and options. Increasing log levels and no alerts to
errors or conflicts beyond the note that DSTM wasn't going to interfere
with SugarCube. I did not realize "not going to interfere" meant "not
going to run", and perhaps I should have recognized that. If the log
went once step further to say "Disable SugarCube on player XXXX to use
DSTM" It would have pointed me to the right place.
Eventually I came back to this forum, searched my old posts and
refreshed myself with the conflicts with SugarCube. I found that if I
properly disable at the player level, or preferably uninstall SugarCube
then DSTM worked properly.
So again, I'm not sure if this is a DSTM request or should be a
SugarCube request, but these plugins do not play nicely with each other
and don't warn the user, either in the UI settings pages or the logs,
when the are conflicting.
I'd recommend that at the top of the screen of the DSTM plugin, if
SugarCube is detected (which it can see because it adds SugarCube as an
option in DSTM which is very surprising), a warning that SugarCube is
installed and must be disabled at the Player level for DSTM to work.
And if the user does not properly disable, then in the logs, preferably
at the Error or Warn level, it says the specific player couldn't run
DSTM because SugarCube is enabled.
Hoping this is helpful. Thanks again for great plugins and all the work
that goes into creating and maintaining them.
------------------------------------------------------------------------
wactuary's Profile: http://forums.slimdevices.com/member.php?userid=233
View this thread: http://forums.slimdevices.com/showthread.php?t=109997
_______________________________________________
Squeezecenter mailing list
[email protected]
http://lists.slimdevices.com/mailman/listinfo/squeezecenter
