Hello everyone,

I'm going to start distributing pieces built with processing and
Csound. To do this right, I'm going to need to include proper
documentation so people can install Csound on their computers, and
install the csnd.jar file in the proper location. I'm on OS X, so I
have this OS covered. However, I'm not sure if the windows and linux
distributions include csnd.jar, and if they do, where to find it once
installed. Could anyone possibly help me out on this?

Best,
Jake

I believe there is currently issues with linking to cnsd.jar on linux.
There was a bug report sent to cs-dev about it. I've just finished a
few pieces using Processing and Csound although I chose to use OSC
instead. I'm interested to see how your pieces turned out. Keep us
posted.

Rory.


On 3 August 2010 05:06, Jacob Joaquin  wrote:
> Hello everyone,
>
> I'm going to start distributing pieces built with processing and
> Csound. To do this right, I'm going to need to include proper
> documentation so people can install Csound on their computers, and
> install the csnd.jar file in the proper location. I'm on OS X, so I
> have this OS covered. However, I'm not sure if the windows and linux
> distributions include csnd.jar, and if they do, where to find it once
> installed. Could anyone possibly help me out on this?
>
> Best,
> Jake
> --
> The Csound Blog - http://csound.noisepages.com/
> Slipmat - http://slipmat.noisepages.com/
>
>
> 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"
>
>


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 Tue, Aug 3, 2010 at 4:04 AM, Rory Walsh  wrote:
> I believe there is currently issues with linking to cnsd.jar on linux.
> There was a bug report sent to cs-dev about it. I've just finished a
> few pieces using Processing and Csound although I chose to use OSC
> instead. I'm interested to see how your pieces turned out. Keep us
> posted.

Hopefully this linux issue only temporary. :)

I would love to see Processing become a viable platform for creating
musical apps and interactive pieces with Csound. The big issue so far
is getting people to install Csound and copying csnd.jar to the right
place. It's a fairly straight forward process on OS X, though I'm
unsure about windows and linux. I think the API is a must since using
OSC I think would turn off people because of the extra steps. The API,
once set up, is fairly seamless.

Beyond this, I'll probably develop a class or a set of Java classes to
allow simplified interfacing between Processing and Csound so others
can jump right in.

I did put up video of one piece a couple of days ago at The Csound Blog:
http://csoundblog.com/2010/08/csound-processing-experiment-i/

Best,
Jake

The Windows installer can install csnd.jar.

Regards,
Mike

On Tue, Aug 3, 2010 at 12:58 PM, Jacob Joaquin  wrote:
> On Tue, Aug 3, 2010 at 4:04 AM, Rory Walsh  wrote:
>> I believe there is currently issues with linking to cnsd.jar on linux.
>> There was a bug report sent to cs-dev about it. I've just finished a
>> few pieces using Processing and Csound although I chose to use OSC
>> instead. I'm interested to see how your pieces turned out. Keep us
>> posted.
>
> Hopefully this linux issue only temporary. :)
>
> I would love to see Processing become a viable platform for creating
> musical apps and interactive pieces with Csound. The big issue so far
> is getting people to install Csound and copying csnd.jar to the right
> place. It's a fairly straight forward process on OS X, though I'm
> unsure about windows and linux. I think the API is a must since using
> OSC I think would turn off people because of the extra steps. The API,
> once set up, is fairly seamless.
>
> Beyond this, I'll probably develop a class or a set of Java classes to
> allow simplified interfacing between Processing and Csound so others
> can jump right in.
>
> I did put up video of one piece a couple of days ago at The Csound Blog:
> http://csoundblog.com/2010/08/csound-processing-experiment-i/
>
> Best,
> Jake
> --
> The Csound Blog - http://csound.noisepages.com/
> Slipmat - http://slipmat.noisepages.com/
>
>
> 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"
>
>



-- 
Michael Gogins
Irreducible Productions
http://www.michael-gogins.com
Michael dot Gogins at gmail dot com


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"

One of my students is working on a Csound lib for processing. It's
part of a bigger project but it might prove useful. I assume it'll
simply provide an easier way to interact with Csound from processing.
OSC is a bit of a pain, no doubt about that.

Rory.



On 3 August 2010 18:14, Michael Gogins  wrote:
> The Windows installer can install csnd.jar.
>
> Regards,
> Mike
>
> On Tue, Aug 3, 2010 at 12:58 PM, Jacob Joaquin  wrote:
>> On Tue, Aug 3, 2010 at 4:04 AM, Rory Walsh  wrote:
>>> I believe there is currently issues with linking to cnsd.jar on linux.
>>> There was a bug report sent to cs-dev about it. I've just finished a
>>> few pieces using Processing and Csound although I chose to use OSC
>>> instead. I'm interested to see how your pieces turned out. Keep us
>>> posted.
>>
>> Hopefully this linux issue only temporary. :)
>>
>> I would love to see Processing become a viable platform for creating
>> musical apps and interactive pieces with Csound. The big issue so far
>> is getting people to install Csound and copying csnd.jar to the right
>> place. It's a fairly straight forward process on OS X, though I'm
>> unsure about windows and linux. I think the API is a must since using
>> OSC I think would turn off people because of the extra steps. The API,
>> once set up, is fairly seamless.
>>
>> Beyond this, I'll probably develop a class or a set of Java classes to
>> allow simplified interfacing between Processing and Csound so others
>> can jump right in.
>>
>> I did put up video of one piece a couple of days ago at The Csound Blog:
>> http://csoundblog.com/2010/08/csound-processing-experiment-i/
>>
>> Best,
>> Jake
>> --
>> The Csound Blog - http://csound.noisepages.com/
>> Slipmat - http://slipmat.noisepages.com/
>>
>>
>> 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"
>>
>>
>
>
>
> --
> Michael Gogins
> Irreducible Productions
> http://www.michael-gogins.com
> Michael dot Gogins at gmail dot com
>
>
> 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"
>
>


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 Tue, Aug 3, 2010 at 11:08 AM, Rory Walsh  wrote:
> One of my students is working on a Csound lib for processing. It's
> part of a bigger project but it might prove useful. I assume it'll
> simply provide an easier way to interact with Csound from processing.
> OSC is a bit of a pain, no doubt about that.

That definitely could prove to be useful. I'm very early on in my
thinking on this, but I figured I'd just create a java class that only
does the basics. Such as loading a CSD, starting/stopping, generate
events, pass info back and forth between busses and tables, etc while
doing same auto-management. Then if people required more of what the
API has to offer, then they could create a child class. Or
alternatively, I could make the instance of the Csound object public
so people could have direct access. Though that might be a bit sloppy
for my tastes.

Since this would be a Java class, it could be used for other things
like arduino or just straight up Java.

If you think your student might be interested in developing something
for the greater public good, perhaps point him over to this thread, or
have him send me an email. I would certainly give credit where credit
is due if this thing happens.

Best,
Jake

It is completely appropriate to use csnd.jar for this kind of thing,
that is what it is for. I and others have used csnd.jar in just this
way. This may indeed be the best way to go.

Nevertheless, when writing an extension for an existing system, there
is the alternative of more directly calling the C or C++ Csound API
using a foreign function interface (FFI). In this approach, you simply
write Processing code, and whenever you need to call the Csound C or
C++ API, you just use the Java FFI (JFFI) library to make these calls
directly from Java.

I have not used JFFI, and I do not know how finished or reliable it
is, but my experience with foreign function interfaces in other
languages such as Python, C#, and Lisp is that they can in some cases
provide a better solution. In particular, you wouldn't need csnd.jar
at all.

Csnd.jar uses wrapper classes generated by SWIG using the Java Native
Interface (JNI) The difference between JNI and JFFI is that JNI calls
must be compiled before running the program, but foreign function
interface calls are constructed dynamically as the program runs.

If you have questions, ask away.

Regards,
Mike


On Tue, Aug 3, 2010 at 2:08 PM, Rory Walsh  wrote:
> One of my students is working on a Csound lib for processing. It's
> part of a bigger project but it might prove useful. I assume it'll
> simply provide an easier way to interact with Csound from processing.
> OSC is a bit of a pain, no doubt about that.
>
> Rory.
>
>
>
> On 3 August 2010 18:14, Michael Gogins  wrote:
>> The Windows installer can install csnd.jar.
>>
>> Regards,
>> Mike
>>
>> On Tue, Aug 3, 2010 at 12:58 PM, Jacob Joaquin  wrote:
>>> On Tue, Aug 3, 2010 at 4:04 AM, Rory Walsh  wrote:
>>>> I believe there is currently issues with linking to cnsd.jar on linux.
>>>> There was a bug report sent to cs-dev about it. I've just finished a
>>>> few pieces using Processing and Csound although I chose to use OSC
>>>> instead. I'm interested to see how your pieces turned out. Keep us
>>>> posted.
>>>
>>> Hopefully this linux issue only temporary. :)
>>>
>>> I would love to see Processing become a viable platform for creating
>>> musical apps and interactive pieces with Csound. The big issue so far
>>> is getting people to install Csound and copying csnd.jar to the right
>>> place. It's a fairly straight forward process on OS X, though I'm
>>> unsure about windows and linux. I think the API is a must since using
>>> OSC I think would turn off people because of the extra steps. The API,
>>> once set up, is fairly seamless.
>>>
>>> Beyond this, I'll probably develop a class or a set of Java classes to
>>> allow simplified interfacing between Processing and Csound so others
>>> can jump right in.
>>>
>>> I did put up video of one piece a couple of days ago at The Csound Blog:
>>> http://csoundblog.com/2010/08/csound-processing-experiment-i/
>>>
>>> Best,
>>> Jake
>>> --
>>> The Csound Blog - http://csound.noisepages.com/
>>> Slipmat - http://slipmat.noisepages.com/
>>>
>>>
>>> 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"
>>>
>>>
>>
>>
>>
>> --
>> Michael Gogins
>> Irreducible Productions
>> http://www.michael-gogins.com
>> Michael dot Gogins at gmail dot com
>>
>>
>> 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"
>>
>>
>
>
> 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"
>
>



-- 
Michael Gogins
Irreducible Productions
http://www.michael-gogins.com
Michael dot Gogins at gmail dot com


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 do not think it is sloppy to provide access to the Csound object in
this case. Nobody will bother with it unless they need it, but if they
need it, there it is.

The CppSound class in Java already can load and save CSDs. The
CppSound.getCsoundFile() method provides access to the CsoundFile
class in CppSound. In C++, this is a base class, in Java, it has to be
exposed as a separate class because Java does not support multiple
inheritance.

So, you may be able to write a new class in Java that inherits from
CppSound, or contains an instance of CppSound.

Regards,
Mike

On Tue, Aug 3, 2010 at 2:58 PM, Jacob Joaquin  wrote:
> On Tue, Aug 3, 2010 at 11:08 AM, Rory Walsh  wrote:
>> One of my students is working on a Csound lib for processing. It's
>> part of a bigger project but it might prove useful. I assume it'll
>> simply provide an easier way to interact with Csound from processing.
>> OSC is a bit of a pain, no doubt about that.
>
> That definitely could prove to be useful. I'm very early on in my
> thinking on this, but I figured I'd just create a java class that only
> does the basics. Such as loading a CSD, starting/stopping, generate
> events, pass info back and forth between busses and tables, etc while
> doing same auto-management. Then if people required more of what the
> API has to offer, then they could create a child class. Or
> alternatively, I could make the instance of the Csound object public
> so people could have direct access. Though that might be a bit sloppy
> for my tastes.
>
> Since this would be a Java class, it could be used for other things
> like arduino or just straight up Java.
>
> If you think your student might be interested in developing something
> for the greater public good, perhaps point him over to this thread, or
> have him send me an email. I would certainly give credit where credit
> is due if this thing happens.
>
> Best,
> Jake
> --
> The Csound Blog - http://csound.noisepages.com/
> Slipmat - http://slipmat.noisepages.com/
>
>
> 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"
>
>



-- 
Michael Gogins
Irreducible Productions
http://www.michael-gogins.com
Michael dot Gogins at gmail dot com


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 definitely want things to be as easy as possible, so I will probably
end up not restricting access to the Csound object. Especially since
Processing culture sets most everything to public, anyways. I'm also
looking into JFFI. If this is simpler for the end-user, then I'm all
for it.

This is where am at right now. Though this very rudimentary, it will
hopefully get across some of my philosophy on how simple I want it for
end-users to interface with Csound.  This is an example of getting
Csound up and running in Processing with my MyCsound class.

MyCsound cs;

void setup() {
    size(640, 480);
    cs = new MyCsound(sketchPath("synth.csd"));
    cs.start();
}


That's about as streamlined as I think I could make it, minus having
the constructor start itself.  As for MySound class:


import csnd.*;

class MyCsound extends Thread {
    private Csound csound;
    private String csd;

    MyCsound(String file) { csd = file; }

    public void run() {
        if (csound == null) {
            csnd.csoundInitialize(null, null,
                                  csnd.CSOUNDINIT_NO_SIGNAL_HANDLER);
            csound = new Csound();
            int compile = csound.Compile(csd);
            if (compile == 0) { while(csound.PerformKsmps() == 0) {} }
        }
    }

    public void score_event(String s) { csound.InputMessage(s); }
}


I doubt this will stay a subclass of Thread. But it might, as it's too
early to rule anything out.

Best,
Jake

Thanks Jacob, and Mike, I'll point my student towards this thread!

On 3 August 2010 19:58, Jacob Joaquin  wrote:
> On Tue, Aug 3, 2010 at 11:08 AM, Rory Walsh  wrote:
>> One of my students is working on a Csound lib for processing. It's
>> part of a bigger project but it might prove useful. I assume it'll
>> simply provide an easier way to interact with Csound from processing.
>> OSC is a bit of a pain, no doubt about that.
>
> That definitely could prove to be useful. I'm very early on in my
> thinking on this, but I figured I'd just create a java class that only
> does the basics. Such as loading a CSD, starting/stopping, generate
> events, pass info back and forth between busses and tables, etc while
> doing same auto-management. Then if people required more of what the
> API has to offer, then they could create a child class. Or
> alternatively, I could make the instance of the Csound object public
> so people could have direct access. Though that might be a bit sloppy
> for my tastes.
>
> Since this would be a Java class, it could be used for other things
> like arduino or just straight up Java.
>
> If you think your student might be interested in developing something
> for the greater public good, perhaps point him over to this thread, or
> have him send me an email. I would certainly give credit where credit
> is due if this thing happens.
>
> Best,
> Jake
> --
> The Csound Blog - http://csound.noisepages.com/
> Slipmat - http://slipmat.noisepages.com/
>
>
> 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"
>
>


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"