On Sunday 11 December 2005 16:25, Hans Verkuil wrote: > On Sunday 11 December 2005 22:12, Niels den Otter wrote: > > Hello Hans, > > > > Hans Verkuil wrote: > > >>I have this problem for some time now and it is very inconvenient. > > >>All suggestions for further debugging or to solve this problem are > > >>more than welcome. > > > > > > This message appears if the reader application cannot keep up with > > > the mpeg stream from the driver. The easiest way to check that this > > > is also the case this time is to run 'cat /dev/video0 >x.mpg'. This > > > should work without problems and you should be able to play x.mpg > > > using mplayer or xine. > > > > > > If the 'cat' test works, then there is something wrong with your > > > MythTV setup (one option is to try a newer version if available). > > > > I have been using MythTV for long time and have not seen this problem > > before. I am on SVN so upgrading is not an option ;-) Problem started > > after the recent LiveTV changes in MythTV. > > So the cause is in those LiveTV changes. Perhaps you should > downgrade :-) > > > The 'cat /dev/video0 ; etc' worked fine. So does watching Live-TV and > > recordings under MythTV. The problem is triggered when I watch > > Live-TV and while watching a planned recording starts. > > > > If I understand you correctly I should have put this question on the > > MythTV mailing-list instead of the IVTV list, because that is where > > the problem presumably is. > > Correct. These ivtv messages always point to a problem with the reader > application, not to a problem with the driver. I really should rewrite > these messages to make them less cryptic and point the user to the > right direction.
Only thing ivtv-side in Myth that's changed recently is that I started reading smaller sizes in at a time (went down to 4k). Look for where it sets bufferSize to 4096 on or about line 80 of libs/libmythtv/mpegrecorder.cpp and bump that up to 32768 or so. Side note, would it be possible to use the complete frame-read mode with ivtv, instead of just getting back the requested raw bytes? It used to work that way, and used to be a lot nicer to know you're getting a complete frame every time you did a read. Isaac _______________________________________________ ivtv-devel mailing list [email protected] http://ivtvdriver.org/mailman/listinfo/ivtv-devel
