Chris,
It's on my list of things to investigate. At the moment (the force is with me
again :-) I'm working on sliced VBI support for PVR150 and on adding an
interface to dynamically check which VBI standards are available in which
line. It will be a demonstrator project that should eventually h
Brian Litzinger wrote:
On the subject of SPAM. I original sent this email to the list
via mailhub.pacbell.net and it was rejected as indicated below.
I have to say, for a technical list, the rules seem a but
poorly setup.
You realize this list is run by sourceforge right? The project/list/etc
On Tue, 9 Aug 2005, Timothy McFadden wrote:
>My /var/log/messages file fills up with the messages below while using
>MythTV (for the most part, only when I'm displaying a live preview of
>my recordings while selecting them from a list). I can minimize the
>affect by de-selecting "Setup->Setup->TV
This patch fixes alevt support: alevt expects a sequence number at the end of
the raw VBI data. This was commented out by someone and has been reinstated
at the proper place.
Also, the alevt patch now also fixes an alignment problem for 64-bit systems.
Regards,
Hans
-
Hi Graeme,
I have three essential questions for you:
- What version of MythTV are you using?
- Are you in PAL or NTSC country?
- Do you set some vbi-related options using ivtvctl before running MythTV?
I looked at MythTV 0.18.1 and I see NO setting for vbi_passthrough, so I fail
to see how Myth
A tiny follow-up patch that doesn't set T_RADIO for the tuner if no radio is
present.
Hans
diff -ru ivtv/driver/ivtv-driver.c ivtv-0.3.7b/driver/ivtv-driver.c
--- ivtv/driver/ivtv-driver.c 2005-08-08 22:41:11.0 +0200
+++ ivtv-0.3.7b/driver/ivtv-driver.c 2005-08-08 22:43:53
Hello all.
I'm running FC3 and ivtv with a PVR-350 and I'm having log file problems.
My /var/log/messages file fills up with the messages below while using
MythTV (for the most part, only when I'm displaying a live preview of my
recordings while selecting them from a list). I can minimize the af
Howdy,
I just upgraded from 3.6x to 3.7b, and after a cold reboot, I had a
working tuner2 (from Myth), but only dark static on tuner1. I did
another cold reboot (~2 minutes off time in both cases), and the
problem went away.
I had a similar problem when I installed 3.6x, but didn't keep trac
On Thu, 4 Aug 2005, Ben Lancki wrote:
Sorry to burst your bubble. I'm actually having a hard time finding
any video card that I can use (with xv). The nv driver doesn't seem to
do xv in interlaced mode. My g400 open driver also doesn't do xv in
interlaced and the binary driver from matrox doesn'
This is something wrong with the firmware I believe, when we go into ff/rw
mode seems to re-init the VBI decoder, so we probably need to re-setup
that when coming out of ff/rw. I hopefully can get around to that here
sooner or later and put some code in to fix that, have been thinking about
th
This is something wrong with the firmware I believe, when we go into
ff/rw mode seems to re-init the VBI decoder, so we probably need to
re-setup that when coming out of ff/rw. I hopefully can get around to
that here sooner or later and put some code in to fix that, have been
thinking about th
The only thing that might've been addressed were horizontal tearing
issues on output on the PVR350 (specifically via xv). Your pictures
are not pictures of tearing. Those are pictures of an interlaced mpeg
being played on a progressive display with no deinterlacing applied.
Dunno what you're using
Hi - I'm not Graeme, but I'm having a similar problem with CC data - it
works fine if I start watching a recorded show from the beginning, but
the moment I skip around it stops.
This is with:
MythTV 0.18.1-r2 (Gentoo)
NTSC
I set the following ivtv options at boot (fairly late in the boot
pr
Now with patch :-)
Hans
On Tuesday 09 August 2005 19:56, Hans Verkuil wrote:
> (Sourceforge seems to have eaten this mail, so I'm mailing it again)
>
> This patch fixes alevt & nxtvepg support: alevt expects a sequence number
> at the end of the raw VBI data. This was commented ou
Hi Hans,
> (Sourceforge seems to have eaten this mail, so I'm mailing it again)
Was your attachment on this mail also eaten? :-)
I'm eager to test the patch, sounds really nice.
Regards,
Simon
---
SF.Net email is Sponsored by the Better Soft
Chris,
A very good source for raw VBI testing and information is the libzvbi library
(http://sourceforge.net/projects/zapping). Especially the test/osc tool which
shows the contents of the VBI area realtime.
I've run nxtvepg with this patch for awhile without any dropped frames. In
what circum
I thought I saw somebody mention that 3.7b fixed their tearing issue. I have
not see this fixed on my system. I have a few images captured using an older
3.6 version that shows what I am seeing.
http://air.planetrichardson.net/fuzzy0.png
http://air.planetrichardson.net/fuzzy1.png
http://air.pl
Hans,
Ah, that's a good thing then, although you hadn't included the patch
:). One question then is if it loses characters ever in teletext mode
like in CC mode, I thought the missing characters were from this
timestamp insert, maybe part of it at least, although I see what your
saying and i
Chris,
This really isn't a problem. The raw VBI parsers don't care if the VBI lines
are offset by a random amount of bytes (within limits, of course. If it's off
by more than 100 bytes you might get into trouble). The start-stop codes are
ignored anyway.
At least alevt and nxtvepg rely on the
Hans,
This was commented out becasue upon further inspection of the raw VBI
data I found that the stop/start codes it is trying to overwrite are not
always there, basically the raw VBI alignment in the chips buffers are
*not* perfectly aligned to the stop/start codes. It's as if we really
ha
Hi,
Thanks for your reply.
If I use those numbers with ivtvctl
--set-freq= and view with mplayer /dev/video
it works fine. The numbers are taken from my cable
television provider multiplied by 16 (got this #
somewhere from the inet).
Though, I figured out that I need the values from my
provider
(Sourceforge seems to have eaten this mail, so I'm mailing it again)
Hi Graeme,
I have three essential questions for you:
- What version of MythTV are you using?
- Are you in PAL or NTSC country?
- Do you set some vbi-related options using ivtvctl before running MythTV?
I looked at MythTV 0.18.
Andrej van der Zee wrote:
Hi,
Hi Andrej,
I have a problem switching channels within freevo. I
get the following message in /var/log/messages:
Aug 9 17:35:25 localhost kernel: tuner: TV freq
(2.93) out of range (44-958)
Aug 9 17:35:41 localhost kernel: tuner: TV freq
(3.43) out of range (4
(Sourceforge seems to have eaten this mail, so I'm mailing it again)
This patch fixes alevt & nxtvepg support: alevt expects a sequence number at
the end of the raw VBI data. This was commented out by someone and has been
reinstated at the proper place.
Also, the alevt patch now also fixes an a
(Sourceforge seems to have eaten this mail, so I'm mailing it again)
A tiny follow-up patch that doesn't set T_RADIO for the tuner if no radio is
present.
Hans
diff -ru ivtv/driver/ivtv-driver.c ivtv-0.3.7b/driver/ivtv-driver.c
--- ivtv/driver/ivtv-driver.c 2005-08-08 22:41:11.00
Hi,
I have a problem switching channels within freevo. I
get the following message in /var/log/messages:
Aug 9 17:35:25 localhost kernel: tuner: TV freq
(2.93) out of range (44-958)
Aug 9 17:35:41 localhost kernel: tuner: TV freq
(3.43) out of range (44-958)
And in /tmp/freefov/main-1001.log:
Graeme Wilford wrote:
I'm not seeing this on my PVR350 with 0.3.7a + latest YUV patch from
John (which includes the tearing fix). Perhaps try that combo instead
of 0.3.7b and if it helps, there's probably only a few lines
difference between the two...
NB. I haven't tried 0.3.7b as the above com
27 matches
Mail list logo
