<div dir="ltr">Thank you!<div><br></div><div style>I had thoughts on trying to get MythTV 0.26 or a version of your plan B working on mine. I have a combined MythTV FE/BE with Freeview and only want to add the odd few freesat channels to my Mythsystem and the sat feed is remote from the current setup.</div>
<div style><br></div><div style>My thoughts were exactly the same. I dont compile MythTV but just use the stock Mythbuntu with various mods of my own to integrate remotes/xbmc etc on the same box. Therefore one less version to compile (ie none) is the ideal :-)</div>
<div style><br></div><div style>Martin</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On 11 April 2013 08:09, Russell Gower <span dir="ltr"><<a href="mailto:mythtv@thegowers.me.uk" target="_blank">mythtv@thegowers.me.uk</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word"><div><div class="h5"><br><div><div>On 11 Apr 2013, at 07:33, "mythtv ." <<a href="mailto:mythtv@harley-jones.co.uk" target="_blank">mythtv@harley-jones.co.uk</a>> wrote:</div>
<br><blockquote type="cite"><div dir="ltr">Well, I've had my MOI for about a week now, As supplied it's running a buildroot/ulibC userspace and a Kernel without NFS support or loadable module support, So i've rebuilt the kernel and installed Debian Wheezy to a SD card. I have it running a v0.26 slave backend from the debian-multimedia repo.<br>
<div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<br>
I've currently got it recording to a NFS sever but the performance is questionable, it can manage a SD single recording, but seems to struggle with two. on Investigation it would appear to be network related, whilst recording two streams the kernel rpciod process uses around 60%CPU (mythbackend is around 35%) I've done some testing with IPERF and could't get it above 50mbits (where as my master backend to the same server hits 950mbits) so there is something wrong with it's network stack, but I'm not sure where to look.<br>
<br>
Any ideas anyone or should I just right this off to experience?<br>
<br>
R.<br></blockquote><div><br></div>Great work Russell!<div><br></div><div>I have mine sat on my desk here at work having just got it and want to run it exactly as you have done (ie as a slave backend)</div><div><br></div>
<div>Are you going to document the steps you have gone through? As it would save me duplicated effort!</div><div><br></div><div>Martin </div></div></div></div></blockquote><br></div></div></div><div><div>Hi,</div><div> Yes I do plan to document the build steps, I just need to find a suitable location to do so - is a page on the MythTV Wiki appropriate?</div>
<div><br></div><div>If I can't resolve the network performance issues then I have a plan B, It's currently completely untested but I'm thinking of setting up a couple of network tuners on the master backend and using a channel changing script to manipulate an instance of dvblast on the MOI - one for each tuner, the Freesat transponders i'm interested in are advertised as between 30mbits/s and 45mbits/s so multirec might not be an option, but it should manage two simultaneous recordings, without the overheads of running backend over NFS.</div>
<div><br></div><div>The more I think about it the network tuner option sounds better than running a slave backend (one less version of Mythtv to compile etc).</div><span class="HOEnZb"><font color="#888888"><div><br></div>
<div>R.</div></font></span></div><br></div><br>_______________________________________________<br>
mythtv-users mailing list<br>
<a href="mailto:mythtv-users@mythtv.org">mythtv-users@mythtv.org</a><br>
<a href="http://www.mythtv.org/mailman/listinfo/mythtv-users" target="_blank">http://www.mythtv.org/mailman/listinfo/mythtv-users</a><br>
<br></blockquote></div><br></div>