From: James Courtier-Dutton <James@superbug.co.uk>
To: PIVATY Bertrand <bertrand.pivaty@eurocontrol.int>
Cc: Martin Habets <errandir_news@mph.eclipse.co.uk>,
alsa-devel@lists.sourceforge.net
Subject: Re: Urgent question
Date: Mon, 09 Jan 2006 14:54:11 +0000 [thread overview]
Message-ID: <43C27913.8040903@superbug.co.uk> (raw)
In-Reply-To: <0AEFDFCCEC85B24E8051B23293C2CB640F2506@MMMSTCAE1.muac.corp.eurocontrol.int>
PIVATY Bertrand wrote:
>Hello all,
>
>Thanks for your quick reaction.
>
>aplay and speaker produce the same good quality on both onboard and PCI
>sound cards.
>
>It is indeed for us obvious that the problem is coming from the audio
>software.
>
>But when checking the source code, I didn't see anything special, I mean
>they mainly use the ALSA api, and it is basically looks like the
>different ALSA tutorials that I've found.
>
>This is a software from one of our provider, and I know that the code
>was ported from SUN microsystem to Linux to meet our requirements, there
>are some statements with "ioctl" calls, do you think that this could be
>an issue, as it bypass the ALSA api?
>
>I know it seems vague, but I can try to send some part of the code with
>ALSA (I think this is not a big issue, the only thing is I don't know
>witch part could be interesting to send).
>
>
Output from this would help me.
cat /proc/asound/cards
As speaker-test worked fine, the problem will be due to one of 2 things.
1) Buffer and Period size setting.
It would be very useful to see how your app decides on buffer and period
sizes. ALSA is somewhat different from other sound APIs, in that it does
not hide the hardware buffer size from the user. I.e. You can only set
buffer and period sizes that the sound card can actually support in
hardware. Some extra care is therefore needed when deciding on buffer
size. If I could see your source code with regard to buffer and period
sizes, I could tell if this was the problem.
2) Sample rate.
If the sound card hardware can only do 48000Hz, and your sound
application works at 44100Hz, there are certain circumstances where
sound quality will suffer.
Here, if I knew which sound cards you were using, and the sample rate
your application was using, I could help here.
Note:
I general fix to both the above problems would be to use a hardware
mixing sound card.
e.g. SB Audigy (Not LS or SE) or a SB Live (not 24bit version)
Would it be acceptable to specifiy the sound card to use? I doubt that
Air traffic control simulators have a very wide audience.
If you are not able to specify the sound card, there are software ways
out of all the problems described above.
James
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
next prev parent reply other threads:[~2006-01-09 14:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-09 14:04 Urgent question PIVATY Bertrand
2006-01-09 14:54 ` James Courtier-Dutton [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-01-09 10:07 PIVATY Bertrand
2006-01-09 11:17 ` James Courtier-Dutton
2006-01-09 11:28 ` Martin Habets
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=43C27913.8040903@superbug.co.uk \
--to=james@superbug.co.uk \
--cc=alsa-devel@lists.sourceforge.net \
--cc=bertrand.pivaty@eurocontrol.int \
--cc=errandir_news@mph.eclipse.co.uk \
/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