INTERACT FORUM

Please login or register.

Login with username, password and session length
Advanced search  
Pages: [1]   Go Down

Author Topic: gizmo "where to play" does not send WOL to designated PC.  (Read 781 times)

gibman

  • Member
  • *
  • Posts: 3
gizmo "where to play" does not send WOL to designated PC.
« on: March 13, 2014, 02:39:14 pm »

using latest gizmo 19.0.114 on an android phone.

I have 2 MC servers.

server1 which is running in livingroom and is connected to an AVR/TV/speaker system.
this machine is often in standby mode. Once on, it automatically turns on TV/AVR etc.

server2 which is running as a standalone server (null audio output).
this machine is running 24-7

server status:
server1: sleeping/standby
server2: running

When I start gizmo I choose:

where to play: server1
where to play from: server2

sadly it seems server1 is not awoken.
workaround:
I need to choose "where to play from: server1
... then the correct WOL is dispatched and the machine is awake :)
then I can change it back to : where to play from: server2

So the "where to play" feature alone does not send off a WOL command.
where as "where to play from" does.

Is this by design ?

another thing that would be nice would be an option to NOT have gizmo automatically use the last used value for "where to play from".

eg. if "where to play from" is server1 (server1 is woken up by WOL=> good) . I then turn of gizmo.
A few days passes by.
This time i want to connect to my 24-7 server (server2). I start gizmo, but now it defaults to the last used server, which is "server1" in this case.
So I am sitting at work realizing that my livingroom PC has now been awoken.
obviously I can now choose to connect to my 24-7 server "server2" and play from there.

a nice feature would be an option where I could tell gizmo to always prompt me for a server to play from.

I hope I made some sense :)

regards
gibman
Logged
Pages: [1]   Go Up