Suspend / Hibernate and Wake Up (1 Viewer)

[igalan]

I've just read that the new TV Engine will not support this feature. So all the users of MP will have to leave at least one PC running 24/7, even when it isn't necessary, to record a few hours of TV. In these times when we have to look for our environment, every spent Watt counts; please allow or boxes to sleep when they do nothing

 

[infinite.loop]

I've just read that the new TV Engine will not support this feature. So all the users of MP will have to leave at least one PC running 24/7, even when it isn't necessary, to record a few hours of TV. In these times when we have to look for our environment, every spent Watt counts; please allow or boxes to sleep when they do nothing

no clue where you have been reading that.

if you run a single-seat setup, the system will be hibernated/resumed as it is with current MediaPortal.

Hibernating a DEDICATED TV-Server PC, is a bad idea, because how do you wake it up when a client wants to watch TV, or see any other stuff that is hosted on this server?
I know that WOL could come in handy there, BUT configuration/setup to get it working in a LAN can be a real PITA (if hardware supports it at all!), and way to much for a "normal" user.

This will maybe supported in the futur. but at first the server/client has to work flawless befor, nifty features can be thought about.

so:
single seat: no difference to current MediaPortal

network setup: DEDICATED TV-Server(s) should be online 24/7

 

[Spragleknas]

Besides; winter is soon here - all watts are released as heat anyway....

 

[igalan]

I've just read that the new TV Engine will not support this feature. So all the users of MP will have to leave at least one PC running 24/7, even when it isn't necessary, to record a few hours of TV. In these times when we have to look for our environment, every spent Watt counts; please allow or boxes to sleep when they do nothing

no clue where you have been reading that.

Here. Maybe I missunderstood the post.

I know that WOL could come in handy there, BUT configuration/setup to get it working in a LAN can be a real PITA (if hardware supports it at all!), and way to much for a "normal" user.

That was the answer, WOL . Nowadays all computers have built in LAN ports which already support WOL. Anyway a feature like this has be optional, as it is now. If it works, that means the backend could be powered off until a recording is due, or a client sends a WOL packet; remaing quiet the rest of the time.

This will maybe supported in the futur. but at first the server/client has to work flawless befor, nifty features can be thought about.

I'm glad to hear that. Probably I missunderstood what Frodo said about no support for hibernating/wake up. Thanks for the clarification .

 

[infinite.loop]

Nowadays all computers have built in LAN ports which already support WOL. .

my life would be muuuuch easier if that would be true. but it isnt.
not every onboard or additional PCI-E/PCI NIC supports WOL.

Even if the manuafaturer says that it is supported, does not mean that it works like it should

Anyway a feature like this has be optional, as it is now. If it works, that means the backend could be powered off until a recording is due, or a client sends a WOL packet; remaing quiet the rest of the time.

But you know that waking up an i.e. Windows Server2003 can take up to 5 minutes?

Adding WOL support as additional feature is a nice idea imo. but ppl have to be aware of the problems (hardware side) and downsides regarding useability.

 

[Maschine]

In the meantime you could play around with the windows task manager and a tool like poweroff: Select a time like 1 in the night (or whenever you are pretty sure that no clients wants to use the server and you don't have any recordings scheduled) to suspend the PC with Poweroff, then schedule another task that wakes the computer in the morning.

This will however NOT care about your scheduled recordings at all!!!

But as "every Watt counts" maybe it's a reasonable workaround for you...

Maschine

 

[pirlone]

and what if i have following config:
one dedicated htpc which acts like server+client (single-seat config, more capture cards) and one remote client which will occasionaly watch live tv and schedule recordings... is that config possible at all? will in that case my htpc (server+client) work like old tv engine was working regarding power saving (powerscheduler plugin - auto suspend, wake-up)? i don't mind if remote client doesn't wake up htpc for watching live tv, so i don't need WOL at this stage...

sorry if this is a dumb Q. just collecting info before i jump into TV engine 3 train

rgs, pirlone

 

[igalan]

my life would be muuuuch easier if that would be true. but it isnt.
not every onboard or additional PCI-E/PCI NIC supports WOL.

Even if the manuafaturer says that it is supported, does not mean that it works like it should

I know, I work on IT and have to "fight" with stuff like this. Hopefully modern hardware (and not that modern) usually works well in this regard.

But you know that waking up an i.e. Windows Server2003 can take up to 5 minutes?

From a cold boot, yes. If you suspend it, it will need seconds to reactivate. I've tested it on a Windows 2003 Server Standard Edition SP1 with no issues (on a Opteron 244 box and on a dual Xeon P4 box). Of course not all hardware supports this properly.

Anyway all points have been made, haven't they? I believe that the ability to suspend the TV Server, even if it's a separate computer, it's important to avoid wasting energy. That's it . I'm glad to hear that on stand alone box it will work just as it does now. I wish I had the skills to help the dev team, but I don't think that knowing VB.NET and no DX could help .

 

[igalan]

In the meantime you could play around with the windows task manager and a tool like poweroff: Select a time like 1 in the night (or whenever you are pretty sure that no clients wants to use the server and you don't have any recordings scheduled) to suspend the PC with Poweroff, then schedule another task that wakes the computer in the morning.

Windows XP and 2003 have the shutdown command to perform those same functions. But since right now I'm using a standalone configuration, it seems that I won't be have to take care of manually scheduling power offs .

Thanks for the tip anyway .

 

[reagan+carter]

hi everyone,

I've modified scriptedlogon (see the plugin download page) in order to handle WOL packets. It may now be used to check whether a machine hosting the upcoming TV server is still used by some clients, or not. Implementing this nifty idea outside of MP code is just a proof-of-concept. It works nicely inside my home LAN:
-when the server doesn't receive any WOL packet (stamped with its own MAC address) for a long time, it then guesses that it's not used anymore and is put to sleep
-a WOL packet, with the MAC address of the server, sent by a client wakes up the server (where the TV engine is autostarted at boot, still using scriptedlogon)
-and the client keeps the server alive by sending the same WOL packets periodically
-etc

make your own changes in the code if needed: the WOL packet is broadcasted, using UDP, toward port 9.

PS The new scriptedlogon download link is pedning for approval right now. Been submitted about 10 minutes ago.