From: "Luiz Augusto von Dentz" <luiz.dentz@gmail.com>
To: "BlueZ development" <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] sound quality is very slow when using helix player.
Date: Sat, 17 May 2008 19:02:58 -0300 [thread overview]
Message-ID: <2d5a2c100805171502r2466b16fuf4fcd4d177a27b25@mail.gmail.com> (raw)
In-Reply-To: <56A45346-8EDB-4B30-85DE-3D371C0EC702@holtmann.org>
>>From 3.19 to 3.31 there are a lot of changes, so we better focus on 2
things, sbc codec and plugin code. As helix happen to not have a
native plugin so I suppose you are using alsa plugin. What really
changed from 3.19 to 3.31 is that the configuration logic moved from
audio service to plugin, so the user application (helix player) is now
able to select the stream frequency and how many channels it has. This
could be a problem if helix is not selecting the same rate as the
stream and might cause audio degradation, it is also possible that
helix is resampling which not only may cause degradation but also
consumes more cpu.
ps: you can play with sbc parameters directly on ~/.asoundrc, so
perhaps you can find a configuration that do not degraded.
-- =
Luiz Augusto von Dentz
Engenheiro de Computa=E7=E3o
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft =
Defy all challenges. Microsoft(R) Visual Studio 2008. =
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
prev parent reply other threads:[~2008-05-17 22:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-17 0:25 [Bluez-devel] sound quality is very slow when using helix player Wang Baisheng
2008-05-17 3:42 ` Zhao, Halley
2008-05-17 7:16 ` Marcel Holtmann
2008-05-17 22:02 ` Luiz Augusto von Dentz [this message]
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=2d5a2c100805171502r2466b16fuf4fcd4d177a27b25@mail.gmail.com \
--to=luiz.dentz@gmail.com \
--cc=bluez-devel@lists.sourceforge.net \
/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