| --sched is a linux-only flag that attempts to "set real-time priority
and lock memory" (from the command-line list of flags csound
generates). I've always found real-time performance really needs this
to not have any dropouts. (BTW: I'm on a Planet CCRMA kernel as well)
steven
On Mon, 2004-05-17 at 06:56, gogins@pipeline.com wrote:
> What is the --sched option? I was running as root. I now have the
> lowlatency option enabled, also, so I have the true Planet CCRMA kernel now
> - I had to turn off the automatic power management. But I still get
> dropouts.
>
> As for the flags, I don't know. I tried overriding from commandline and it
> wouldn't do it, but I didn't look into it.
>
> Original Message:
> -----------------
> From: stevenyi stevenyi@csounds.com
> Date: Sun, 16 May 2004 23:09:23 -0700
> To: csound-dev@eartha.mills.edu
> Subject: [CSOUND-DEV:4738] Re: Linux audio
>
>
> Hi Michael,
>
> For dropouts, are you running as root and with --sched flag? I'm
> running a PIII-M 1.2ghz with 768megs ram and it's running in realtime
> with these settings without any dropouts.
>
> Sidenote: I just tried to run csound5 with examples/trappedrt.csd and
> it took me a couple of minutes to realize that I wasn't able to set the
> soundcard on it on the commandline because the settings in the CsOptions
> was overriding what I fed in the commandline. Shouldn't flags fed in on
> the command line override CsOptions?
>
> Thanks,
> steven
>
>
> On Sun, 2004-05-16 at 08:16, gogins@pipeline.com wrote:
> > Thanks, I understand your situation now. This is not good for Csound. Do
> > you want to experiment with rtaudio in place of PortAudio?
> >
> > I should add that I am still getting dropouts with ALSA. My Linux machine
> > is a 1 gigahertz PIII with 256 megabytes RAM, and top shows only a slight
> > load for rendering trappedrt.csd, so I am starting to wonder if the
> > dropouts are a PortAudio problem and not a PC problem.
> >
> > How important is ASIO on Windows for Csound? Is this something that you
> can
> > live without, or wait for the PortAudio developers to do?
> >
> > Original Message:
> > -----------------
> > From: jpff@codemist.co.uk
> > Date: Sun, 16 May 2004 07:07:58 +0100
> > To: csound-dev@eartha.mills.edu, csound-dev@eartha.mills.edu
> > Subject: [CSOUND-DEV:4727] Re: Linux audio
> >
> >
> > >>>>> "gogins@pipeline" == gogins@pipeline com
> writes:
> >
> > gogins@pipeline> Well, I seem to recall that you said PortAudio
> > gogins@pipeline> reports only one interface.
> >
> > No, I see exactly 2 devices, /dev/dsp and the sound card, just like
> > you
> >
> > gogins@pipeline> I infer that PortAudio, OSS, and Csound do not play well
> > together, but I
> > gogins@pipeline> guess that PortAudio, ALSA, and Csound may well be quite
> > usable - I am
> > gogins@pipeline> probably getting dropouts because my machine is still
> old
> > and slow, just
> > gogins@pipeline> not as old and slow as the old one! The aplay utility
> > works just fine, so
> > gogins@pipeline> does xmms.
> >
> > Yes, aplay works correctly. What does not is csound creating a mono
> > output, or a stereo file on the M-Audio (which is a 12 channel chip)
> > The PA setup does not look at the .asoundrc file and so in my set ups
> > I cannot select the SPDIF output on the Hamerfall or the analog output
> > on the M-Audio.
> >
> > ==John ffitch
> >
> >
> > --------------------------------------------------------------------
> > mail2web - Check your email from the web at
> > http://mail2web.com/ .
> >
> >
> >
>
>
> --------------------------------------------------------------------
> mail2web - Check your email from the web at
> http://mail2web.com/ .
>
>
> |