[mythtv-commits] Ticket #9684: HDHomerun terminating recordings with multiple tuners running

[MythTV]

#9684: HDHomerun terminating recordings with multiple tuners running
-----------------------------------------------+---------------------------
 Reporter:  sean@…                             |          Owner:
     Type:  Bug Report - General               |  silicondust
 Priority:  trivial                            |         Status:  closed
Component:  MythTV - HDHomeRun                 |      Milestone:  unknown
 Severity:  low                                |        Version:
 Keywords:  hdhomerun multirec stop recording  |  0.24-fixes
                                               |     Resolution:  Works for
                                               |  me
                                               |  Ticket locked:  1
-----------------------------------------------+---------------------------
Description changed by wagnerrp:

Old description:

> I don't think this is a dupe, and it is VERY repeatable.  Rebuilt
> mythbuntu box this weekend and bumped to 10.04 and mythtv 0.24.  Noticed
> that my hdhomerun recordings were wigging out.
>
> removed all tuners and readded.  set up recordings filling all multirec
> (even tried without multirec).
>
> records for a short time, then Myth stops accepting traffic, even though
> the lights on the HDHomerun stay on.  Going to configure with only one
> tuner to appease the WAF, but betting I'm going to hear about it
> anyway...
>
> Reading some threads sounds like 0.24 had a library update for HDHomerun
> and there's an acknowledged issue, but it's way old.
>
> When I set up the tuners, I did NOT use the IP.  I autodiscovered and
> selected each tuner.
>
> When I looked at the debug on the HDHomerun, my signal strenght is high
> 80s to low 90s, so don't think its on that end.
>
> help, help.  Tell me what I need to try...
>

> Please attach all output as a file in bug reports.
> MythTV Version   : v0.24-231-gc2baf1b
> MythTV Branch    : fixes/0.24
> Network Protocol : 63
> Library API      : 0.24.20101129-1
> QT Version       : 4.6.2
> Options compiled in:
>  linux debug using_alsa using_oss using_pulse using_pulseoutput
> using_backend using_bindings_perl using_bindings_python using_directfb
> using_dvb using_firewire using_frontend using_hdhomerun using_hdpvr
> using_iptv using_ivtv using_joystick_menu using_lirc using_mheg
> using_opengl_video using_opengl_vsync using_qtdbus using_qtwebkit
> using_v4l using_x11 using_xrandr using_xv using_bindings_perl
> using_bindings_python using_mythtranscode using_opengl using_vdpau
> using_ffmpeg_threads using_live using_mheg

New description:

 I don't think this is a dupe, and it is VERY repeatable.  Rebuilt
 mythbuntu box this weekend and bumped to 10.04 and mythtv 0.24.  Noticed
 that my hdhomerun recordings were wigging out.

 removed all tuners and readded.  set up recordings filling all multirec
 (even tried without multirec).

 records for a short time, then Myth stops accepting traffic, even though
 the lights on the HDHomerun stay on.  Going to configure with only one
 tuner to appease the WAF, but betting I'm going to hear about it anyway...

 Reading some threads sounds like 0.24 had a library update for HDHomerun
 and there's an acknowledged issue, but it's way old.

 When I set up the tuners, I did NOT use the IP.  I autodiscovered and
 selected each tuner.

 When I looked at the debug on the HDHomerun, my signal strenght is high
 80s to low 90s, so don't think its on that end.

 help, help.  Tell me what I need to try...


 {{{Please attach all output as a file in bug reports.
 MythTV Version   : v0.24-231-gc2baf1b
 MythTV Branch    : fixes/0.24
 Network Protocol : 63
 Library API      : 0.24.20101129-1
 QT Version       : 4.6.2}}}

--

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