Finally managed to build a version of The Csoundo Processing Library
that supports doubles. This may also require that Csound be compiled
for 32-bit mode.

Csoundo 0.1.2.double:
http://github.com/jacobjoaquin/Csoundo/downloads

If anyone tries it, please let me know if it works or doesn't, and a
brief description of your system and version of Csound you're running.

Thanks!
Jake

The last version had a glaring error.  Here's the new package with the fix:

http://github.com/downloads/jacobjoaquin/Csoundo/csoundo-0.1.2.double.1.zip

Best,
Jake

Francois PINOT wrote:

> Works fine here. Ubuntu 10.4, csound5.12 double built from CVS. I 
> followed the instructions from the README file. 

Ditto. And the fun begins. Your examples have been working well, they'll 
function nicely as guides into the Proceesing/Csound connection.

> Great job Jake!

Indeed, and thanks for this little helper.

Btw, is there any easy way to let it know that I'd rather use JACK 
instead of PortAudio ? I can recompile if necessary.

Best,

dp



Send bugs reports to the Sourceforge bug tracker
            https://sourceforge.net/tracker/?group_id=81968&atid=564599
Discussions of bugs and features can be posted here
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

On Fri, Sep 3, 2010 at 4:06 AM, Dave Phillips  wrote:
> Btw, is there any easy way to let it know that I'd rather use JACK instead
> of PortAudio ? I can recompile if necessary.

I've not used JACK with Csound myself. Though if it's a command-line
option, you can use the method setOptions().  For example:


cs = new Csoundo(this, "foo.csd");
cs.setOptions("-d -odac");  // Change command-line options here
cs.run();


In some future version of Csoundo, I will allow users to create a
configuration file similar to .csoundrc, so that people can set up
their system once, and not then not have to worry about it.

Best,
Jake

Jacob Joaquin wrote:
> On Fri, Sep 3, 2010 at 4:06 AM, Dave Phillips  wrote:
>   
>> Btw, is there any easy way to let it know that I'd rather use JACK instead
>> of PortAudio ? I can recompile if necessary.
>>     
>
> I've not used JACK with Csound myself. Though if it's a command-line
> option, you can use the method setOptions().  For example:
>
>
> cs = new Csoundo(this, "foo.csd");
> cs.setOptions("-d -odac");  // Change command-line options here
> cs.run();
>   

That's great, thanks. This setting worked fine :

cs.setOptions("-+rtaudio=jack -odac:system:playback_ ")


>
> In some future version of Csoundo, I will allow users to create a
> configuration file similar to .csoundrc, so that people can set up
> their system once, and not then not have to worry about it.
>   

Would also be nice.

Btw, your example experiment_1 blows up when I run it. The display 
window opens for a moment then immediately closes. Any suggestions ? The 
only error message is a segfault notice from Csound on exit.

Best,

dp



Send bugs reports to the Sourceforge bug tracker
            https://sourceforge.net/tracker/?group_id=81968&atid=564599
Discussions of bugs and features can be posted here
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

On Fri, Sep 3, 2010 at 9:48 AM, Dave Phillips  wrote:
> Btw, your example experiment_1 blows up when I run it. The display window
> opens for a moment then immediately closes. Any suggestions ? The only error
> message is a segfault notice from Csound on exit.

And it's my favorite public example, too. :)

It's the oldest example, so maybe I need to update something in the
code, though it does work on my system.  Can you do me a favor and set
IS_SOUND_ON to false in experiment_1.pde? This will let me know if
it's truly a Csoundo issue (which I suspect it is), and not a
Processing issue.

Best,
Jake

Jacob Joaquin wrote:
> On Fri, Sep 3, 2010 at 9:48 AM, Dave Phillips  wrote:
>   
>> Btw, your example experiment_1 blows up when I run it. The display window
>> opens for a moment then immediately closes. Any suggestions ? The only error
>> message is a segfault notice from Csound on exit.
>>     
>
> And it's my favorite public example, too. :)
>
> It's the oldest example, so maybe I need to update something in the
> code, though it does work on my system.  Can you do me a favor and set
> IS_SOUND_ON to false in experiment_1.pde? This will let me know if
> it's truly a Csoundo issue (which I suspect it is), and not a
> Processing issue.
>   

Thanks for the tip. I changed the value, the display starts but freezes 
immediately with an error regarding the cs.event line in the Animation 
code. I'm waiting for a student now, I'll have to send the exact message 
later.

Btw, Rory's 'random' code works fine.

Best,

dp



Send bugs reports to the Sourceforge bug tracker
            https://sourceforge.net/tracker/?group_id=81968&atid=564599
Discussions of bugs and features can be posted here
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

> I changed the value, the display starts but freezes
> immediately with an error regarding the cs.event line in the Animation code.

My memory of the code was slightly off. The reason it's breaking now
is because the sketch calls cs.event() when cs hasn't been
instantiated.

In addition to changing IS_SOUND_ON to false, can you comment out
"sound();" in line 74  of Animation.pde. This ensure that Csoundo
doesn't run and that a cs.event() isn't called. Then we'll know for
sure if it's Csoundo or not causing the problem.

There is another example that uses Csoundo.event() called event.pde.
Does this one work for you?

Best,
Jake

Jacob Joaquin wrote:
>> I changed the value, the display starts but freezes
>> immediately with an error regarding the cs.event line in the Animation code.
>>     
>
> My memory of the code was slightly off. The reason it's breaking now
> is because the sketch calls cs.event() when cs hasn't been
> instantiated.
>
> In addition to changing IS_SOUND_ON to false, can you comment out
> "sound();" in line 74  of Animation.pde. This ensure that Csoundo
> doesn't run and that a cs.event() isn't called. Then we'll know for
> sure if it's Csoundo or not causing the problem.
>   

Okay, the graphics display without problem after making those changes.


> There is another example that uses Csoundo.event() called event.pde.
> Does this one work for you?
>
>   

Works perfectly.

Best,

dp



Send bugs reports to the Sourceforge bug tracker
            https://sourceforge.net/tracker/?group_id=81968&atid=564599
Discussions of bugs and features can be posted here
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

On Sun, Sep 5, 2010 at 8:27 AM, Dave Phillips  wrote:
> Okay, the graphics display without problem after making those changes.

One thing it might be is that Csound isn't finished starting by the
time the first frame is drawn, which could cause the crash. This
should be fixed once I have memory protection and thread locking built
into Csoundo. Though it might be something else. I'll take a long look
at the code.

Best,
Jake

On Sun, Sep 5, 2010 at 5:22 PM, Brian Wong  wrote:
> I do have a suggestion; a basic .sco +/or .csd
> reader that can be used to grab pfield values for timing and numbers. This
> would give us a simple non-realtime way to sync up and control Processing
> video with our disk-rendered pieces.

Thanks for the suggestion. Being able to use Csoundo in non-realtime
as well will allow others to create some elaborate processor intensive
pieces for playback. One thing that could be done now is to have
Processing generate a Csound score.  A custom method may be called
like this:

printToScore("i 1 " + ((float) frameCount / (float) frameRate) + " 1
0.707 440");

where the current frame divided by the frameRate would give the start time.

Best,
Jake