Please check the wiki http://ivtv.writeme.ch/tiki-index.php?page=TvOutHowto
to get started. The versions mentioned there are a little outdated but it is
still valid in priciple (load ivtv-fb and have a X display associated with
it).
When you have that running you can reference the TV out display ju
I just purchased a PVR-350. I'm using FedoraCore3 and have been following the Redhat Guide.
Receiving static similiar to http://www.bodgit-n-scarper.com/pvr350.jpg
When I "dd" a mpg file to video16, the output shows but only briefly. A 6 second file shows for one second or so. I have verified
I set mpg_buffers=8 and my prebuffering pauses are almost all fixed.
I also was getting ringbuffer errors, which are now solved... I'm still
getting some slight prebuffering pauses - but I second the faster
channel changes.
Now it takes only ~ 3 seconds instead of 5~10.-- -Bretthttp:saltybeagle.co
I would like to display a playlist directly on a tv output of wintv350
using mplayer.
I've tried to do mplayer -vo xv /dev/video16 video_file.avi but
the video is displayed on a computer monitor.
Has anyone idea how to send the output of mplayer to the wintv350 video output?
Thank you
marcos
This is a recently purchased Hauppauge PVR-150 (non-MCE) card. Let me know if
I can provide any more info. Interestingly enough, when using
ivtv-0.2.0-rc3j, the tuner type defaulted to PVR-150, not -250. It didn't
work either way.
-=Mark
ivtv: START INIT IVTV
I have one PVR500 on a nForce2 based Chaintech 7NJL6 motherboard. I
used to get 1 or 2 short prebuffering pauses when I was switching
channels in liveTV mode in Myth. I couldn't get these to go away no
matter what option I tweaked in Myth.
I just tried 0.3.6r and set mpg_buffers=8, and now the pre
2005-06-25 00:49 skrev Robin Marlow <[EMAIL PROTECTED]>
>Hello!
> i have been enjoying use of my pvr350 for the last 6 months, until i
>decided to upgrade to a more powerful machine. so reinstalled from
>scratch, and everything is beautiful. except i can\'t understand why
>the blinki
Hello!
i have been enjoying use of my pvr350 for the last 6 months, until i
decided to upgrade to a more powerful machine. so reinstalled from
scratch, and everything is beautiful. except i can't understand why
the blinking thing won't work!
i am using 0.2.9-rc3j (0.3.6o had terrible st
On 6/24/05, Keith C <[EMAIL PROTECTED]> wrote:
> On Jun 24, 2005, at 4:42 PM, Mark Knecht wrote:
>
> >
> > Interesting. I'm a hardware guy with a bit of PCI background. Do you
> > know how are they placing two turners on the same card? Are the tuners
> > PCI devices and then the card has a PCI bri
On Jun 24, 2005, at 4:42 PM, Mark Knecht wrote:
Interesting. I'm a hardware guy with a bit of PCI background. Do you
know how are they placing two turners on the same card? Are the tuners
PCI devices and then the card has a PCI bridge?
Looks like it is :
01:08.0 PCI bridge: Hint Corp HB6 Uni
On 6/24/05, Bryan Mayland <[EMAIL PROTECTED]> wrote:
> Mark Knecht wrote:
>
> >>Actually, this is the way the 500 works, it shows up as 2x150. So
> >>autodetect is fine. The only problem I see is a missing tda9887
> >>module. You have the same D492 card as me, and this is what I need
> >>in modp
Bryan Mayland wrote:
> Tyler Trafford wrote:
>
>> If 0.3.5 is the last, then this must be more 'black magic' (tda9887) fallout.
>
> I would think that too, but that only messed with the audio. His
> picture is wonky too.
If he loads 0.3.5, unloads, and then loads 0.3.5a - it works, but
0.3.5
Mark Knecht wrote:
Actually, this is the way the 500 works, it shows up as 2x150. So
autodetect is fine. The only problem I see is a missing tda9887
module. You have the same D492 card as me, and this is what I need
in modprobe.conf to make it work :
Thanks Keith. I had no idea that's wh
On 6/24/05, Keith C <[EMAIL PROTECTED]> wrote:
> On Jun 24, 2005, at 1:24 PM, Mark Knecht wrote:
>
> > On 6/24/05, Brad Dorner <[EMAIL PROTECTED]> wrote:
> >
> >> It would appear that the capture card is now getting recognized,
> >> but I
> >> am still not able to receive anything other then stati
On Jun 24, 2005, at 1:24 PM, Mark Knecht wrote:
On 6/24/05, Brad Dorner <[EMAIL PROTECTED]> wrote:
It would appear that the capture card is now getting recognized,
but I
am still not able to receive anything other then static.
This is running on a SUSE 9.3 system.
Here is what dmesg is say
Yes - it really would be great to see ivtv in the kernel tree. I totally
agree with Aran on appreciating all the good work - I think getting
officially supported would be a well deserved reward!
But (there is alway a 'but', isn't it) IMHO the PVR-350 TV-Out features have
proven not to be as flawle
Couple of tips:
The ivtv version should be listed when the module loads - check dmesg |
grep ivtv
Depending on your OS (didn't notice it listed) you can query your
package manager to see whats installed (for example in Fedora you could
do rpm -qa | grep ivtv or rpm -qa | grep video4linux)
You ca
On 6/24/05, Brad Dorner <[EMAIL PROTECTED]> wrote:
> It would appear that the capture card is now getting recognized, but I
> am still not able to receive anything other then static.
>
> This is running on a SUSE 9.3 system.
>
> Here is what dmesg is saying now. Any ideas as to why I am getting
Hello all,
New listguy Steve here. I am running ivtv 0.3.6g right now on my Myth
system, and am considering an upgrade to the latest revisions to see if
that helps me with a memory issue. I'll post that exact memory problem
in my next message, but in an effort to get y'all the most informati
El Miércoles, 22 de Junio de 2005 17:17, Oscar Curero escribió:
> Hi,
>
> Christoph Schulz write:
> > I think this is the problem. You have a type 38 tuner but this is
> > ignored because your tuner module is loaded with a "type=1" argument.
> > Remove it and try it again. (I don't have any experi
It would appear that the capture card is now getting recognized, but I
am still not able to receive anything other then static.
This is running on a SUSE 9.3 system.
Here is what dmesg is saying now. Any ideas as to why I am getting
static and no sound?
Thanks
Brad
ivtv: S
Firstly, ivtv has been working so well for me for so long now I
stopped reading the list. 0.3.2q has worked flawlessly for me more or
less since it came out with 2 PVR-250's on a Via(!) motherboard. So
flawlessly that I forget ivtv ever gave me any problems at all.
(Various previous versions had
Hi,
I'm experiencing cracking sounds again with this version of ivtv.
the 0.3.3q didn't had this problem, but it had others that caused the
card to stop working.
Im not sure how this can be realated to the driver, but playing music of
video works fine otherwise - The issue only occurs when playing
These are all good questions, right now there are defaults which work as
we have seen, they could be changed, depending on the system. The
m.system_free=16384
parameter could probably be increased, even could have that amount *
cards used
possibly, think it was for 1 card.
Hrmm. Interestin
Chris Kennedy wrote:
> This allows changing the default amount and max amount of memory
> allocated per stream, basically use modinfo ivtv to find out the new
> options, but have this syntax... mpg_buffers=4 (4 megs default)
> max_mpg_buffers=16 (16 megs max memory allocated).
Is this possibly the
Bryan,
tried this but gave another effect. Image was "scrambled". I think it
was using the secam settings for pal. I'm back to removing the one
line.
N.
On 6/23/05, Bryan Mayland <[EMAIL PROTECTED]> wrote:
> Nick,
> Would you do me a favor and try something? I'm wondering if I have the
> setup
These are all good questions, right now there are defaults which work as
we have seen, they could be changed, depending on the system. The
m.system_free=16384
parameter could probably be increased, even could have that amount *
cards used
possibly, think it was for 1 card. With dynamic buffers
One note:
modprobe ivtv cardtype=1
Correctly sets up the PVR-250 and things work, but why should I have to do that?
Thanks,
Mark
On 6/24/05, Mark Knecht <[EMAIL PROTECTED]> wrote:
> Hi,
>I keep running into this problem where ivtv loads but complains.
> Sometimes it works, mostly it doesn't
Hi,
I keep running into this problem where ivtv loads but complains.
Sometimes it works, mostly it doesn't. Here's the dmesg data and lsmod
data. What am I not building right? I figure it must be some part of
i2c but I don't know what.
The machine is 2.6.11-gentoo-r11, Intel P4, 512MB, PVR-250,
Is there now some recommended set of values to use? I have 4 encoder
cards (PVR-150's, 250 Rev 1 and 2's) in my MythTV masterbackend (along
with a M179 that still doesn't work) and I'll get messages like "IVTV:
ENC: Sleep timeout activated".
During periods of heavy loading I'll also get captu
This allows changing the default amount and max amount of memory
allocated per stream, basically use modinfo ivtv to find out the new
options, but have this syntax... mpg_buffers=4 (4 megs default)
max_mpg_buffers=16 (16 megs max memory allocated). So with that the
driver would allocated 4 meg
Tyler Trafford wrote:
If 0.3.5 is the last, then this must be more 'black magic' (tda9887) fallout.
I would think that too, but that only messed with the audio. His
picture is wonky too.
This could be unrelated to your problem, but these are not messages
from the cx25840.ko included w
Bryan Mayland wrote:
> Morten Rønseth wrote:
>
> > BTW, I'd love for the 0.3.6 series to be able to start my pvr150
> > correctly after a cold boot - the last version that does is 0.3.5. (re
> > "pvr150 only capturing noise"). :-)
>
> What kind of noise are you seeing? A screen full of stati
Morten Rønseth wrote:
> Output from /var/løog/messages:
>
> ivtv: START INIT IVTV
> ivtv: version 0.3.6 (q) loading
> ivtv: Linux version: 2.6.8.1-12mdk 686 gcc-3.4
> cx25840: FW image '/lib/modules/HcwMakoA.ROM' of size 13883 loaded.
> cx25840: FW image
Hi Bryan,
Bryan Mayland wrote:
Morten Rønseth wrote:
ioctl IVTV_IOC_S_VBI_EMBED failed: Invalid argument
This is because the cx25840-based cards (150 and 500) don't have
sliced VBI support in the driver (or at least so says the error
message in the code):
ivtv: Sliced VBI not supporte
yeah didn't have it in the right place, now it allocates dma in IVTV
INIT but not after that. Have gone 24hrs without a lockup.
Larry Symms wrote:
sounds like my module option isn't in the right place. I'll try
/etc/mythtv/modules/ivtv next
Bryan Mayland wrote:
:/ you'd think that you'd
Morten Rønseth wrote:
ioctl IVTV_IOC_S_VBI_EMBED failed: Invalid argument
This is because the cx25840-based cards (150 and 500) don't have
sliced VBI support in the driver (or at least so says the error message
in the code):
ivtv: Sliced VBI not supported for cx25840 so no vbi re-insertio
37 matches
Mail list logo
