>From what I understand, OLPCsound will be around as long as the XO-1 is 
around, or until a new Fedora build and download method for Activities (that 
is standard) is established for the XO-1. The software situation with XO is 
basically frozen (for the average user) and in a major state of flux.

I'm assuming by OLPCsound you mean a slightly stripped-down version of 5.08 
(the one john ff described some time ago). I assume by Csound you are 
referring to 5.10. Is this Csound comparably stripped down to OLPCsound? 
(Hopefully it is, if it is designed to work with Sugar on a Stick and less 
powerful [older] systems.)

Also, OLPCsound has the advantage that it works with python scripts in 
Sugar; at least for the moment "Csound" doesn't - not on the XO, not on 
SoaS, not on *anything*.

Yes, I'm working with Peter Robinson; unfortunately, I'm technically naive, 
and my "help" usually amounts to fumbling in the dark.

Art Hunkins

----- Original Message ----- 
From: "Victor Lazzarini" 
To: "Developer discussions" 
Sent: Monday, July 27, 2009 9:26 AM
Subject: Re: [Cs-dev] Linux 5.10 build hints?


> There is no OLPCsound anymore, it's just csound. If the RPM is
> broken you will need to tell Peter Robinson who is the package
> maintainer.
>
> Victor
>
> At 19:44 26/07/2009, you wrote:
>>John,
>>
>>AFAIK, the problem may not actually be in the Csound build itself, but in
>>the building of the Python interface.
>>
>>When installing Csound in Sugar on a Stick, a csound-python package must 
>>be
>>installed as well. It is this latter package that is probably faulty. The
>>signs are (when running Csound from your python script - the way things 
>>are
>>done in Sugar): cannot import csnd.py or _csnd.so. (Those files are either
>>void or absent or bad or misplaced.)
>>
>>In a word, what is required here is simply a 5.10-updated OLPCsound. I
>>assume that python2.6 is required instead of the 2.5 you list.
>>
>>Also, I recall your saying that FLTK is not built for the OLPC (same 
>>should
>>be for Sugar - to keep things lean), nor are the ambisonic opcodes 
>>included.
>>I think other features were also not included; can you recall which ones?
>>
>>Thanks for your insights.
>>
>>Art Hunkins
>>
>>----- Original Message -----
>>From: 
>>To: "Art Hunkins" ; "Developer discussions"
>>
>>Sent: Sunday, July 26, 2009 2:11 PM
>>Subject: Re: [Cs-dev] Linux 5.10 build hints?
>>
>>
>> >> I'd appreciate knowing of *anyone* with a successful Linux build of 
>> >> 5.10,
>> >> and what (if any) tricks you needed to play in order for it to work.
>> >
>> > No tricks; just ran my usual script
>> >
>> > scons buildCsoundVST=0 generateTags=1 useJack=1 generateZip=0
>> > usePortMIDI=1 install=0 useALSA=1 useOSC=1 buildInterfaces=1
>> > buildTclcsound=1 buildJavaWrapper=1 pythonVersion=2.5 
>> > buildPythonOpcodes=1
>> > noDebug=0 buildPDClass=1 buildWinsound=1 useUDP=1 buildNewParser=1
>> > useGettext=1 gcc4opt=i386 buildVirtual=1 buildCsoundAC=0 includeMP3=1
>> > includeWii=1 includeP5Glove=1 NewParserDebug=1
>> >
>> > No problems at all.
>> >
>> > What re the problemsyou are experiencing?
>> >
>> > ==John ff
>> >
>> >
>> >
>> ------------------------------------------------------------------------------
>> > _______________________________________________
>> > Csound-devel mailing list
>> > Csound-devel@lists.sourceforge.net
>> > https://lists.sourceforge.net/lists/listinfo/csound-devel
>>
>>
>>------------------------------------------------------------------------------
>>_______________________________________________
>>Csound-devel mailing list
>>Csound-devel@lists.sourceforge.net
>>https://lists.sourceforge.net/lists/listinfo/csound-devel
>
> Victor Lazzarini
> Music Technology Laboratory
> Music Department
> National University of Ireland, Maynooth
>
>
> ------------------------------------------------------------------------------
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel 


------------------------------------------------------------------------------
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

olpcsound is not going to be updated to 5.10 because it clashes with csound.
This situation now exists because the olpc and fedora branches were
merged, so we decided it was better to have a full csound 5.10 package
instead of a stripped-down. There are not a lot of significant diffferences,
as the csound rpm is separated into subpackages (csound-python,
csound-java, etc) that make it easy to install separate components.

If the csound rpm package is broken, then it needs to be fixed.

Victor

At 16:09 27/07/2009, you wrote:
> >From what I understand, OLPCsound will be around as long as the XO-1 is
>around, or until a new Fedora build and download method for Activities (that
>is standard) is established for the XO-1. The software situation with XO is
>basically frozen (for the average user) and in a major state of flux.
>
>I'm assuming by OLPCsound you mean a slightly stripped-down version of 5.08
>(the one john ff described some time ago). I assume by Csound you are
>referring to 5.10. Is this Csound comparably stripped down to OLPCsound?
>(Hopefully it is, if it is designed to work with Sugar on a Stick and less
>powerful [older] systems.)
>
>Also, OLPCsound has the advantage that it works with python scripts in
>Sugar; at least for the moment "Csound" doesn't - not on the XO, not on
>SoaS, not on *anything*.
>
>Yes, I'm working with Peter Robinson; unfortunately, I'm technically naive,
>and my "help" usually amounts to fumbling in the dark.
>
>Art Hunkins
>
>----- Original Message -----
>From: "Victor Lazzarini" 
>To: "Developer discussions" 
>Sent: Monday, July 27, 2009 9:26 AM
>Subject: Re: [Cs-dev] Linux 5.10 build hints?
>
>
> > There is no OLPCsound anymore, it's just csound. If the RPM is
> > broken you will need to tell Peter Robinson who is the package
> > maintainer.
> >
> > Victor
> >
> > At 19:44 26/07/2009, you wrote:
> >>John,
> >>
> >>AFAIK, the problem may not actually be in the Csound build itself, but in
> >>the building of the Python interface.
> >>
> >>When installing Csound in Sugar on a Stick, a csound-python package must
> >>be
> >>installed as well. It is this latter package that is probably faulty. The
> >>signs are (when running Csound from your python script - the way things
> >>are
> >>done in Sugar): cannot import csnd.py or _csnd.so. (Those files are either
> >>void or absent or bad or misplaced.)
> >>
> >>In a word, what is required here is simply a 5.10-updated OLPCsound. I
> >>assume that python2.6 is required instead of the 2.5 you list.
> >>
> >>Also, I recall your saying that FLTK is not built for the OLPC (same
> >>should
> >>be for Sugar - to keep things lean), nor are the ambisonic opcodes
> >>included.
> >>I think other features were also not included; can you recall which ones?
> >>
> >>Thanks for your insights.
> >>
> >>Art Hunkins
> >>
> >>----- Original Message -----
> >>From: 
> >>To: "Art Hunkins" ; "Developer discussions"
> >>
> >>Sent: Sunday, July 26, 2009 2:11 PM
> >>Subject: Re: [Cs-dev] Linux 5.10 build hints?
> >>
> >>
> >> >> I'd appreciate knowing of *anyone* with a successful Linux build of
> >> >> 5.10,
> >> >> and what (if any) tricks you needed to play in order for it to work.
> >> >
> >> > No tricks; just ran my usual script
> >> >
> >> > scons buildCsoundVST=0 generateTags=1 useJack=1 generateZip=0
> >> > usePortMIDI=1 install=0 useALSA=1 useOSC=1 buildInterfaces=1
> >> > buildTclcsound=1 buildJavaWrapper=1 pythonVersion=2.5
> >> > buildPythonOpcodes=1
> >> > noDebug=0 buildPDClass=1 buildWinsound=1 useUDP=1 buildNewParser=1
> >> > useGettext=1 gcc4opt=i386 buildVirtual=1 buildCsoundAC=0 includeMP3=1
> >> > includeWii=1 includeP5Glove=1 NewParserDebug=1
> >> >
> >> > No problems at all.
> >> >
> >> > What re the problemsyou are experiencing?
> >> >
> >> > ==John ff
> >> >
> >> >
> >> >
> >> 
> ------------------------------------------------------------------------------
> >> > _______________________________________________
> >> > Csound-devel mailing list
> >> > Csound-devel@lists.sourceforge.net
> >> > https://lists.sourceforge.net/lists/listinfo/csound-devel
> >>
> >>
> >>------------------------------------------------------------------ 
> ------------
> >>_______________________________________________
> >>Csound-devel mailing list
> >>Csound-devel@lists.sourceforge.net
> >>https://lists.sourceforge.net/lists/listinfo/csound-devel
> >
> > Victor Lazzarini
> > Music Technology Laboratory
> > Music Department
> > National University of Ireland, Maynooth
> >
> >
> > 
> ------------------------------------------------------------------------------
> > _______________________________________________
> > Csound-devel mailing list
> > Csound-devel@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/csound-devel
>
>
>------------------------------------------------------------------------------
>_______________________________________________
>Csound-devel mailing list
>Csound-devel@lists.sourceforge.net
>https://lists.sourceforge.net/lists/listinfo/csound-devel

Victor Lazzarini
Music Technology Laboratory
Music Department
National University of Ireland, Maynooth 


------------------------------------------------------------------------------
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Hi,

I think the reason for OLPCsound had to do with performance but mostly
with patents and code licenses. It's still possible to build a Csound
5.10 with only the parts available for OLPCsound if you build with:
buildOLPC=1

Apart from not building certain opcode plugins, it also force FLTK not
to be built. I wouldn't think OLPCsound is significantly better in
terms of performance than ordinary csound.

I would think Fedora can still host the two packages but make them
conflict. I.e. you need to uninstall one to install the other one. I
know this can be done with apt, so I suspect its not a problem with
yum. Having OLPCsound available as well means that it can be installed
without having to get many of Csound's dependencies like FLTK and
portaudio.

Cheers,
Andrés

On Mon, Jul 27, 2009 at 10:09 AM, Art Hunkins wrote:
> >From what I understand, OLPCsound will be around as long as the XO-1 is
> around, or until a new Fedora build and download method for Activities (that
> is standard) is established for the XO-1. The software situation with XO is
> basically frozen (for the average user) and in a major state of flux.
>
> I'm assuming by OLPCsound you mean a slightly stripped-down version of 5.08
> (the one john ff described some time ago). I assume by Csound you are
> referring to 5.10. Is this Csound comparably stripped down to OLPCsound?
> (Hopefully it is, if it is designed to work with Sugar on a Stick and less
> powerful [older] systems.)
>
> Also, OLPCsound has the advantage that it works with python scripts in
> Sugar; at least for the moment "Csound" doesn't - not on the XO, not on
> SoaS, not on *anything*.
>
> Yes, I'm working with Peter Robinson; unfortunately, I'm technically naive,
> and my "help" usually amounts to fumbling in the dark.
>
> Art Hunkins
>
> ----- Original Message -----
> From: "Victor Lazzarini" 
> To: "Developer discussions" 
> Sent: Monday, July 27, 2009 9:26 AM
> Subject: Re: [Cs-dev] Linux 5.10 build hints?
>
>
>> There is no OLPCsound anymore, it's just csound. If the RPM is
>> broken you will need to tell Peter Robinson who is the package
>> maintainer.
>>
>> Victor
>>
>> At 19:44 26/07/2009, you wrote:
>>>John,
>>>
>>>AFAIK, the problem may not actually be in the Csound build itself, but in
>>>the building of the Python interface.
>>>
>>>When installing Csound in Sugar on a Stick, a csound-python package must
>>>be
>>>installed as well. It is this latter package that is probably faulty. The
>>>signs are (when running Csound from your python script - the way things
>>>are
>>>done in Sugar): cannot import csnd.py or _csnd.so. (Those files are either
>>>void or absent or bad or misplaced.)
>>>
>>>In a word, what is required here is simply a 5.10-updated OLPCsound. I
>>>assume that python2.6 is required instead of the 2.5 you list.
>>>
>>>Also, I recall your saying that FLTK is not built for the OLPC (same
>>>should
>>>be for Sugar - to keep things lean), nor are the ambisonic opcodes
>>>included.
>>>I think other features were also not included; can you recall which ones?
>>>
>>>Thanks for your insights.
>>>
>>>Art Hunkins
>>>
>>>----- Original Message -----
>>>From: 
>>>To: "Art Hunkins" ; "Developer discussions"
>>>
>>>Sent: Sunday, July 26, 2009 2:11 PM
>>>Subject: Re: [Cs-dev] Linux 5.10 build hints?
>>>
>>>
>>> >> I'd appreciate knowing of *anyone* with a successful Linux build of
>>> >> 5.10,
>>> >> and what (if any) tricks you needed to play in order for it to work.
>>> >
>>> > No tricks; just ran my usual script
>>> >
>>> > scons buildCsoundVST=0 generateTags=1 useJack=1 generateZip=0
>>> > usePortMIDI=1 install=0 useALSA=1 useOSC=1 buildInterfaces=1
>>> > buildTclcsound=1 buildJavaWrapper=1 pythonVersion=2.5
>>> > buildPythonOpcodes=1
>>> > noDebug=0 buildPDClass=1 buildWinsound=1 useUDP=1 buildNewParser=1
>>> > useGettext=1 gcc4opt=i386 buildVirtual=1 buildCsoundAC=0 includeMP3=1
>>> > includeWii=1 includeP5Glove=1 NewParserDebug=1
>>> >
>>> > No problems at all.
>>> >
>>> > What re the problemsyou are experiencing?
>>> >
>>> > ==John ff
>>> >
>>> >
>>> >
>>> ------------------------------------------------------------------------------
>>> > _______________________________________________
>>> > Csound-devel mailing list
>>> > Csound-devel@lists.sourceforge.net
>>> > https://lists.sourceforge.net/lists/listinfo/csound-devel
>>>
>>>
>>>------------------------------------------------------------------------------
>>>_______________________________________________
>>>Csound-devel mailing list
>>>Csound-devel@lists.sourceforge.net
>>>https://lists.sourceforge.net/lists/listinfo/csound-devel
>>
>> Victor Lazzarini
>> Music Technology Laboratory
>> Music Department
>> National University of Ireland, Maynooth
>>
>>
>> ------------------------------------------------------------------------------
>> _______________________________________________
>> Csound-devel mailing list
>> Csound-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>
>
> ------------------------------------------------------------------------------
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel
>



-- 


Andrés

------------------------------------------------------------------------------
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net