[mythtv-users] missing recordings from 2 DVB recorders (HVR-950Qs)

[Devin Heitmueller]

On Fri, Feb 5, 2010 at 5:29 PM, Andrew Cagney <andrew.cagney at gmail.com> wrote:
>> Do you have the 950q devices also setup for analog capture (even if
>> you are not using it)?
>
> Right now they are listed in the devices section, but nothing more.
> During startup mythtv complains vis:
>
> 2010-02-05 16:11:56.602 Channel(/dev/video-HVR-950Q-F04BEC59): Device
> name 'Hauppauge HVR950Q' driver 'au0828'.
> 2010-02-05 16:11:56.605 MSqlQuery::exec() "SELECT cardinputid,
> inputname,   startchan,        tunechan,    externalcommand,
> sourceid FROM cardinput WHERE cardid = '6'"
> 2010-02-05 16:11:56.605 ChannelBase(6) Error: InitializeInputs():
>                        Could not get inputs for the capturecard.
>                        Perhaps you have forgotten to bind video
>                        sources to your card's inputs?

Try removing them from the capture devices list in mythtv-setup.  You
don't want to have any v4l entries associated with the 950Q devices.

> and marks them as broken.  I'm pretty sure I've also encountered the
> problem when those analog devices weren't even listed.
>
>> Do you have both 950q devices plugged into the same USB bus?
>
> Hmm, does this:
>
> tv at tv-desktop:~$ udevadm info -q path -n /dev/dvb/adapterF04BEC59/frontend0
> /devices/pci0000:00/0000:00:04.1/usb1/1-2/dvb/dvb0.frontend0
> tv at tv-desktop:~$ udevadm info -q path -n /dev/dvb/adapterF0677017/frontend0
> /devices/pci0000:00/0000:00:04.1/usb1/1-4/dvb/dvb1.frontend0
>
> answer your question  (yes I've been playing with udev names)? I guess
> they are on the same bus, aong with the PVR-USB2 and the disk being
> used to store recordings.

Yeah, looks like they are on the same bus.

>>
>> In the scenario you described, do both recordings fail, or just one of them?
>
> Based on today's results, the second recording to start is the one
> that fails.  But not always.

I'm wondering at this point whether perhaps the problem has to do with
the bus allocation - perhaps the driver is selecting an alternate
which consumes too much bandwidth, and therefore both devices cannot
capture at the same time on the same USB bus segment.

I'll have to look at the code and see which alternate it's picking.

Devin

-- 
Devin J. Heitmueller - Kernel Labs
http://www.kernellabs.com