View Full Version : x264 and hibernate


Arcon
10th September 2007, 22:39
i'm currently encoding with x264 and megui, but apparently that setup is not really happy with the system going to hibernate during an encode. once the system gets out of hibernate megui just hangs, i.e. the time keeps counting, but no further frame gets encoded.

i guess the problem is that the underlying network connection to the samba share which x264 is reading from got terminated during the hibernation, but for e.g. vdubmod it's no problem to resume an encode from/to a smb-sahre even with multiple hibernation phases.

is this a problem of megui or of x264 and is there anything one (or even i) can do about it apart from moving all files to a local disk before encoding?

btw, who's deleting the current output file if i press abort in megui? is that megui or x264? because i'd appreciated it if the result of multiple hours of encoding would have been kept on the disk when i aborted the encode ;)

Dark Shikari
10th September 2007, 22:59
x264 works fine with hibernate and standby on every computer I've tried. Haven't tried MeGUI itself though.

Arcon
11th September 2007, 17:53
were also network-based drives involved when you tried it?

ACrowley
14th September 2007, 15:31
x264 works fine with hibernate and standby on every computer I've tried. Haven't tried MeGUI itself though.

Yep, it works fine...System goes in hibernate Mode while x264/megui encodes. After restart the encoding goes on without Problems

Sharktooth
16th September 2007, 01:50
i guess your network card driver is making some mess...

squid_80
16th September 2007, 03:48
Hibernation and DHCP don't get always get along. If the lease time has expired when the system resumes a new IP address must be obtained, killing any open connections. You could try assigning a static ip address if it's not got one already.

Sharktooth
16th September 2007, 03:52
most DHCP servers can be set to recognize the client MAC address and assign ALWAYS the same IP to that interface.
the connection closure is still a problem though...