--- kevin thayer <[EMAIL PROTECTED]> wrote:
> the 'decode to memory' function is not possible.
> This
> was discussed at length near the start of
> development,
> but we got word from someone who had helped design
> the
> chip that this was not possible
Oh, well.
Thanks for the speedy response, t
Do you have a windows box you could try the card in? It seems to me
like you're not getting a signal, so testing to see if it's a hardware
problem probably makes sense.
On 7/8/05, Andrew <[EMAIL PROTECTED]> wrote:
> when i do
>
> ivtv-radio -f 93.1 -j -g
>
> "/dev/video24" has an obnoxious hum,
Two things: 1. are you decoding an mpeg2 with the card before you try
and use Xv? 2. are you putting the Option "XVideo" "On" line in the
device section of your xorg.conf?
If those aren't your problems, post your log file after trying to play
something and the output of xvinfo maybe.
On 7/10/05,
I don't think the mpeg2 the encoder produces can get directly burned
to dvd. The audio is in the wrong format I believe... I'd assume that
whatever it's encoding would have to be in the exact raw format the
card gets from the tuner, so that's not very useful anyways.
On 7/10/05, Nick Rout <[EMAIL
Silly question perhaps, but can the hardware mpeg-2 encoder in the
Hauppauge PVR cards (specifically PVR-150) be used to help encode a
video file to mpeg2? i have a whole lot of stuff I want to convert
tompeg2 and then put onto dvd,
Or is it restricted to encoding what comes out of the
tuner/compo
While ivtv 0.3.6y seems to work fine for me, if I use
this ivtv_drv for X with it, I get lots of horizontal
dark lines over the video, which are slightly tilted
(almost like the scan lines during vertical sync in
old tubes). This is both from myth and xine.
NTSC land here.
Relevant portion of me
Hi everyone,
I've got a fresh install of FC4 with an M179 to try to build a MythTV backend.
I've followed the Myth(TV)ology setup as much as I could (kudos to Jarod for
this site), but it still references FC3. The only major deviations I've taken
from this guide are using yum instead of apt for
the 'decode to memory' function is not possible. This
was discussed at length near the start of development,
but we got word from someone who had helped design the
chip that this was not possible
-tmk
--- "Scott A. Conway" <[EMAIL PROTECTED]> wrote:
> Hi,
>
> I was just wondering if there is a
This patch doesn't work for me. With just 0.3.6y and either the June
12th X driver or the one you just sent out, things are generally fine
except for scaling problems (black bars at the bottom and / or right
of the screen) with some files.
With this patch, the frames sometimes seem to alternately
I've finally made the plunge to the new YUV ivtv and X driver (0.3.6y
and latest X driver). I'm having some difficulties getting everything
to work, and can't seem to find similar situations in the archives.
So hopefully these aren't too obvious.
NTSC, Athlon, PVR-350. MythTV 0.18, mplayer
Hi,
I was just wondering if there is a way to display
directly on the computer display the output from
/dev/video on a PVR350.
By that, I mean is there a way to use the integral
hardware decoder to display to the computer monitor
instead of being strictly restricted to feeding to a
TV hooked up to
I've been running 0.3.2h with my pvr-150 NTSC retail
edition for some months now with pretty good success.
I'm running mythtv 0.17 on Debian.
Unfortunately, sometimes the audio has an annoying
high-pitched whine to it. It can last for an hour or two
on a given channel, and happens on various chann
Coming through loud and clear Nuno...
as was your earlier posting, attached.:
From: "nuno alexandre" <[EMAIL PROTECTED]>
To:
Subject: Re: [ivtv-devel] Problems with 350
Date: Sunday, July 10, 2005 2:16 AM
On Sat, 2005-07-09 at 22:13 +0200, Mischa Meier wrote:
hi,
i have read many different
Henk,
On Sun, Jul 10, 2005 at 04:47:36PM +0200, Michel vd Laan wrote:
seem to make it work. I have not found consistency here (Henk seems to
have
sound without saa7127 channels with the very same pvr500 in pal-europe).
I don't know if I have the very same type of unit, since you use tuner
Hi,
just some warnings im getting when building the driver on a64 platform.
CC [M] /home/ikaro/ivtv-0.3.6y/driver/cx25840-audio.o
CC [M] /home/ikaro/ivtv-0.3.6y/driver/cx25840-firmware.o
CC [M] /home/ikaro/ivtv-0.3.6y/driver/ivtv-osd.o
/home/ikaro/ivtv-0.3.6y/driver/ivtv-osd.c: In function `i
John, could you attach the source so I can build a 64bit version of it to test
the new positioning code?
Thanks,
Rutger
On Monday 11 July 2005 00:13, John Harvey wrote:
> Nope it was me.
> Sorry
>
> > -Original Message-
> > From: [EMAIL PROTECTED] [mailto:ivtv-devel-
> > [EMAIL PROTECTED]
Nope it was me.
Sorry
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:ivtv-devel-
> [EMAIL PROTECTED] On Behalf Of Drew Bernat
> Sent: 10 July 2005 23:09
> To: ivtv-devel@lists.sourceforge.net
> Subject: Re: [ivtv-devel] [PATCH]New Test x driver (0.10.4)
>
> I didn't get an attach
I didn't get an attached file. Was it just me?
Drew
On Jul 10, 2005, at 4:07 PM, John Harvey wrote:
Attached is the latest binary release of the X driver. It is
numbered 0.10.4
and I'm still treating it as a test release.
It require 0.3.6y of ivtv since it users a colorkey to enable the
Xv
The one that's included in the utils directory of the ivtv
distributions (XFree86-4.3-incr-DMA-08.tgz). I've simply been
installing the ivtvdev_drv.o from the utils directory.
Thanks,
-Dave
On 7/10/05, John Harvey <[EMAIL PROTECTED]> wrote:
> Which Incremental DMA patch?
> Is this the very old
Attached is the latest binary release of the X driver. It is numbered 0.10.4
and I'm still treating it as a test release.
It require 0.3.6y of ivtv since it users a colorkey to enable the Xv code to
display instead of setting the Alpha. This means
1) xine/mplayer windows appear in the correct plac
Oh and we have been looking at some
interesting issues with interrupts so there may well be some fixes coming for
the tearing problems people have seen.
This patch is almost entirely Ian’s
work again.
John
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Jo
Which Incremental DMA patch?
Is this the very old one needed to get X running at all? If so then it is no
longer relevant.
John
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:ivtv-devel-
> [EMAIL PROTECTED] On Behalf Of David Smith
> Sent: 10 July 2005 08:00
> To: ivtv-development
With this patch the YUV picture should now be scaled
& positioned correctly as requested by the caller (ie Xv).
There is an updated Xv driver coming shortly that
adds the correct positioning information.
John
ivtv-0.3.6y.diffs.bz2
Description: Binary data
On Sun, Jul 10, 2005 at 04:47:36PM +0200, Michel vd Laan wrote:
> seem to make it work. I have not found consistency here (Henk seems to have
> sound without saa7127 channels with the very same pvr500 in pal-europe).
I don't know if I have the very same type of unit, since you use tuner
51 and I
Do I get "ivtv: i2c client addr: 0x44 not found for command" errors?
Well, now I do.
In my continued quest to get this working, I'm always surfing trying to find
answers. And now, I seem to have screwed it up such that NEITHER tuner works.
They both yield a 0 byte file when I 'cat /dev/vide
Crap, I just realized that I was putting out an ERROR severity log
message when reporting that I was going to enable mastering. This patch
superscedes and usese ivtv debug level.
Bryan Mayland wrote:
patch
Index: driver/ivtv-driver.c
=
Don Brown wrote:
Also, "cx25840ctl -l -d /dev/video2" yields
Opening /dev/video2
ioctl: IVTV_IOC_G_CX25840_SETTING failed.
If you dump your dmesg, do you see a lot of
ivtv: i2c client addr: 0x44 not found for command
error messages?
-
Morten,
I believe Sigurd has both a 350 and a 500, hence the need for lines
dis/en-abling of cx25480/saa7127.
I have a 150 and a 500 (both PAL, one tuner type 38, the other tuner
types 56) but only have sound on the 150 - the two tuners on the 500 are
both mute...-:(
Meanwhile searching th
Screwing around with lirc, I somehow disabled busmastering on my ivtv
cards. Of course, once this happens, ivtv will fail to load since
busmastering is required. This simple patch attempts to enable bus
mastering on the device if it isn't on when the module loads.
I also added a line to pci_
I was wondering if someone could tell me the purpose of the
incremental DMA patch made to X Windows? What kind of problems would
I see if I didn't have this patch applied (I do not have it applied).
I'm using a PVR-350. I've been bouncing around different versions of
IVTV and for the most part,
30 matches
Mail list logo
