[pulseaudio-discuss] Csound

[Sergio]

Hi Colin,



Thank's !


 > I'm assuming that things just die after this?

Yes : after "I: Creating new entry for <pulsecore/protocol-native.c$csound>"


 > the client app locks up?

Yes.


 > If so, a few questions:
 >  1. When the csound client is locked, can you run paplay OK and the
 >     server responds or has it now been locked too?

Yes, paplay fine OK :

I: Daemon startup complete.
I: Unloading "module-detect" (index: #1).
I: Unloaded "module-detect" (index: #1).
   = Pulsaudio initialisation released ;
   
I: created 0 "Native client (UNIX socket client)"
I: client 0 changed name from "Native client (UNIX socket client)" to 
"csound"
I: created 0 "csound-out" on solaris_output with sample spec float32le 
2ch 44100Hz
I: Creating new entry for <pulsecore/protocol-native.c$csound>
   = realtime render for Csound launched (and locked) ;

I: created 1 "Native client (UNIX socket client)"
I: client 1 changed name from "Native client (UNIX socket client)" to 
"paplay"
I: created 1 "/export/home/user/scwk/scmu/lindau.wav" on solaris_output 
with sample spec s16be 2ch 44100Hz
I: Creating new entry for <pulsecore/protocol-native.c$paplay>
   = Paplay still playing another file called "lindau.wav" ;

I: freed 1 "/export/home/user/scwk/scmu/lindau.wav"
I: freed 1 "paplay"
   = lindau.wav released ;

I: freed 0 "csound-out"
I: freed 0 "csound"
   = realtime Csound session killed manually.


 >  2. (assuming server lock in 1.) If you kill the csound client, does
 >     the server recover?

No problem in all cases, i can kill and relaunch my csound client every 
time i want, even while Paplay is working.


 >  3. Can you connect to either the client or the server in gdb and get a
 >     backtrace?

Unfortunately no.

On the client i get :

(gdb) run -+rtaudio=pulse -o dac examples/xanadu.csd
Starting program: /export/home/root/Csound5.09.0.cc.64/csound 
-+rtaudio=pulse -o dac examples/xanadu.csd
procfs:4285 -- process not stopped.
procfs: ...giving up...

and nothing after.


On the server i get :

(gdb) run -v
Starting program: /usr/local/bin/sparcv9/pulseaudio/pulseaudio -v
procfs: target_wait (wait_for_stop) line 3934, /proc/1712: Resource 
temporarily unavailable.

and nothing after.



 > I'm guessing that something has entered a deadlocked state and that's
  why things are freezing.
 
Yes, however i get really communication between the client and the 
server. With another csound example file i get even like any parasite 
sound in my speakers (but locks also immediately after), that means the 
hope exists...


 > Hopefully it will provide some insight into the csound implementation
 > and can point the way to a fix.

Yes, but the Pulseaudio Csound module works, as i readed from the team, 
fine on Linux. Other hand, from my Csound port on Solaris now i can 
still get a right output to disk as .wav file. For these reasons i think 
that the realtime render on Pulseaudio is already possible, probably 
configuring something as needed.



Cheers,

Sergio