I have registered my "interest" with Farnell; remains to be seen when I 
will get one. The memory size may be an issue - can't have many huge 
soundfiles in memory, I suspect. It could be a good case for a 
'cut-down" small-footprint version.

Richard Dobson



On 29/02/2012 17:52, Roger Kelly wrote:
> http://www.raspberrypi.org/
>
> Would CSound be able to run on the Raspberry Pi $25 computer?
>
> Lots of possibilites here if so.

The small amount of RAM, which is shared with the GPU is also an
issue. I think the max is 256mb? I was joking today that I could stick
one to the back of a flat-screen monitor and make my own imac. Might
be nice for installations where space is a premium.

On 29 February 2012 18:01, Richard Dobson
 wrote:
> I have registered my "interest" with Farnell; remains to be seen when I will
> get one. The memory size may be an issue - can't have many huge soundfiles
> in memory, I suspect. It could be a good case for a 'cut-down"
> small-footprint version.
>
> Richard Dobson
>
>
>
>
> On 29/02/2012 17:52, Roger Kelly wrote:
>>
>> http://www.raspberrypi.org/
>>
>> Would CSound be able to run on the Raspberry Pi $25 computer?
>>
>> Lots of possibilites here if so.
>
>
>
>
> 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"
>

You can write games with very small footprints, e.g. Rollercoaster
Tycoon, in assembly language, so I don't see why Csound couldn't be
ported from C to assembly. (I've always wanted to do that!) I love
assembly, I just need to write in it more.

What would it be called, ... "asound?" Nope, sorry... Linux already
has an asound for ALSA if I'm not mistaken.

On 2/29/12, Richard Dobson  wrote:
> I have registered my "interest" with Farnell; remains to be seen when I
> will get one. The memory size may be an issue - can't have many huge
> soundfiles in memory, I suspect. It could be a good case for a
> 'cut-down" small-footprint version.
>
> Richard Dobson
>
>
>
> On 29/02/2012 17:52, Roger Kelly wrote:
>> http://www.raspberrypi.org/
>>
>> Would CSound be able to run on the Raspberry Pi $25 computer?
>>
>> Lots of possibilites here if so.
>
>
>
> 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"
>
>

So how do you program one of those computers unless you write in Assembly?

On 2/29/12, Rory Walsh  wrote:
> The small amount of RAM, which is shared with the GPU is also an
> issue. I think the max is 256mb? I was joking today that I could stick
> one to the back of a flat-screen monitor and make my own imac. Might
> be nice for installations where space is a premium.
>
> On 29 February 2012 18:01, Richard Dobson
>  wrote:
>> I have registered my "interest" with Farnell; remains to be seen when I
>> will
>> get one. The memory size may be an issue - can't have many huge soundfiles
>> in memory, I suspect. It could be a good case for a 'cut-down"
>> small-footprint version.
>>
>> Richard Dobson
>>
>>
>>
>>
>> On 29/02/2012 17:52, Roger Kelly wrote:
>>>
>>> http://www.raspberrypi.org/
>>>
>>> Would CSound be able to run on the Raspberry Pi $25 computer?
>>>
>>> Lots of possibilites here if so.
>>
>>
>>
>>
>> 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"
>
>

Just throw an operating system on it and away you go. Ubuntu ARM seems
like an obvious choice?


d case for a 'cut-down"
>>> small-footprint version.
>>>
>>> Richard Dobson
>>>
>>>
>>>
>>>
>>> On 29/02/2012 17:52, Roger Kelly wrote:
>>>>
>>>> http://www.raspberrypi.org/
>>>>
>>>> Would CSound be able to run on the Raspberry Pi $25 computer?
>>>>
>>>> Lots of possibilites here if so.
>>>
>>>
>>>
>>>
>>> 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"
>>
>>
>
>
> 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 think I read there was a Fedora distribution that you can run with
it from SD card; if so, csound may already be there through package
manager, which would be nice.  The processor seems enough to get a
fair amount of polyphony with small complexity instruments with a few
effects; large sample sets would be a mess, though possibly streaming
from the SD card could work depending on the speed of the SD reader.
We have csound running on arm processors so I don't see any problems
for this machine.

The RS site has specs:

http://uk.rs-online.com/web/generalDisplay.html?id=raspberrypi&cm_mmc=UK-PPC-0212-_-02_Raspberry_PI-_-Raspberry_PI-_-Raspberry_Pi



On Wed, Feb 29, 2012 at 6:06 PM, Adam Puckett  wrote:
> You can write games with very small footprints, e.g. Rollercoaster
> Tycoon, in assembly language, so I don't see why Csound couldn't be
> ported from C to assembly. (I've always wanted to do that!) I love
> assembly, I just need to write in it more.
>
> What would it be called, ... "asound?" Nope, sorry... Linux already
> has an asound for ALSA if I'm not mistaken.
>
> On 2/29/12, Richard Dobson  wrote:
>> I have registered my "interest" with Farnell; remains to be seen when I
>> will get one. The memory size may be an issue - can't have many huge
>> soundfiles in memory, I suspect. It could be a good case for a
>> 'cut-down" small-footprint version.
>>
>> Richard Dobson
>>
>>
>>
>> On 29/02/2012 17:52, Roger Kelly wrote:
>>> http://www.raspberrypi.org/
>>>
>>> Would CSound be able to run on the Raspberry Pi $25 computer?
>>>
>>> Lots of possibilites here if so.
>>
>>
>>
>> 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 02/29/2012 10:01 AM, Richard Dobson wrote:
> I have registered my "interest" with Farnell; remains to be seen when I 
> will get one. The memory size may be an issue - can't have many huge 
> soundfiles in memory, I suspect. It could be a good case for a 
> 'cut-down" small-footprint version.

At the risk of sparking discussions of punch tape, I first ran
csound under Linux on a 486 with 4 *meg* of ram.

On 01/03/2012 18:06, Toby wrote:
> On 02/29/2012 10:01 AM, Richard Dobson wrote:
>> I have registered my "interest" with Farnell; remains to be seen when I
>> will get one. The memory size may be an issue - can't have many huge
>> soundfiles in memory, I suspect. It could be a good case for a
>> 'cut-down" small-footprint version.
>
> At the risk of sparking discussions of punch tape, I first ran
> csound under Linux on a 486 with 4 *meg* of ram.
>


I am sure it will run (my first exposure to Csound was on a 1MB Atari 
ST), unanticipated tech issues notwithstanding; but clearly there will 
be limits on loading large soundfiles/analysis-files into RAM, compared 
to what we are used to on milti-GB machines.

Richard Dobson

Current csound on this macine is 2Mb of code and fixed data.  Probably a
little less on 32bit arm

>
> 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"
>
>
>
>

This is a specific area of interest for me; using Csound in embedded systems.

The current trend seems to be in moving Csound to a complex build
system heavily reliant on C++ and a myriad of other bindings which may
complicate the parallel trend in computing where users consider
working with Csound on "micro" installations, such as the Raspberry
Pi.

What's the current best way to set up a "micro" Csound build from
source without any of the algorithmic/ C++/ Lua/ Boost/ Swig/ Python/
etc etc stuff?

Say I just wanted the standard sound generating and synthesis opcodes
from a vanilla Csound build. Assume as a user maybe I know 1 or 2
things about sound synthesis, maybe enough to get a 1000 Hz sine wave
out of oscil with a lot of clicks at the start and end of note
events... would I have to cross-compile Csound from a "regular"
computer for use on the Raspberry Pi?

What alternative solutions are there currently for building Csound
from source on something like the Raspberry Pi that are lightweight?
Is the whole build system still necessarily based on SConstruct?


-David

I have a micro Csound build using qmake that I use.  It only builds
the Csound C API library.  It depends on libsndfile, and if you're
compiling on Windows it depends on pthreads, too.  If you're familiar
with qmake feel free to take a look at
http://gitorious.org/audiocarver/audiocarver/trees/master/src/libs/csound

The last time I updated it was back in December so it may be a little
out of date, but the csound.pri file should give you the necessary
compiler flags and source files even if you're not familiar with
qmake.

If you go one directory up at
http://gitorious.org/audiocarver/audiocarver/trees/master/src/libs
you'll see libsndfile and pthreads builds, too, but I'm not sure I'm
building libsndfile correctly for all platforms.

All the builds in my project work with Intel x86 and x64 based systems
running Linux, OSX Lion, or WIndows 7.  That much I do know for sure
=)

Cheers,
~ andy.f



On Fri, Mar 2, 2012 at 12:55 AM, David Akbari  wrote:
> This is a specific area of interest for me; using Csound in embedded systems.
>
> The current trend seems to be in moving Csound to a complex build
> system heavily reliant on C++ and a myriad of other bindings which may
> complicate the parallel trend in computing where users consider
> working with Csound on "micro" installations, such as the Raspberry
> Pi.
>
> What's the current best way to set up a "micro" Csound build from
> source without any of the algorithmic/ C++/ Lua/ Boost/ Swig/ Python/
> etc etc stuff?
>
> Say I just wanted the standard sound generating and synthesis opcodes
> from a vanilla Csound build. Assume as a user maybe I know 1 or 2
> things about sound synthesis, maybe enough to get a 1000 Hz sine wave
> out of oscil with a lot of clicks at the start and end of note
> events... would I have to cross-compile Csound from a "regular"
> computer for use on the Raspberry Pi?
>
> What alternative solutions are there currently for building Csound
> from source on something like the Raspberry Pi that are lightweight?
> Is the whole build system still necessarily based on SConstruct?
>
>
> -David
>
>
> 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"
>