Here is a patch to limit the mythtv bps used for seeks to a reasonable
value.   It has been tested and appears to work.

The basic problem I was having is that some audio converted ATSC video
from a couple of stations appear to somehow cause very high Bps's to show
up and when used for seeks result in incorrect huge seeks.

Here is sample output I have from one of those ATSC recordings that have
the issue:
Seek Bps was 2835 kbps
Seek Bps was 3726 kbps
Seek Bps was 0 kbps
Seek Bps was 3164 kbps
Seek Bps was 80436 kbps too high - set to 4Mbps
Seek Bps was 4195 kbps
Seek Bps was 3140 kbps
Seek Bps was 0 kbps
Seek Bps was 0 kbps
Seek Bps was 3179 kbps
Seek Bps was 3406 kbps

I don't know where the 80kbps came from, the OSD is also showing similar
high numbers but does not cause issues.

                                Roger


diff --git a/src/video.c b/src/video.c
index 0c428af..598a62b 100644
--- a/src/video.c
+++ b/src/video.c
@@ -592,6 +592,17 @@ seek_by(int seconds)
         size = video_functions->size();

         seek_seconds = seek_start_seconds + seconds;
+
+       /* The mvpmc hardware can only handle 12Mbps and some ATSC SD broadcasts
+          appear to some way result in huge (200+Mbps) values to appear in the
+          seeks and cause 30 seconds seeks to go for a lot longer */
+       if ( seek_Bps > (12/8)*1024*1024) {
+               printf("Seek Bps was %d kbps too high - set to 
4Mbps\n",8*seek_Bps/1024);
+               seek_Bps = (4/8) * 1024 * 1024;
+       }
+       else
+               printf("Seek Bps was %d kbps\n",8*seek_Bps/1024);
+
         delta = seek_Bps * seconds;

         /*

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Mvpmc-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mvpmc-users
mvpmc wiki: http://mvpmc.wikispaces.com/

Reply via email to