I actually just want MC to separate the library storage and serving duties (server) from the management of lists and views and tags (profile).
No matter if there are multiple machines and users and locations, or one user on one machine. Just always keep these parts separate.
One part of MC keeps track of what's located where and how to play it back (codecs and conversions), then let users/profiles keep their "front end" setup the way they want, and any playback request is just handled internally by these 2 parts of MC, whether over the network, or on the very same machine.
by separating the pieces this way, the server part is always up to date with the media available (auto-update), and is always ready to server whatever to whoever, wherever.
The user/profile has the ability to select files for playback or tag or change the view of whatever media is available, and doesn't need to manage the technicalities of the playback part at all.
If making the server part a Windows Service facilitates this, great. if MC needs to just run it in the background on startup, or upon an opening of an instance of MC anywhere on the network, okay.
I hope that makes sense. and I also hope this can be implemented some day (soon?), as it will just make everything so much easier.
Author
Topic: Share one instance of MediaServer among multiple Windows users? (Read 1262 times)