Print

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

[fitbrit]

A couple of reference threads:
Daveman's recent MC19 thread, points 1 and 4 of post #1: http://yabb.jriver.com/interact/index.php?topic=84880.0
Daveman's MC18 post from Feb 2013: http://yabb.jriver.com/interact/index.php?topic=78510.msg533889

I ran into this yesterday. I have a friend whom I'm courting with MC19. I think I convinced him to get it yesterday.
I got him the trial and we connected to my home library from about 40 miles away. He was very impressed.

One thing I noticed, however, was that he could go into Overview and see what I was playing in all of my local zones. Indeed, he could control things there if he wished to do so. However, the converse was not true; what he was playing from my library was not shown in my home computer's overview. Indeed, even if he were transcoding and streaming video, which could be taxing on my system and affecting my own computer's playback quality, I could only take a guess at this if I were sitting in my home. Now, I don't foresee him having long term access to my library unless I can serve it from directly from my unraid server in the future, but there will definitely be situations in the future where one of the family is travelling and will need media on-the-go while other media is being played from the same server locally.

This seems to be kind of the opposite priority system to me. IMO, the local user, or admin user, should at least have all the control and be allowed to stop a remote client's playback if required. ALL zones connected, including webgizmo etc. should be visible in overview.

Could a guest user type be created who can connect via Gizmo, library client, etc. that cannot see the overview, but can only control and see their own zone?

[fitbrit]

I could imagine such a scenario if we could extend users (and their passwords) when connecting to a media library remotely. i.e. replace the current media network username and password with those from our user list. That way we could define which zones a user can or cannot access if Matt et al make that a feature too.