From: Hamish Moffatt <moffatt@cs.rmit.edu.au>
To: linux-sound@vger.kernel.org
Subject: Re: gmod and xmp, cannot open /dev/sequencer !
Date: Sat, 19 Sep 1998 13:02:56 +0000 [thread overview]
Message-ID: <marc-linux-sound-90621003326481@msgid-missing> (raw)
In-Reply-To: <marc-linux-sound-90586345324981@msgid-missing>
On Fri, Sep 18, 1998 at 12:19:57PM +0300, Tuukka Toivonen wrote:
> On Fri, 18 Sep 1998, Alamais wrote:
> >mod,xm,s3m,etc files include their own samples,
> >and [do not/should not] use the midi sequencer.
>
> I don't know if awe drivers support it (but I assume they do) -- but at
> least with GUS this is completely wrong way to play modules. Using /dev/dsp
> eats CPU time since the processor has to mix the samples. With proper sound
> card (ie. GUS) the sample are downloaded to the soundcard memory and the
> player just says "play this sample with this pitch". Eats practically 0%
> CPU time. And this is where to use /dev/sequencer.
That's a loaded statement if ever there was one. If the GUS was
such a great sound card, surely Gravis would still be in business? :-)
Hamish
--
Hamish Moffatt, StudIEAust hamish@debian.org, hamish@moffatt.nu
Student, computer science & computer systems engineering. 4th year, RMIT.
http://hamish.home.ml.org/ (PGP key here) CPOM: [******* ] 73%
Get a stable, reliable & upgradable operating system free at www.debian.org
next prev parent reply other threads:[~1998-09-19 13:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-09-15 10:32 gmod and xmp, cannot open /dev/sequencer ! Alexis DOMJAN
1998-09-18 4:03 ` Alamais
1998-09-18 9:19 ` Tuukka Toivonen
1998-09-19 13:02 ` Hamish Moffatt [this message]
1998-09-21 10:51 ` Tuukka Toivonen
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-90621003326481@msgid-missing \
--to=moffatt@cs.rmit.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.