From: Benno Senoner <sbenno@em.gardena.net>
To: linux-sound@vger.kernel.org
Subject: Re: playing MP3 vs CPU usage
Date: Sat, 28 Aug 1999 08:52:15 +0000 [thread overview]
Message-ID: <marc-linux-sound-93583019213770@msgid-missing> (raw)
In-Reply-To: <marc-linux-sound-93577292904421@msgid-missing>
>
>
>
>
> On Fri, 27 Aug 1999, Benno Senoner wrote:
> >
> > Linux actually has some problems in this area, especially on slow computers.
> > The trick is to increase audio buffers of your mp3 player (what player are you
> > using ?),
>
> I'm using mpg123 to play it.
> How can I increase the audio buffer of it?
mpg123 -b 1000 mp3file
should help
( In 1-2 days I will post the URL to mingo's patch ( for kernel 2.2.10) ),
this will help even on the crappiest hardware.
>
> > plus tuning your EIDE disk with
> > hdparm -d 1 -u 1 -m 8 -c 1 /dev/hda
> > because when there are disk accesses, the kernel stalls sometimes, especially
> > when you run non-DMAed disks
> > most distros don't tune your disk properly.
>
> what does that command do? I'm use an EIDE non-DMAed harddisk.
> does that line of command tune all kind of disks?
> Does the size of disk matter?
this command turns on all useful EIDE options, like
-d 1 = DMA on
-u 1 = unmask irqs during disk writes
-c 1 = enable 32 bit access
-m 8 = enable multicount disk transfers
even if DMA is not supported the other options are still useful,
just give the commandline as is, unsupported options will be ignored
by hdparm (ie turning on DMA on a non DMAed disk)
Disk size does not matter.
>
>
> So many questions. =P Thanks for helping me.
No prob.
:-)
regards,
Benno.
prev parent reply other threads:[~1999-08-28 8:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-08-27 16:31 playing MP3 vs CPU usage Yau Chan
1999-08-27 18:06 ` Benno Senoner
1999-08-28 5:16 ` Yau Chan
1999-08-28 8:52 ` Benno Senoner [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-93583019213770@msgid-missing \
--to=sbenno@em.gardena.net \
--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