On Jul 28, 2008, at 6:04 PM, Harry Coin wrote:
Correction: Should have been
v4l2-ctl -c audio_later_ii_bitrate=13
not 'v4l-ctl...'
FYI:
I have a PVR-150 running on an old Dell Optiplex (no PCIe, just PCI).
I had no problems until upgrading to the lastest ivtv driver, and
published
Correction: Should have been
v4l2-ctl -c audio_later_ii_bitrate=13
not 'v4l-ctl...'
FYI:
I have a PVR-150 running on an old Dell Optiplex (no PCIe, just PCI).
I had no problems until upgrading to the lastest ivtv driver, and
published firmware and the lastest mythtv stable on Debian Etch
On Mon, 2008-07-14 at 22:47 -0300, [EMAIL PROTECTED]
wrote:
Hi,
i have finaly had some time, i created a diff kernel tree of the 23 kernel
that works and the 25 that has the tinny audio.
i didnt notice anything that stood out, but when i reviewed cx25840-core.c
i noticed that it had what
Hi,
i have finaly had some time, i created a diff kernel tree of the 23 kernel
that works and the 25 that has the tinny audio.
i didnt notice anything that stood out, but when i reviewed cx25840-core.c
i noticed that it had what looked like code thats changing registers, with
that in mind and
Andy Walls wrote:
On Wed, 2008-07-02 at 11:25 -0300, Kevin Blair wrote:
Ok correction on modules in usage,
with the 2.6.25 kernel and bleeding edge driver the modules used are as
fallows:
# lsmod
Module Size Used by
tuner_simple 11600 1
tuner_types
On Wed, 2008-07-02 at 01:20 -0300, Kevin Blair wrote:
well i did a simpler test, since i know that with the 2.6.25 kernel
driver or bleeding edge driver i get the bad audio, and i have moved the
testing to my slave system which is not dependant on running a 2.6.25
kernel i backsteped it to a
On Wed, 2008-07-02 at 11:10 -0300, Kevin Blair wrote:
Overall, I cannot say you are wrong, you have found a causal
relationship.
The question is where is the problem: the ivtv driver, the cx28540
module, the i2c drivers, or the firmware image request process? (Doing
a great big
On Wed, 2008-07-02 at 11:25 -0300, Kevin Blair wrote:
Ok correction on modules in usage,
with the 2.6.25 kernel and bleeding edge driver the modules used are as
fallows:
# lsmod
Module Size Used by
tuner_simple 11600 1
tuner_types13376 1
On Sun, 2008-06-29 at 23:57 -0300, Kevin Blair wrote:
Humm, well ill look into adjusting the latency on the pci bus though i
have played with that before with no luck but i have little to know how
on doing that,
Since you may have a mix of PCI and PCIe devices things are a little
different
Humm, well ill look into adjusting the latency on the pci bus though i
have played with that before with no luck but i have little to know how
on doing that, but to rule out both kernel/driver/firmware conflict and
to check and make sure that the drives stop failing(dont want to lose
data no
ok ill give that a try, though i think i may have another direction that
could be the issue, i had a suspicion but since i had a very similar
issue with out ivtv affecting things i didnt think so, but due to the
failure i just had and recovered from, i am suspecting it may be!
i noticed a point
ok, here is the debug reports, i did the fallowing, i got the system to be
producining the bad audio
and generated the log status file, and a debug file, then i used the
set-audio-input switch which
brought the audio to being normal, and generated another set of logs and
debug logs
since this is
another update, i updated the revision of mythtv but it did not fix the
audio issue.
i also tryed a new copy of the firmware with no change.
Kevin
well i tryed the lattest bleeding edge driver as of 8pm last night and it
does not fix the issue i still get the bad audio. below is the dmesg
On Tue, 2008-06-24 at 08:12 -0300, [EMAIL PROTECTED]
wrote:
well i tryed the lattest bleeding edge driver as of 8pm last night and it
does not fix the issue i still get the bad audio. below is the dmesg info
when the driver is loaded.
Linux video capture interface: v2.00
ivtv: Start
well im not sure now, i have just had a major systemboard failure, i
have yet to fully test what has failed but the entire usb system has
failed, so it may have bin a bad system board causing the issues for me,
ill know for sure when i get a new replacement.
Kevin
Scott Harris wrote:
Hans
Hans Verkuil wrote:
Hi Mike,
The tinny audio problem plagued a lot of people in the past, but I
haven't heard about this for quite some time now. Please make sure you
are using the latest version (preferably the 'bleeding edge' code from
: [ivtv-users] Tinny Audio problem on ivtv 1.0.3
To: User discussion about IVTV ivtv-users@ivtvdriver.org
Message-ID: [EMAIL PROTECTED]
Content-Type: text/plain
On Fri, 2008-05-09 at 21:28 -0300, Kevin Blair wrote:
upgrade to myth .21 didnt do anything, i tried a pvr250 i have and it
doesnt
On Wed, 2008-05-07 at 22:55 -0300, Kevin Blair wrote:
humm, these errors are sparse but i have errors and warnings saying:
Error: Error getting codec params using old IVTV ioctl
Warning: Error getting codec params using old IVTV ioctl
i guess this version of myth doesnt like this version of
upgrade to myth .21 didnt do anything, i tried a pvr250 i have and it
doesnt seem to do it, i have a second pvr150 card in the second system
which i swaped to rule out hardware (and chipset it has a older
revision) but no difference. also tried older and newer(was same as
current) firmware,
On Fri, 2008-05-09 at 21:28 -0300, Kevin Blair wrote:
upgrade to myth .21 didnt do anything, i tried a pvr250 i have and it
doesnt seem to do it, i have a second pvr150 card in the second system
which i swaped to rule out hardware (and chipset it has a older
revision) but no difference.
I have been fighting the Tinny Audio issue for a couple of years now.
I have a PVR500 with Phillips tuners, and I've tried the 1.0.x series
ivtv drivers, but I ultimately settled on 0.6.7.
I can say for sure that I experience the tinny audio without MythTV
being in the loop. If I capture
On Wed, 2008-05-07 at 19:06 -0300, Kevin Blair wrote:
Hi,
im having the bad tinny audio issue on my mythtv system it has only
started recently, and is intermittent so some recordings are fine some
have bad audio, for live playback majortiy of the time audio is fine
only after going in
On Wed, 2008-05-07 at 21:05 -0300, Kevin Blair wrote:
the fallowing is the differnce between when the audio is good and bad
from $ v4l2-ctl --log-status
--- record.good 2008-05-07 20:51:09.250606270 -0300
+++ record.bad 2008-05-07 20:53:28.747993406 -0300
@@ -32,17 +32,16 @@
ivtv0:
23 matches
Mail list logo
