> and time is used to seed the C library's PRNG.  Note that the output
> of this PRNG could also be affected by other programs running on the
> computer, which could be seeding the PRNG and taking numbers from it
> - either of which would affect the numbers being returned to the
> various points in Csound which call rand() to get pseudo random
> numbers.
>

how is this possible?  how can a function in one program call a function in
another program, unless designed to do so?  csound doesnt use a common dll for
the rand() function does it?

also, i think the seed opcode should be put in the manual, as i had the same
problem that i discussed on the list a year ago, and just now i heard of the
seed opcode.

pete

Hello, I'm a new Csounder and I experiment some timing irregularities with
the MIDI OUT opcodes. 

Another strange thing is that when I compile a orc/sco with " -Q0 -n "
or " -Q0 -o /dev/null " as it is indicated in the Linux-midiOUT text file
joigning the 3.48X Linux distribution, all the notes of the score are
read at the same time with no more regards at their placement. 
I have to maintain "-odevaudio" for the things to work.

Is there a way to solve these problems ?  In a score where I
have both a bass drum on the beat (a simple soundin) and a MIDI instrument 
off the beat, the both together are not all right.
 

Francois Ernst.

Thanks to all the Csound Community.


PS: I have OSS Linux and a SB64 gold, RH5 linux 2.0.32 on a 233mhz PPRo/64
    megs

After a long search: 
The solution is to reduce "-b" value. 1024 is the default one, 512 seems
ok. 

A comment should be add in the readme file LINUX_MIDIOUT.TXT

F.ernst