On Monday 09 May 2005 02:36, Chris Kennedy wrote:
> Ah, it is working now, but seems it will output garbled CC, repeat
> letters alot, and not output all the CC, comes in spurts kinda, very
> odd, I'm looking closer, but sounds like still a possible parsing issue,
> seems like there's alot of stuff
On Sunday 08 May 2005 20:31, Hans Verkuil wrote:
> On Sunday 08 May 2005 18:34, Chris Kennedy wrote:
> > Wondering how this is supposed to work, I know Myth inserts the VBI into
> > the mpeg stream, and that it's there, and during playback you can run
> > vbi /dev/vbi4 and see the CC there. But ho
Ah, it is working now, but seems it will output garbled CC, repeat
letters alot, and not output all the CC, comes in spurts kinda, very
odd, I'm looking closer, but sounds like still a possible parsing issue,
seems like there's alot of stuff with the first 2 bytes 0x80...
May 8 19:36:13 digit ke
Yes I do have sound working without qss=0. I'm not sure that the audiofmt line
sorted it but I have yet to take the plunge and remove it to see what happens. I
suspect it doesn't do much because the output near the bottom of the card load
info says:
Setting audiofmt = 0x01
Cheers,
Rick
> Hi the
On Sun, May 08, 2005 at 08:31:10PM +0200, Hans Verkuil wrote:
> On Sunday 08 May 2005 18:34, Chris Kennedy wrote:
> > Wondering how this is supposed to work, I know Myth inserts the VBI into
> > the mpeg stream, and that it's there, and during playback you can run
> > vbi /dev/vbi4 and see the CC t
On Sunday 08 May 2005 18:34, Chris Kennedy wrote:
> Wondering how this is supposed to work, I know Myth inserts the VBI into
> the mpeg stream, and that it's there, and during playback you can run
> vbi /dev/vbi4 and see the CC there. But how do we, or can we already?
> output that data to the 350
On Sunday 08 May 2005 17:44, Don wrote:
> Well, no, actually I ran into some problems with the rebuild that I
> didn't have with the original, but the rebuild is probably more
> correct. With the original, I did lots of experimenting with the 2.6
> kernel and SATA. I eventually gave up and staye
This would be wonderful, really an mplayer output for hm12 is all we need to
get this going, and if anything it could just initialize the decoder with
some fake mpeg2 if really needed, but that could be something later if really
needed. I'm not working on it, really bad at all this video format co
Hi Chris,
> Please test VBI and let me know what is problematic, seems this should
> get things very close, if not there, ... [snip]
This one works great for me! I can now use raw VBI in DMA mode without
any problems.
Thank you so much for your work!
Regards,
Simon
---
Heya,
Reading about the new YUV decoding advances, I'd figure to take the risk
and install a .3 version of ivtv to play around with the YUV stuff.
after running yuv_setup.sh, cat /dev/video32 > /dev/video48 seems to
work. it is very stuttery, but the images produces look fine, and I can
still s
Well, no, actually I ran into some problems with the
rebuild that I didn't have with the original, but the rebuild is
probably more correct. With the original, I did lots of experimenting
with the 2.6 kernel and SATA. I eventually gave up and stayed with
the 2.4.29 kernel. When I did the re
Wondering how this is supposed to work, I know Myth inserts the VBI into
the mpeg stream, and that it's there, and during playback you can run
vbi /dev/vbi4 and see the CC there. But how do we, or can we already?
output that data to the 350 output, does /dev/vbi8 do this, but how?
I haven't ever
This has some big VBI fixes for re-insertion and decoding vbi, seems to
mostly work now, and you won't get the overflow stealing buffer errors,
maybe even VBI will actually work now in Myth, but can at least read from
/dev/vbi4 with the 'vbi /dev/vbi4' cmd (seems to segfault if reading
with cat??
On Saturday 07 May 2005 20:17, Don wrote:
> OK, here's some more detail. By the way, I'm trying to get the Mythtv
> menus on the tv, which is connected to the prv350. Thanks for the help.
When you reinstalled the software, did you install exactly the same versions
as were previously installed
On Sun, May 08, 2005 at 10:14:05AM -0400, Joe Briggs wrote:
> Chris, et al:
>
>
> I am starting a project to create a GTK GUI to control MPEG recording
> via IVTV and needed some guidance. I want to pull out raw YUV and PCM
> and push them out to the display and soundcard to assist in setting up
Chris, et al:
I am starting a project to create a GTK GUI to control MPEG recording
via IVTV and needed some guidance. I want to pull out raw YUV and PCM
and push them out to the display and soundcard to assist in setting up
the tuner and other settings; as opposed to just real-time decoding the
Hi there!
Thanks everyone that are developing these drivers!
Sadly they won't work for me at this stage and I would appriciate help
and suggestions to get it working!
I just bought a Hauppauge PAL PVR-150 (non-MCE).
I downloaded the 0.3.4b drivers (the log below states 0.3.3y, but it is
0.3.4b)
I'm seeing exactly the same thing on my PVR-500. Sound works on SVideo with
0.3.2y, but all later version are broken.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Chris Petersen
Sent: Saturday, May 07, 2005 11:59 PM
To: ivtv-devel@lists.sourceforge.net
After getting my pvr-150 MCE working on my workstation with 0.3.3r, I
figured it was save to move it into my mythbox. But there, I can't get
any of the .3.[34] drivers to give sound (same as Arjen, 0.2.0j works
but the sound quality is crap) -- I'm working my way backwards from r now.
A little
19 matches
Mail list logo
