From: David Liontooth <lionteeth@cogweb.net>
To: hermann pitton <hermann-pitton@arcor.de>
Cc: Mauro Carvalho Chehab <mchehab@infradead.org>,
linux-media@vger.kernel.org
Subject: Re: Audio drop on saa7134
Date: Mon, 21 Sep 2009 00:53:22 -0700 [thread overview]
Message-ID: <4AB730F2.4090203@cogweb.net> (raw)
In-Reply-To: <1253496615.3257.25.camel@pc07.localdom.local>
hermann pitton wrote:
> Hi,
>
> Am Sonntag, den 20.09.2009, 06:02 -0300 schrieb Mauro Carvalho Chehab:
>
>> Em Sun, 20 Sep 2009 01:24:12 -0700
>> David Liontooth <lionteeth@cogweb.net> escreveu:
>>
>>
>>> Sep 18 07:00:01 prato kernel: saa7133[4]/audio: dsp write reg 0x464 = 0x000000
>>> Sep 18 07:00:01 prato kernel: saa7133[4]/audio: dsp write reg 0x46c = 0xbbbbbb
>>>
>> This means mute. With this, audio will stop.
>>
>>
>>> Sep 18 07:00:01 prato kernel: saa7133[4]/audio: dsp write reg 0x464 = 0x000000
>>> Sep 18 07:00:01 prato kernel: saa7133[4]/audio: dsp write reg 0x46c = 0xbbbb10
>>>
>> This means unmute.
>>
>> It seems that the auto-mute code is doing some bad things for you. What happens
>> if you disable automute? This is a control that you can access via v4l2ctl or
>> on your userspace application.
>>
>> Are you using the last version of the driver? I'm not seeing some debug log messages
>> that should be there...
>>
>>
>>
>> Cheers,
>> Mauro
>>
>
> despite of still 1001 messages unread, Mauro is right here.
>
> You are also for sure not on a saa7134, likely you would not ever had a
> reason to come up here on such. But the much better is to have you now.
>
lspci says
00:07.0 Multimedia controller: Philips Semiconductors SAA7133/SAA7135
Video Broadcast Decoder (rev 10)
The cards apparently have the saa7133HL-v101 chip. Are you suggesting
the saa7134 would be better?
> Means, you are at least on a saa7133, not able to decode stereo TV sound
> on PAL and SECAM systems, vice versa counts for the saa7134 on SYSTEM-M.
>
I'm recording NTSC -- are you saying the saa7133 should be able to
decode stereo on NTSC?
If "vice versa" for the saa7134, does that mean this chip is not able to
decode stereo on NTSC?
Sorry, I don't know what SYSTEM-M is in this context.
If you could help me find a chip that avoids this audio drop problem,
that would be great.
> The automute is for convenience of the users, say not to have loud noise
> on channel switching.
I see. That's irrelevant for my purposes; the channels are switched
before the recording starts.
> It is also controlled by different registers for
> analog sound and PCI dma sound.
>
I'm using PCI dma sound.
> If debugging those issues, one more thing to mention is that external
> video in without audio will kick in mute on those cards too at the first
> round.
>
> It should be possible to disable all such funny stuff on production
> systems, pleasant for the average user's conditions, and then see if
> anything should still remain.
>
> On bad mobos, needing PCI quirks and other such stuff, we are likely not
> any further than what you have seen on bttv previously, but in 99.9
> percent of the known cases it seems to work.
>
> Else Mauro again is right, even audio_debug = 1 should deliver the
> related mute ioctl prints.
>
I see -- it may be a couple of weeks before I can run tests on a more
recent kernel, but I'll do that if turning off audiomute doesn't solve
the problem.
Cheers,
Dave
next prev parent reply other threads:[~2009-09-21 7:53 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-15 2:41 Reliable work-horse capture device? David Liontooth
2009-09-15 3:08 ` Mauro Carvalho Chehab
2009-09-15 4:02 ` David Liontooth
2009-09-15 4:21 ` hermann pitton
2009-09-15 5:16 ` Audio drop on saa7134 David Liontooth
2009-09-15 5:36 ` hermann pitton
2009-09-15 6:07 ` David Liontooth
2009-09-20 8:24 ` David Liontooth
2009-09-20 9:02 ` Mauro Carvalho Chehab
2009-09-21 1:30 ` hermann pitton
2009-09-21 7:53 ` David Liontooth [this message]
2009-09-23 0:42 ` hermann pitton
2009-09-21 7:40 ` David Liontooth
2009-09-15 4:34 ` Reliable work-horse capture device? Mauro Carvalho Chehab
2009-09-15 5:03 ` David Liontooth
2009-09-15 10:39 ` Andy Walls
2009-09-15 14:48 ` David Liontooth
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4AB730F2.4090203@cogweb.net \
--to=lionteeth@cogweb.net \
--cc=hermann-pitton@arcor.de \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox