[mythtv-users] Error opening jump program file buffer

[Douglas Peale]

On 10/04/2010 06:41 PM, David Whyte wrote:
> On Tue, Oct 5, 2010 at 11:35 AM, Douglas Peale
> <Douglas_Peale at comcast.net> wrote:
>> I get this error every time I attempt to change channels from an SD channel to an HD channel, but only on cable.
>> On OTA tuners, I can freely change channels between SD and HD.
>> I have 5 tuners, 4 are HDHomeRuns, and the other is an ATI HDTV Wonder. The tests I have run however are all on the HDHomeRuns.
> 
> 
> Sorry, no help from me here but I have seen this too (and there are
> many mentions of it on the list) and thought my tuner was half to
> blame.  Are you saying this happened with your HDHomeRun tuners (I
> have dodgy PCI DVB-T tuners).
> 
> Also, it may be helpful to those that can help if you mention a bit
> about your setup, such as mythTV version, OS, hardware etc.
> 
> Regards,
> Whytey


Requested additional detail:

Commit Log for Mon Oct  4 10:24:37 2010
Upgraded the following packages:
libmyth-0.23-0 (0.24.0~trunk26618-0ubuntu0~mythbuntu1) to 0.24.0~trunk26630-0ubuntu0~mythbuntu1
libmyth-python (0.24.0~trunk26618-0ubuntu0~mythbuntu1) to 0.24.0~trunk26630-0ubuntu0~mythbuntu1
libmythtv-perl (0.24.0~trunk26618-0ubuntu0~mythbuntu1) to 0.24.0~trunk26630-0ubuntu0~mythbuntu1
mytharchive (0.24.0~trunk26618-0ubuntu0~mythbuntu1) to 0.24.0~trunk26630-0ubuntu0~mythbuntu1
mythgallery (0.24.0~trunk26618-0ubuntu0~mythbuntu1) to 0.24.0~trunk26630-0ubuntu0~mythbuntu1
mythmovies (0.24.0~trunk26618-0ubuntu0~mythbuntu1) to 0.24.0~trunk26630-0ubuntu0~mythbuntu1
mythmusic (0.24.0~trunk26618-0ubuntu0~mythbuntu1) to 0.24.0~trunk26630-0ubuntu0~mythbuntu1
mythplugins-dbg (0.24.0~trunk26618-0ubuntu0~mythbuntu1) to 0.24.0~trunk26630-0ubuntu0~mythbuntu1
mythtv (0.24.0~trunk26618-0ubuntu0~mythbuntu1) to 0.24.0~trunk26630-0ubuntu0~mythbuntu1
mythtv-backend (0.24.0~trunk26618-0ubuntu0~mythbuntu1) to 0.24.0~trunk26630-0ubuntu0~mythbuntu1
mythtv-backend-master (0.24.0~trunk26618-0ubuntu0~mythbuntu1) to 0.24.0~trunk26630-0ubuntu0~mythbuntu1
mythtv-common (0.24.0~trunk26618-0ubuntu0~mythbuntu1) to 0.24.0~trunk26630-0ubuntu0~mythbuntu1
mythtv-database (0.24.0~trunk26618-0ubuntu0~mythbuntu1) to 0.24.0~trunk26630-0ubuntu0~mythbuntu1
mythtv-dbg (0.24.0~trunk26618-0ubuntu0~mythbuntu1) to 0.24.0~trunk26630-0ubuntu0~mythbuntu1
mythtv-frontend (0.24.0~trunk26618-0ubuntu0~mythbuntu1) to 0.24.0~trunk26630-0ubuntu0~mythbuntu1
mythtv-theme-arclight (1:0.24.0~trunk26618-0ubuntu0~mythbuntu1) to 1:0.24.0~trunk26630-0ubuntu0~mythbuntu1
mythtv-theme-childish (1:0.24.0~trunk26618-0ubuntu0~mythbuntu1) to 1:0.24.0~trunk26630-0ubuntu0~mythbuntu1
mythtv-theme-graphite (1:0.24.0~trunk26618-0ubuntu0~mythbuntu1) to 1:0.24.0~trunk26630-0ubuntu0~mythbuntu1
mythtv-theme-metallurgy (1:0.24.0~trunk26618-0ubuntu0~mythbuntu1) to 1:0.24.0~trunk26630-0ubuntu0~mythbuntu1
mythtv-theme-mythbuntu (1:0.24.0~trunk26618-0ubuntu0~mythbuntu1) to 1:0.24.0~trunk26630-0ubuntu0~mythbuntu1
mythtv-themes (1:0.24.0~trunk26618-0ubuntu0~mythbuntu1) to 1:0.24.0~trunk26630-0ubuntu0~mythbuntu1
mythtv-transcode-utils (0.24.0~trunk26618-0ubuntu0~mythbuntu1) to 0.24.0~trunk26630-0ubuntu0~mythbuntu1
mythvideo (0.24.0~trunk26618-0ubuntu0~mythbuntu1) to 0.24.0~trunk26630-0ubuntu0~mythbuntu1
mythweather (0.24.0~trunk26618-0ubuntu0~mythbuntu1) to 0.24.0~trunk26630-0ubuntu0~mythbuntu1
mythweb (0.24.0~trunk26618-0ubuntu0~mythbuntu1) to 0.24.0~trunk26630-0ubuntu0~mythbuntu1

Ubuntu 10.04
Kernel 2.6.32-25-generic
Processor Intel i7
Memory 6 GB
Video AMD HD4850 @ 2560x1600
Combined frontend/backend/desktop no additional frontends or slave backends

Tuners
HDHomerun box 1: two tuners on cable
ATI HDTV Wonder on cable (analog nonfunctional)
HDHomeRun box 2: one tuner on an antenna pointed NW, another on an antenna pointed S

The surprising thing to me is that this bug affects cable, but not OTA. By the time the data comes out of the HDHomeRun, I would
have thought it was identical.
I got curious and just proved to myself that any of my tuners connected to cable will cause this problem. However in the process
I discovered a work around.
If I switch to a tuner other than the 1st tuner, and change the channel to an HD channel, I will get the error, but if I
re-enter "watch TV", and switch back to the same tuner that just failed, it is still tuned to the HD Channel (Oddly the 1st
tuner gets switched to the channel I was on on the other tuner before I attempted to change to the HD channel), and will
properly display it. Once the HD channel is properly displayed, I can change channels for the rest of the session without problems.

For example:
Tuner 1 is on channel 2, an SD channel
I switch to tuner 4, it is on channel 8 an SD channel
I enter 5.1 an HD channel and I get dumped to the main menu with the Error opening jump program file buffer.
I re-start live TV
I find I'm on Tuner 1 which is now on channel 8 (I did not ever change channel on tuner 1).
I switch to tuner 4, I find it is on channel 5.1 which it tunes correctly.
I can now tune freely without running into the jump program file buffer error.