Well this brings up a suggestion What about implementing a builtin caching sort of thing, similar to how you would cache something streamed over the web in real player. Something that would at least fill the buffer to a certain amount based upon the speed its being sent at?
On Fri, 25 Mar 2005 18:02:43 -0800, Brad Templeton <[EMAIL PROTECTED]> wrote: > On Thu, Mar 24, 2005 at 04:10:38PM -0800, Richard J. Sears wrote: > > Is there any way to deal with this by caching to the frontend to help > > this problem out...? > > > > So you hit the "play" button and it starts a 3 to 5 minute caching > > process (which should be enough) and then starts playing. > > > > Wireless is the only way for me to get there. > > > > What about "non-HD" cable channels..what is the requirement there..? > > Well, you could pull the following trick. If the frontend magically > finds a copy of the file on the local machine, it plays that instead of > trying to pull it from the backend over the net. > > So you could fire up a task on the frontend to start copying the file from > the backend with rsync, for example (might want to use the rsync protocol > instead > of ssh) and start the actual playing shortly thereafter. As long as your > average wireless throughput is sufficient, you will not suffer from the > temporary dropouts. > > You would have to remember to delete locally etc. > > > _______________________________________________ > mythtv-users mailing list > mythtv-users@mythtv.org > http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users > > > _______________________________________________ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users