it's been awhile, but i'm pretty sure it's all
mpeg-2.. no mp3 audio.
you might need to capture at a different bitrate (44.1
khz vs 48?)
-tmk
--- Steven Ellis [EMAIL PROTECTED] wrote:
Am I correct in assuming that the PVR-150 produces
an MP3 audio stream
as part of the MPEG produced on
Le 9 oct. 05, à 23:02, Mark Weaver a écrit :
Julien Pervillé wrote:
PS: on a totaly different subject, what's up with the lirc driver
turning unresponsive after a few minutes with the PVR 150 remote? It
starts working just fine, then it silently stops working.
I think this may be an issue
kevin thayer wrote:
it's been awhile, but i'm pretty sure it's all
mpeg-2.. no mp3 audio.
you might need to capture at a different bitrate (44.1
khz vs 48?)
I can use dvdauthor to produce a dvd based on the mpeg files generated
from the PVR-150 but the audio won't work in any of my DVD
Hi!
I'm just in the middle of upgrading a ivtv(ivtv-0.2.0-rc2r) /
MythTV(0.16.0) setup that's about a year old. And I decided to try
Ivtv 0.4.0 and MythTV 0.18.1. I'm using a PVR-350 and ivtv-fb to run
Myth on, and do TV out. The host is running with root (and all
filesystems) NFS mounted
On Fri, Oct 07, 2005, Hans Verkuil wrote:
I have retried with the latest SVN, and the behaviour has changed. When
I switch to radio mode, every time I cat /dev/video0 /tmp/toto, it
creates a /tmp/toto file of exactly 12224 bytes. It contains a pack
header, a system header and the first I
On 10/10/05, Christophe Massiot [EMAIL PROTECTED] wrote:
On Fri, Oct 07, 2005, Hans Verkuil wrote:
I have retried with the latest SVN, and the behaviour has changed. When
I switch to radio mode, every time I cat /dev/video0 /tmp/toto, it
creates a /tmp/toto file of exactly 12224 bytes.
Based on recent developments on v4l I think we should go with the initial
idea: build v4l, then ivtv. In the meantime we keep 0.4 up to date with bug
fixes and new features, at least for the duration of the 0.5 development
series.
Hans
Hi Hans
How can I help with 0.5 development?
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Philip Rowlands
Sent: Sunday, October 09, 2005 8:28 PM
To: Discussion list for development of the IVTV driver
Subject: Re: [ivtv-devel] Cannot install new 0.4.0 ivtv drivers
Hi Phil...
There is,
Hmmm. I was following Jarod's guide which uses apt to install
precompiled binaries. I don't recall seeing anything like this,
but I'll go back a look.On 10/9/05, Adam Forsyth [EMAIL PROTECTED] wrote:
If you followed the mythtv on fedora guide preivously, you need toremove the ivtv rpms, depmod -a,
I apologize in advance if this isn't what you were talking about, or if
this is too off topic or newbie-ish for this list.
Mark Knecht wrote:
What would your suggestion be for pair of rm and ln commands?
Under /usr/src/ you should have one directory called something like
2.6.13-gentoo-r3
Hi,
I have two different hauppauge cards, and i have problems with both of them.
I live in Sweden and uses Europe-pal. using .0.4.0
First of is a PVR-250. With this one i get a nice clear picture, but
no sound (except for one channel.
it has a label with PAL-B/G-I-D/K-SECAM 32059.
Output from
On Monday 10 October 2005 16:44, Mauro Carvalho Chehab wrote:
Hans,
Em Dom, 2005-10-09 às 17:44 +0200, Hans Verkuil escreveu:
On Sunday 09 October 2005 17:27, Adam Forsyth wrote:
It says right at the top of the the cvs info page that it often only
works on the current -rc, and a patch
Hi,
I just upgraded to v.0.4.0 from v.0.2.0-r1.
First I tried to compile under Debian sid, kernel-2.4.31 with gcc-4.0.1. It
ended with this:
gcc -D__KERNEL__ -D__KERNEL_SYSCALLS__ -DMODULE -DMODVERSIONS
-DEXPORT_SYMTAB -I/lib/modules/2.4.31-ct-1/build/include -O2
-fomit-frame-pointer
Tyler Trafford wrote:
Tyler Trafford wrote:
Hans Verkuil wrote:
On Monday 10 October 2005 01:38, Tyler Trafford wrote:
Mauro Carvalho Chehab wrote:
Latest V4L CVS version can be obtained at linuxtv.org:
Hmm, tveeprom here doesn't work with my PVR150 tuner=50, but the one in
2.6.12 does,
Hi,
Tommy Persson wrote:
The size could be fixed by choosing another size in nvtv but I still
think the aspect ratio is not entirelt correct but this can be my
graphics card or its configuration. It seems that the image from
mplayer is to high.
PAL resolution of 720:576 == 5:4. So to display
mt wrote:
Hi,
Tommy Persson wrote:
The size could be fixed by choosing another size in nvtv but I still
think the aspect ratio is not entirelt correct but this can be my
graphics card or its configuration. It seems that the image from
mplayer is to high.
If you're using mplayer, you can
Tim,
I don't see that anywhere in Jarod's guide. Appreciate further info.On 10/10/05, Timothy McFadden [EMAIL PROTECTED]
wrote:Also check to see if you used Jarod's mkinit-rd patch to include the
ivtv drivers.You need to re-make the initial ramdisk with the newdrivers
I now have the right version of the ivtv driver loading. To do
this I had to upgrade to kernel 2.6-12-1.1378 in order to get atrpms to
install the driver properly. I was using 2.6-10.x and there
appears to be no prepackaged ivtv 0.3.x driver for this kernel.
Now, having gotten the ivtv driver
dragonfly ivtv-0.4.0 # /lib/modules/`uname -r`/ivtv/
-bash: /lib/modules/2.6.13-gentoo-r3/ivtv/: No such file or directory
dragonfly ivtv-0.4.0 #
As I said, ivtv doesn't get installed!
try making the /lib/modules/2.6.13-gentoo-r3/ivtv directory before hand?
try running
make
One additional thing I fergot to mention. If I take out the 3 alias commands from modprobe.conf:
alias tveeprom tveeprom-ivtv
alias tuner tuner-ivtv
alias msp3400 msp3400-ivtv
The unknown module messages go away in the dmesg output. Then, the modprobe info looks the same as above.
Any
On Monday 10 October 2005 22:13, Larry K wrote:
I now have the right version of the ivtv driver loading. To do this I had
to upgrade to kernel 2.6-12-1.1378 in order to get atrpms to install the
driver properly. I was using 2.6-10.x and there appears to be no
prepackaged ivtv 0.3.x driver for
On Oct 10, 2005, at 3:13 PM, Larry K wrote:
I now have the right version of the ivtv driver loading. To do
this I had to upgrade to kernel 2.6-12-1.1378 in order to get
atrpms to install the driver properly. I was using 2.6-10.x and
there appears to be no prepackaged ivtv 0.3.x driver
On 10/10/05, Keith C [EMAIL PROTECTED] wrote:
On Oct 10, 2005, at 3:13 PM, Larry K wrote: I now have the right version of the ivtv driver loading.To do this I had to upgrade to kernel 2.6-12-1.1378 in order to get atrpms to install the driver properly.I was using
2.6-10.x and there appears to be
2.6.13-1.1526_FC4
So, what I've done in this: checkout the v4l-kernel and dvb-kernel sources.
Then
make merge-trees -- works fine
make --- has errors relating to a single header file.
If I edit Make.config to remove the few lines Michael suggested, I get
that file only included in two
I don't have the tveeprom.c anywhere on my system ( I searched for it like so: find / -name tveeprom.c).
I suspect I am using the kernel version of tveeprom now. However,
I still have the original issue that is the source of my angst: I
get good audio and video on /video1, but nothing but static
Keith C wrote:
On Oct 10, 2005, at 3:13 PM, Larry K wrote:
I now have the right version of the ivtv driver loading. To do this I
had to upgrade to kernel 2.6-12-1.1378 in order to get atrpms to
install the driver properly. I was using 2.6-10.x and there appears
to be no prepackaged ivtv
1. Do you have any module options specified?
2. Make sure you are using the newest firmware versions:
http://ivtvdriver.org/index.php/Firmware
On 10/10/05, Johan Asterholm [EMAIL PROTECTED] wrote:
Hi,
I have two different hauppauge cards, and i have problems with both of them.
I live in
I can certainly install the card on my win2k machine as a test.
What I'm doing now to test the card is to cat from /dev/video0 and /dev/video1, like so:
# /usr/bin/ivtvctl -u 0x3000 -d /dev/video0
# /usr/bin/ivtvctl -p 6 -d /dev/video0
# /usr/bin/ivtvctl -f width=720,height=480 -d /dev/video0
This problem has come up on the list several times before. lirc_i2c
sometimes pulls in the cx88xx module for some reason (doesn't happen
to me any more, but did until fairly recently) and that conflicts with
the ivtv version of tveeprom. For me, editing tveeprom.c did NOT fix
the problem, I still
I've rewritten ivtvfbctl using getopt.
http://ivtvdriver.org/trac/attachment/ticket/38/ivtvfbctl.c?format=raw
It seemed to be too big to send to the list.
Please test it, as I can't because I don't have a tv right now. Note
that I have cleaned up a few typos and the patch is attached (just so
you
Why is cx88xx loading? You have another capture card in there
somewhere? And if you do, this is a conflict where the kernel cx88xx
module will not use the ivtv tveeprom. So you'll have to use the
kernel version of tveeprom.
I don't have anything installed except the PVR-500MCE. I have no
Hi,
from my experience:
- I don't have /usr/src/linux at all since my last update about
2 weeks ago (for me, /usr/src always was a link to /var/src
anyways and this I removed). It is not needed for ivtv or
lirc (the 2 modules I recompile after a kernel update). I
think this
I'm busy reorganizing ivtv-0.5. I had hoped to finish it today but I don't
have enough time (well, not if I want to stay awake tomorrow :-). However I
expect to complete it tomorrow. BTW, Mauro has already merged msp3400 into
v4l, so that saves a lot of time. Thanks, Mauro!
Hans
I don't have anything installed except the PVR-500MCE. I have no
idea why cx88xx is loading. The machine has the pvr-500 and an
nvidia video card. That's it.
Then you should probably look into why bttv/cx88xx is loading. Thats
not a good thing. Look through dmesg for more bttv and
mt wrote:
So to me it appears that it is a Bad Thing to build different kernels
within the same source tree, because then the links I mentioned above
point to the same directory, but only for one kernel it actually contains
the correct files. It will probably work, if you use different build
On 10/10/05, Kieron Wilkinson [EMAIL PROTECTED] wrote:
I managed to find out what was causing my problem. I had a duplicate
version of the ivtv modules installed in /lib/modules/'uname -r'/extra
(which were prefixed by 'ivtv-'). Once I had got rid of the module
loaded fine! Yay!
Did you
On Mon, Oct 10, 2005 at 05:13:45PM -0500, Keith C wrote:
Here is my modprobe.conf:
snip
#ivtv PVR500
alias char-major-81 videodev
alias char-major-81-0 ivtv
alias char-major-81-1 ivtv
alias tveeprom tveeprom-ivtv
alias tuner tuner-ivtv
alias msp3400 msp3400-ivtv
I'm not
I had *thought* that I had perceived a quality difference betwee the
0.2rc driver and the 3.9 driver. Over the weekend, I finally got to
try it out. I fired up SVN and grabbed 0.2 (final) and 4.1 (snapshot)
drivers, and recorded the closest thing I could find to identical
programming, a few
On 10/10/05, Larry K [EMAIL PROTECTED] wrote:
Actually, I'm using 0.3.8. Not 0.4.x.
Ok. Well, I looked back at the thread and there were so many messages
that I'm a bit confused.
Do locate tveeprom.ko, then move any it finds to tveeprom.ko.HIDE.
Repeat for tuner and tda9887. Then reboot. Since
39 matches
Mail list logo
