[mythtv-commits] Ticket #9830: error changing channel on PVR350

MythTV noreply at mythtv.org
Fri Jan 27 22:37:29 UTC 2012


#9830: error changing channel on PVR350
-------------------------------------------+-----------------------------
 Reporter:  Simon Kenyon <simon@…>         |          Owner:
     Type:  Bug Report - General           |         Status:  new
 Priority:  minor                          |      Milestone:  unknown
Component:  MythTV - General               |        Version:  Master Head
 Severity:  medium                         |     Resolution:
 Keywords:                                 |  Ticket locked:  0
-------------------------------------------+-----------------------------

Comment (by Bob K Mertz <online@…>):

 This issue is also affecting me since upgrading to 0.25 on a Mythbuntu
 11.10 system.  On my system I am using a total of 3 PVR-150 tuner cards
 with 2 being connected to analog cable and 1 being connected to a Dish
 Network receiver.  Everything functioned perfectly on 0.24 (I was not
 running 0.24 fixes) but now everything works but I exhibit the same
 results with not being able to change channels directly from one dish
 network channel to another (ie. on the same tuner).  I can, however,
 switch to a channel on an analog cable tuner and then switch back with no
 issues.  The error that I get on the front end varies between "Error
 opening jump program file" or an error related to waiting for video
 buffers.  I have done a lot of googling on this issue and it seems that
 there were reports of this error back in 0.22 and 0.23 but not in 0.24
 until 0.24-fixes came out.  I found that in 0.24 the ringbuffer time was
 increased to 10 seconds because ''Several tickets recently have suggested
 the default 2 second timeout is potentially too short for certain tuner
 types and configurations and leads to unnecessary playback failures.''
 This was then changed back for 0.25 and it appears this was something that
 was backported to 0.24-fixes.

 0.24 change:
 https://github.com/MythTV/mythtv/commit/0651d1c9ae5f8c965f7e49a3310d0d9962a3df22

 0.25 change:
 https://github.com/MythTV/mythtv/commit/4e8d935

 In my opinion I think that Ticket #9846 is the same issue as this.

 I am going to attach my backend log file as well.  Note that I have
 removed a ton of device poll errors from the log since they continued for
 the duration of the issue.

 root at mythtv-backend:~# mythbackend --version
 Please attach all output as a file in bug reports.
 MythTV Version : v0.25pre-4159-gf2d222c
 MythTV Branch : master
 Network Protocol : 71
 Library API : 0.25.20120123-2
 QT Version : 4.7.4
 Options compiled in:
  linux profile use_hidesyms using_alsa using_oss using_pulse
 using_pulseoutput using_backend using_bindings_perl using_bindings_python
 using_bindings_php using_crystalhd using_dvb using_firewire using_frontend
 using_hdhomerun using_ceton using_hdpvr using_iptv using_ivtv
 using_joystick_menu using_libcrypto using_libdns_sd using_lirc using_mheg
 using_opengl_video using_qtwebkit using_qtscript using_qtdbus using_v4l2
 using_x11 using_xrandr using_xv using_bindings_perl using_bindings_python
 using_bindings_php using_mythtranscode using_opengl using_vaapi
 using_vdpau using_ffmpeg_threads using_live using_mheg

 Additional information on my system:  I am running a backend server with 2
 front ends that both exhibit the same issues.  The backend machine is
 using multiple arrays on a 3ware 9500 PCI card and is a dual AMD Opteron
 246 system with 8GB of RAM (running 32bit).  Both front end machines are
 connected over a 10/100 network.

-- 
Ticket URL: <http://code.mythtv.org/trac/ticket/9830#comment:6>
MythTV <http://code.mythtv.org/trac>
MythTV Media Center


More information about the mythtv-commits mailing list