Csound Csound-dev Csound-tekno Search About

[Csnd] Csound Wiki

Date2013-07-31 11:39
FromSteven Yi
Subject[Csnd] Csound Wiki
Hi All,

Just FYI, I've updated the Csound Wiki page on Sourceforge:

https://sourceforge.net/p/csound/wiki/Home/

I've added a section on the home page for installation/buildilng that
links to the existing Homebrew page, as well as have added a page on
buliding and installation for Debian/Ubuntu.

I think it'd be be great for the site to have information like Bernt's
latest on Raspberry Pi settings, etc. all collected in the Wiki.  If
you'd like to contribute, please email me and I can look at setting
you up as a wiki contributor.

Thanks!
steven

Date2013-07-31 16:56
FromDavid Akbari
SubjectRe: [Csnd] Csound Wiki
Hello Steven,

Would it be appropriate to use this Wiki resource to document steps to using non-GNU compilers (i.e. Intel icc / icpc)? It seems that this model would be more efficient than maintaining a separate text file in the canonical repository.

What about posting performance systems that account for non-Csound related things that can influence success with Csound? For example common operating system issues, performance settings, alternate controller, and systems design considerations. This might be a nice way to add additional details to certain opcodes and algorithms that would otherwise be inappropriate in the manual or don't highlight the features of one opcode specifically.

If the answer is yes to one or both of these questions I would like to contribute information to this Wiki. If no, then I will continue using the canonical and UDO repositories only.

Cheers,
David


On Wed, Jul 31, 2013 at 5:39 AM, Steven Yi <stevenyi@gmail.com> wrote:
Hi All,

Just FYI, I've updated the Csound Wiki page on Sourceforge:

https://sourceforge.net/p/csound/wiki/Home/

I've added a section on the home page for installation/buildilng that
links to the existing Homebrew page, as well as have added a page on
buliding and installation for Debian/Ubuntu.

I think it'd be be great for the site to have information like Bernt's
latest on Raspberry Pi settings, etc. all collected in the Wiki.  If
you'd like to contribute, please email me and I can look at setting
you up as a wiki contributor.

Thanks!
steven


Send bugs reports to the Sourceforge bug trackers
csound6:
            https://sourceforge.net/p/csound/tickets/
csound5:
            https://sourceforge.net/p/csound/bugs/
Discussions of bugs and features can be posted here
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"




Date2013-07-31 17:09
FromSteven Yi
SubjectRe: [Csnd] Csound Wiki
Hi Dave,

It's a public wiki so I think whatever the community wants in it is
appropriate.  That said, I think the things you mentioned all sound
good.  I think we should still target the manual for all reference
information, and the UDO repository should be for downloadable UDO's.

I also think we should consider it an experiment and feel free to
enter in information which seems appropriate.  Over time, we can
re-evaluate and move things to the FLOSS manual, to the Csound
Reference manual, etc. if they seem like better places for it.  But at
least for the interim, we can capture useful information somewhere.

Thanks!
steven

On Wed, Jul 31, 2013 at 5:56 PM, David Akbari  wrote:
> Hello Steven,
>
> Would it be appropriate to use this Wiki resource to document steps to using
> non-GNU compilers (i.e. Intel icc / icpc)? It seems that this model would be
> more efficient than maintaining a separate text file in the canonical
> repository.
>
> What about posting performance systems that account for non-Csound related
> things that can influence success with Csound? For example common operating
> system issues, performance settings, alternate controller, and systems
> design considerations. This might be a nice way to add additional details to
> certain opcodes and algorithms that would otherwise be inappropriate in the
> manual or don't highlight the features of one opcode specifically.
>
> If the answer is yes to one or both of these questions I would like to
> contribute information to this Wiki. If no, then I will continue using the
> canonical and UDO repositories only.
>
> Cheers,
> David
>
>
> On Wed, Jul 31, 2013 at 5:39 AM, Steven Yi  wrote:
>>
>> Hi All,
>>
>> Just FYI, I've updated the Csound Wiki page on Sourceforge:
>>
>> https://sourceforge.net/p/csound/wiki/Home/
>>
>> I've added a section on the home page for installation/buildilng that
>> links to the existing Homebrew page, as well as have added a page on
>> buliding and installation for Debian/Ubuntu.
>>
>> I think it'd be be great for the site to have information like Bernt's
>> latest on Raspberry Pi settings, etc. all collected in the Wiki.  If
>> you'd like to contribute, please email me and I can look at setting
>> you up as a wiki contributor.
>>
>> Thanks!
>> steven
>>
>>
>> Send bugs reports to the Sourceforge bug trackers
>> csound6:
>>             https://sourceforge.net/p/csound/tickets/
>> csound5:
>>             https://sourceforge.net/p/csound/bugs/
>> Discussions of bugs and features can be posted here
>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
>> csound"
>>
>>
>

Date2013-07-31 20:09
FromMichael Rhoades
Subject[Csnd] Winsound for Mac
Hello,

Can anyone tell me where I can find Winsound for the MAC? As I 
understand it, it used to be part of the Csound download but is not any 
longer.

Any help would be appreciated.

Thanks,

Michael



Date2013-07-31 20:59
FromAnthony Palomba
SubjectRe: [Csnd] Winsound for Mac


On Wed, Jul 31, 2013 at 2:09 PM, Michael Rhoades <mrhoades@perceptionfactory.com> wrote:
Hello,

Can anyone tell me where I can find Winsound for the MAC? As I understand it, it used to be part of the Csound download but is not any longer.

Any help would be appreciated.

Thanks,

Michael




Send bugs reports to the Sourceforge bug trackers
csound6:
           https://sourceforge.net/p/csound/tickets/
csound5:
           https://sourceforge.net/p/csound/bugs/
Discussions of bugs and features can be posted here
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"




Date2013-07-31 23:05
FromMichael Rhoades
SubjectRe: [Csnd] Winsound for Mac
Thanks Anthony... but that is not what I am looking for. Winsound and 
Csound5GUI both were distributed with Csound 5. I just downloaded 5.19 
for a new laptop and it did not include the folder that was called 
"Csound 5 Frontends", which used to contain the apps I am looking for. 
Does anyone know what version of Csound 5 had that folder with the 
installer?

The reason I am looking for it is that I will be teaching part of a 
synthesis course this fall with Csound and want to keep the interface 
and overall interaction ultimately simple for the students.

Wxsound is fantastic by the way...

Michael




On 7/31/13 3:59 PM, Anthony Palomba wrote:
> http://winxound.codeplex.com/
>
>
> On Wed, Jul 31, 2013 at 2:09 PM, Michael Rhoades 
>  > wrote:
>
>     Hello,
>
>     Can anyone tell me where I can find Winsound for the MAC? As I
>     understand it, it used to be part of the Csound download but is
>     not any longer.
>
>     Any help would be appreciated.
>
>     Thanks,
>
>     Michael
>
>
>
>
>     Send bugs reports to the Sourceforge bug trackers
>     csound6:
>     https://sourceforge.net/p/csound/tickets/
>     csound5:
>     https://sourceforge.net/p/csound/bugs/
>     Discussions of bugs and features can be posted here
>     To unsubscribe, send email sympa@lists.bath.ac.uk
>      with body "unsubscribe csound"
>
>
>


Date2013-08-01 09:50
FromBernt Isak Wærstad
SubjectRe: [Csnd] Csound Wiki
My Raspberry PI investigations are part of larger project making a Csound stomp box together with Kim and Alex (we call it the COSMO project - Csound on Stage : Music Operator) where we are collecting data to make a comprehensive wiki of how to build this box. Since it will contain a lot of Linux and hardware/circuit specifics it's better to place this wiki outside the source forge wiki or FLOSS manuals, but we could easy make a subset of how to make Csound run on a Raspberry PI to put in either of those places (maybe with a link to the whole COSMO project wiki). 

Any suggestions for a good place to put such a wiki btw?

On Wed, Jul 31, 2013 at 6:09 PM, Steven Yi <stevenyi@gmail.com> wrote:
Hi Dave,

It's a public wiki so I think whatever the community wants in it is
appropriate.  That said, I think the things you mentioned all sound
good.  I think we should still target the manual for all reference
information, and the UDO repository should be for downloadable UDO's.

I also think we should consider it an experiment and feel free to
enter in information which seems appropriate.  Over time, we can
re-evaluate and move things to the FLOSS manual, to the Csound
Reference manual, etc. if they seem like better places for it.  But at
least for the interim, we can capture useful information somewhere.

Thanks!
steven

On Wed, Jul 31, 2013 at 5:56 PM, David Akbari <dakbari@gmail.com> wrote:
> Hello Steven,
>
> Would it be appropriate to use this Wiki resource to document steps to using
> non-GNU compilers (i.e. Intel icc / icpc)? It seems that this model would be
> more efficient than maintaining a separate text file in the canonical
> repository.
>
> What about posting performance systems that account for non-Csound related
> things that can influence success with Csound? For example common operating
> system issues, performance settings, alternate controller, and systems
> design considerations. This might be a nice way to add additional details to
> certain opcodes and algorithms that would otherwise be inappropriate in the
> manual or don't highlight the features of one opcode specifically.
>
> If the answer is yes to one or both of these questions I would like to
> contribute information to this Wiki. If no, then I will continue using the
> canonical and UDO repositories only.
>
> Cheers,
> David
>
>
> On Wed, Jul 31, 2013 at 5:39 AM, Steven Yi <stevenyi@gmail.com> wrote:
>>
>> Hi All,
>>
>> Just FYI, I've updated the Csound Wiki page on Sourceforge:
>>
>> https://sourceforge.net/p/csound/wiki/Home/
>>
>> I've added a section on the home page for installation/buildilng that
>> links to the existing Homebrew page, as well as have added a page on
>> buliding and installation for Debian/Ubuntu.
>>
>> I think it'd be be great for the site to have information like Bernt's
>> latest on Raspberry Pi settings, etc. all collected in the Wiki.  If
>> you'd like to contribute, please email me and I can look at setting
>> you up as a wiki contributor.
>>
>> Thanks!
>> steven
>>
>>
>> Send bugs reports to the Sourceforge bug trackers
>> csound6:
>>             https://sourceforge.net/p/csound/tickets/
>> csound5:
>>             https://sourceforge.net/p/csound/bugs/
>> 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 trackers
csound6:
            https://sourceforge.net/p/csound/tickets/
csound5:
            https://sourceforge.net/p/csound/bugs/
Discussions of bugs and features can be posted here
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"





--
Mvh.

Bernt Isak Wærstad



Date2013-08-01 11:43
FromSteven Yi
SubjectRe: [Csnd] Csound Wiki
Hi Bernt,

Have you though to create an open source project on Github, Bitbucket,
or Sourceforge?  All of these platforms have wiki's as part of their
project systems. If you did that then it seems like it'd be good to do
as you say, add a basic intro page about Raspberry PI and link to
COSMO from there.

Cheers!
steven

On Thu, Aug 1, 2013 at 10:50 AM, Bernt Isak Wærstad  wrote:
> My Raspberry PI investigations are part of larger project making a Csound
> stomp box together with Kim and Alex (we call it the COSMO project - Csound
> on Stage : Music Operator) where we are collecting data to make a
> comprehensive wiki of how to build this box. Since it will contain a lot of
> Linux and hardware/circuit specifics it's better to place this wiki outside
> the source forge wiki or FLOSS manuals, but we could easy make a subset of
> how to make Csound run on a Raspberry PI to put in either of those places
> (maybe with a link to the whole COSMO project wiki).
>
> Any suggestions for a good place to put such a wiki btw?
>
>
> On Wed, Jul 31, 2013 at 6:09 PM, Steven Yi  wrote:
>>
>> Hi Dave,
>>
>> It's a public wiki so I think whatever the community wants in it is
>> appropriate.  That said, I think the things you mentioned all sound
>> good.  I think we should still target the manual for all reference
>> information, and the UDO repository should be for downloadable UDO's.
>>
>> I also think we should consider it an experiment and feel free to
>> enter in information which seems appropriate.  Over time, we can
>> re-evaluate and move things to the FLOSS manual, to the Csound
>> Reference manual, etc. if they seem like better places for it.  But at
>> least for the interim, we can capture useful information somewhere.
>>
>> Thanks!
>> steven
>>
>> On Wed, Jul 31, 2013 at 5:56 PM, David Akbari  wrote:
>> > Hello Steven,
>> >
>> > Would it be appropriate to use this Wiki resource to document steps to
>> > using
>> > non-GNU compilers (i.e. Intel icc / icpc)? It seems that this model
>> > would be
>> > more efficient than maintaining a separate text file in the canonical
>> > repository.
>> >
>> > What about posting performance systems that account for non-Csound
>> > related
>> > things that can influence success with Csound? For example common
>> > operating
>> > system issues, performance settings, alternate controller, and systems
>> > design considerations. This might be a nice way to add additional
>> > details to
>> > certain opcodes and algorithms that would otherwise be inappropriate in
>> > the
>> > manual or don't highlight the features of one opcode specifically.
>> >
>> > If the answer is yes to one or both of these questions I would like to
>> > contribute information to this Wiki. If no, then I will continue using
>> > the
>> > canonical and UDO repositories only.
>> >
>> > Cheers,
>> > David
>> >
>> >
>> > On Wed, Jul 31, 2013 at 5:39 AM, Steven Yi  wrote:
>> >>
>> >> Hi All,
>> >>
>> >> Just FYI, I've updated the Csound Wiki page on Sourceforge:
>> >>
>> >> https://sourceforge.net/p/csound/wiki/Home/
>> >>
>> >> I've added a section on the home page for installation/buildilng that
>> >> links to the existing Homebrew page, as well as have added a page on
>> >> buliding and installation for Debian/Ubuntu.
>> >>
>> >> I think it'd be be great for the site to have information like Bernt's
>> >> latest on Raspberry Pi settings, etc. all collected in the Wiki.  If
>> >> you'd like to contribute, please email me and I can look at setting
>> >> you up as a wiki contributor.
>> >>
>> >> Thanks!
>> >> steven
>> >>
>> >>
>> >> Send bugs reports to the Sourceforge bug trackers
>> >> csound6:
>> >>             https://sourceforge.net/p/csound/tickets/
>> >> csound5:
>> >>             https://sourceforge.net/p/csound/bugs/
>> >> 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 trackers
>> csound6:
>>             https://sourceforge.net/p/csound/tickets/
>> csound5:
>>             https://sourceforge.net/p/csound/bugs/
>> Discussions of bugs and features can be posted here
>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
>> csound"
>>
>>
>
>
>
> --
> Mvh.
>
> Bernt Isak Wærstad
>
>


Date2013-08-01 14:06
FromBernt Isak Wærstad
SubjectRe: [Csnd] Csound Wiki
Could be a solution, but we haven't got any code for this project except some CSD-files - it's more about how to set up everything, where to buy the components and how to assemble it all. Was thinking more of something like http://www.wikispaces.com/, but I haven't got a clue really of where the best place to put it is.

On Thu, Aug 1, 2013 at 12:43 PM, Steven Yi <stevenyi@gmail.com> wrote:
Hi Bernt,

Have you though to create an open source project on Github, Bitbucket,
or Sourceforge?  All of these platforms have wiki's as part of their
project systems. If you did that then it seems like it'd be good to do
as you say, add a basic intro page about Raspberry PI and link to
COSMO from there.

Cheers!
steven

On Thu, Aug 1, 2013 at 10:50 AM, Bernt Isak Wærstad <berntisak@gmail.com> wrote:
> My Raspberry PI investigations are part of larger project making a Csound
> stomp box together with Kim and Alex (we call it the COSMO project - Csound
> on Stage : Music Operator) where we are collecting data to make a
> comprehensive wiki of how to build this box. Since it will contain a lot of
> Linux and hardware/circuit specifics it's better to place this wiki outside
> the source forge wiki or FLOSS manuals, but we could easy make a subset of
> how to make Csound run on a Raspberry PI to put in either of those places
> (maybe with a link to the whole COSMO project wiki).
>
> Any suggestions for a good place to put such a wiki btw?
>
>
> On Wed, Jul 31, 2013 at 6:09 PM, Steven Yi <stevenyi@gmail.com> wrote:
>>
>> Hi Dave,
>>
>> It's a public wiki so I think whatever the community wants in it is
>> appropriate.  That said, I think the things you mentioned all sound
>> good.  I think we should still target the manual for all reference
>> information, and the UDO repository should be for downloadable UDO's.
>>
>> I also think we should consider it an experiment and feel free to
>> enter in information which seems appropriate.  Over time, we can
>> re-evaluate and move things to the FLOSS manual, to the Csound
>> Reference manual, etc. if they seem like better places for it.  But at
>> least for the interim, we can capture useful information somewhere.
>>
>> Thanks!
>> steven
>>
>> On Wed, Jul 31, 2013 at 5:56 PM, David Akbari <dakbari@gmail.com> wrote:
>> > Hello Steven,
>> >
>> > Would it be appropriate to use this Wiki resource to document steps to
>> > using
>> > non-GNU compilers (i.e. Intel icc / icpc)? It seems that this model
>> > would be
>> > more efficient than maintaining a separate text file in the canonical
>> > repository.
>> >
>> > What about posting performance systems that account for non-Csound
>> > related
>> > things that can influence success with Csound? For example common
>> > operating
>> > system issues, performance settings, alternate controller, and systems
>> > design considerations. This might be a nice way to add additional
>> > details to
>> > certain opcodes and algorithms that would otherwise be inappropriate in
>> > the
>> > manual or don't highlight the features of one opcode specifically.
>> >
>> > If the answer is yes to one or both of these questions I would like to
>> > contribute information to this Wiki. If no, then I will continue using
>> > the
>> > canonical and UDO repositories only.
>> >
>> > Cheers,
>> > David
>> >
>> >
>> > On Wed, Jul 31, 2013 at 5:39 AM, Steven Yi <stevenyi@gmail.com> wrote:
>> >>
>> >> Hi All,
>> >>
>> >> Just FYI, I've updated the Csound Wiki page on Sourceforge:
>> >>
>> >> https://sourceforge.net/p/csound/wiki/Home/
>> >>
>> >> I've added a section on the home page for installation/buildilng that
>> >> links to the existing Homebrew page, as well as have added a page on
>> >> buliding and installation for Debian/Ubuntu.
>> >>
>> >> I think it'd be be great for the site to have information like Bernt's
>> >> latest on Raspberry Pi settings, etc. all collected in the Wiki.  If
>> >> you'd like to contribute, please email me and I can look at setting
>> >> you up as a wiki contributor.
>> >>
>> >> Thanks!
>> >> steven
>> >>
>> >>
>> >> Send bugs reports to the Sourceforge bug trackers
>> >> csound6:
>> >>             https://sourceforge.net/p/csound/tickets/
>> >> csound5:
>> >>             https://sourceforge.net/p/csound/bugs/
>> >> 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 trackers
>> csound6:
>>             https://sourceforge.net/p/csound/tickets/
>> csound5:
>>             https://sourceforge.net/p/csound/bugs/
>> Discussions of bugs and features can be posted here
>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
>> csound"
>>
>>
>
>
>
> --
> Mvh.
>
> Bernt Isak Wærstad
>
>


Send bugs reports to the Sourceforge bug trackers
csound6:
            https://sourceforge.net/p/csound/tickets/
csound5:
            https://sourceforge.net/p/csound/bugs/
Discussions of bugs and features can be posted here
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"





--
Mvh.

Bernt Isak Wærstad



Date2013-08-02 12:39
FromTarmo Johannes
SubjectRe: [Csnd] Csound Wiki

I cannot suggest for a good wiki place, but the whole project sound really exicting!

 

Lot's of success and keep us informed!

 

tarmo

 

On Thursday 01 August 2013 10:50:02 Bernt Isak Wærstad wrote:

My Raspberry PI investigations are part of larger project making a Csound stomp box together with Kim and Alex (we call it the COSMO project - Csound on Stage : Music Operator) where we are collecting data to make a comprehensive wiki of how to build this box. Since it will contain a lot of Linux and hardware/circuit specifics it's better to place this wiki outside the source forge wiki or FLOSS manuals, but we could easy make a subset of how to make Csound run on a Raspberry PI to put in either of those places (maybe with a link to the whole COSMO project wiki). 


Any suggestions for a good place to put such a wiki btw?

On Wed, Jul 31, 2013 at 6:09 PM, Steven Yi <stevenyi@gmail.com> wrote:

Hi Dave,

It's a public wiki so I think whatever the community wants in it is
appropriate.  That said, I think the things you mentioned all sound
good.  I think we should still target the manual for all reference
information, and the UDO repository should be for downloadable UDO's.

I also think we should consider it an experiment and feel free to
enter in information which seems appropriate.  Over time, we can
re-evaluate and move things to the FLOSS manual, to the Csound
Reference manual, etc. if they seem like better places for it.  But at
least for the interim, we can capture useful information somewhere.

Thanks!
steven


On Wed, Jul 31, 2013 at 5:56 PM, David Akbari <dakbari@gmail.com> wrote:
> Hello Steven,
>
> Would it be appropriate to use this Wiki resource to document steps to using
> non-GNU compilers (i.e. Intel icc / icpc)? It seems that this model would be
> more efficient than maintaining a separate text file in the canonical
> repository.
>
> What about posting performance systems that account for non-Csound related
> things that can influence success with Csound? For example common operating
> system issues, performance settings, alternate controller, and systems
> design considerations. This might be a nice way to add additional details to
> certain opcodes and algorithms that would otherwise be inappropriate in the
> manual or don't highlight the features of one opcode specifically.
>
> If the answer is yes to one or both of these questions I would like to
> contribute information to this Wiki. If no, then I will continue using the
> canonical and UDO repositories only.
>
> Cheers,
> David
>
>
> On Wed, Jul 31, 2013 at 5:39 AM, Steven Yi <stevenyi@gmail.com> wrote:
>>
>> Hi All,
>>
>> Just FYI, I've updated the Csound Wiki page on Sourceforge:
>>
>> https://sourceforge.net/p/csound/wiki/Home/
>>
>> I've added a section on the home page for installation/buildilng that
>> links to the existing Homebrew page, as well as have added a page on
>> buliding and installation for Debian/Ubuntu.
>>
>> I think it'd be be great for the site to have information like Bernt's
>> latest on Raspberry Pi settings, etc. all collected in the Wiki.  If
>> you'd like to contribute, please email me and I can look at setting
>> you up as a wiki contributor.
>>
>> Thanks!
>> steven
>>
>>
>> Send bugs reports to the Sourceforge bug trackers
>> csound6:
>>             https://sourceforge.net/p/csound/tickets/
>> csound5:
>>             https://sourceforge.net/p/csound/bugs/
>> 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 trackers
csound6:
            https://sourceforge.net/p/csound/tickets/
csound5:
            https://sourceforge.net/p/csound/bugs/
Discussions of bugs and features can be posted here
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"





--
Mvh.


Bernt Isak Wærstad





Date2013-08-02 13:46
FromBernt Isak Wærstad
SubjectRe: [Csnd] Csound Wiki
Thanks! We'll of course keep you all informed. Hopefully there will be a paper on the Csound Conf. too!

fredag 2. august 2013 skrev Tarmo Johannes følgende:

I cannot suggest for a good wiki place, but the whole project sound really exicting!

 

Lot's of success and keep us informed!

 

tarmo

 

On Thursday 01 August 2013 10:50:02 Bernt Isak Wærstad wrote:

My Raspberry PI investigations are part of larger project making a Csound stomp box together with Kim and Alex (we call it the COSMO project - Csound on Stage : Music Operator) where we are collecting data to make a comprehensive wiki of how to build this box. Since it will contain a lot of Linux and hardware/circuit specifics it's better to place this wiki outside the source forge wiki or FLOSS manuals, but we could easy make a subset of how to make Csound run on a Raspberry PI to put in either of those places (maybe with a link to the whole COSMO project wiki). 


Any suggestions for a good place to put such a wiki btw?

On Wed, Jul 31, 2013 at 6:09 PM, Steven Yi <stevenyi@gmail.com> wrote:

Hi Dave,

It's a public wiki so I think whatever the community wants in it is
appropriate.  That said, I think the things you mentioned all sound
good.  I think we should still target the manual for all reference
information, and the UDO repository should be for downloadable UDO's.

I also think we should consider it an experiment and feel free to
enter in information which seems appropriate.  Over time, we can
re-evaluate and move things to the FLOSS manual, to the Csound
Reference manual, etc. if they seem like better places for it.  But at
least for the interim, we can capture useful information somewhere.

Thanks!
steven


On Wed, Jul 31, 2013 at 5:56 PM, David Akbari <dakbari@gmail.com> wrote:
> Hello Steven,
>
> Would it be appropriate to use this Wiki resource to document steps to using
> non-GNU compilers (i.e. Intel icc / icpc)? It seems that this model would be
> more efficient than maintaining a separate text file in the canonical
> repository.
>
> What about posting performance systems that account for non-Csound related
> things that can influence success with Csound? For example common operating
> system issues, performance settings, alternate controller, and systems
> design considerations. This might be a nice way to add additional details to
> certain opcodes and algorithms that would otherwise be inappropriate in the
> manual or don't highlight the features of one opcode specifically.
>
> If the answer is yes to one or both of these questions I would like to
> contribute information to this Wiki. If no, then I will continue using the
> canonical and UDO repositories only.
>
> Cheers,
> David
>
>
> On Wed, Jul 31, 2013 at 5:39 AM, Steven Yi <stevenyi@gmail.com> wrote:
>>
>> Hi All,
>>
>> Just FYI, I've updated the Csound Wiki page on Sourceforge:
>>
>> https://sourceforge.net/p/csound/wiki/Home/
>>
>> I've added a section on the home page for installation/buildilng that
>> links to the existing Homebrew page, as well as have added a page on
>> buliding and installation for Debian/Ubuntu.
>>
>> I think it'd be be great for the site to have information like Bernt's
>> latest on Raspberry Pi settings, etc. all collected in the Wiki.  If
>> you'd like to contribute, please email me and I can look at setting
>> you up as a wiki contributor.
>>
>> Thanks!
>> steven
>>
>>
>> Send bugs reports to the Sourceforge bug trackers
>> csound6:
>>            



--
Mvh.

Bernt Isak Wærstad




Date2013-08-04 20:44
FromAndres Cabrera
SubjectRe: [Csnd] Csound Wiki
Hi,

How are you guys communicating? I'm very interested in this project, as it aligns very well with something I'm working on:
https://github.com/mantaraya36/asuar

I'm interested in keeping up with your work, and maybe seeing how we can collaborate.

Cheers,
Andrés



On Fri, Aug 2, 2013 at 5:46 AM, Bernt Isak Wærstad <berntisak@gmail.com> wrote:
Thanks! We'll of course keep you all informed. Hopefully there will be a paper on the Csound Conf. too!

fredag 2. august 2013 skrev Tarmo Johannes følgende:

I cannot suggest for a good wiki place, but the whole project sound really exicting!

 

Lot's of success and keep us informed!

 

tarmo

 

On Thursday 01 August 2013 10:50:02 Bernt Isak Wærstad wrote:

My Raspberry PI investigations are part of larger project making a Csound stomp box together with Kim and Alex (we call it the COSMO project - Csound on Stage : Music Operator) where we are collecting data to make a comprehensive wiki of how to build this box. Since it will contain a lot of Linux and hardware/circuit specifics it's better to place this wiki outside the source forge wiki or FLOSS manuals, but we could easy make a subset of how to make Csound run on a Raspberry PI to put in either of those places (maybe with a link to the whole COSMO project wiki). 


Any suggestions for a good place to put such a wiki btw?

On Wed, Jul 31, 2013 at 6:09 PM, Steven Yi <stevenyi@gmail.com> wrote:

Hi Dave,

It's a public wiki so I think whatever the community wants in it is
appropriate.  That said, I think the things you mentioned all sound
good.  I think we should still target the manual for all reference
information, and the UDO repository should be for downloadable UDO's.

I also think we should consider it an experiment and feel free to
enter in information which seems appropriate.  Over time, we can
re-evaluate and move things to the FLOSS manual, to the Csound
Reference manual, etc. if they seem like better places for it.  But at
least for the interim, we can capture useful information somewhere.

Thanks!
steven


On Wed, Jul 31, 2013 at 5:56 PM, David Akbari <dakbari@gmail.com> wrote:
> Hello Steven,
>
> Would it be appropriate to use this Wiki resource to document steps to using
> non-GNU compilers (i.e. Intel icc / icpc)? It seems that this model would be
> more efficient than maintaining a separate text file in the canonical
> repository.
>
> What about posting performance systems that account for non-Csound related
> things that can influence success with Csound? For example common operating
> system issues, performance settings, alternate controller, and systems
> design considerations. This might be a nice way to add additional details to
> certain opcodes and algorithms that would otherwise be inappropriate in the
> manual or don't highlight the features of one opcode specifically.
>
> If the answer is yes to one or both of these questions I would like to
> contribute information to this Wiki. If no, then I will continue using the
> canonical and UDO repositories only.
>
> Cheers,
> David
>
>
> On Wed, Jul 31, 2013 at 5:39 AM, Steven Yi <stevenyi@gmail.com> wrote:
>>
>> Hi All,
>>
>> Just FYI, I've updated the Csound Wiki page on Sourceforge:
>>
>> https://sourceforge.net/p/csound/wiki/Home/
>>
>> I've added a section on the home page for installation/buildilng that
>> links to the existing Homebrew page, as well as have added a page on
>> buliding and installation for Debian/Ubuntu.
>>
>> I think it'd be be great for the site to have information like Bernt's
>> latest on Raspberry Pi settings, etc. all collected in the Wiki.  If
>> you'd like to contribute, please email me and I can look at setting
>> you up as a wiki contributor.
>>
>> Thanks!
>> steven
>>
>>
>> Send bugs reports to the Sourceforge bug trackers
>> csound6:
>>            



--
Mvh.

Bernt Isak Wærstad





Date2013-08-04 22:27
FromAlex Hofmann
SubjectRe: [Csnd] Csound Wiki / Raspberry Pi
Hi Andres,

what an interesting project you've been working on! Hoped to see you at SMC in Stockholm last week as I've seen you in the author's list.

Looks like your program should run on our Csound on Stage Music Operator. Bernt, Kim and I have been working on that the week befor Stockholm, I've done a bit of documentation on www.trashsounddesign.org.

This Picture shows the box, including Raspberry Pi, Soundcard and GPIO interface for the Knobs and Buttons.
http://www.trashsounddesign.org/wp-content/uploads/2013/07/2013-07-29-22.50.24-300x200.jpg

Best wishes,

Alex

Am 04.08.13 21:44, schrieb Andres Cabrera:
Hi,

How are you guys communicating? I'm very interested in this project, as it aligns very well with something I'm working on:
https://github.com/mantaraya36/asuar

I'm interested in keeping up with your work, and maybe seeing how we can collaborate.

Cheers,
Andrés



On Fri, Aug 2, 2013 at 5:46 AM, Bernt Isak Wærstad <berntisak@gmail.com> wrote:
Thanks! We'll of course keep you all informed. Hopefully there will be a paper on the Csound Conf. too!

fredag 2. august 2013 skrev Tarmo Johannes følgende:

I cannot suggest for a good wiki place, but the whole project sound really exicting!

 

Lot's of success and keep us informed!

 

tarmo

 

On Thursday 01 August 2013 10:50:02 Bernt Isak Wærstad wrote:

My Raspberry PI investigations are part of larger project making a Csound stomp box together with Kim and Alex (we call it the COSMO project - Csound on Stage : Music Operator) where we are collecting data to make a comprehensive wiki of how to build this box. Since it will contain a lot of Linux and hardware/circuit specifics it's better to place this wiki outside the source forge wiki or FLOSS manuals, but we could easy make a subset of how to make Csound run on a Raspberry PI to put in either of those places (maybe with a link to the whole COSMO project wiki). 


Any suggestions for a good place to put such a wiki btw?

On Wed, Jul 31, 2013 at 6:09 PM, Steven Yi <stevenyi@gmail.com> wrote:

Hi Dave,

It's a public wiki so I think whatever the community wants in it is
appropriate.  That said, I think the things you mentioned all sound
good.  I think we should still target the manual for all reference
information, and the UDO repository should be for downloadable UDO's.

I also think we should consider it an experiment and feel free to
enter in information which seems appropriate.  Over time, we can
re-evaluate and move things to the FLOSS manual, to the Csound
Reference manual, etc. if they seem like better places for it.  But at
least for the interim, we can capture useful information somewhere.

Thanks!
steven


On Wed, Jul 31, 2013 at 5:56 PM, David Akbari <dakbari@gmail.com> wrote:
> Hello Steven,
>
> Would it be appropriate to use this Wiki resource to document steps to using
> non-GNU compilers (i.e. Intel icc / icpc)? It seems that this model would be
> more efficient than maintaining a separate text file in the canonical
> repository.
>
> What about posting performance systems that account for non-Csound related
> things that can influence success with Csound? For example common operating
> system issues, performance settings, alternate controller, and systems
> design considerations. This might be a nice way to add additional details to
> certain opcodes and algorithms that would otherwise be inappropriate in the
> manual or don't highlight the features of one opcode specifically.
>
> If the answer is yes to one or both of these questions I would like to
> contribute information to this Wiki. If no, then I will continue using the
> canonical and UDO repositories only.
>
> Cheers,
> David
>
>
> On Wed, Jul 31, 2013 at 5:39 AM, Steven Yi <stevenyi@gmail.com> wrote:
>>
>> Hi All,
>>
>> Just FYI, I've updated the Csound Wiki page on Sourceforge:
>>
>> https://sourceforge.net/p/csound/wiki/Home/
>>
>> I've added a section on the home page for installation/buildilng that
>> links to the existing Homebrew page, as well as have added a page on
>> buliding and installation for Debian/Ubuntu.
>>
>> I think it'd be be great for the site to have information like Bernt's
>> latest on Raspberry Pi settings, etc. all collected in the Wiki.  If
>> you'd like to contribute, please email me and I can look at setting
>> you up as a wiki contributor.
>>
>> Thanks!
>> steven
>>
>>
>> Send bugs reports to the Sourceforge bug trackers
>> csound6:
>>            



--
Mvh.

Bernt Isak Wærstad






Date2013-08-05 13:43
FromBernt Isak Wærstad
SubjectRe: [Csnd] Csound Wiki
For the time being we communicate through facebook chat and have a shared google document where we put all documentation, but we're looking for a suitable place to put it in some sort of wiki. Once we have something online we'll let you all know here. Collaboration would of course be great! Let's see how it can be done when the wiki is up and running.

On Sun, Aug 4, 2013 at 9:44 PM, Andres Cabrera <mantaraya36@gmail.com> wrote:
Hi,

How are you guys communicating? I'm very interested in this project, as it aligns very well with something I'm working on:
https://github.com/mantaraya36/asuar

I'm interested in keeping up with your work, and maybe seeing how we can collaborate.

Cheers,
Andrés



On Fri, Aug 2, 2013 at 5:46 AM, Bernt Isak Wærstad <berntisak@gmail.com> wrote:
Thanks! We'll of course keep you all informed. Hopefully there will be a paper on the Csound Conf. too!

fredag 2. august 2013 skrev Tarmo Johannes følgende:

I cannot suggest for a good wiki place, but the whole project sound really exicting!

 

Lot's of success and keep us informed!

 

tarmo

 

On Thursday 01 August 2013 10:50:02 Bernt Isak Wærstad wrote:

My Raspberry PI investigations are part of larger project making a Csound stomp box together with Kim and Alex (we call it the COSMO project - Csound on Stage : Music Operator) where we are collecting data to make a comprehensive wiki of how to build this box. Since it will contain a lot of Linux and hardware/circuit specifics it's better to place this wiki outside the source forge wiki or FLOSS manuals, but we could easy make a subset of how to make Csound run on a Raspberry PI to put in either of those places (maybe with a link to the whole COSMO project wiki). 


Any suggestions for a good place to put such a wiki btw?

On Wed, Jul 31, 2013 at 6:09 PM, Steven Yi <stevenyi@gmail.com> wrote:

Hi Dave,

It's a public wiki so I think whatever the community wants in it is
appropriate.  That said, I think the things you mentioned all sound
good.  I think we should still target the manual for all reference
information, and the UDO repository should be for downloadable UDO's.

I also think we should consider it an experiment and feel free to
enter in information which seems appropriate.  Over time, we can
re-evaluate and move things to the FLOSS manual, to the Csound
Reference manual, etc. if they seem like better places for it.  But at
least for the interim, we can capture useful information somewhere.

Thanks!
steven


On Wed, Jul 31, 2013 at 5:56 PM, David Akbari <dakbari@gmail.com> wrote:
> Hello Steven,
>
> Would it be appropriate to use this Wiki resource to document steps to using
> non-GNU compilers (i.e. Intel icc / icpc)? It seems that this model would be
> more efficient than maintaining a separate text file in the canonical
> repository.
>
> What about posting performance systems that account for non-Csound related
> things that can influence success with Csound? For example common operating
> system issues, performance settings, alternate controller, and systems
> design considerations. This might be a nice way to add additional details to
> certain opcodes and algorithms that would otherwise be inappropriate in the
> manual or don't highlight the features of one opcode specifically.
>
> If the answer is yes to one or both of these questions I would like to
> contribute information to this Wiki. If no, then I will continue using the
> canonical and UDO repositories only.
>
> Cheers,
> David
>
>
> On Wed, Jul 31, 2013 at 5:39 AM, Steven Yi <stevenyi@gmail.com> wrote:
>>
>> Hi All,
>>
>> Just FYI, I've updated the Csound Wiki page on Sourceforge:
>>
>> https://sourceforge.net/p/csound/wiki/Home/
>>
>> I've added a section on the home page for installation/buildilng that
>> links to the existing Homebrew page, as well as have added a page on
>> buliding and installation for Debian/Ubuntu.
>>
>> I think it'd be be great for the site to have information like Bernt's
>> latest on Raspberry Pi settings, etc. all collected in the Wiki.  If
>> you'd like to contribute, please email me and I can look at setting
>> you up as a wiki contributor.
>>
>> Thanks!
>> steven
>>
>>
>> Send bugs reports to the Sourceforge bug trackers
>> csound6:
>>            



--
Mvh.

Bernt Isak Wærstad







--
Mvh.

Bernt Isak Wærstad



Date2013-08-07 11:35
FromSteven Yi
SubjectRe: [Csnd] Winsound for Mac
Hi Michael,

I built a version of Winsound locally for CS5 and placed it at:

http://www.kunstmusik.com/winsound_mac.zip

It opened, but I didn't try it out beyond that.  I'm afraid if there's
any issues I won't have time to support this build though.

steven

On Thu, Aug 1, 2013 at 12:05 AM, Michael Rhoades
 wrote:
> Thanks Anthony... but that is not what I am looking for. Winsound and
> Csound5GUI both were distributed with Csound 5. I just downloaded 5.19 for a
> new laptop and it did not include the folder that was called "Csound 5
> Frontends", which used to contain the apps I am looking for. Does anyone
> know what version of Csound 5 had that folder with the installer?
>
> The reason I am looking for it is that I will be teaching part of a
> synthesis course this fall with Csound and want to keep the interface and
> overall interaction ultimately simple for the students.
>
> Wxsound is fantastic by the way...
>
> Michael
>
>
>
>
>
> On 7/31/13 3:59 PM, Anthony Palomba wrote:
>>
>> http://winxound.codeplex.com/
>>
>>
>>
>> On Wed, Jul 31, 2013 at 2:09 PM, Michael Rhoades
>> >
>> wrote:
>>
>>     Hello,
>>
>>     Can anyone tell me where I can find Winsound for the MAC? As I
>>     understand it, it used to be part of the Csound download but is
>>     not any longer.
>>
>>     Any help would be appreciated.
>>
>>     Thanks,
>>
>>     Michael
>>
>>
>>
>>
>>     Send bugs reports to the Sourceforge bug trackers
>>     csound6:
>>     https://sourceforge.net/p/csound/tickets/
>>     csound5:
>>     https://sourceforge.net/p/csound/bugs/
>>     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 trackers
> csound6:
>            https://sourceforge.net/p/csound/tickets/
> csound5:
>            https://sourceforge.net/p/csound/bugs/
> Discussions of bugs and features can be posted here
> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
> csound"
>
>

Date2013-08-07 12:12
FromMichael Rhoades
SubjectRe: [Csnd] Winsound for Mac
Thanks so much Steven... That is fantastic! I will give it a try.

I did find that it is version 5.08 that includes a folder named "Csound 
5 Frontends". Surprisingly WinSound and Csound5GUI both run fine on OSX 
10.8.

Michael


On 8/7/13 6:35 AM, Steven Yi wrote:
> Hi Michael,
>
> I built a version of Winsound locally for CS5 and placed it at:
>
> http://www.kunstmusik.com/winsound_mac.zip
>
> It opened, but I didn't try it out beyond that.  I'm afraid if there's
> any issues I won't have time to support this build though.
>
> steven
>
> On Thu, Aug 1, 2013 at 12:05 AM, Michael Rhoades
>  wrote:
>> Thanks Anthony... but that is not what I am looking for. Winsound and
>> Csound5GUI both were distributed with Csound 5. I just downloaded 5.19 for a
>> new laptop and it did not include the folder that was called "Csound 5
>> Frontends", which used to contain the apps I am looking for. Does anyone
>> know what version of Csound 5 had that folder with the installer?
>>
>> The reason I am looking for it is that I will be teaching part of a
>> synthesis course this fall with Csound and want to keep the interface and
>> overall interaction ultimately simple for the students.
>>
>> Wxsound is fantastic by the way...
>>
>> Michael
>>
>>
>>
>>
>>
>> On 7/31/13 3:59 PM, Anthony Palomba wrote:
>>> http://winxound.codeplex.com/
>>>
>>>
>>>
>>> On Wed, Jul 31, 2013 at 2:09 PM, Michael Rhoades
>>> >
>>> wrote:
>>>
>>>      Hello,
>>>
>>>      Can anyone tell me where I can find Winsound for the MAC? As I
>>>      understand it, it used to be part of the Csound download but is
>>>      not any longer.
>>>
>>>      Any help would be appreciated.
>>>
>>>      Thanks,
>>>
>>>      Michael
>>>
>>>
>>>
>>>
>>>      Send bugs reports to the Sourceforge bug trackers
>>>      csound6:
>>>      https://sourceforge.net/p/csound/tickets/
>>>      csound5:
>>>      https://sourceforge.net/p/csound/bugs/
>>>      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 trackers
>> csound6:
>>             https://sourceforge.net/p/csound/tickets/
>> csound5:
>>             https://sourceforge.net/p/csound/bugs/
>> 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 trackers
> csound6:
>              https://sourceforge.net/p/csound/tickets/
> csound5:
>              https://sourceforge.net/p/csound/bugs/
> Discussions of bugs and features can be posted here
> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
>
>
>
>


Date2013-08-14 19:23
Frommenno
Subject[Csnd] Re: Csound Wiki
Hi Steven,

thanks for your Wiki entry on building Csound on Ubuntu.
But i have a problem on my system (Bodhi Linux 12.04 = Ubuntu 12.04) when i
run:
sudo apt-get build-dep csound

i get:
E: Build-Depends dependency for csound cannot be satisfied because candidate
version of package cdbs can't satisfy version requirements

version of cdbs is 0.4.100. Do you think this version is too old?

greetings
Menno



--
View this message in context: http://csound.1045644.n5.nabble.com/Csound-Wiki-tp5726168p5726692.html
Sent from the Csound - General mailing list archive at Nabble.com.

Date2013-08-14 19:36
FromSteven Yi
SubjectRe: [Csnd] Re: Csound Wiki
Hi Menno,

I don't use Ubuntu or Debian regularly enough to be able to answer that question, and I haven't ran into this problem myself. But let's see if we can figure out the problem.  Is this a fresh installation of Bodhi Linux, or had you previously upgraded?  Are you using using 32-bit or 64-bit?  Also, did you add any repos after installation (for things like testing or unstable, etc.) I'm downloading 64-bit (says version 2.3.0) now from bodhilinux.com and will try installing into a virtual machine to help diagnose.  

Thanks!
steven




On Wed, Aug 14, 2013 at 2:23 PM, menno <nabob_cd@yahoo.com> wrote:
Hi Steven,

thanks for your Wiki entry on building Csound on Ubuntu.
But i have a problem on my system (Bodhi Linux 12.04 = Ubuntu 12.04) when i
run:
sudo apt-get build-dep csound

i get:
E: Build-Depends dependency for csound cannot be satisfied because candidate
version of package cdbs can't satisfy version requirements

version of cdbs is 0.4.100. Do you think this version is too old?

greetings
Menno



--
View this message in context: http://csound.1045644.n5.nabble.com/Csound-Wiki-tp5726168p5726692.html
Sent from the Csound - General mailing list archive at Nabble.com.


Send bugs reports to the Sourceforge bug trackers
csound6:
            https://sourceforge.net/p/csound/tickets/
csound5:
            https://sourceforge.net/p/csound/bugs/
Discussions of bugs and features can be posted here
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"




Date2013-08-14 19:52
Frommenno
Subject[Csnd] Re: Csound Wiki
it is a bit complicated: i have Bodhi Linux 64 bit installed en after that i
installed debs from KXStudio. The KXStudio stuff has to do with GUI programs
for jack and up-to-date music related programs but they do not affect the
fundamental packages of Bodhi Linux and, in turn, this uses Ubuntu packages
(at least, that i what i think).
 So, no Gnome or KDE but Enlightenment as a WM. And i use Synaptic for the
updates. 
Quite a lot to run in a virtual machine :) ?




--
View this message in context: http://csound.1045644.n5.nabble.com/Csound-Wiki-tp5726168p5726694.html
Sent from the Csound - General mailing list archive at Nabble.com.

Date2013-08-14 23:09
FromSteven Yi
SubjectRe: [Csnd] Re: Csound Wiki
Hi Menno,

I install bodhi linux then added some source repositories using synaptic. After that, I did "sudo apt-get build-dep csound" and it gave me a large list of dependencies it would install.  One think I noticed is that cdbs I have listed in apt-cache is 0.4.100ubuntu2 (used apt-cache show cdbs).  I'm wondering if you have a different cdbs?  Otherwise, I'm wondering if kxstudio repos have other packages that might mess up something?  (Maybe try disabling them in synaptic, do a refresh, then try build-dep again on the commandline)

steven


On Wed, Aug 14, 2013 at 2:52 PM, menno <nabob_cd@yahoo.com> wrote:
it is a bit complicated: i have Bodhi Linux 64 bit installed en after that i
installed debs from KXStudio. The KXStudio stuff has to do with GUI programs
for jack and up-to-date music related programs but they do not affect the
fundamental packages of Bodhi Linux and, in turn, this uses Ubuntu packages
(at least, that i what i think).
 So, no Gnome or KDE but Enlightenment as a WM. And i use Synaptic for the
updates.
Quite a lot to run in a virtual machine :) ?




--
View this message in context: http://csound.1045644.n5.nabble.com/Csound-Wiki-tp5726168p5726694.html
Sent from the Csound - General mailing list archive at Nabble.com.


Send bugs reports to the Sourceforge bug trackers
csound6:
            https://sourceforge.net/p/csound/tickets/
csound5:
            https://sourceforge.net/p/csound/bugs/
Discussions of bugs and features can be posted here
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"




Date2013-08-15 11:26
Frommenno
Subject[Csnd] Re: Csound Wiki
I did as you said Steven. I disabled the KXStudio repos, did a refresh and
did:
~/csound6-git$ sudo apt-get build-dep csound

I get:
E: Unable to find a source package for csound

I do have the same cdbs version as you have, Steven(Version:
0.4.100ubuntu2).
pt-cache show cdbs
Package: cdbs
Priority: optional
Section: devel
Installed-Size: 283
Maintainer: Ubuntu Developers 
Original-Maintainer: CDBS Hackers

Date2013-08-15 14:48
FromSteven Yi
SubjectRe: [Csnd] Re: Csound Wiki
Hi Menno,

This message:

"E: Unable to find a source package for csound"

seems relevant. Could you go into Synaptic, then under
"Settings->Repositories", check that the "Source Code" option is
selected for the options that you have selected?  (I have the one
checked under the Ubuntu Software tab, as well as in "Other Software"
tab for "Canonical Partners".  After doing that, try again on the
commandline with build-deps and hopefully you should get a different
message now.

steven

On Thu, Aug 15, 2013 at 6:26 AM, menno  wrote:
> I did as you said Steven. I disabled the KXStudio repos, did a refresh and
> did:
> ~/csound6-git$ sudo apt-get build-dep csound
>
> I get:
> E: Unable to find a source package for csound
>
> I do have the same cdbs version as you have, Steven(Version:
> 0.4.100ubuntu2).
> pt-cache show cdbs
> Package: cdbs
> Priority: optional
> Section: devel
> Installed-Size: 283
> Maintainer: Ubuntu Developers 
> Original-Maintainer: CDBS Hackers
>  Architecture: all
> Version: 0.4.100ubuntu2
> Depends: dh-translations, python-scour
> Recommends: autotools-dev
> Suggests: devscripts
> Filename: pool/main/c/cdbs/cdbs_0.4.100ubuntu2_all.deb
> Size: 47578
> MD5sum: 88623d86dfe8c6f942c10ceb129be163
> SHA1: 8ff71b1428449b3b2fe1b84eb9f7cd358351ea77
> SHA256: 793cddf5d0c99415f4b5f09f181af8275e38ec24646031a875c84f6b23d37486
> Description-en: common build system for Debian packages
>  This package contains the Common Debian Build System, an abstract build
>  system based on Makefile inheritance which is completely extensible and
>  overridable.  In other words, CDBS provides a sane set of default rules
>  upon which packages can build; any or all rules may be overridden as
>  needed.
> Multi-Arch: foreign
> Description-md5: 600297a26a1bc2bcf29442cdb6deb9f8
> Bugs: https://bugs.launchpad.net/ubuntu/+filebug
> Origin: Ubuntu
> Supported: 5y
>
> Menno
>
>
>
> --
> View this message in context: http://csound.1045644.n5.nabble.com/Csound-Wiki-tp5726168p5726726.html
> Sent from the Csound - General mailing list archive at Nabble.com.
>
>
> Send bugs reports to the Sourceforge bug trackers
> csound6:
>             https://sourceforge.net/p/csound/tickets/
> csound5:
>             https://sourceforge.net/p/csound/bugs/
> Discussions of bugs and features can be posted here
> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
>
>

Date2013-08-15 15:49
Frommenno
Subject[Csnd] Re: Csound Wiki
This gives the desired results:

menno@muziek:~/csound6-git$ sudo apt-get build-dep csound
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages will be REMOVED:
  libfltk1.3-dev
The following NEW packages will be installed:
  default-jdk default-jre default-jre-headless devscripts dh-buildinfo
doxygen
  graphviz libavahi-client-dev libavahi-common-dev
libboost-serialization-dev
  libboost-serialization1.46-dev libboost-serialization1.46.1 libcdt4
  libcgraph5 libfltk1.1 libfltk1.1-dev libfontconfig1-dev libfreetype6-dev
  libgraph4 libgvc5 libgvpr1 liblua5.1-0-dev libpathplan4 libportaudiocpp0
  libportmidi-dev libportmidi0 libpulse-dev libpulse-mainloop-glib0
  librtaudio-dev librtaudio4 librtmidi-dev librtmidi1 libstk0-dev libstk0c2a
  libxft-dev libxrender-dev libxss-dev openjdk-6-jdk openjdk-6-jre
  openjdk-6-jre-headless openjdk-6-jre-lib portaudio19-dev puredata-dev
  python-dev tcl tcl-dev tcl8.5-dev tk tk-dev tk8.5-dev ttf-dejavu
  x11proto-render-dev x11proto-scrnsaver-dev
0 upgraded, 53 newly installed, 1 to remove and 0 not upgraded.
Need to get 52.6 MB/53.3 MB of archives.
After this operation, 153 MB of additional disk space will be used.
Do you want to continue [Y/n]?

I have openjdk-7 installed. Will the needed openjdk-6 packages not conflict
with openjdk-7? Also, un-installing FLTK1.3 seems a step back...?
What do you think?



--
View this message in context: http://csound.1045644.n5.nabble.com/Csound-Wiki-tp5726168p5726742.html
Sent from the Csound - General mailing list archive at Nabble.com.

Date2013-08-15 18:16
Frommenno
Subject[Csnd] Re: Csound Wiki
i went ahead and installed csound using cmake-gui.
finally it all installed in /usr/local

But:
menno@muziek:~/temp/csound$ csound
csound: error while loading shared libraries: libcsound64.so.6.0: cannot
open shared object file: No such file or directory

i found libcsound64.so.6.0 in /usr/local/lib

What is the problem?

thanks




--
View this message in context: http://csound.1045644.n5.nabble.com/Csound-Wiki-tp5726168p5726750.html
Sent from the Csound - General mailing list archive at Nabble.com.

Date2013-08-15 18:21
FromJason Timm
SubjectRe: [Csnd] Re: Csound Wiki
Same problem here on Raspbian. 

On Aug 15, 2013, at 1:16 PM, menno  wrote:

> i went ahead and installed csound using cmake-gui.
> finally it all installed in /usr/local
> 
> But:
> menno@muziek:~/temp/csound$ csound
> csound: error while loading shared libraries: libcsound64.so.6.0: cannot
> open shared object file: No such file or directory
> 
> i found libcsound64.so.6.0 in /usr/local/lib
> 
> What is the problem?
> 
> thanks
> 
> 
> 
> 
> --
> View this message in context: http://csound.1045644.n5.nabble.com/Csound-Wiki-tp5726168p5726750.html
> Sent from the Csound - General mailing list archive at Nabble.com.
> 
> 
> Send bugs reports to the Sourceforge bug trackers
> csound6:
>            https://sourceforge.net/p/csound/tickets/
> csound5:
>            https://sourceforge.net/p/csound/bugs/
> Discussions of bugs and features can be posted here
> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
> 
> 


Date2013-08-15 19:01
FromJustin Smith
SubjectRe: [Csnd] Re: Csound Wiki
Did you run ldconfig after installing the library? Is /usr/local/lib set up to be a default place for libraries (/etc/ld.so.conf)?


On Thu, Aug 15, 2013 at 10:21 AM, Jason Timm <jasontimm@me.com> wrote:
Same problem here on Raspbian.

On Aug 15, 2013, at 1:16 PM, menno <nabob_cd@yahoo.com> wrote:

> i went ahead and installed csound using cmake-gui.
> finally it all installed in /usr/local
>
> But:
> menno@muziek:~/temp/csound$ csound
> csound: error while loading shared libraries: libcsound64.so.6.0: cannot
> open shared object file: No such file or directory
>
> i found libcsound64.so.6.0 in /usr/local/lib
>
> What is the problem?
>
> thanks
>
>
>
>
> --
> View this message in context: http://csound.1045644.n5.nabble.com/Csound-Wiki-tp5726168p5726750.html
> Sent from the Csound - General mailing list archive at Nabble.com.
>
>
> Send bugs reports to the Sourceforge bug trackers
> csound6:
>            https://sourceforge.net/p/csound/tickets/
> csound5:
>            https://sourceforge.net/p/csound/bugs/
> 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 trackers
csound6:
            https://sourceforge.net/p/csound/tickets/
csound5:
            https://sourceforge.net/p/csound/bugs/
Discussions of bugs and features can be posted here
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"




Date2013-08-15 19:04
FromBernt Isak Wærstad
SubjectRe: [Csnd] Re: Csound Wiki
Not sure, but maybe "sudo ldconfig" will fix this?


On Thu, Aug 15, 2013 at 7:21 PM, Jason Timm <jasontimm@me.com> wrote:
Same problem here on Raspbian.

On Aug 15, 2013, at 1:16 PM, menno <nabob_cd@yahoo.com> wrote:

> i went ahead and installed csound using cmake-gui.
> finally it all installed in /usr/local
>
> But:
> menno@muziek:~/temp/csound$ csound
> csound: error while loading shared libraries: libcsound64.so.6.0: cannot
> open shared object file: No such file or directory
>
> i found libcsound64.so.6.0 in /usr/local/lib
>
> What is the problem?
>
> thanks
>
>
>
>
> --
> View this message in context: http://csound.1045644.n5.nabble.com/Csound-Wiki-tp5726168p5726750.html
> Sent from the Csound - General mailing list archive at Nabble.com.
>
>
> Send bugs reports to the Sourceforge bug trackers
> csound6:
>            https://sourceforge.net/p/csound/tickets/
> csound5:
>            https://sourceforge.net/p/csound/bugs/
> 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 trackers
csound6:
            https://sourceforge.net/p/csound/tickets/
csound5:
            https://sourceforge.net/p/csound/bugs/
Discussions of bugs and features can be posted here
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"





--
Mvh.

Bernt Isak Wærstad



Date2013-08-15 21:58
Frommenno
Subject[Csnd] Re: Csound Wiki
Bernt, Justin, yes, that was it! 
I was not aware of the existence of ldconfig and the necessity to run it,
but sudo ldconfig solved the problem.

It's great to have csound6 on my system :)
Thanks, and thanks also to Steven!



--
View this message in context: http://csound.1045644.n5.nabble.com/Csound-Wiki-tp5726168p5726761.html
Sent from the Csound - General mailing list archive at Nabble.com.

Date2013-08-16 03:52
FromSteven Yi
SubjectRe: [Csnd] Re: Csound Wiki
Glad to hear you've got it setup now!

On Thu, Aug 15, 2013 at 4:58 PM, menno  wrote:
> Bernt, Justin, yes, that was it!
> I was not aware of the existence of ldconfig and the necessity to run it,
> but sudo ldconfig solved the problem.
>
> It's great to have csound6 on my system :)
> Thanks, and thanks also to Steven!
>
>
>
> --
> View this message in context: http://csound.1045644.n5.nabble.com/Csound-Wiki-tp5726168p5726761.html
> Sent from the Csound - General mailing list archive at Nabble.com.
>
>
> Send bugs reports to the Sourceforge bug trackers
> csound6:
>             https://sourceforge.net/p/csound/tickets/
> csound5:
>             https://sourceforge.net/p/csound/bugs/
> Discussions of bugs and features can be posted here
> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
>
>

Date2013-08-16 13:22
Frommenno
Subject[Csnd] Re: Csound Wiki
hi,
i do not have had yet the pleasure of hearing a sound from csound in
realtime, using jack. 
I do get a result when i render csound to a wav file, no problems there.

I found out that Blue did not discover a Jack client, so i am trying to run
from the commandline:

menno@muziek:~/csound/csd$ csound -+rtaudio=jack -odac -r48000 -k750
noisernd.csd
virtual_keyboard real time MIDI plugin for Csound
graph init
0dBFS level = 32768.0
Csound version 6.00.1 (double samples) Aug 15 2013
libsndfile-1.0.25
UnifiedCSD:  noisernd.csd
STARTING FILE
Creating options
Creating orchestra
Creating score
rtmidi: ALSA Raw MIDI module enabled
rtaudio: JACK module enabled
sample rate overrides: esr = 48000.0000, ekr = 750.0000, ksmps = 64
Elapsed time at end of orchestra compile: real: 0.002s, CPU: 0.000s
sorting score ...
        ... done
Elapsed time at end of score sort: real: 0.002s, CPU: 0.000s
Csound version 6.00.1 (double samples) Aug 15 2013
0dBFS level = 32768.0
orch now loaded
audio buffered in 256 sample-frame blocks
 0: dac:system:playback_ (system:playback_)
 1: dac:jack2alsa:playback_ (jack2alsa:playback_)
 *** rtjack: error connecting output ports
*** glibc detected *** csound: corrupted double-linked list:
0x00000000017ad170 ***
======= Backtrace: =========
/lib/x86_64-linux-gnu/libc.so.6(+0x7eb96)[0x7ff08bb56b96]
/lib/x86_64-linux-gnu/libc.so.6(+0x7ef00)[0x7ff08bb56f00]
/lib/x86_64-linux-gnu/libc.so.6(+0x7fb29)[0x7ff08bb57b29]
/usr/lib/x86_64-linux-gnu/libjack.so.0(+0x44a04)[0x7ff089186a04]
/usr/lib/x86_64-linux-gnu/libjack.so.0(jack_client_close+0xcf)[0x7ff08918641e]
/usr/local/lib/csound/plugins64-6.0/librtjack.so(+0x441a)[0x7ff081b7d41a]
/usr/local/lib/csound/plugins64-6.0/librtjack.so(+0x4509)[0x7ff081b7d509]
/usr/local/lib/csound/plugins64-6.0/librtjack.so(+0x2f77)[0x7ff081b7bf77]
/usr/local/lib/csound/plugins64-6.0/librtjack.so(+0x35bb)[0x7ff081b7c5bb]
/usr/local/lib/libcsound64.so.6.0(+0x6e43f)[0x7ff08c12243f]
/usr/local/lib/libcsound64.so.6.0(+0x5a0db)[0x7ff08c10e0db]
/usr/local/lib/libcsound64.so.6.0(csoundStart+0x905)[0x7ff08c24f33c]
/usr/local/lib/libcsound64.so.6.0(csoundCompile+0x42)[0x7ff08c24f384]
csound[0x40140f]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xed)[0x7ff08baf976d]
csound[0x400fb9]
======= Memory map: ========
00400000-00403000 r-xp 00000000 08:05 283177                            
/usr/local/bin/csound
00602000-00603000 r--p 00002000 08:05 283177                            
/usr/local/bin/csound
00603000-00604000 rw-p 00003000 08:05 283177                            
/usr/local/bin/csound
01609000-017c1000 rw-p 00000000 00:00 0                                 
[heap]
7ff06c000000-7ff06c021000 rw-p 00000000 00:00 0
7ff06c021000-7ff070000000 ---p 00000000 00:00 0
7ff078000000-7ff078021000 rw-p 00000000 00:00 0
7ff078021000-7ff07c000000 ---p 00000000 00:00 0
7ff07f90e000-7ff07f90f000 ---p 00000000 00:00 0
7ff07f90f000-7ff07f98f000 rw-p 00000000 00:00 0
7ff07f98f000-7ff07f991000 r-xp 00000000 08:05 281712                    
/usr/local/lib/csound/plugins64-6.0/libipmidi.so
7ff07f991000-7ff07fb90000 ---p 00002000 08:05 281712                    
/usr/local/lib/csound/plugins64-6.0/libipmidi.so
7ff07fb90000-7ff07fb91000 r--p 00001000 08:05 281712                    
/usr/local/lib/csound/plugins64-6.0/libipmidi.so
7ff07fb91000-7ff07fb92000 rw-p 00002000 08:05 281712                    
/usr/local/lib/csound/plugins64-6.0/libipmidi.so
7ff07fb92000-7ff07fb9c000 r-xp 00000000 08:05 281577                    
/usr/local/lib/csound/plugins64-6.0/librtalsa.so
7ff07fb9c000-7ff07fd9b000 ---p 0000a000 08:05 281577                    
/usr/local/lib/csound/plugins64-6.0/librtalsa.so
7ff07fd9b000-7ff07fd9c000 r--p 00009000 08:05 281577                    
/usr/local/lib/csound/plugins64-6.0/librtalsa.so
7ff07fd9c000-7ff07fd9d000 rw-p 0000a000 08:05 281577                    
/usr/local/lib/csound/plugins64-6.0/librtalsa.so
7ff07fd9d000-7ff07fdce000 r-xp 00000000 08:05 283181                    
/usr/local/lib/csound/plugins64-6.0/libstdutil.so
7ff07fdce000-7ff07ffcd000 ---p 00031000 08:05 283181                    
/usr/local/lib/csound/plugins64-6.0/libstdutil.so
7ff07ffcd000-7ff07ffce000 r--p 00030000 08:05 283181                    
/usr/local/lib/csound/plugins64-6.0/libstdutil.so
7ff07ffce000-7ff07ffcf000 rw-p 00031000 08:05 283181                    
/usr/local/lib/csound/plugins64-6.0/libstdutil.so
7ff07ffcf000-7ff07ffd0000 rw-p 00000000 00:00 0
7ff07ffd0000-7ff07ffd1000 r-xp 00000000 08:05 281561                    
/usr/local/lib/csound/plugins64-6.0/liburandom.so
7ff07ffd1000-7ff0801d0000 ---p 00001000 08:05 281561                    
/usr/local/lib/csound/plugins64-6.0/liburandom.so
7ff0801d0000-7ff0801d1000 r--p 00000000 08:05 281561                    
/usr/local/lib/csound/plugins64-6.0/liburandom.so
7ff0801d1000-7ff0801d2000 rw-p 00001000 08:05 281561                    
/usr/local/lib/csound/plugins64-6.0/liburandom.so
7ff0801d2000-7ff0801d6000 r-xp 00000000 08:05 281555                    
/usr/local/lib/csound/plugins64-6.0/libfractalnoise.so
7ff0801d6000-7ff0803d5000 ---p 00004000 08:05 281555                    
/usr/local/lib/csound/plugins64-6.0/libfractalnoise.so
7ff0803d5000-7ff0803d6000 r--p 00003000 08:05 281555                    
/usr/local/lib/csound/plugins64-6.0/libfractalnoise.so
7ff0803d6000-7ff0803d7000 rw-p 00004000 08:05 281555                    
/usr/local/lib/csound/plugins64-6.0/libfractalnoise.so
7ff0803d7000-7ff0803d9000 r-xp 00000000 08:05 281552                    
/usr/local/lib/csound/plugins64-6.0/libcs_date.so
7ff0803d9000-7ff0805d8000 ---p 00002000 08:05 281552                    
/usr/local/lib/csound/plugins64-6.0/libcs_date.so
7ff0805d8000-7ff0805d9000 r--p 00001000 08:05 281552                    
/usr/local/lib/csound/plugins64-6.0/libcs_date.so
7ff0805d9000-7ff0805da000 rw-p 00002000 08:05 281552                    
/usr/local/lib/csound/plugins64-6.0/libcs_date.so
7ff0805da000-7ff0805db000 r-xp 00000000 08:05 281553                    
/usr/local/lib/csound/plugins64-6.0/libsystem_call.so
7ff0805db000-7ff0807da000 ---p 00001000 08:05 281553                    
/usr/local/lib/csound/plugins64-6.0/libsystem_call.so
7ff0807da000-7ff0807db000 r--p 00000000 08:05 281553                    
/usr/local/lib/csound/plugins64-6.0/libsystem_call.so
7ff0807db000-7ff0807dc000 rw-p 00001000 08:05 281553                    
/usr/local/lib/csound/plugins64-6.0/libsystem_call.so
7ff0807dc000-7ff0807dd000 r-xp 00000000 08:05 281567                    
/usr/local/lib/csound/plugins64-6.0/libjackTransport.so
7ff0807dd000-7ff0809dc000 ---p 00001000 08:05 281567                    
/usr/local/lib/csound/plugins64-6.0/libjackTransport.so
7ff0809dc000-7ff0809dd000 r--p 00000000 08:05 281567                    
/usr/local/lib/csound/plugins64-6.0/libjackTransport.so
7ff0809dd000-7ff0809de000 rw-p 00001000 08:05 281567                    
/usr/local/lib/csound/plugins64-6.0/libjackTransport.so
7ff0809de000-7ff0809e0000 r-xp 00000000 08:05 552065                    
/lib/x86_64-linux-gnu/libutil-2.15.so
7ff0809e0000-7ff080bdf000 ---p 00002000 08:05 552065                    
/lib/x86_64-linux-gnu/libutil-2.15.so
7ff080bdf000-7ff080be0000 r--p 00001000 08:05 552065                    
/lib/x86_64-linux-gnu/libutil-2.15.so
7ff080be0000-7ff080be1000 rw-p 00002000 08:05 552065                    
/lib/x86_64-linux-gnu/libutil-2.15.so
7ff080be1000-7ff080d92000 r-xp 00000000 08:05 544791                    
/lib/x86_64-linux-gnu/libcrypto.so.1.0.0
7ff080d92000-7ff080f92000 ---p 001b1000 08:05 544791                    
/lib/x86_64-linux-gnu/libcrypto.so.1.0.0
7ff080f92000-7ff080fad000 r--p 001b1000 08:05 544791                    
/lib/x86_64-linux-gnu/libcrypto.so.1.0.0
7ff080fad000-7ff080fb8000 rw-p 001cc000 08:05 544791                    
/lib/x86_64-linux-gnu/libcrypto.so.1.0.0
7ff080fb8000-7ff080fbc000 rw-p 00000000 00:00 0
7ff080fbc000-7ff081010000 r-xp 00000000 08:05 544792                    
/lib/x86_64-linux-gnu/libssl.so.1.0.0
7ff081010000-7ff081210000 ---p 00054000 08:05 544792                    
/lib/x86_64-linux-gnu/libssl.so.1.0.0
7ff081210000-7ff081213000 r--p 00054000 08:05 544792                    
/lib/x86_64-linux-gnu/libssl.so.1.0.0
7ff081213000-7ff081219000 rw-p 00057000 08:05 544792                    
/lib/x86_64-linux-gnu/libssl.so.1.0.0
7ff081219000-7ff08121a000 rw-p 00000000 00:00 0
7ff08121a000-7ff08149b000 r-xp 00000000 08:05 159713                    
/usr/lib/libpython2.7.so.1.0
7ff08149b000-7ff08169a000 ---p 00281000 08:05 159713                    
/usr/lib/libpython2.7.so.1.0
7ff08169a000-7ff08169c000 r--p 00280000 08:05 159713                    
/usr/lib/libpython2.7.so.1.0
7ff08169c000-7ff081705000 rw-p 00282000 08:05 159713                    
/usr/lib/libpython2.7.so.1.0
7ff081705000-7ff081717000 rw-p 00000000 00:00 0
7ff081717000-7ff081727000 r-xp 00000000 08:05 281571                    
/usr/local/lib/csound/plugins64-6.0/libpy.so
7ff081727000-7ff081926000 ---p 00010000 08:05 281571                    
/usr/local/lib/csound/plugins64-6.0/libpy.so
7ff081926000-7ff081927000 r--p 0000f000 08:05 281571                    
/usr/local/lib/csound/plugins64-6.0/libpy.so
7ff081927000-7ff081929000 rw-p 00010000 08:05 281571                    
/usr/local/lib/csound/plugins64-6.0/libpy.so
7ff081929000-7ff081976000 r-xp 00000000 08:05 281714                    
/usr/local/lib/csound/plugins64-6.0/libwidgets.so
7ff081976000-7ff081b75000 ---p 0004d000 08:05 281714                    
/usr/local/lib/csound/plugins64-6.0/libwidgets.so
7ff081b75000-7ff081b77000 r--p 0004c000 08:05 281714                    
/usr/local/lib/csound/plugins64-6.0/libwidgets.so
7ff081b77000-7ff081b79000 rw-p 0004e000 08:05 281714                    
/usr/local/lib/csound/plugins64-6.0/libwidgets.so
7ff081b79000-7ff081b7f000 r-xp 00000000 08:05 281713                    
/usr/local/lib/csound/plugins64-6.0/librtjack.so
7ff081b7f000-7ff081d7e000 ---p 00006000 08:05 281713                    
/usr/local/lib/csound/plugins64-6.0/librtjack.so
7ff081d7e000-7ff081d7f000 r--p 00005000 08:05 281713                    
/usr/local/lib/csound/plugins64-6.0/librtjack.so
7ff081d7f000-7ff081d80000 rw-p 00006000 08:05 281713                    
/usr/local/lib/csound/plugins64-6.0/librtjack.so
7ff081d80000-7ff081da2000 r-xp 00000000 08:05 527924                    
/lib/x86_64-linux-gnu/libtinfo.so.5.9
7ff081da2000-7ff081fa2000 ---p 00022000 08:05 527924                    
/lib/x86_64-linux-gnu/libtinfo.so.5.9
7ff081fa2000-7ff081fa6000 r--p 00022000 08:05 527924                    
/lib/x86_64-linux-gnu/libtinfo.so.5.9
7ff081fa6000-7ff081fa7000 rw-p 00026000 08:05 527924                    
/lib/x86_64-linux-gnu/libtinfo.so.5.9
7ff081fa7000-7ff081fe3000 r-xp 00000000 08:05 527900                    
/lib/x86_64-linux-gnu/libpcre.so.3.12.1
7ff081fe3000-7ff0821e2000 ---p 0003c000 08:05 527900                    
/lib/x86_64-linux-gnu/libpcre.so.3.12.1
7ff0821e2000-7ff0821e3000 r--p 0003b000 08:05 527900                    
/lib/x86_64-linux-gnu/libpcre.so.3.12.1
7ff0821e3000-7ff0821e4000 rw-p 0003c000 08:05 527900                    
/lib/x86_64-linux-gnu/libpcre.so.3.12.1
7ff0821e4000-7ff08221d000 r-xp 00000000 08:05 527910                    
/lib/x86_64-linux-gnu/libreadline.so.6.2
7ff08221d000-7ff08241d000 ---p 00039000 08:05 527910                    
/lib/x86_64-linux-gnu/libreadline.so.6.2
7ff08241d000-7ff08241f000 r--p 00039000 08:05 527910                    
/lib/x86_64-linux-gnu/libreadline.so.6.2
7ff08241f000-7ff082425000 rw-p 0003b000 08:05 527910                    
/lib/x86_64-linux-gnu/libreadline.so.6.2
7ff082425000-7ff082426000 rw-p 00000000 00:00 0
7ff082426000-7ff082518000 r-xp 00000000 08:05 527852                    
/lib/x86_64-linux-gnu/libglib-2.0.so.0.3200.3
7ff082518000-7ff082718000 ---p 000f2000 08:05 527852                    
/lib/x86_64-linux-gnu/libglib-2.0.so.0.3200.3
7ff082718000-7ff082719000 r--p 000f2000 08:05 527852                    
/lib/x86_64-linux-gnu/libglib-2.0.so.0.3200.3
7ff082719000-7ff08271a000 rw-p 000f3000 08:05 527852                    
/lib/x86_64-linux-gnu/libglib-2.0.so.0.3200.3Csound tidy up: Aborted


I have the csd attached:  noisernd.csd
  
i hope to get it working.

thanks



--
View this message in context: http://csound.1045644.n5.nabble.com/Csound-Wiki-tp5726168p5726798.html
Sent from the Csound - General mailing list archive at Nabble.com.

Date2013-08-16 16:15
FromTarmo Johannes
SubjectRe: [Csnd] Re: Csound Wiki
Hi,

I think jack does not connect this way csound to output automatically try

 csound -+rtaudio=jack -odac:system:playback_ -r48000 -k750 noisernd.csd

or can you see csound running in qjackctl ? Can you connect it manually to 
output?

hope it helps,
tarmo

On Friday 16 August 2013 05:22:41 menno wrote:
> I found out that Blue did not discover a Jack client, so i am trying to run
> from the commandline:
> 
> menno@muziek:~/csound/csd$ csound -+rtaudio=jack -odac -r48000 -k750
> noisernd.csd

Date2013-08-16 16:29
Frommenno
Subject[Csnd] Re: Csound Wiki
Of course - it works, i have sound!
 i had a few weeks of holiday and forgot all about the Csound commands.
The commandline and WinXound both are working. Thanks!



--
View this message in context: http://csound.1045644.n5.nabble.com/Csound-Wiki-tp5726168p5726805.html
Sent from the Csound - General mailing list archive at Nabble.com.

Date2013-08-16 19:55
FromSteven Yi
SubjectRe: [Csnd] Re: Csound Wiki
HI Menno,

Just a note, the issue with Blue detecting devices has to do with the
way the devices are reported in the output (it's a little different
than in CS5). The API methods for CS6 aren't usable from interfaces
(i.e. java, python, etc.) so I'm working on updating the device
parsing code to work with both CS5 and CS6.  Hopefully will have a new
release of Blue to fix all this by tomorrow.

Thanks!
steven

On Fri, Aug 16, 2013 at 8:22 AM, menno  wrote:
> hi,
> i do not have had yet the pleasure of hearing a sound from csound in
> realtime, using jack.
> I do get a result when i render csound to a wav file, no problems there.
>
> I found out that Blue did not discover a Jack client, so i am trying to run
> from the commandline:
>
> menno@muziek:~/csound/csd$ csound -+rtaudio=jack -odac -r48000 -k750
> noisernd.csd
> virtual_keyboard real time MIDI plugin for Csound
> graph init
> 0dBFS level = 32768.0
> Csound version 6.00.1 (double samples) Aug 15 2013
> libsndfile-1.0.25
> UnifiedCSD:  noisernd.csd
> STARTING FILE
> Creating options
> Creating orchestra
> Creating score
> rtmidi: ALSA Raw MIDI module enabled
> rtaudio: JACK module enabled
> sample rate overrides: esr = 48000.0000, ekr = 750.0000, ksmps = 64
> Elapsed time at end of orchestra compile: real: 0.002s, CPU: 0.000s
> sorting score ...
>         ... done
> Elapsed time at end of score sort: real: 0.002s, CPU: 0.000s
> Csound version 6.00.1 (double samples) Aug 15 2013
> 0dBFS level = 32768.0
> orch now loaded
> audio buffered in 256 sample-frame blocks
>  0: dac:system:playback_ (system:playback_)
>  1: dac:jack2alsa:playback_ (jack2alsa:playback_)
>  *** rtjack: error connecting output ports
> *** glibc detected *** csound: corrupted double-linked list:
> 0x00000000017ad170 ***
> ======= Backtrace: =========
> /lib/x86_64-linux-gnu/libc.so.6(+0x7eb96)[0x7ff08bb56b96]
> /lib/x86_64-linux-gnu/libc.so.6(+0x7ef00)[0x7ff08bb56f00]
> /lib/x86_64-linux-gnu/libc.so.6(+0x7fb29)[0x7ff08bb57b29]
> /usr/lib/x86_64-linux-gnu/libjack.so.0(+0x44a04)[0x7ff089186a04]
> /usr/lib/x86_64-linux-gnu/libjack.so.0(jack_client_close+0xcf)[0x7ff08918641e]
> /usr/local/lib/csound/plugins64-6.0/librtjack.so(+0x441a)[0x7ff081b7d41a]
> /usr/local/lib/csound/plugins64-6.0/librtjack.so(+0x4509)[0x7ff081b7d509]
> /usr/local/lib/csound/plugins64-6.0/librtjack.so(+0x2f77)[0x7ff081b7bf77]
> /usr/local/lib/csound/plugins64-6.0/librtjack.so(+0x35bb)[0x7ff081b7c5bb]
> /usr/local/lib/libcsound64.so.6.0(+0x6e43f)[0x7ff08c12243f]
> /usr/local/lib/libcsound64.so.6.0(+0x5a0db)[0x7ff08c10e0db]
> /usr/local/lib/libcsound64.so.6.0(csoundStart+0x905)[0x7ff08c24f33c]
> /usr/local/lib/libcsound64.so.6.0(csoundCompile+0x42)[0x7ff08c24f384]
> csound[0x40140f]
> /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xed)[0x7ff08baf976d]
> csound[0x400fb9]
> ======= Memory map: ========
> 00400000-00403000 r-xp 00000000 08:05 283177
> /usr/local/bin/csound
> 00602000-00603000 r--p 00002000 08:05 283177
> /usr/local/bin/csound
> 00603000-00604000 rw-p 00003000 08:05 283177
> /usr/local/bin/csound
> 01609000-017c1000 rw-p 00000000 00:00 0
> [heap]
> 7ff06c000000-7ff06c021000 rw-p 00000000 00:00 0
> 7ff06c021000-7ff070000000 ---p 00000000 00:00 0
> 7ff078000000-7ff078021000 rw-p 00000000 00:00 0
> 7ff078021000-7ff07c000000 ---p 00000000 00:00 0
> 7ff07f90e000-7ff07f90f000 ---p 00000000 00:00 0
> 7ff07f90f000-7ff07f98f000 rw-p 00000000 00:00 0
> 7ff07f98f000-7ff07f991000 r-xp 00000000 08:05 281712
> /usr/local/lib/csound/plugins64-6.0/libipmidi.so
> 7ff07f991000-7ff07fb90000 ---p 00002000 08:05 281712
> /usr/local/lib/csound/plugins64-6.0/libipmidi.so
> 7ff07fb90000-7ff07fb91000 r--p 00001000 08:05 281712
> /usr/local/lib/csound/plugins64-6.0/libipmidi.so
> 7ff07fb91000-7ff07fb92000 rw-p 00002000 08:05 281712
> /usr/local/lib/csound/plugins64-6.0/libipmidi.so
> 7ff07fb92000-7ff07fb9c000 r-xp 00000000 08:05 281577
> /usr/local/lib/csound/plugins64-6.0/librtalsa.so
> 7ff07fb9c000-7ff07fd9b000 ---p 0000a000 08:05 281577
> /usr/local/lib/csound/plugins64-6.0/librtalsa.so
> 7ff07fd9b000-7ff07fd9c000 r--p 00009000 08:05 281577
> /usr/local/lib/csound/plugins64-6.0/librtalsa.so
> 7ff07fd9c000-7ff07fd9d000 rw-p 0000a000 08:05 281577
> /usr/local/lib/csound/plugins64-6.0/librtalsa.so
> 7ff07fd9d000-7ff07fdce000 r-xp 00000000 08:05 283181
> /usr/local/lib/csound/plugins64-6.0/libstdutil.so
> 7ff07fdce000-7ff07ffcd000 ---p 00031000 08:05 283181
> /usr/local/lib/csound/plugins64-6.0/libstdutil.so
> 7ff07ffcd000-7ff07ffce000 r--p 00030000 08:05 283181
> /usr/local/lib/csound/plugins64-6.0/libstdutil.so
> 7ff07ffce000-7ff07ffcf000 rw-p 00031000 08:05 283181
> /usr/local/lib/csound/plugins64-6.0/libstdutil.so
> 7ff07ffcf000-7ff07ffd0000 rw-p 00000000 00:00 0
> 7ff07ffd0000-7ff07ffd1000 r-xp 00000000 08:05 281561
> /usr/local/lib/csound/plugins64-6.0/liburandom.so
> 7ff07ffd1000-7ff0801d0000 ---p 00001000 08:05 281561
> /usr/local/lib/csound/plugins64-6.0/liburandom.so
> 7ff0801d0000-7ff0801d1000 r--p 00000000 08:05 281561
> /usr/local/lib/csound/plugins64-6.0/liburandom.so
> 7ff0801d1000-7ff0801d2000 rw-p 00001000 08:05 281561
> /usr/local/lib/csound/plugins64-6.0/liburandom.so
> 7ff0801d2000-7ff0801d6000 r-xp 00000000 08:05 281555
> /usr/local/lib/csound/plugins64-6.0/libfractalnoise.so
> 7ff0801d6000-7ff0803d5000 ---p 00004000 08:05 281555
> /usr/local/lib/csound/plugins64-6.0/libfractalnoise.so
> 7ff0803d5000-7ff0803d6000 r--p 00003000 08:05 281555
> /usr/local/lib/csound/plugins64-6.0/libfractalnoise.so
> 7ff0803d6000-7ff0803d7000 rw-p 00004000 08:05 281555
> /usr/local/lib/csound/plugins64-6.0/libfractalnoise.so
> 7ff0803d7000-7ff0803d9000 r-xp 00000000 08:05 281552
> /usr/local/lib/csound/plugins64-6.0/libcs_date.so
> 7ff0803d9000-7ff0805d8000 ---p 00002000 08:05 281552
> /usr/local/lib/csound/plugins64-6.0/libcs_date.so
> 7ff0805d8000-7ff0805d9000 r--p 00001000 08:05 281552
> /usr/local/lib/csound/plugins64-6.0/libcs_date.so
> 7ff0805d9000-7ff0805da000 rw-p 00002000 08:05 281552
> /usr/local/lib/csound/plugins64-6.0/libcs_date.so
> 7ff0805da000-7ff0805db000 r-xp 00000000 08:05 281553
> /usr/local/lib/csound/plugins64-6.0/libsystem_call.so
> 7ff0805db000-7ff0807da000 ---p 00001000 08:05 281553
> /usr/local/lib/csound/plugins64-6.0/libsystem_call.so
> 7ff0807da000-7ff0807db000 r--p 00000000 08:05 281553
> /usr/local/lib/csound/plugins64-6.0/libsystem_call.so
> 7ff0807db000-7ff0807dc000 rw-p 00001000 08:05 281553
> /usr/local/lib/csound/plugins64-6.0/libsystem_call.so
> 7ff0807dc000-7ff0807dd000 r-xp 00000000 08:05 281567
> /usr/local/lib/csound/plugins64-6.0/libjackTransport.so
> 7ff0807dd000-7ff0809dc000 ---p 00001000 08:05 281567
> /usr/local/lib/csound/plugins64-6.0/libjackTransport.so
> 7ff0809dc000-7ff0809dd000 r--p 00000000 08:05 281567
> /usr/local/lib/csound/plugins64-6.0/libjackTransport.so
> 7ff0809dd000-7ff0809de000 rw-p 00001000 08:05 281567
> /usr/local/lib/csound/plugins64-6.0/libjackTransport.so
> 7ff0809de000-7ff0809e0000 r-xp 00000000 08:05 552065
> /lib/x86_64-linux-gnu/libutil-2.15.so
> 7ff0809e0000-7ff080bdf000 ---p 00002000 08:05 552065
> /lib/x86_64-linux-gnu/libutil-2.15.so
> 7ff080bdf000-7ff080be0000 r--p 00001000 08:05 552065
> /lib/x86_64-linux-gnu/libutil-2.15.so
> 7ff080be0000-7ff080be1000 rw-p 00002000 08:05 552065
> /lib/x86_64-linux-gnu/libutil-2.15.so
> 7ff080be1000-7ff080d92000 r-xp 00000000 08:05 544791
> /lib/x86_64-linux-gnu/libcrypto.so.1.0.0
> 7ff080d92000-7ff080f92000 ---p 001b1000 08:05 544791
> /lib/x86_64-linux-gnu/libcrypto.so.1.0.0
> 7ff080f92000-7ff080fad000 r--p 001b1000 08:05 544791
> /lib/x86_64-linux-gnu/libcrypto.so.1.0.0
> 7ff080fad000-7ff080fb8000 rw-p 001cc000 08:05 544791
> /lib/x86_64-linux-gnu/libcrypto.so.1.0.0
> 7ff080fb8000-7ff080fbc000 rw-p 00000000 00:00 0
> 7ff080fbc000-7ff081010000 r-xp 00000000 08:05 544792
> /lib/x86_64-linux-gnu/libssl.so.1.0.0
> 7ff081010000-7ff081210000 ---p 00054000 08:05 544792
> /lib/x86_64-linux-gnu/libssl.so.1.0.0
> 7ff081210000-7ff081213000 r--p 00054000 08:05 544792
> /lib/x86_64-linux-gnu/libssl.so.1.0.0
> 7ff081213000-7ff081219000 rw-p 00057000 08:05 544792
> /lib/x86_64-linux-gnu/libssl.so.1.0.0
> 7ff081219000-7ff08121a000 rw-p 00000000 00:00 0
> 7ff08121a000-7ff08149b000 r-xp 00000000 08:05 159713
> /usr/lib/libpython2.7.so.1.0
> 7ff08149b000-7ff08169a000 ---p 00281000 08:05 159713
> /usr/lib/libpython2.7.so.1.0
> 7ff08169a000-7ff08169c000 r--p 00280000 08:05 159713
> /usr/lib/libpython2.7.so.1.0
> 7ff08169c000-7ff081705000 rw-p 00282000 08:05 159713
> /usr/lib/libpython2.7.so.1.0
> 7ff081705000-7ff081717000 rw-p 00000000 00:00 0
> 7ff081717000-7ff081727000 r-xp 00000000 08:05 281571
> /usr/local/lib/csound/plugins64-6.0/libpy.so
> 7ff081727000-7ff081926000 ---p 00010000 08:05 281571
> /usr/local/lib/csound/plugins64-6.0/libpy.so
> 7ff081926000-7ff081927000 r--p 0000f000 08:05 281571
> /usr/local/lib/csound/plugins64-6.0/libpy.so
> 7ff081927000-7ff081929000 rw-p 00010000 08:05 281571
> /usr/local/lib/csound/plugins64-6.0/libpy.so
> 7ff081929000-7ff081976000 r-xp 00000000 08:05 281714
> /usr/local/lib/csound/plugins64-6.0/libwidgets.so
> 7ff081976000-7ff081b75000 ---p 0004d000 08:05 281714
> /usr/local/lib/csound/plugins64-6.0/libwidgets.so
> 7ff081b75000-7ff081b77000 r--p 0004c000 08:05 281714
> /usr/local/lib/csound/plugins64-6.0/libwidgets.so
> 7ff081b77000-7ff081b79000 rw-p 0004e000 08:05 281714
> /usr/local/lib/csound/plugins64-6.0/libwidgets.so
> 7ff081b79000-7ff081b7f000 r-xp 00000000 08:05 281713
> /usr/local/lib/csound/plugins64-6.0/librtjack.so
> 7ff081b7f000-7ff081d7e000 ---p 00006000 08:05 281713
> /usr/local/lib/csound/plugins64-6.0/librtjack.so
> 7ff081d7e000-7ff081d7f000 r--p 00005000 08:05 281713
> /usr/local/lib/csound/plugins64-6.0/librtjack.so
> 7ff081d7f000-7ff081d80000 rw-p 00006000 08:05 281713
> /usr/local/lib/csound/plugins64-6.0/librtjack.so
> 7ff081d80000-7ff081da2000 r-xp 00000000 08:05 527924
> /lib/x86_64-linux-gnu/libtinfo.so.5.9
> 7ff081da2000-7ff081fa2000 ---p 00022000 08:05 527924
> /lib/x86_64-linux-gnu/libtinfo.so.5.9
> 7ff081fa2000-7ff081fa6000 r--p 00022000 08:05 527924
> /lib/x86_64-linux-gnu/libtinfo.so.5.9
> 7ff081fa6000-7ff081fa7000 rw-p 00026000 08:05 527924
> /lib/x86_64-linux-gnu/libtinfo.so.5.9
> 7ff081fa7000-7ff081fe3000 r-xp 00000000 08:05 527900
> /lib/x86_64-linux-gnu/libpcre.so.3.12.1
> 7ff081fe3000-7ff0821e2000 ---p 0003c000 08:05 527900
> /lib/x86_64-linux-gnu/libpcre.so.3.12.1
> 7ff0821e2000-7ff0821e3000 r--p 0003b000 08:05 527900
> /lib/x86_64-linux-gnu/libpcre.so.3.12.1
> 7ff0821e3000-7ff0821e4000 rw-p 0003c000 08:05 527900
> /lib/x86_64-linux-gnu/libpcre.so.3.12.1
> 7ff0821e4000-7ff08221d000 r-xp 00000000 08:05 527910
> /lib/x86_64-linux-gnu/libreadline.so.6.2
> 7ff08221d000-7ff08241d000 ---p 00039000 08:05 527910
> /lib/x86_64-linux-gnu/libreadline.so.6.2
> 7ff08241d000-7ff08241f000 r--p 00039000 08:05 527910
> /lib/x86_64-linux-gnu/libreadline.so.6.2
> 7ff08241f000-7ff082425000 rw-p 0003b000 08:05 527910
> /lib/x86_64-linux-gnu/libreadline.so.6.2
> 7ff082425000-7ff082426000 rw-p 00000000 00:00 0
> 7ff082426000-7ff082518000 r-xp 00000000 08:05 527852
> /lib/x86_64-linux-gnu/libglib-2.0.so.0.3200.3
> 7ff082518000-7ff082718000 ---p 000f2000 08:05 527852
> /lib/x86_64-linux-gnu/libglib-2.0.so.0.3200.3
> 7ff082718000-7ff082719000 r--p 000f2000 08:05 527852
> /lib/x86_64-linux-gnu/libglib-2.0.so.0.3200.3
> 7ff082719000-7ff08271a000 rw-p 000f3000 08:05 527852
> /lib/x86_64-linux-gnu/libglib-2.0.so.0.3200.3Csound tidy up: Aborted
>
>
> I have the csd attached:  noisernd.csd
> 
> i hope to get it working.
>
> thanks
>
>
>
> --
> View this message in context: http://csound.1045644.n5.nabble.com/Csound-Wiki-tp5726168p5726798.html
> Sent from the Csound - General mailing list archive at Nabble.com.
>
>
> Send bugs reports to the Sourceforge bug trackers
> csound6:
>             https://sourceforge.net/p/csound/tickets/
> csound5:
>             https://sourceforge.net/p/csound/bugs/
> Discussions of bugs and features can be posted here
> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
>
>