I might have a similar problem. I have a 150, and sometimes it is
autodetected as a 250. Also, sometimes the picture quality is good even
though it is seen as a 250, and sometimes picture quality is bad even when
seen as a 150. Usually I can get good picture by removing and reloading
the modules.
Might that be a PAL vs. NTSC issue? Xvinfo shows the PAL-Resolution as max.
xv size while ivtv-fb et al are correct about their NTSC assumptions.
Just thinking.
Martin
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Andrew Kohlsmith
Sent:
That xvideo size thing looks like a bug but i don't
think it's causing this. I'll take a look over the
next couple of days.
Andrew
I noticed you are running 3.4p driver.
This is almost definately not going to work for NTSC.
I would suggest moving to a recent (probably latest
3.6u?) and take
On 6/29/05, Sigurd Nes [EMAIL PROTECTED] wrote:
I lost the audio on the both 500-tuners when moving to ivtv-0.3.6v.
ivtv-0.3.6n,ivtv-0.3.6p and ivtv-0.3.6u works fine.
1 x pvr350
1 x pvr500mce
PAL
Kernel 2.6.12
Regards
Sigurd
Ant Daniel wrote:
I've just managed to get the
On Thursday 30 June 2005 04:30, John Harvey wrote:
I noticed you are running 3.4p driver.
This is almost definately not going to work for NTSC.
I would suggest moving to a recent (probably latest
3.6u?) and take the latest xdriver from there as well
and see how you get on with that.
Tried
On 6/30/05, Ant Daniel [EMAIL PROTECTED] wrote:
On 6/29/05, Sigurd Nes [EMAIL PROTECTED] wrote:
I lost the audio on the both 500-tuners when moving to ivtv-0.3.6v.
ivtv-0.3.6n,ivtv-0.3.6p and ivtv-0.3.6u works fine.
1 x pvr350
1 x pvr500mce
PAL
Kernel 2.6.12
Regards
Sigurd
Haven't checked /proc/bus/pci/01, but will do that when I get the
time.
However, one difference I have seen in /var/log/messages between good
picture and bad picture is that when bad
kernel: ivtv: Unreasonably low latency timer, setting to 64 (was 32)
is displayed in /var/log/messages.
Keith C wrote:
Haven't checked /proc/bus/pci/01, but will do that when I get the time.
However, one difference I have seen in /var/log/messages between good
picture and bad picture is that when bad
kernel: ivtv: Unreasonably low latency timer, setting to 64 (was 32)
is displayed in
thanks for doing this. i'll try and find some time to
play with the windowing soon. Let me know how your own
testing goes.
IIRC, from others that have tried this (quite a while
ago) the scaling works OK, but doesn't want to scale
to less than half (i guess technically 1/4) of the
original video
I'm using the ivtvdev_drv with YUV on my PVR350. I'm very happy that John
has developed it, but the quality is a little bit blocked.
Is the because mplayer is scaling badly or a problem in the YUV driver.
--
gr.
patrick
---
SF.Net email
Hello,
This just started on my system. I'm running
ivtv-0.3.6u. I get these and after about a day my
system becomes unresponsive, I can ping it but I'm
unable to ssh in or watch any recordings. After doing
a hard reboot these VBI errors are the last things
written to the log.
Any help would
On 6/30/05, Patrick de Brabander [mythtv] [EMAIL PROTECTED] wrote:
I'm using the ivtvdev_drv with YUV on my PVR350. I'm very happy that John
has developed it, but the quality is a little bit blocked.
Is the because mplayer is scaling badly or a problem in the YUV driver.
I've got the same
Ian has been working on things so there are more fixes to come. I'll take a
look at things from him tomorrow.
I'm also starting to look at using this in myth so I'm sure we can get to
the bottom of what is happening.
Some players make some very strange decisions about the requested width.
Well, I spoke too soon. I'm getting distorted recordings with 0.3.6u.
The funny thing is, they are not too loud any more, but they are
distorted the same as they would be if the peaks were being clipped
off. Image you tried to record something at too high a volume so that
the input was
Hello,
To see if the radio part of my pvr150 had a problem, I have tried a
pvr-500 in the same machine today.
Identification went great (2 pvr-150's) but after setting a frequency
and doing cat /dev/video0 test.mpg, the computer goes to a reboot after
about 4 seconds of capturing.
If I don't
What is YUV output? I can't really find any references to it in the
Wiki/etc.
Can someone fill me in on this? I HAVE seen where ivtv can supposedly
output NV12-formatted raw video, but I'm drawing a blank on this YUV thing.
Is it the actual, true raw data? Or is it the mpeg2 video stream
On Thursday 30 Jun 2005 22:30, John Harvey wrote:
snip
I'll see if I can work out why myth wants to scale to something odd like
that. I wouldn't expect it to request anything bigger than the screen size
so something strange is going on.
Is there more than one display in use ? I can't
I actually just noticed this happening yesterday to me, although
things were wroking fine when it happened except I was getting
occasional single green screen frames. I assumed that was cause by
me poking around at stuff with ivtvctl and ivtvfbctl and it losing a
frame while the card was changing
Hi-
I've got a nforce2 based computer with a pvr-350 and pvr-500mce in it
running FC3 and mythtv 0.18.1. Using tv-out of 350 and ivtv 0.3.6r
All seems stable except when I try to watch live tv after the machine
has been running a while. Might be after I've recorded on one or both
of the
That happened to me too when I raised the valuse from whatever it
defaulted to. Try lowering the levels a bit and it should go away.
On 6/30/05, William Powers [EMAIL PROTECTED] wrote:
Well, I spoke too soon. I'm getting distorted recordings with 0.3.6u.
The funny thing is, they are not too
On Thursday 30 June 2005 09:19, Andrew Kohlsmith wrote:
Tried 3.6u and it seemed to work (I was remote so I couldn't see the TV) --
thank you for your help, I'd tried several versions earlier to this and got
always the same result.
Well it *does* work (very low CPU use) but the display seems
On Thursday 30 June 2005 21:46, Andrew Kohlsmith wrote:
I'll poke around the list here and see if anything sounds like this. :-)
I'm 100% working now.
I was using ivtv_drv.o-09 instead of ivtv_drv_o. (What is the difference
between them anyway?)
-A.
I could try, but I'm afraid that defeats the purpose: My MythTV
recording volume setting is already set to the optimum value for
recording with a PVR-250. Backing off on the volume substantially in
order to accommodate my PVR-500 idiosyncracies puts me right back where
I was before: I can
I have a PVR-150 that is behaveing strangely. Useing the newest 3.6w
drivers (I've also tried the newest stable drivers) the tuner modulesis
detected as a TCL_2002N (tuner 50) but when trying to use it I am only
able to recieve channel 5 6 and those only in black and white the
rest of the
Yeah, I meant that you could lower all three and raise the mythtv
volume. It's not great but it should solve your problem?
On 6/30/05, William Powers [EMAIL PROTECTED] wrote:
I could try, but I'm afraid that defeats the purpose: My MythTV
recording volume setting is already set to the optimum
25 matches
Mail list logo
