You might also want to change the group name for the remote recording (to maybe , 'Remote')so that they are not mixed with the rest of the local recordings(Default) and you wont select with mythfrontend accidentally on a nonlocal file. On the master backend, create a batch script and run with cron that compares local and remote filesizes for each individual mpeg files under the 'Remote' group and then have it change the group name entry on the recorded table to Default once local and remote file sizes are equal. This way if the recording shows up in Default, then you know you have the complete file locally.
<br><br>Of course, I could be wrong at so many levels. But this is indeed interesting. I might try it myself.<br><br><br><br><div><span class="gmail_quote">On 10/4/07, <b class="gmail_sendername">Chris Isip</b> <<a href="mailto:cmisipster@gmail.com">
cmisipster@gmail.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">It might be possible. Lets say we have a slave remote backend and a master local backend with each recording to their own local directories. The only difference I think between the entries in recorded will be the hostname setting (provided the local directories are similarly named). If you change the hostname setting on ALL the recorded programs to the hostname of the master backend, selecting a recording that does not exist locally on the master will result in an error message. (Right?) Now all you need is to do an periodic rsync between the two boxes and as soon as the video file is transferred to the master backend, you should be able to access it from mythfrontend in the same network as the master backend. You probably just want the remote slave backend to sit in a corner and not have anybody mess with it. Rsync has a setting for transfer speed limit with the option --bwlimit so you wont hog the bandwidth. It might be possible...
<div><span class="e" id="q_1156daaedbf2cf78_1"><br><br> <br><br><div><span class="gmail_quote">On 10/4/07, <b class="gmail_sendername">Blammo</b> <<a href="mailto:blammo.doh@gmail.com" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
blammo.doh@gmail.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
On 10/4/07, Taco Mel <<a href="mailto:taco_mel@yahoo.com" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">taco_mel@yahoo.com</a>> wrote:<br>> I wish to record a small number of shows that are not
<br>> available in my area (mainly a couple PBS shows our<br>> local affiliate does not pick up). I have a spare
<br>> machine and tuner card to place at a family member's<br>> home. My plan is to transfer the files using DVDs or,<br>> when I visit, a portable HDD. (Or occasionally a<br>> network copy in the middle of the night.)
<br>><br>> My first thought was to set the remote machine up as a<br>> completely isolated MythTV system, with its own<br>> database, and occasionally log in to it remotely by<br>> SSH to check things out or burn files to a DVD. I'll
<br>> then have *.mpg files that I can somehow import into<br>> MythTV. Somehow I will then have to construct<br>> metadata.<br>><br>> My second thought was to integrate the remote system<br>> into my existing MythTV setup so that I can manage and
<br>> monitor the entire system from one place. I'll set up<br>> OpenVPN between the sites, which I have done before<br>> for various projects so that's no problem. I believe<br>> that I will then have all the metadata and when I move
<br>> the corresponding *.mpg file into one of my storage<br>> groups, it will stream from my local backend.<br>><br>> However, I *do not* want my local frontends to try to<br>> stream a program from the remote backend, because it
<br>> either will be too slow to work, or it will use enough<br>> bandwidth that said family member might no longer be<br>> willing to host said remote backend.<br><br>I'm thinking a combination of:<br>-- "master backend override" to force streaming from the "master"
<br>-- "commflag/transcode only on recording backend"<br>-- rsync over a reasonable WAN<br><br>and you could probably run a completely remote backend. Nice idea,<br>makes me tempted to try..<br>_______________________________________________
<br>mythtv-users mailing list<br><a href="mailto:mythtv-users@mythtv.org" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">mythtv-users@mythtv.org</a><br><a href="http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
</a><br></blockquote></div><br>
</span></div></blockquote></div><br>