More > JRiver Media Center 23 for Windows
Feature request: close to tray and autostart MC reduced to tray
AndrewFG:
The MC application should ideally be split into two separate applications..
1) MC Player should become a Windows Service Application. This exposes no UI at all, and runs when Windows starts. It always runs in th background regardless of whether a user is logged on, and regardless of whether th UI application (see below) is running.
2) MC Browser should be (should remain) a Windows Application. This exposes the whole UI, including track browser, play commands, playing now, tagging, audio analysis, file rename, copy, move etc. It only runs when a user starts it. And stops when the user stops it.
The Browser application talks to the Player application by means of standard Windows interprocess calls. In the case of MC, probably either by the COM interface, of MCWS.
I know that this architecture can work, since this exactly how Logitech Media Server (Squeeze Box player) works. And my own Whitebear Media Server UPNP shim for LMS works also in the same way.
This is quite liberating as a design architecture, since it represents a real and proper split into the client/server architecture.
PS if MC were ever to shift to a 64 bit build, this would be the perfect opportunity to split the application into client (regular application) and server Windows Service Application) parts..
And indeed when MC is operating as a networked client/server application across several PCs it is in fact functioning virtually as described above. It is only in the case when MC is operating on a single PC that it does not clearly separate the client/server parts.
Hendrik:
We're not going to change the entire architecture of Media Center. And being 32-bit or 64-bit is absolutely unrelated to that entire topic either way.
JimH:
I think we would rather write an OS before restructuring MC.
RD James:
While it would be nice if JRiver had unlimited resources to do something like that, I think it's a big leap from what some of us are asking for.
Activating "Media Server" really is just the same thing as "close to tray" already - it just adds a second icon for it. (I'm not sure why)
The main issue with it right now is that it stops playback in all zones right now when you do that.
I don't think it would require any major changes to the Media Server behavior to satisfy those of use who want to use JRiver as more of a "server".
1. Closing to tray no longer issues stop commands. Playback continues in all zones without interruption.
2. The "Close Media Server" option asks for confirmation.
3. The context menu for Media Server is updated with a few commands:[*]Stop playback in all zones.
[*]Zones are listed on the main context menu rather than a sub-menu
[*]Play/Pause/Stop/Next/Prev controls as a sub-menu for individual zones (similar to the "Controls" menu for Zones in Media Cetner)
[*]If it is possible, add icons to indicate playback status for a zone in the Media Server context menu. (active/paused/stopped)[/list]
AndrewFG:
--- Quote from: JimH on June 13, 2017, 09:20:10 am ---I think we would rather write an OS before restructuring MC.
--- End quote ---
Yeh. I know.
Navigation
[0] Message Index
[*] Previous page
Go to full version