Is anyone out there actively using a slave backend that is streaming from it? I know this is a less common setup.. but it seems unlikely that I would be the first to report it, so i'm wondering if something else is going on with my setup.<br>
It does not seem to be working with .24. This seems to be a regression, as it used to work with .23<br><br>Setup:<br>Master backend with lots of storage, and several tuners.<br>Multiple frontends (ion boxen)<br>Slave backend with hdpvr connected over wifi - 802.11 g. It has it own limited storage. Connection is pretty decent, can rsync file at ~1.1 MB/sec <br>
<br>Typically, after a recording is complete, I have a user job to run a python script to copy the recording to the master backend.. but streaming the file did generally work over the myth protocol (unless I happening to be using the microwave at the same time). <br>
<br>Since I hadn't fixed my script to use the .24 bindings, I was trying to watch some recordings last weekend, and discovered that this didn't work anymore.<br><br>I had a theory that it was timing out, due to the higher latency wifi connection, and that a timeout changed with .24, Well I changed one timeout that was set for 2000 ms to 9000ms, and it made no difference. As it seems to fail the connection after 3 seconds in the log. <br>
<br>Frontend, trying to watch recording:<br><a href="http://pastebin.com/f20EFzTt">http://pastebin.com/f20EFzTt</a><br><br>Slave backend, with hosting file:<br><a href="http://pastebin.com/SauRX2w2">http://pastebin.com/SauRX2w2</a><br>
<br>Anyone using streaming protocol w/ 0.24. Is this a problem with my setup that has crept in, or new bug?<br><br>Thanks<br>--Glen Dragon<br><br><br><br><br>