> I use MSys/MinGW, not Cygwin.

Ok, I think I will try that tomorrow. I'm getting annoyed at Cygwin as I can't 
get scons to even fail, and it seems to want to start my windows version of 
python for some wacked reason, ( at least this makes no sense to me ) so I 
don't even know how to get scons to do anything.
 
> ./configure --with-winapi=wmme for PortAudio 19.

What would I use for a linux version with alsa drivers? 

And am I supposed to do a make/make install with portaudio?

I will try and keep notes on my problems so we can write a "compiling csound 5 
for dummies" to get more testers.
 
> I can now get about 40 ms latency with this. I am going to try to make an
> ASIO build, which should do much better.

Midi is not done yet correct? And what's the scoop for piping in line oriented 
score events, should that be functional?

Thanks
Iain


 
> ----- Original Message ----- 
> From: 
> To: "Csound Developers Discussion List" 
> Sent: Thursday, May 06, 2004 11:56 PM
> Subject: [CSOUND-DEV:4600] Re: Csound5 and Portaudio
> 
> 
> > ok, I am joining Andres, but getting stuck even further away. I have been
> > essentially following the instructions in the csound.pdf file.
> >
> > - installed cygwin, no problems
> > - installed cvs, no problems
> > - installed scons, fine
> > - installed libsnd, fine
> >
> > Portaudio, not fine. Now, I know that I don't know what the hell I'm
> doing,
> > but even then, compared to the above this seems bad. I understand we need
> > PA19. I don't really understand what to do beyond "./configure, make,
> make
> > install". The above fails for me using both snapshots on the portaudio
> site
> > and the cvs v19 checkout. Is there something more I need to do that I
> don't
> > know about to install portaudio? Would it perhaps be a good plan for
> csound to
> > host a known good snapshot of portaudio v19 for now considering v19 is
> dev
> on
> > the portaudio site? The problem for me is that I don't know enough to
> know
> > whether I should be hunting through port audio docs to find out what I
> did
> > wrong, or whether the current cvs snapshot just doesn't work.
> >
> > I also don't know which version of portaudio I should be looking through.
> I'm
> > using cygwin but I'm trying to build for windows so I should be using the
> asio
> > right?
> >
> > Sorry for the ignorance!
> > Iain
> >
> >
> 
> 

I use MSys/MinGW, not Cygwin.

./configure --with-winapi=wmme for PortAudio 19.

I can now get about 40 ms latency with this. I am going to try to make an
ASIO build, which should do much better.

----- Original Message ----- 
From: 
To: "Csound Developers Discussion List" 
Sent: Thursday, May 06, 2004 11:56 PM
Subject: [CSOUND-DEV:4600] Re: Csound5 and Portaudio


> ok, I am joining Andres, but getting stuck even further away. I have been
> essentially following the instructions in the csound.pdf file.
>
> - installed cygwin, no problems
> - installed cvs, no problems
> - installed scons, fine
> - installed libsnd, fine
>
> Portaudio, not fine. Now, I know that I don't know what the hell I'm
doing,
> but even then, compared to the above this seems bad. I understand we need
> PA19. I don't really understand what to do beyond "./configure, make, make
> install". The above fails for me using both snapshots on the portaudio
site
> and the cvs v19 checkout. Is there something more I need to do that I
don't
> know about to install portaudio? Would it perhaps be a good plan for
csound to
> host a known good snapshot of portaudio v19 for now considering v19 is dev
on
> the portaudio site? The problem for me is that I don't know enough to know
> whether I should be hunting through port audio docs to find out what I did
> wrong, or whether the current cvs snapshot just doesn't work.
>
> I also don't know which version of portaudio I should be looking through.
I'm
> using cygwin but I'm trying to build for windows so I should be using the
asio
> right?
>
> Sorry for the ignorance!
> Iain
>
>

OK! Good news, I have a rt version of Csound5 (with FLTK!)! My problem was 
that I mistankenly thought the 'portaudio' module in CVS refers to v19, and it 
actually is version 18, so I downloaded a snapshot for v19, did the configure 
and make, and Csound5 compiled and ran trapped in realtime! Great work! 
Csound5 is actually not that hard to build, but it might be good if 
this 'newbie' pitfalls I've encountered could be documented.
Just wanted to add that using -dac0 I got:
Using Portaudio Device 0
PortAudio error -9998: Invalid number of channels

But looking at the list, I notice that outs come after the ins so using dac4 
yields the desired result. What could be confusing is that adc's are listed as 
dac's. It might be good to separate them.

Cheers,
Andres

Hi,
With my new realtime csound5 *grin* I tested a CsoundAV widget csd, but even 
though no error is produced and sound comes out, no widgets window is created.
FLTK is working becuse I see the window with the ftable. Are there differences 
in usage of FLTK in csound5?
Do I need to add a flag to enable FLTK?
The csd from Gabriel's examples:



-odac4



sr=44100
kr=441
ksmps=100
nchnls=1

	FLpanel	"This Panel contains some Buttons",400,300
gk1,ihb2	FLbutton	"This Button activates instr1 for 3 seconds 
giving it a frequency of 150 cps",  150,150, 1,300,50,50,20,    0,1,0,3
gk1,ihb2	FLbutton	"This Light-Button switches the oscillator 
frequency between 100 and 200 cps",  200,100, 2,300,50,50,80,    0,1,0,3
gk1,ihb2	FLbutton	"This Check-Button switches the oscillator 
frequency between 300 and 500 cps",  500,300, 3,300,50,50,150,   0,1,0,3
gk1,ihb2	FLbutton	"This Round-Button switches the oscillator 
frequency between 800 and 1500 cps", 800,1500,4,300,50,50,210,   0,1,0,3
	FLpanelEnd
	FLrun

	instr 1
ampenv	linseg	3000,p3/2,100,p3/2,0
a1	oscili	ampenv, i(gk1), 1
	out	a1
	endin



f1 0 1024 10 1
f0 3600
i1 0 500
e



Cheers,
Andrees

Guy I wish I could do all that work and compile it by myself :)
Josep M

On Sat, 8 May 2004 acabrera@teleset.com.co wrote:

> Just wanted to add that using -dac0 I got:
> Using Portaudio Device 0
> PortAudio error -9998: Invalid number of channels

You are doing better than I!  If I use -o dac0 it runs but the noise is 
horrid.  If I use -o dac1 it just crashes

Found 2 audio devices:
PortAudio device 0
  /dev/dsp
  Maximum channels in:     16
  Maximum channels out:    16
  Default sample rate:  44100.000
PortAudio device 1
  Intel 82801CA-ICH3
  Maximum channels in:      2
  Maximum channels out:     2
  Default sample rate:  44100.000
Using Portaudio Device 1
Suggested PortAudio latency = 0.023220 seconds.
PortAudio error -9993: Illegal combination of I/O devices
unable to open soundcard for audio output

Other values fro dac give no-such-device

==John ff

In my system, when using realtime, I get:

Found 6 audio devices:
PortAudio device 0
  Asignador de sonido de Microsof - Input
  Maximum channels in:      2
  Maximum channels out:     0
  Default sample rate:  44100.000
PortAudio device 1
  Crystal WDM Audio
  Maximum channels in:      2
  Maximum channels out:     0
  Default sample rate:  44100.000
PortAudio device 2
  Mona Analog 1-Digital 8 In
  Maximum channels in:      2
  Maximum channels out:     0
  Default sample rate:  44100.000
PortAudio device 3
  Asignador de sonido de Microsof - Output
  Maximum channels in:      0
  Maximum channels out:     2
  Default sample rate:  44100.000
PortAudio device 4
  Crystal WDM Audio
  Maximum channels in:      0
  Maximum channels out:     2
  Default sample rate:  44100.000
PortAudio device 5
  Mona Analog 1-Digital 8 Out
  Maximum channels in:      0
  Maximum channels out:     2
  Default sample rate:  44100.000
Using Portaudio Device 4
Suggested PortAudio latency = 0.371519 seconds.

The ins and outs appear as separate devices... but it works...=)

Andres