<div class="gmail_quote">On Thu, May 8, 2008 at 7:51 AM, Ben Dailey <<a href="mailto:ben@inspiredtechs.com">ben@inspiredtechs.com</a>> wrote:<br>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">
<div>
<div></div>
<div class="Wj3C7c">On Thu, May 8, 2008 at 8:18 AM, Kevin Kuphal <<a href="mailto:kkuphal@gmail.com">kkuphal@gmail.com</a>> wrote:<br>><br>> On Wed, May 7, 2008 at 8:48 AM, J <<a href="mailto:jsweepstakes@gmail.com">jsweepstakes@gmail.com</a>> wrote:<br>
><br>> > Hi,<br>> > I'm looking for a way to add a front end over ssh, is there a way to cache<br>> the data in order to download it and then watch it after its done? [this<br>> also would be useful for wireless clients that are on a slower connection<br>
> then the encoded rate]<br>><br>><br>> The best option I came up with for very slow links would be:<br>><br>> - Remote frontend<br>> - Custom user job on master backend that transcodes (to reduce size) and<br>
> SCP (to move file) to frontend<br>><br>> Now, here I think you have some options. You could just leave the frontend<br>> connected to the backend and put the files in the same mount locations that<br>> the backend has but leave them local and do not mount the actual storage<br>
> from the backend. I *think* that the frontend will play local files first,<br>> then try to go to the backend for streaming.<br>><br>> You also might be able to run a slave backend on the frontend and do some<br>
> hostname changes in the DB for recordings to "move" them to the slave<br>> backend storage and Myth will load them from there<br>><br>> A third option might be to run a completely separate Myth system, move the<br>
> file, insert the DB entry (nuvexport will make SQL for you), then<br>> mythcommflag to rebuild the seektable and your frontend would have a list of<br>> only recordings it had cached. I think this has often been proposed for a<br>
> car type configuration where the connectivity is intermittent.<br>><br>> I hope this gives you something to chew on and some ideas.<br>><br>> Kevin<br><br></div></div>Maybe this has already been proposed but just in case it hasn't here<br>
we go. How about creating "virtual tuning device" that is capable of<br>connecting to a unique and separate mythtv backend.<br><br>Example:<br><br>I setup a working mythtv backend at my home and have a couple of ATSC<br>
tuners I record shows and they are stored on my backend.<br><br>I setup a new mythtv baackend at my lake home and have no tuners but I<br>setup a "virtual tuning device" with a channel that is attached to the<br>
backend at my home receives a list of recorded programs and then<br>beginnings "recording" them as any other tuner would do. The recording<br>would actually just be a download.</blockquote>
<div> </div>
<div>Seems like an awful lot of work for something that could be accomplished with a post-recording user job or a simple rsync script on the remote system to sync the folders.</div>
<div> </div>
<div>Kevin</div></div>