Opened 9 years ago

Closed 9 years ago

#9020 closed defect (Invalid)

Simultaneous ivtv recordings fail

Reported by: bob@… Owned by:
Priority: minor Milestone: unknown
Component: MythTV - General Version: Master Head
Severity: medium Keywords:
Cc: Ticket locked: no

Description

Running trunk (26533) on Ubuntu 10.04 with master backend having an HDhomerun and two PVR-250s (slave backend not connected). If two PVR-250 recordings are scheduled for the same time, the second recording will fail every time. This was never a problem in previous versions (.23 and earlier - first time running trunk). If one of the recordings is on the HDhomerun, then there isn't a problem, only if both are on the PVR-250s. I attached a backend log using -v network,extra,socket. First recording occurs at Please let me know if you need anything else.

Attachments (1)

backend log.zip (105.4 KB) - added by bob@… 9 years ago.
backend log

Download all attachments as: .zip

Change History (4)

Changed 9 years ago by bob@…

Attachment: backend log.zip added

backend log

comment:1 Changed 9 years ago by Raymond Wagner

Status: newinfoneeded_new

Just to make sure, could you log into MySQL and paste the output of:

select cardid,videodevice,hostname from capturecard where cardtype='MPEG';

comment:2 Changed 9 years ago by anonymous

I have the following from the requested select:

+--------+-------------+--------------+ | cardid | videodevice | hostname | +--------+-------------+--------------+ | 5 | /dev/video0 | mythbox | | 6 | /dev/video0 | mythbasement | | 7 | /dev/video0 | mythbox | +--------+-------------+--------------+ 3 rows in set (0.00 sec)

cardid 6 is a PVR-150 in the slave backend which was not connected at the time of the issue due to a problem with the HDhomerun recordings with the slave connected (provided under ticket 7608).

comment:3 Changed 9 years ago by Raymond Wagner

Resolution: Invalid
Status: infoneeded_newclosed

You are using the same video device node for both cards. MythTV is failing to record because you're trying to use the same tuner twice.

Note: See TracTickets for help on using tickets.