Thanks for the reply.... The short answer is that it is all wire ... not wireless.
I have tried a couple of things... I tried just wiring the 2 boxes together by themselves on their own hub. This did not work. Same problems as before...however with this configuration they were not connected to the internet so NTP 'could' have been an issue. I now have the machines back on my standard home network. This is a 3COM 8 port hub, ISDN router. I put ethereal on the backend and watched the traffic. I saw no correlation between 2 backend stops. I couldn't point to NTP, CUPS, etc. etc. I have also put ethereal on the frontend as well. Again nothing pointing to a specific cause. One odd thing ... with ethereal running it can take over 20+ minutes before it stops with the errors described. Without ethereal I cannot make it 10 minutes....ever. Also, I have been watching TV on the system for hours today .... not one problem...... Hmmmmmmmm Greg On Thu, 2005-02-03 at 19:54, Michael Wester wrote: > > I wrote about this particular problem yesterday ... > > http://www.gossamer-threads.com/lists/mythtv/users/108116 > > > > The only thing I can think of ... is that the Live TV has more code > > around pausing, getting behind, etc. etc. whereas if you are watching a > > recording (nuv file) any errors and you are popped out .... > > What kind of network are you using to connect the two boxes? I have > been seeing similar issues when I tried to add a remote frontend to my > working frontend/backend system with similar error messages on the > remote frontend. All are Myth v.16, SuSE 9.2. Using PVR-350 on > combo frontend/backend box with no problems recording, playing or > otherwise. Remote frontend box is connected via wireless g bridge to > the network and I'm viewing through nvidia quadro card to monitor. I > see similar issues as you've described, only live tv will also die. > Here's the thing, on the remote frontend, live tv is more stable than > recordings. Recordings will die within 1-3 minutes while live tv can > make it 15 minutes before displaying this behavior. Of course this is > pretty anecdotal data-(I didn't perform the test in triplicate and > record the times or anything- [but I might tonight]) but the > phenomenon was enough that I did make a mental note of it. When I > physically move the remote frontend box and make a wired connection to > the router to which my backend is directly wired (thereby making a > 100mbs connection), it did not crash even when watching recordings- It > worked fine for over 30 minutes so I called it stable and moved > everything back. As of tuesday morning when I did this test I was > thinking that my network is a little flaky (even though there are no > other issues with streaming media to windows boxes connected through > the wireless bridge), but there may be more to it. I also feel like > if there was a way to just bump up the buffering a little bit, I'd be > fine... My other thought is to try to transcode, instead of streaming > MPEG-2, smaller files should stream better. But, since my main system > uses the PVR-350 tv-out, I hesitate to even go down this path as it's > not a real long term solution for me. The remote frontend is a > workstation and should get minimal use with myth... > > ______________________________________________________________________ > _______________________________________________ > mythtv-users mailing list > [email protected] > http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
_______________________________________________ mythtv-users mailing list [email protected] http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
