[mythtv-users] Query wrt using a pvr150/ivtv card in mythtv - tuner broken?

[Don]

>On Sun, Aug 11, 2013 at 3:28 PM, Don <myheadblewoff at gmail.com> wrote:
>> On Sun, Aug 11, 2013 at 12:14 PM, Stephen Worthington
>> <stephen_agent at jsw.gen.nz> wrote:
>>
//snip//
>>
>> When setting up the PVR-150 to use the S-Video or composite inputs,
>> you need to go into mythtv-setup and go to Input Connections.  You
>> will currently have an input connection set up on:
>>
>>   [MPEG : /dev/video0] (Tuner)
>>
>> and you need to change the connection to be on:
>>
>>   [MPEG : /dev/video0] (S-Video)
>>
>> or
>>
>>   [MPEG : /dev/video0] (Composite)
>>
>> Just copy the setup you currently have for (Tuner) and I think it
>> should work.
>
> Yep, that's how the picture looked in my mind for setup ; when I get a
> spare moment, I'll give it a whirl and post back results. Thanks for all
> your advice/help =)
>

Kudos Stephen for all your help/guidance here, particularly the bash
snippets wrt selecting the correct audio inputs (why can't I find a manpage
for v4l2-ctl? ;) - I tested both the S-Video & Composite in routes, and
with no surprises both easily beat the RF route wrt picture quality, with
S-Video being the best ; audio capture is good with no sundry noise...

...in the other thread I mentioned, I think Raymond also said he thought
that using the mthtv-setup GUI to do this sort of shizzle was 'clumsy' ;
I'd have to agree, if for no other reason than these types of inputs really
shouldn't be associated with a tuner, channels, or anything else like
this...ie; when one goes into 'Input connections' -> '[MPEG : /dev/video1 ]
 (S-Video) ->' , the fields 'Preset tuner to channel:', 'Scan for channels',
'Fetch channels from listing source' and 'Starting channel' really do not
apply here (same for the Composite input) ; perhaps in a 'perfect' world,
selecting this type of input could throw you to a slightly different page,
where these moot fields might for example be a place to enter custom
params or scripts to be executed for that input to be setup correctly, blabla...
not that I'm complaining, but I too think it could be less clumsy...

 Again, thanks for the help, now I just have to tame the onboard alc887
soundchip, and the BE will be good to go, better than ever =)

Cheers!