INTERACT FORUM
More => Old Versions => Media Center 15 (Development Ended) => Topic started by: cncb on June 17, 2010, 03:16:32 pm
-
I want to have MediaServer running all the time and then have any user logged in on the same PC share the same instance and settings and be able to make changes when they bring up the MC UI. I tried to add a task in the Task Scheduler to launch MC as the "SYSTEM" user (to eventually be run at startup) which does start MC but there is no MediaServer icon and when I try to launch MC normally I get an error. When I enable the "allow multiple instances" option it tells me that the database will be opened read only. Is there any way to get the behavior I want?
-
not currently, but I have made some suggestion on how to resolve this; but it does not appear to be a priority at the moment.
I would love to see this also, and MANY people have requested this functionality over the years. here is my suggestion on how to make it happen...
http://yabb.jriver.com/interact/index.php?topic=57440.0
-
I guess this would only be feasible if MediaServer could be a true Windows Service and split from the UI (as, I think, Justin suggests)? I have requested a Windows Service before for the "core library" stuff and it sounded unlikely to happen but I guess it can't hurt to request it again...
-
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.