Opened 10 years ago

Closed 10 years ago

#7786 closed defect (invalid)

MythTV 0.22 picks wrong PVR-150 audio input

Reported by: Guy Delamarter <gdlex001@…> Owned by: Isaac Richards
Priority: major Milestone: unknown
Component: MythTV - General Version: 0.22
Severity: high Keywords:
Cc: Ticket locked: no

Description

PVR-150 is set to input (external) composite input, and for the video this is clearly set correctly in MythTV: live TV shows video. But there is no sound.

v4l2-ctl lists three audio inputs for PVR-150. 0 is cable tuner (not used in my setup), 1 is line in 1 (Composite), and 2 is line in 2 (internal?). The selected input after MythTV sets it is 2. Using v4l2-ctl to manually change card audio to input 1 while live TV is playing recovers the sound to go with video! At this point, exiting and turning live TV on again to the PVR-150 again provides the opportunity for MythTV backend to reset card audio to input 2 which as before, provides for silent video.

There doesn't appear to be any way to influence this behavior in configuration (i.e. mythtvsetup). Only selection available is to use Composite 1 or Composite 2 (selected composite 1) and that is clearly correct for video.

From v4l2-ctl it appears that the video input for Composite 1 has index 2. Perhaps the code error is made under the (incorrect) assumption that the audio index should be set the same as the video index. Since there are more video inputs than audio inputs, the correspondence cannot follow in that way. Only a guess...

This used to work fine under mythtv 0.21. Upgraded to using latest 0.22 from rpmfusion repository.

Note that under this defect, MythTV conspires to make unattended recording of TV with audio very difficult.

Change History (3)

comment:1 Changed 10 years ago by stuartm

Milestone: 0.220.23

comment:2 Changed 10 years ago by robertm

Milestone: 0.23unknown

comment:3 Changed 10 years ago by sphery

Resolution: invalid
Status: newclosed

This looks like you upgraded your ivtv drivers and left the MythTV configuration you created with the old drivers in place. If you upgrade your capture card drivers to a different driver version, you sometimes need to delete and re-create your capture cards, then re-connect inputs. I recommend using "Delete all capture cards" (and not "Delete all capture cards on host") to do so.

Note: See TracTickets for help on using tickets.