From: Conrad Parker <conradp@cse.unsw.edu.au>
To: linux-sound@vger.kernel.org
Subject: Re: sound/gui interaction
Date: Thu, 20 Jul 2000 05:37:03 +0000 [thread overview]
Message-ID: <marc-linux-sound-96407145801360@msgid-missing> (raw)
In-Reply-To: <marc-linux-sound-96407043600178@msgid-missing>
On Thu, Jul 20, 2000 at 01:15:07AM -0400, douglas irving repetto wrote:
>
> hi there linux-sound,
>
> i'm working on a linux sound app. my signal processing loop runs in its
> own thread. whenever i do a full drawing update of my GUI, i get a
> glitch in the sound output. my CPU usage goes up during the redraw, but
> not very much. does anyone know what's happening and how i can avoid it?
> i would think that doing the graphics and the sound in seperate threads
> would shield the one from the other, but apparently that's not the case.
> is this an XWindows issue perhaps?
your thinking is pretty much correct (as threads in Linux are
independently scheduled). What's most important is which thread is
writing to the sound device -- make sure you're not doing your
write()s in the same thread as dealing with X events.
If that's not the case... can we see the code?
Conrad.
prev parent reply other threads:[~2000-07-20 5:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-07-20 5:15 sound/gui interaction douglas irving repetto
2000-07-20 5:37 ` Conrad Parker [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=marc-linux-sound-96407145801360@msgid-missing \
--to=conradp@cse.unsw.edu.au \
--cc=linux-sound@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