From: pinguin74 <pinguin74@gmx.com>
To: unlisted-recipients:; (no To-header on input)@casper.infradead.org
Cc: Linux Media Mailing List <linux-media@vger.kernel.org>
Subject: Re: sound dropouts with DVB
Date: Fri, 07 Mar 2014 22:19:59 +0100 [thread overview]
Message-ID: <531A37FF.5080509@pinguin74.gmx.com> (raw)
In-Reply-To: <CA+O4pC+R8ZXZ_wYfa2y82TPwCD4q_fUh96pgbYu2VUhVyGPGvQ@mail.gmail.com>
Am 07.03.2014 00:36, schrieb Markus Rechberger:
>> I will try with mplayer later. What does codec issue mean? I think the
>> audio stream in DVB-C is a digital stream that does not need to be
>> changed or encoded in any way? I thought DVB playback simply is a kind
>> of pass thru the digital streamt to the media player....
>
> The mediaplayer is using a codec for decoding/unpacking the compressed
> digital stream.
Oh yes, of course. Is this not also called "demuxing"? Or is demuxing
just the splitting of the stream?
I found out this may be an issue with the snd-hda-intel module.
When I use a different model option for this module, the siutation
changes, at least the bluetooth headphone does not lose connection, but
audio still drops out.
MPlayer reports I and B frame errors, but DVB works.
I now use
modprobe snd-hda-intel model=acer-aspire align_buffer_size=128000
I will try out VLC now with DVB to see if the VLC codecs work better
than Xine/kaffeine.
Thanx.
next prev parent reply other threads:[~2014-03-07 21:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-06 21:48 sound dropouts with DVB pinguin74
2014-03-06 22:30 ` Markus Rechberger
2014-03-06 23:19 ` pinguin74
2014-03-06 23:36 ` Markus Rechberger
2014-03-07 21:19 ` pinguin74 [this message]
2014-03-07 22:33 ` pinguin74
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=531A37FF.5080509@pinguin74.gmx.com \
--to=pinguin74@gmx.com \
--cc=linux-media@vger.kernel.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