On Tuesday 18 April 2006 8:35 am, Istvan Varga wrote:
> On Tuesday 18 April 2006 16:10, Aaron Krister Johnson wrote:
> > Thanks for your quick reply. I did try PortMidi, and had similar
> > problems. I'll try again.
> >
> > However, if it's not hard, I'm sure not only I but others would benefit
> > from and rejoice at having arbitrary /dev reading of MIDI streams back in
> > the code, instead of a forced standard like ALSA or PortMIDI. After all,
> > the Linux philosophy is about freedom of choice, right? ;)
>
> OK, then it will be added in 5.02. Did you have success with any of the
> suggested workarounds ?

That would be most excellent!

I'm going to give the alternatives another shot when I have a moment tonight. 
I took a *long* time on them last night, and I dread another disappointing 
session of problem-solving ahead, so.....oh heck, I'll try them while a have 
1/2 hour now. I'll let you know what happens, and I'll post the text of the 
session if that would help.

> > One other major issue I noticed was that "-+rtaudio=alsa" seems broken,
> > in that if I open my score with a dummy ftable for say 1000 seconds like
> > so:
> >
> >  f0 1000
> >  e
> >
> > ...then run it, my performance time is only a few seconds.
>
> There can be a number of reasons why this could happen; it would be easier
> to find out if the Csound console messages were posted. Also, if you cannot
> get ALSA to work, you can still use PortAudio or JACK.

Has anyone else gotten the alsa driver to work?

One thing I wanted to say was this--it's a poor choice to have the INSTALL or 
README docs about how to build with Scons refer to online documentation as 
csounds.com or whatever--it ought to be packaged with the source--why make 
the user jump through another hoop? What if they can't get online for some 
reason? 

It also says to refer to the docs in the "/doc" directory of the build, 
logically enough, but then you look there, and you have a strange lone 
"doxygen.sty" file in the "latex" folder, and no instructions anywhere on how 
to build the docs (apparantly, this needs to be built too?) I sure didn't 
know what to do, and it's bad practice to assume a certain level of knowledge 
on the part of the user of such things.....hand holding is good...even for 
seasoned Linux users it is (and I've been using Linux since 1997)...there's 
always something new to learn...scons, for instance (it was new to me--the 
first time I encountered it was csound5). New standards come and compete with 
old. People get used to the "difficult" old, and the "easy" new seems 
"difficult". cvs, for example, to me, is so hopelessly baroque and 
user-unfriendly, I prefer tarballs by far, but I won't go there.....

Whoever puts together these source packages *might* want to think about 
that---this is why people shy away from open source projects alot. The entire 
open source movement almost has a blindness to the importance of easy to use 
and existent docs!

Best,
Aaron.


-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net