From: Nick Rout <nick@rout.co.nz>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: audio with TV crd [solved]
Date: Fri, 28 Jul 2006 12:20:16 +1200 [thread overview]
Message-ID: <20060728120513.8993.NICK@rout.co.nz> (raw)
In-Reply-To: <200607260910.42909.uwix@iway.na>
On Wed, 26 Jul 2006 09:10:42 +0100
Uwe Thiem wrote:
> On 26 July 2006 00:54, Nick Rout wrote:
>
> > There is a current "scratchy" noise problem with PVR-150 drivers.
> >
> > AFTER you have started playing/recording the stream execute
> >
> > ivtvctl -qX
> >
> > where X is the audio input you are using. This fixes it for me and a
> > number of other mythtv users. Some have even set up a cron script to
> > execute that command every 10 seconds.
>
> I'll try that, weird as it is. ;-)
>
> > >
> > To get as close as possible to a DVD compatible stream use
> >
> > ivtvctl -c stream_type=X where X is the stream type you want from :
> >
> > /* Stream types */
> > #define IVTV_STREAM_PS 0
> > #define IVTV_STREAM_TS 1
> > #define IVTV_STREAM_MPEG1 2
> > #define IVTV_STREAM_PES_AV 3
> > #define IVTV_STREAM_PES_V 5
> > #define IVTV_STREAM_PES_A 7
> > #define IVTV_STREAM_DVD 10
> > #define IVTV_STREAM_VCD 11
> > #define IVTV_STREAM_SVCD 12
> > #define IVTV_STREAM_DVD_S1 13
> > #define IVTV_STREAM_DVD_S2 14
> >
> > I cannot for the life of me remember whether you want 10,13 or 14.
>
> Interesting. is there actually any comprehensive documentation about ivtv? I
> only found scratches and pieces.
>
> Uwe
Only what comes with it I think. The doc directory in the source is
worth a look.
This is also worth a look: http://ivtvdriver.org/index.php/Main_Page
The driver has been in such a rapid state of development that any
documentation would quickly be out of date. It is considerably more
mature lately.
The mythtv mailing list archives are also a very good source of
knowledge. I would say that a very big percentage of people using these
cards under linux do so in a mythtv box. The archives are very good and
appear here:
http://www.gossamer-threads.com/lists/mythtv/users/
simply running
ivtvctl | less gives you a good idea of what you can control.
--
Nick Rout <nick@rout.co.nz>
--
gentoo-user@gentoo.org mailing list
next prev parent reply other threads:[~2006-07-28 0:24 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200607211059.44959.uwix@iway.na>
2006-07-21 10:11 ` [gentoo-user] audio with TV crd Raymond Lewis Rebbeck
[not found] ` <200607211209.46822.uwix@iway.na>
2006-07-21 15:09 ` [gentoo-user] " Marco Costa
2006-07-21 16:54 ` Uwe Thiem
2006-07-24 9:00 ` Marco Costa
2006-07-21 16:40 ` James
2006-07-22 2:45 ` Nick Rout
2006-07-22 9:05 ` Uwe Thiem
2006-07-22 9:18 ` Uwe Thiem
2006-07-23 8:58 ` Nick Rout
2006-07-23 12:41 ` Uwe Thiem
[not found] ` <20060723133813.f8de080b.nick@rout.co.nz>
2006-07-23 11:19 ` Uwe Thiem
2006-07-23 21:41 ` Nick Rout
2006-07-23 23:52 ` Nick Rout
2006-07-24 10:31 ` Uwe Thiem
2006-07-24 11:30 ` Nick Rout
2006-07-24 12:43 ` Uwe Thiem
2006-07-25 0:37 ` Nick Rout
2006-07-25 10:11 ` [gentoo-user] Re: audio with TV crd [solved] Uwe Thiem
2006-07-25 23:54 ` Nick Rout
2006-07-26 8:10 ` Uwe Thiem
2006-07-28 0:20 ` Nick Rout [this message]
2006-07-22 18:07 ` [gentoo-user] Re: audio with TV crd James
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20060728120513.8993.NICK@rout.co.nz \
--to=nick@rout.co.nz \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox