From: Jonathan Oppenheim <jono@Phys.UAlberta.CA>
To: linux-sound@vger.kernel.org
Subject: Re: no recording w/ emu10k1 (SBLive! and SBPCI512)
Date: Wed, 12 Apr 2000 00:35:56 +0000 [thread overview]
Message-ID: <marc-linux-sound-95550481610388@msgid-missing> (raw)
In-Reply-To: <marc-linux-sound-95495756630733@msgid-missing>
just an update on the SBLive driver, since a number of
people emailed me and had similar problems.
It seems to record fine now with the CVS driver (available
at www.opensource.com)
recording with SLab works (if you run SLab as root!)
i have not yet got kvoice to work, but understand that
other people (with different soundcards) get similar error
messages, so it may just be a bad program (i heard that it is
no longer supported).
if anyone knows what permissions to change to get SLab to
work without being root, please let me know.
thanks for the help,
jonathan
On Wed, 5 Apr 2000, Paco wrote:
Hello...
I've spoken with the CEO of 4front technologies about my recording
problems using OSS/Commercial with the SBPCI512 card. (Some one else
posted recoding problems with the Live! yesterday, too.)
He has informed me that there *is* a bug in the recording code for these
two cards, and recording is absolutely not possible unless you download
the emo10k1 driver from creative labs' website.
They have no plans to fix this bug until sometime in the summer.
peace,
-Paco
-----BEGIN PGP PUBLIC KEY BLOCK-----
Version: 2.6.2
mQCNAzc5/rwAAAEEALGi/cKupURWMeRs3xKx7+3PHi1hqfswOuM5suJhTEJZiR+p
xYsVYB/B/uNwrr+m+Rzd8sEJlB2D/JkkCHMUplDR2OC0hfUYmQGIXEg9kShudRsO
E+1oVFFevj6MTgIY6c5nSWvz3n+zLHrcHk/k8pLDpI6qcIGqrAEcX2GVzVwNAAUR
tARqb25vtBU8am9ub0BwaHlzaWNzLnViYy5jYT4ýxR
-----END PGP PUBLIC KEY BLOCK-----
prev parent reply other threads:[~2000-04-12 0:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-04-05 17:59 no recording w/ emu10k1 (SBLive! and SBPCI512) Paco
2000-04-12 0:35 ` Jonathan Oppenheim [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-95550481610388@msgid-missing \
--to=jono@phys.ualberta.ca \
--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