Hi Tim...

Tim wrote:
>> I am trying to add a remote control feature to MClient.
>>
>> I thought this feature would just drop out of the code if I changed the
>> MAC address to the client I wanted to control.  I was wrong.  Turns out
>> I have these MClient state machines I forgot about.  Maybe the code
>> would work as is with an older / real slimserver client.  But, when
>> masquerading for another MClient, all heck breaks loose (i.e. the two
>> MClients trigger each other into a "ask for a play list" frenzy).
>>
>> I envisioned this feature to look like what you see when controlling the
>> local hardware (i.e. the only difference would be the word REMOTE
>> CONTROL MODE plastered on the top of the screen).
>>
>> Why?  Well, say you were listening to music somewhere in the house and
>> you walked into the den and decided to stay and... read your e-mail.
>> You start up some new music but still can hear what you left playing
>> somewhere else in the house.  Simply take control of that other
>> slimserver client and shut it down.
>>
>> Ok, as you were reading your e-mail, it follows you could have done the
>> above w/your browser instead.  So...  turn everything around and say you
>> started in your den and ended up somewhere in the house w/o a computer.
>>
>> Getting to the point - what would make this feature useful?
>>
>> That is, would you use it if all you had was the "REMOTE CONTROL MODE"
>> message at the top of the screen?
>>
>> Or would you need one or more of the following?:
>>
>> 1) State of the remote client (i.e. STOP, PLAY, PAUSE...).
>>
>> 2) Two line widget as seen on the remote client (the classic slimserver
>> two line display).
>>
>> 3) Image of the album (if available) as displayed on the remote client.
>>
>> 4) List of titles in play list (this may be difficult) as seen on the
>> remote client.
>>
>> 5) Listen to what is playing on the remote unit (may not be as hard as
>> one might think).
>>
> 
> I have been using the Slimserver Server Plugin Shadow Play
> (http://www.gwendesign.com/slimserver/dev_software.htm#shadowplay) to 
> accomplish
> something similar to what you describe.  With this plugin, I use the MediaMVP 
> to
> remotely control the Softsqueeze client on my myth box that also feeds the 
> whole
> house audio speaker distribution system. In remote mode, the MClient interface
> properly displays playlist and appears as if I were at the local display.
> 
> The only problem I have encountered is that I have been unsuccessful exiting
> remote mode to return to controlling local MClient.  The Shadow play looks for
> an extended continuous press of the left arrow button on the remote and my
> suspicion is that the MVP does not properly detect this.  I haven't bothered 
> to
> look into this any further as it has only been a minor annoyance.....

Interesting, this was mentioned to me on the slimserver list - but now 
it clicks.  I see your point.  If I encounter problems with implementing 
this feature I'll have to consider this a viable alternative.

As far as the left button, almost all MClient button presses go through 
the slimserver before being returned as an action the client needs to 
execute. So, I am surprised this doesn't already work. Unless pressing 
and holding the left arrow key has to be processed locally on the 
client.  For example, until recently, pressing and holding the Fast 
Forward button didn't change the slimserver jump forward multiplier 
until someone pointed out to me that the client detects this locally and 
issue CLI commands accordingly.

If you find out how this left arrow thing works, let me know - we can 
probably change MClient software if necessary.



-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Mvpmc-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mvpmc-users
mvpmc wiki: http://mvpmc.wikispaces.com/

Reply via email to