Peter Karlsson wrote:
On Sun, 16 Jan 2005, Michel Verbraak wrote:
Peter,
I have the same card.
Mine is working allright.
I use the following startup script:
#!/bin/bash
echo Loading IVTV drivers.
echo Loading tve
Here is my debug information, can you help? I have been trying to get
this Mythtv box running for a few days. Thanks in advance!!!
vtv: START INIT IVTV
ivtv: version 0.1.10 (0.1.10-48.4_pre2_ck100zz.rhfc2.at) loading
ivtv: Linux version: 2.6.10-1.9_FC2 6
> IMHO, your time is much better spent debugging a known-working defintion
> for your tuner. If you really want to diagnose the effect of the bad
> tuner definition on radio tuning, feel free to do so, but there's a good
> definition that's easily available, so if you instead just want radio, I
> h
well, we still haven't gotten a real good answer as to
why yuv decoding doesn't tell us where to send the
data.
that's all that's really buggin' me
-tmk
--- Axel Thimm <[EMAIL PROTECTED]> wrote:
> I suggest to collect questions on current ivtv
> issues that Hauppauge
> engineering and developme
I suggest to collect questions on current ivtv issues that Hauppauge
engineering and development can help solving. Hauppauge is open to the
Linux community, nevertheless the process to acquire and clear out
information is slow. It pays off to do so for a set of questions IMHO,
at least that was the
Update:
It turns out that I use the tuner.ko from the 2.6.10 kernel. (didn't
rename the kernel provided tuner.ko)
In tuner.c this tuner is called 'Philips PAL/SECAM_D (FM 1256 I-H3)' but
the label on my card sais 'TAPE-S001D' (as does tveeprom)
I'm confused: the LG tuner seems to work quite well
First, I really apologize for sending five times the same message but my
mail soft said it wasn't sent, really sorry.
Concerning the interrupts, I did a lot of tries today with settings in
the bios relating the interrupts. I tried first disabling the interrupts
of all that isn't necssary for iv
Hi,
I have a simple question for people who have written code for ivtv-fb.
Filling the framebuffer using ioctl IVTVFB_IOCTL_BLT_FILL (720 * 576
pixels) takes around 30 ms here.
Is this normal performance?
Thanks in advance,
Thomas
--
9876543210 Magic tab-o-meter. http://www.
Hi,
I posted this error a while ago, but no-one spotted anything obvious.
I'm reposting to see if it anyone can throw any light on it.
I've got a PVR-350 + PVR-250 that work most of the time with MythTv 0.16,
Occasionally I get problems with sound. At any point during a recording
I'll suddenly get
You're right, there are a few posts reporting that tv-out doesn't work
on this model but when I bought this card I also found posts reporting
that this card didn't work at all so right now captures works like a
charm, X works like a charm, and ivtv-fb loads up without any problems
why not the decod
I guess the other thing is to make sure you aren't sharing the interrupt
with something else.
John
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:ivtv-devel-
> [EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED]
> Sent: 17 January 2005 20:02
> To: ivtv-devel@lists.sourceforge.net
> S
You're right, there are a few posts reporting that tv-out doesn't work
on this model but when I bought this card I also found posts reporting
that this card didn't work at all so right now captures works like a
charm, X works like a charm, and ivtv-fb loads up without any problems
why not the d
This also feels like a scheduling problem. If this is happening then
presumably we are running out of buffers somewhere. The encoder is stealing
buffers so this means the app isn't taking them fast enough which maybe just
down to scheduling.
Also ivtv now has threads for handling a lot of this whic
You're right, there are a few posts reporting that tv-out doesn't work
on this model but when I bought this card I also found posts reporting
that this card didn't work at all so right now captures works like a
charm, X works like a charm, and ivtv-fb loads up without any problems
why not the decod
You're right, there are a few posts reporting that tv-out doesn't work
on this model but when I bought this card I also found posts reporting
that this card didn't work at all so right now captures works like a
charm, X works like a charm, and ivtv-fb loads up without any problems
why not the d
You're right, there are a few posts reporting that tv-out doesn't work
on this model but when I bought this card I also found posts reporting
that this card didn't work at all so right now captures works like a
charm, X works like a charm, and ivtv-fb loads up without any problems
why not the d
I also noticed that you said you have a PVR-350 (model 992).
I think model 990 is the most common, have you done a search on the archive on
"992" ??? Hopefully not, but it might be a compatibility problem. If it were I
would imagine there is some mention of it in the archive. Sorry don't mean to
On Sun, 16 Jan 2005, Michel Verbraak wrote:
> Peter,
>
> I have the same card.
>
> Mine is working allright.
>
> I use the following startup script:
>
>
> #!/bin/bash
> echo Loading IVTV drivers.
> echo Loading tveeprom
> modprobe tv
Are you saying that you are attempting to playback a recording from a command
line while X is running on the PVR 350's framebuffer tv out port?
- Original Message -
From: Nicolas Mainil <[EMAIL PROTECTED]>
Date: Monday, January 17, 2005 11:21 am
Subject: [ivtv-devel] X working on PVR-350
No, I've not been very clear. All the command lines were done while X
wasn't launched on the PVR-350, I did them for testing purposes. But
when starting X on the PVR-350 to use mythtv, the myth frontend is
properly displayed but when attempting to play livetv or a recording I
get no video or really
Hi,
I want to use the PVR-350 output for mythtv. I managed to get X
working on the PVR-350 (with the latest ivtvdev v0.8 driver) anr
recording works very well but the decoder doesn't work or sometimes at
really really poor framerate.
When I do :
cat /dev/video0 > tmp.mpg
followed by
dd if=tmp.mpg
Peter,
I have the same card.
Mine is working allright.
I use the following startup script:
#!/bin/bash
echo Loading IVTV drivers.
echo Loading tveeprom
modprobe tveeprom
sleep 1
echo Loading videodev
modprobe videodev
sleep 1
echo Loa
Sorry to remail this. My ISP (panix.com) had it's domain hijacked over the
weekend (even made Slashdot!), and I lost all email conectivity, so I don't
_think_ this even got to the list.
Again, sorry if it's a dupe.
I've bee loosely following this list for several months now.
I had a machine wrok
George Lopez wrote:
I have a critical issue with mythtv. I am not sure if
I need to post the issue on ivtv or on mythtv list. I
cannot capture because I am not able to get ivtv to
load. Not sure if this is a Jarod's guide issue, ivtv
issue, or user issue. I have gotten everything up and
running
On Monday 17 January 2005 5:26 am, TheNop wrote:
> Hi everybody,
>
> this could be stupid question, but I don't find anything regarding the
> codec setting parameter of ivtvctl.
> I'm very interesting in the differences of the strem_type and audio
> parameter values.
>
> Where can I find informatio
Am Montag, 17. Januar 2005 13:39 schrieb Gerd Knorr:
> > Hi Gerd,
> >
> > here are the driver logs from snapshot 20050114-132940 and ivtv
> > 0.2.0-rc3b. One log is without and one is with ivtv tuner option
> > specified.
>
> Ahh, stupid bug, just a forgotten i2c_attach_client(). Fixed in cvs now,
Hi,
I am running 0.2.0-rc2j of ivtv drivers on FC3. This seems to be pretty
stable but I am thinking of moving to next stable version.
Does nybody suggest any version?
Also, I see a lot of parameters to ivtv driver have gone away like
mpg_buffers etc. Was it intended? See modinfo output
I managed to clear off the drive. It turned out to be that when the drive fills
up the it is not able to write the recorded stream fast enough, so the result
is dropped frames. Sorry for the posting... I should have tested this out
beforehand.
- Original Message -
From: Steven Schaefer
> Hi Gerd,
>
> here are the driver logs from snapshot 20050114-132940 and ivtv 0.2.0-rc3b.
> One log is without and one is with ivtv tuner option specified.
Ahh, stupid bug, just a forgotten i2c_attach_client(). Fixed in cvs now,
please try again.
Gerd
-
Hi,
I'm trying to get either mplayer or xine (latest tarballs) to play xvid and
divx videos (640x352 res typically) to play normally on the PVR-350's TV-out
under X. I am using the 0.3.2b ivtv driver and the 0.8 ivtvdev_drv X driver
to run things. Mythtv-suite 0.16 is from atrpms.net.
Having mana
Hi everybody,
this could be stupid question, but I don't find anything regarding the
codec setting parameter of ivtvctl.
I'm very interesting in the differences of the strem_type and audio
parameter values.
Where can I find information or documentation of these parameters?
Best regards
TheNop
31 matches
Mail list logo
