Date: Fri, 29 May 2009 21:37:58 +0200 (CEST) From: Juergen Lock <nox@jelal.kn-bremen.de> To: jason.harmening@gmail.com Cc: freebsd-multimedia@freebsd.org Subject: Re: [...] a (hacky) way to grab composite/svideo in [...] Message-ID: <200905291937.n4TJbwGd009522@triton.kn-bremen.de> In-Reply-To: <2d1264630905291103s5b1219f5u4f6b8df9ef99c5dc@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
In article <2d1264630905291103s5b1219f5u4f6b8df9ef99c5dc@mail.gmail.com> you write: >>> > 2) allows selecting non-tuner inputs by passing `magic' channel names >>> > via -c: "input_mux2" (composite in on my card), "input_mux3" (most likely >>> > s-video in here), and "input_mux4" (I don't know if that's used on my >>> > card, but it might be on others.) >> >> Jason, any thoughts on access to the composite & s-video inputs? >> > >Well, I was planning on adding an input-mux option to be passed by the >-o option, but I kind of like Juergen's idea of using channel >definitions in the XML file instead. We can "de-hackify" his >implementation a little, and then users will be able to define >easy-to-remember aliases for their inputs. I mainly did it that way to be able to still use the video signal definitions from the xml since that usually won't change (like, pal-b in my case...) Juergen
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200905291937.n4TJbwGd009522>