From: Marcel Holtmann <marcel@holtmann.org>
To: James Courtier-Dutton <James@superbug.demon.co.uk>
Cc: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] SCO. Some ideas.
Date: Sun, 29 Feb 2004 23:01:46 +0100 [thread overview]
Message-ID: <1078092105.1942.93.camel@pegasus> (raw)
In-Reply-To: <4042575B.20305@superbug.demon.co.uk>
Hi James,
> alsa handles format conversion automatically, all we have to tell alsa
> is which formats we can do, and alsa does the rest. So, if alsa is not
> allowed to modify the hciconfig hci0 voice XX setting, it can just be
> told what it is via an IOCTL and then tell alsa to do conversions for
> any other formats.
we don't need an ioctl for that, because the current voice setting for a
HCI device is already present in the hci_dev structure.
> Some audio applications need this "pointer" feature, which is why alsa
> provides it.
> An example of this is playback of DVDs.
> Video output needs to be kept closely in sync with the audio, and this
> "pointer" and "trigger" feature allow the application to closely control
> exactly when the sound plays. "trigger" handles the "start the sound
> exactly now", and "pointer" provides feedback, saying that "sound sample
> xyz is currently playing, so display video frame xyz now". "pointer"
> also provides for "audio is playing 0.25 seconds ahead of video, adjust
> it to match".
> These are not hardware specific features, all sound hardware has these
> features, including bluetooth audio, and we just need some way for
> higher layers to get access to the values.
> Another example is Voice over IP. If using a headset, one might want to
> use it to make VoIP calls over the internet. One of the most important
> issues with VoIP is latency. The lower the latency, the more natural the
> conversation will be. Long latency produces conversations will long
> breaks in between and possible delayed echos. It is a lot more difficult
> to have a natually smooth conversation if the latency is high. These
> "pointer" and "trigger" and "period_time_elapsed" functions allow for
> applications to program minimum latancy that any particular hardware can
> handle.
You shouldn't think so much about it. Try to implement the ALSA driver
without it and we see how it goes.
Regards
Marcel
-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2004-02-29 22:01 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-29 16:15 [Bluez-devel] SCO. Some ideas James Courtier-Dutton
2004-02-29 17:02 ` Marcel Holtmann
2004-02-29 18:40 ` James Courtier-Dutton
2004-02-29 20:38 ` Marcel Holtmann
2004-02-29 21:19 ` James Courtier-Dutton
2004-02-29 22:01 ` Marcel Holtmann [this message]
2004-02-29 23:25 ` James Courtier-Dutton
2004-02-29 23:38 ` Marcel Holtmann
2004-03-01 14:11 ` James Courtier-Dutton
2004-03-01 15:28 ` Marcel Holtmann
-- strict thread matches above, loose matches on Subject: below --
2004-03-01 16:27 Williams, Richard
2004-03-01 17:20 ` Simon Vogl
2004-03-01 17:22 ` Marcel Holtmann
2004-03-02 7:43 ` Simon Vogl
2004-03-01 17:39 ` James Courtier-Dutton
2004-03-01 19:08 Williams, Richard
2004-03-01 19:45 ` James Courtier-Dutton
2004-03-01 19:46 ` James Courtier-Dutton
2004-03-01 20:25 Williams, Richard
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=1078092105.1942.93.camel@pegasus \
--to=marcel@holtmann.org \
--cc=James@superbug.demon.co.uk \
--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