I recently added a PVR-150MCE (NTSC) card to my Mythtv system which
already has a working PVR-250 (NTSC). After spending virtually the
entire weekend on this, I'm finding that I simply cannot get audio
working properly on this card. Depending on how I set the wm8775
mixer parameter, I can either
This fixes VBI to use DMA instead of PIO mode, should be alot better on
system load when using raw vbi, or normal, the new DMA improvements I
added recently allowed this to be possible now.
http://www.ivtv.tv/releases/ivtv-0.3/
Thanks,
Chris
--
---
Chris Kennedy / [EMAIL PROTECTED]
Engineer
On 4/17/05, Tom McKearney <[EMAIL PROTECTED]> wrote:
> I get no video out of /dev/video* with my PVR-500.
>
> I've tried the tuner and the s-video connection... I just can't get
> any video (empty mpeg file when catting the device)
>
> I am running SUSE 9.1 with kernel 2.5.6
> I have 2 pcHDTV 300
My drivers are in "extra", not "ivtv". I compiled from source.
I did have to modify the source to make it compile on SUSE
(module_param's new style didn't work for some reason).
I don't have a msp34000-ivtv, so I removed that alias
T
On 4/17/05, William Powers <[EMAIL PROTECTED]> wrote:
> Just
With this version I get no sound on S-Video. 0.3.2y worked great.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Chris Kennedy
Sent: Saturday, April 16, 2005 12:03 PM
To: ivtv-devel@lists.sourceforge.net
Subject: [ivtv-devel] #0.3.2z pvr150/500 audio/t
Just some random guesses. If you didn't install IVTV via ATRPMS, which
doesn't seem likely on SUSE, then it seems possible you may not actually
have a module named msp3400-ivtv.ko. The -ivtv extension is just a way
to eliminate problems due to duplicate modules. Assuming you don't have
an ms
I get no video out of /dev/video* with my PVR-500.
I've tried the tuner and the s-video connection... I just can't get
any video (empty mpeg file when catting the device)
I am running SUSE 9.1 with kernel 2.5.6
I have 2 pcHDTV 3000 cards installed.
I have one PVR-500 MCE (D492) installed.
I am
I have this on my VIA 32bit system, second X screen does this, seems to be
hitting the FB constantly with odd data, flashes pink colors till it crashes,
seems like the same problem. I figured it was my Video cards X driver and
ivtv's X driver not getting along, but didn't have time to revisit yet.
If you run
lspci -v
can you see any/many other devices sharing the same IRQ as the PVR-350
card? At one point my system was automatically disabling the IRQ due
to a conflict resulting in my 350 being unusable for recordings until
I either rebooted and it didn't disable the card, or looked into th
On Sunday 17 April 2005 15:13, Hans Verkuil wrote:
> Does anyone have any experience with this?
>
> I'm trying to setup a second X display using the ivtvdev driver. I've tried
> both ivtv-0.2.0-rc3i and ivtv-0.3.2w. I'm using XFree86-4.3-incr-DMA-08.tgz
> as the ivtvdev driver for X.org 6.8.2. I ha
On 4/17/05, Peter Martens <[EMAIL PROTECTED]> wrote:
> Are you using MythTV, and if so, is your card working with Myth? Is
> there any reason not to the modules in modprobe.conf in Fedora Core 3?
> I just went from Gentoo to Fedora Core 3 and having a very difficult
> time to get my PVR150 (MCE) to
Hi,
Hans Verkuil wrote:
> Does anyone have any experience with this?
With this error, yes. Not with these components.
Thus I suppose this is neither AMD64 nor Xorg specific.
I mentioned something similar first in a message on Nov. 4, 04, relating
it to the different framebuffers (which was probab
Dan,
try to cat /dev/video0 > temp.mpg, then open with any editing software to see recorded resolution.
Well, even mplayer could tell this. On 4/17/05, Dan Meehl <[EMAIL PROTECTED]> wrote:
It doesnt seem to work on my 150 either. My image doesnt seem to becropped but you cant really see what it i
> I use the following for a PVR150 (PAL nonMCE) and a PVR350 (PAL) in the
> Netherlands on Fedora Core 3:
> (the PVR150 is first in line, tuner 38, and the PVR350 second, tuner 5)
>
> in /etc/modprobe.conf:
>
> options saa7127 i2c_enable=-1,1
> options cx25840 i2c_enable=1,-1
> options ivtv ivtv_
Bummer. Another user, who posted to this mailing list some time back,
was able to get his card working by tweaking his PCI settings in his
BIOS setup. You may want to try doing that before replacing your
motherboard.
robert
Ian Cartwright wrote:
Robert,
Unfortunately for me, my motherboard is
On zo, 2005-04-17 at 07:03 -0400, Gregory J. Haase wrote:
> I had a similar problem, and it turned out to be that the device was
> specified incorrectly in /etc/conf.d/lircd file.
>
> I had originally put /dev/lircd as the device, but it turned out that on
> my particular installation, the device
It doesnt seem to work on my 150 either. My image doesnt seem to be
cropped but you cant really see what it is either. It is hard to
explain what exactly it does. This is also in myth.
-Dan
On 4/17/05, William Powers <[EMAIL PROTECTED]> wrote:
> Sergey,
>
> Thanks for the comment.
>
> FWIW, I c
Sergey,
Thanks for the comment.
FWIW, I can tell you that horizontal scaling does not work on my 500
(either side) using either version 'y' or 'z'. Not only do I get a
cropped image, but I get vertical chroma artifacts as well. This using
Myth for the recording - I haven't played with the driv
Looks like your MythTV setting was 480x480 (default) but horizontal scaling
starts to work only in "y" version. So, give a try to "w" version.On 4/17/05, Mike Lee <
[EMAIL PROTECTED]> wrote:Hello all, I am having a problem with my pvr and thought I would start here
first to solve the problem.
Hi William,
Actually, horizontal scaling works with latest derivers, but only horizontal.
so you can use resolutions like 720x480, 480x480,352x480. No vertical scaling
yet. Chris can tell you more, probably, as I can see, in latest driver he just
commented out setting of vertical scaling register.
I'm running kernel 2.6.5-7.111.30-smp and trying to compile ivtv and I
get this error repeated in lots of places:
/home/tom/tmp/ivtv-0.3.2z/driver/msp3400.c:131: error: parse error before "int"
/home/tom/tmp/ivtv-0.3.2z/driver/msp3400.c:131: warning: type defaults
to `int' in declaration of `modul
Op za 16-04-2005, om 21:03 schreef Chris Kennedy:
> http://www.ivtv.tv/releases/ivtv-0.3/ivtv-0.3.2z.tgz
I forgot to mention: after installing modules, the depmod command has to
be manualy excecuted.
2.6.11.7
--
Groetjes Japie
---
SF email i
Hello all,
I am having a problem with my pvr and thought I would start here
first to solve the problem. First, I'll give some background. I have
an Asus Pundit-R with a Hauppauge pvr150 (NTSC-M). Running MythTV
0.17.
I downloaded the latest .3 ivtv drivers, compiled and installed,
mad
Robert,
Unfortunately for me, my motherboard is rather old. The latest BIOS
update for it is from April 2003. Looks like it may be time for a new
motherboard for my Myth box.
-- Ian
On Sat, 2005-04-16 at 20:17 -0500, Robert Del Huerto wrote:
> I was getting a lot of artifacts on the captured mpe
Op za 16-04-2005, om 21:03 schreef Chris Kennedy:
> This adds the recent patches for the pvr150/500 audio/tuner fixes
Excelent!
Works great...
--
Groetjes Japie
---
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews
Ok, I'm probably completely full of it, so just do what my wife does and
forgive me in advance.
:-)
Back in March, there was in interesting discussion in the list about
scaling on the 150/500's between Sergey, Tyler, and Chris about scaling,
referenced here:
http://www.gossamer-threads.com/lis
On 4/17/05, Jasper van der Neut - Stulen <[EMAIL PROTECTED]> wrote:
> On Sat, Apr 16, 2005 at 06:07:59PM -0400, Tyler Trafford wrote:
> > Jasper van der Neut - Stulen <[EMAIL PROTECTED]> wrote:
> >
> > > This patch fixes audio format detection for my
> > > PVR150 MCE PAL, which was broken since 0.3
AFAIK, the card initializes ok. Tuners are detected ok. It's just when
I try to capture something on the 150, it just "hangs" (dd
if=/dev/video1 of=vid1.mpg bs=64k count=100). The capture file just
remains 0 bytes. The 350 on the other hand just grabs fine.
With my options (which don't seem to diff
Does anyone have any experience with this?
I'm trying to setup a second X display using the ivtvdev driver. I've tried
both ivtv-0.2.0-rc3i and ivtv-0.3.2w. I'm using XFree86-4.3-incr-DMA-08.tgz
as the ivtvdev driver for X.org 6.8.2. I have no problem loading ivtv and
ivtv-fb. I can run ivtvfbc
Nick,
I use the following for a PVR150 (PAL nonMCE) and a PVR350 (PAL) in the
Netherlands on Fedora Core 3:
(the PVR150 is first in line, tuner 38, and the PVR350 second, tuner 5)
in /etc/modprobe.conf:
options saa7127 i2c_enable=-1,1
options cx25840 i2c_enable=1,-1
options ivtv ivtv_std=2
To s
Just upgraded from 0.3.2p -> 0.3.2q and capturing stopped working on
the 150. I've enable debugging (level 63).
In attach the logs for loading the driver and a (failed) capture.
Anyone else running a 350 in combination with a 150MCE. What are the
recommended module-options? The ones that work for p
sometimes I get such error messages in my syslog and my backend stopps
recording:
ivtv: ENC IRQ OVERFLOW: #390 Stealing a Buffer, 1024 currently allocated
I have a quire old ivtv:
ivtv-0.2.0-rc3i
but I use it a long time and it was stable since last year.
can anyone sayme what triggers t
I had a similar problem, and it turned out to be that the device was
specified incorrectly in /etc/conf.d/lircd file.
I had originally put /dev/lircd as the device, but it turned out that on
my particular installation, the device was /dev/lirc/0. I also seen
posts where they claim it may be /dev/
I've tried my PVR150 again and with this patch (the new 0.3.2 (z)
release) it works just great. Great image quality and SECAM sound. Tuner
get autodetected and all.
But (there always has to be one...) I tried using the remote but
couldn't get it to work. I've downloaded and compiled one of the lat
> I may be wrong, however, the 150 doesn't have a saa7127, and the 350
> doesn't have a cx25340. Therefore, you only need one parameter for each.
>
> (I only have 2 150s, so am not sure on this)
You're right in that assumption. That is the whole issue. I have two
parameters for both the cx2584
Louie Ilievski wrote:
The 350 is detected first, and then the 150, so those module options
look right. However, when modprobing ivtv, it seems that only the
first number for the i2c_enable parameter is honored for saa7127 and
cx25840. The 350 initializes properly, but the 150 does not. The
cx258
On Sat, Apr 16, 2005 at 06:07:59PM -0400, Tyler Trafford wrote:
> Jasper van der Neut - Stulen <[EMAIL PROTECTED]> wrote:
>
> > This patch fixes audio format detection for my
> > PVR150 MCE PAL, which was broken since 0.3.2s. I can only
> > test the tuner input, so maybe other input need something
37 matches
Mail list logo
