2008-05-07, 01:09 AM 
	
	
	
		Does the recording service use the TCP connection continuously when recording? (as opposed to when doing nothing?)
I see that utility has an option to prevent standby if there is activity on a specified port.
So is there any difference between the TCP activity on port 76xx (forget which ones the recording service uses locally) when recording vs waiting?
Also, I could use this to prevent me pushing the standby button when a client is connected I guess (port 7968?)
Cheers
	
	
I see that utility has an option to prevent standby if there is activity on a specified port.
So is there any difference between the TCP activity on port 76xx (forget which ones the recording service uses locally) when recording vs waiting?
Also, I could use this to prevent me pushing the standby button when a client is connected I guess (port 7968?)
Cheers
"Shut up brain, or I'll stab you with a Q-Tip!"
--= Win7, C2D 2.93 GHz, ASUS 9400GT Silent, 2GB Ram, Few HDD's, 3TB unRAID server, Samsung 50" 1080p Plasma via HDMI, 40" 1080i LCD via VGA =-- * PVR2000 Analog PCI / Avermedia DVB-S PCI / Hauppauge 2200 DVB/Analog * PCH GBPVR Client * *BD-E6500 w/ NPVR client*
	
--= Win7, C2D 2.93 GHz, ASUS 9400GT Silent, 2GB Ram, Few HDD's, 3TB unRAID server, Samsung 50" 1080p Plasma via HDMI, 40" 1080i LCD via VGA =-- * PVR2000 Analog PCI / Avermedia DVB-S PCI / Hauppauge 2200 DVB/Analog * PCH GBPVR Client * *BD-E6500 w/ NPVR client*
 





 it's the logic involved where the complexity kicks in. how should it behave? ask 4 people & you'll get 7 opinions. that's where he would have to make it configurable
 it's the logic involved where the complexity kicks in. how should it behave? ask 4 people & you'll get 7 opinions. that's where he would have to make it configurable
	
 ystem" in Task Manager, so it runs with default options which is "standby allowed".
ystem" in Task Manager, so it runs with default options which is "standby allowed".