Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[mattkhan]

running latest MC33 as a client connected to a server

open theatre view settings
change the menus (e.g. add netflix, move some other entries in the menu)
launch theatre view
updated settings are present
exit MC
open it again
check theatre view still looks the same
now exit MC *and* media server (i.e. a complete restart)
launch it again
go to theatre view
configuration is now back to the previously saved settings

make the same config changes again to theatre view
check they load ok
now unload the server and load the default local library
check theatre view settings
it's back to the previously saved settings


IIRC there was a change to allow client settings to be saved, my guess is that broke this

i.e. now you have to unload the server, edit the client settings in theatre view and then load the server back again? or perhaps you have to edit it on the server not the client? I don't recall ever having to do that before but maybe it's always been that way? it's v confusing anyway

[mwillems]

So my recollection is that clients have never been able to edit the menu structure in standard or theater view, those are pushed down from the server.  It *seems* like you can edit them, but the changes are reverted on the next restart, and AFAIK that's how it's always worked, the server is the one source of truth for menus.  If there was ever a period where clients could change the views, I missed it.

There are some local theater view settings (graphical settings, maybe themes?, etc.) that are configurable on the client though, which may be part of the confusion?

[tzr916]

It's always been like this. You can change/add menus to on the Client, but they all revert when you restart the Client.

[mattkhan]

that's pretty strange behaviour, why not just prevent editing on a client?

[mwillems]

that's pretty strange behaviour, why not just prevent editing on a client?

There are a handful of places where they've created UI that blocks clients from doing things they can't actually do (like the rename copy move tool, which will now just tell you no on a client), but there are a bunch of places where the client can seemingly make changes but they don't take (e.g. cover art, views).  It's the same deal when you connect to a read-only library: the client can "make" tag changes, but they won't "take."

I'm not sure why it's set up that way.  I suspect it's just a function of clients downloading a copy of the server library and then treating it like a local library, which makes most things work correctly without a lot of dev tinkering, but the cases where the client can't edit (either due to read-only permissions or architectural choices) just silently fail.

[mattkhan]

ok well anyway, mystery solved, thanks!