Hi,

I would also like to see a new release soon. What I would most love to
see in the next release:
- Simple cross-platform editor/front-end particularly to ease running
and editing examples, that newbies can easily step into.

Cheers,
Andres

Steven Yi wrote:
> Hi All,
>
> It being a new year I thought I'd query the list to see what everyone
> thought about Csound's current status as well as seeing about things
> we would all like to achieve with where to take Csound.
>
> Regarding the current release of Csound, I think that the fix that
> Anthony suggested and that I checked in regarding paths on Windows
> seems like it should get out to the public as quickly as possible and
> I'd like to request that at least a new Windows build be released and
> better if a new release all around was to happen.  I don't think it
> would have to be a major point release, just a minor mostly bug fix
> release so maybe 5.04.1.  It seems that the bug has caused a number of
> problems for people either using the GUI's or API.  Any thoughts?
>
> Also, I don't remember the status of the problem David Akbari posted
> about and if that was ever resolved.
>
> Regarding where Csound is going, I realized that in the past when
> there was heated ranting by a user or users that it often spurred a
> lot of quick (if stressful!) changes.  Rather than waiting for a
> heated rant, shall we poll the main list for user thoughts on where
> they see deficiencies in the current Csound releases?
>
> As for personal work, I've taken a long break from the new parser but
> I think will resume work on that next week.  Rather than continue to
> work on that in a separate branch I'd like to integrate that back into
> the HEAD branch as well as do as I mentioned a month or so ago, which
> is to set up two layers of options to use: one in SConstruct that
> would build in the new parser or not, and second a commandline flag to
> enable using the new parser.  Both of those would default to no,
> meaning if you just checked out from CVS and didn't turn on to build
> the parser, nothing would change for you.  Even if you built with the
> new parser, it wouldn't be used unless explicitly told to via
> commandline, so again nothing would change for normal usage.  The code
> is encapsulated into its own files so does not affect the current use
> of Csound even when compiled in, so I think this is very safe to
> integrate.  If everyone is okay with this, I'll go ahead on Monday to
> integrate and start working from there.
>
> Thanks!
> steven
>
> -------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share your
> opinions on IT & business topics through brief surveys - and earn cash
> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel
>
>   


-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

I agree completely - and this would include a version for IntelMacs!

-dB

On Jan 10, 2007, at 7:34 PM, Andres Cabrera wrote:

> Hi,
>
> I would also like to see a new release soon. What I would most love to
> see in the next release:
> - Simple cross-platform editor/front-end particularly to ease running
> and editing examples, that newbies can easily step into.
>
> Cheers,
> Andres
>
> Steven Yi wrote:
>> Hi All,
>>
>> It being a new year I thought I'd query the list to see what everyone
>> thought about Csound's current status as well as seeing about things
>> we would all like to achieve with where to take Csound.
>>
>> Regarding the current release of Csound, I think that the fix that
>> Anthony suggested and that I checked in regarding paths on Windows
>> seems like it should get out to the public as quickly as possible and
>> I'd like to request that at least a new Windows build be released and
>> better if a new release all around was to happen.  I don't think it
>> would have to be a major point release, just a minor mostly bug fix
>> release so maybe 5.04.1.  It seems that the bug has caused a  
>> number of
>> problems for people either using the GUI's or API.  Any thoughts?
>>
>> Also, I don't remember the status of the problem David Akbari posted
>> about and if that was ever resolved.
>>
>> Regarding where Csound is going, I realized that in the past when
>> there was heated ranting by a user or users that it often spurred a
>> lot of quick (if stressful!) changes.  Rather than waiting for a
>> heated rant, shall we poll the main list for user thoughts on where
>> they see deficiencies in the current Csound releases?
>>
>> As for personal work, I've taken a long break from the new parser but
>> I think will resume work on that next week.  Rather than continue to
>> work on that in a separate branch I'd like to integrate that back  
>> into
>> the HEAD branch as well as do as I mentioned a month or so ago, which
>> is to set up two layers of options to use: one in SConstruct that
>> would build in the new parser or not, and second a commandline  
>> flag to
>> enable using the new parser.  Both of those would default to no,
>> meaning if you just checked out from CVS and didn't turn on to build
>> the parser, nothing would change for you.  Even if you built with the
>> new parser, it wouldn't be used unless explicitly told to via
>> commandline, so again nothing would change for normal usage.  The  
>> code
>> is encapsulated into its own files so does not affect the current use
>> of Csound even when compiled in, so I think this is very safe to
>> integrate.  If everyone is okay with this, I'll go ahead on Monday to
>> integrate and start working from there.
>>
>> Thanks!
>> steven
>>
>> --------------------------------------------------------------------- 
>> ----
>> Take Surveys. Earn Cash. Influence the Future of IT
>> Join SourceForge.net's Techsay panel and you'll get the chance to  
>> share your
>> opinions on IT & business topics through brief surveys - and earn  
>> cash
>> http://www.techsay.com/default.php? 
>> page=join.php&p=sourceforge&CID=DEVDEV
>> _______________________________________________
>> Csound-devel mailing list
>> Csound-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>
>>
>
>
> ---------------------------------------------------------------------- 
> ---
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to  
> share your
> opinions on IT & business topics through brief surveys - and earn cash
> http://www.techsay.com/default.php? 
> page=join.php&p=sourceforge&CID=DEVDEV
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel


-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Agree with you there that MacCsound is an amazingly productive and  
intuitive front-end.

-dB

On Jan 10, 2007, at 7:57 PM, Steven Yi wrote:

> Hi Andres and all,
>
> I was thinking of a quick release now with the fix for Windows paths
> as it's sort of a showstopper.  I imagine the simple cross-platform
> editor/front-end would be great for the next major point release
> (5.05) but I have some feelings that it won't be something that will
> be ironed out quickly and probably *should* have some rounds of beta
> testing, feedback, etc.  Also, I think we've had a few emails here
> about things to have, but I think it might be best if we drafted a
> requirements doc; nothing overly formal, but I think if the past has
> shown anything, someone programs something thinking this is what
> everyone wants, then everyone tells them what they really want, then
> there's time lost and no one's the better for it.  Also, there's a lot
> of code in csound5gui and winsound that could probably be gathered
> from.
>
> BTW: My take on a cross-platform GUI would be something like MacCsound
> but without the GUI parts.  Dave's syntax code editor could be the
> main area, parts of csound5gui and winsound could be used to fill in
> the rest of the functionality.  (Matt probably doesn't hear it enough
> from me, but MacCsound is A+ on usability in my book. =) )
>
> steven
>
>
>
> On 1/11/07, Andres Cabrera  wrote:
>> Hi,
>>
>> I would also like to see a new release soon. What I would most  
>> love to
>> see in the next release:
>> - Simple cross-platform editor/front-end particularly to ease running
>> and editing examples, that newbies can easily step into.
>>
>> Cheers,
>> Andres
>>
>> Steven Yi wrote:
>>> Hi All,
>>>
>>> It being a new year I thought I'd query the list to see what  
>>> everyone
>>> thought about Csound's current status as well as seeing about things
>>> we would all like to achieve with where to take Csound.
>>>
>>> Regarding the current release of Csound, I think that the fix that
>>> Anthony suggested and that I checked in regarding paths on Windows
>>> seems like it should get out to the public as quickly as possible  
>>> and
>>> I'd like to request that at least a new Windows build be released  
>>> and
>>> better if a new release all around was to happen.  I don't think it
>>> would have to be a major point release, just a minor mostly bug fix
>>> release so maybe 5.04.1.  It seems that the bug has caused a  
>>> number of
>>> problems for people either using the GUI's or API.  Any thoughts?
>>>
>>> Also, I don't remember the status of the problem David Akbari posted
>>> about and if that was ever resolved.
>>>
>>> Regarding where Csound is going, I realized that in the past when
>>> there was heated ranting by a user or users that it often spurred a
>>> lot of quick (if stressful!) changes.  Rather than waiting for a
>>> heated rant, shall we poll the main list for user thoughts on where
>>> they see deficiencies in the current Csound releases?
>>>
>>> As for personal work, I've taken a long break from the new parser  
>>> but
>>> I think will resume work on that next week.  Rather than continue to
>>> work on that in a separate branch I'd like to integrate that back  
>>> into
>>> the HEAD branch as well as do as I mentioned a month or so ago,  
>>> which
>>> is to set up two layers of options to use: one in SConstruct that
>>> would build in the new parser or not, and second a commandline  
>>> flag to
>>> enable using the new parser.  Both of those would default to no,
>>> meaning if you just checked out from CVS and didn't turn on to build
>>> the parser, nothing would change for you.  Even if you built with  
>>> the
>>> new parser, it wouldn't be used unless explicitly told to via
>>> commandline, so again nothing would change for normal usage.  The  
>>> code
>>> is encapsulated into its own files so does not affect the current  
>>> use
>>> of Csound even when compiled in, so I think this is very safe to
>>> integrate.  If everyone is okay with this, I'll go ahead on  
>>> Monday to
>>> integrate and start working from there.
>>>
>>> Thanks!
>>> steven
>>>
>>> -------------------------------------------------------------------- 
>>> -----
>>> Take Surveys. Earn Cash. Influence the Future of IT
>>> Join SourceForge.net's Techsay panel and you'll get the chance to  
>>> share your
>>> opinions on IT & business topics through brief surveys - and earn  
>>> cash
>>> http://www.techsay.com/default.php? 
>>> page=join.php&p=sourceforge&CID=DEVDEV
>>> _______________________________________________
>>> Csound-devel mailing list
>>> Csound-devel@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>>
>>>
>>
>>
>> --------------------------------------------------------------------- 
>> ----
>> Take Surveys. Earn Cash. Influence the Future of IT
>> Join SourceForge.net's Techsay panel and you'll get the chance to  
>> share your
>> opinions on IT & business topics through brief surveys - and earn  
>> cash
>> http://www.techsay.com/default.php? 
>> page=join.php&p=sourceforge&CID=DEVDEV
>> _______________________________________________
>> Csound-devel mailing list
>> Csound-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>
>
> ---------------------------------------------------------------------- 
> ---
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to  
> share your
> opinions on IT & business topics through brief surveys - and earn cash
> http://www.techsay.com/default.php? 
> page=join.php&p=sourceforge&CID=DEVDEV
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel


-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

I am disappointed about the current state of Csound.  It is hard to
compile on too many platforms, and seems to depend on too many software
systems, some of which are decidedly iffy.  At present I am struggling
to build csound, which is not leaving much time to think about
developments.

In some previous years I had asked for suggestions over the Christmas
break as it was a good time to develop without distractions, but this
year there were too many problems to solicit more.

I certainly want to see the parser integrated into the tree so we can
ensure that it works.

There are oddities I would like fixed, like allowing printf to run
without any values.  There are still oddities with strings and UDOs.
It works most of the time for me, but seems sensitive.

Current system talks too much, giving a commentary on what is being
loaded which is of little interest to users.

I am too close to the problems at present to see the bigger picture.

==John ffitch

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

when did this come about? It used to build OK a few months ago, what
has changed? Can you identify the areas?

At 06:50 11/01/2007, you wrote:
>I am disappointed about the current state of Csound.  It is hard to
>compile on too many platforms, and seems to depend on too many software
>systems, some of which are decidedly iffy.  At present I am struggling
>to build csound, which is not leaving much time to think about
>developments.

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


-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Some of the problems:

SWIG is capable of generating illegal C++.  Some versions ago it was
easy to edit by hand but the more recent versions generate even more
contorted code; but it seems as if one has to use one of the newer
versions.

g++ fails to compile a number of files in the frontends unless i
switch off optimisation -- I think this is a GCC/G++ bug but it does
get in the way!

Csound now apparently needs python, and I have been caught with
upgrading my machine also moving python on a version -- and as I do
not use python I was not aware of the change

FLTK 1.1.7 did not build on my machine so the code that depends on it
collapses.  At present I cannot find how to avoid

g++ -o frontends/fltk_gui/CsoundPerformanceSettingsPanel_FLTK.o -c -fexceptions -Wall -g -gstabs -fPIC -DLINUX -DPIPES -DHAVE_LIBSNDFILE=1016 -DHAVE_FLTK -DBETA -DUSE_DOUBLE -DHAVE_SOCKETS -DHAVE_FCNTL_H -DHAVE_UNISTD_H -DHAVE_STDINT_H -DHAVE_SYS_TIME_H -DHAVE_SYS_TYPES_H -DHAVE_TERMIOS_H -DHAVE_SOCKETS -DHAVE_DIRENT_H -I. -IH -I/usr/local/include -I/usr/include -I/usr/X11R6/include -Iinterfaces frontends/fltk_gui/CsoundPerformanceSettingsPanel_FLTK.cpp
frontends/fltk_gui/CsoundPerformanceSettingsPanel_FLTK.cpp: In member function 'void CsoundPerformanceSettingsPanel::cb_Buffer_i(Fl_Choice*, void*)':
frontends/fltk_gui/CsoundPerformanceSettingsPanel_FLTK.cpp:342: error: 'numBuffersInput' was not declared in this scope
frontends/fltk_gui/CsoundPerformanceSettingsPanel_FLTK.cpp:344: error: 'numBuffersInput' was not declared in this scope
scons: *** [frontends/fltk_gui/CsoundPerformanceSettingsPanel_FLTK.o] Error 1
scons: building terminated because of errors.

which has been around for a month or so -- I think related to fltk
1.1.7 but I cannot understand where numBuffersInput is supposed to be
declared

Not infrequently a failure to build is due to the wrapper code not
being in step with something or other -- but if this were build too
readily then one would never be able to correct the SWIG errors

Reading the mailing list of late I have been struck by how many
messages were of the form "I am having trouble building on platform
xxx"

Some things are just irritating, like not being 64bit clean

That will do for now, but I devoted much of yesterday to building
Csound and basically failing

==John ffitch

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

At 11:39 11/01/2007, you wrote:
>Some of the problems:
>
>SWIG is capable of generating illegal C++.  Some versions ago it was
>easy to edit by hand but the more recent versions generate even more
>contorted code; but it seems as if one has to use one of the newer
>versions.

can we keep to previous versions of swig?


>g++ fails to compile a number of files in the frontends unless i
>switch off optimisation -- I think this is a GCC/G++ bug but it does
>get in the way!

which frontends? Can we make these optional?


>Csound now apparently needs python, and I have been caught with
>upgrading my machine also moving python on a version -- and as I do
>not use python I was not aware of the change

How is Python needed? It should only be needed for certain plugin
opcodes and wrappers.

This seems to be a SConstruct issue. We should edit it to make python
optional.


>FLTK 1.1.7 did not build on my machine so the code that depends on it
>collapses.  At present I cannot find how to avoid

This is Csound5GUI, which should be optional.


>g++ -o frontends/fltk_gui/CsoundPerformanceSettingsPanel_FLTK.o -c 
>-fexceptions -Wall -g -gstabs -fPIC -DLINUX -DPIPES -DHAVE_LIBSNDFILE=1016 
>-DHAVE_FLTK -DBETA -DUSE_DOUBLE -DHAVE_SOCKETS -DHAVE_FCNTL_H 
>-DHAVE_UNISTD_H -DHAVE_STDINT_H -DHAVE_SYS_TIME_H -DHAVE_SYS_TYPES_H 
>-DHAVE_TERMIOS_H -DHAVE_SOCKETS -DHAVE_DIRENT_H -I. -IH 
>-I/usr/local/include -I/usr/include -I/usr/X11R6/include -Iinterfaces 
>frontends/fltk_gui/CsoundPerformanceSettingsPanel_FLTK.cpp
>frontends/fltk_gui/CsoundPerformanceSettingsPanel_FLTK.cpp: In member 
>function 'void CsoundPerformanceSettingsPanel::cb_Buffer_i(Fl_Choice*, void*)':
>frontends/fltk_gui/CsoundPerformanceSettingsPanel_FLTK.cpp:342: error: 
>'numBuffersInput' was not declared in this scope
>frontends/fltk_gui/CsoundPerformanceSettingsPanel_FLTK.cpp:344: error: 
>'numBuffersInput' was not declared in this scope
>scons: *** [frontends/fltk_gui/CsoundPerformanceSettingsPanel_FLTK.o] Error 1
>scons: building terminated because of errors.
>
>which has been around for a month or so -- I think related to fltk
>1.1.7 but I cannot understand where numBuffersInput is supposed to be
>declared


>Not infrequently a failure to build is due to the wrapper code not
>being in step with something or other -- but if this were build too
>readily then one would never be able to correct the SWIG errors

This a scons bug. When there are changes in the headers, the wrapper
C++ code should be automatically re-built, by invoking swig. But scons
does not seem to catch that. It requires a removal of the wrapper source
code. Perhaps we should just add a command to do that all the time to 
SConstruct,
what do you think?


>Reading the mailing list of late I have been struck by how many
>messages were of the form "I am having trouble building on platform
>xxx"

yes, but a lot of it is because Csound 5 is a complex system to build anyway,
and has always depended on many external libraries. The messages I have
been reading seem to indicate that many people do not know what is involved
and get trapped by it.


>Some things are just irritating, like not being 64bit clean

That is certainly an issue. We have to track down what is not 64bit clean.

>That will do for now, but I devoted much of yesterday to building
>Csound and basically failing

I blame a lot of this on the default options of SConstruct. They should 
build just
a basic system, a static library, with only libsndfile as a dependency 
(because in
reality it is the ONLY dependable external library in all systems).

I will try and do some changes to SConstruct to that effect.

Victor


>==John ffitch
>
>-------------------------------------------------------------------------
>Take Surveys. Earn Cash. Influence the Future of IT
>Join SourceForge.net's Techsay panel and you'll get the chance to share your
>opinions on IT & business topics through brief surveys - and earn cash
>http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
>_______________________________________________
>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 


-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

changed SConstruct to default to mininal system. Can you try scons with no 
options
and see if it builds?


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


-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

scons with word64=1 and usedouble=1 fails to build as it crashes in 
building fltk_gui just like when in my usual format.

as a matter of interest, where is numBuffersInput declared?

==John ff

On Thu, 11 Jan 2007, Victor Lazzarini wrote:

> changed SConstruct to default to mininal system. Can you try scons with no 
> options
> and see if it builds?
> 
> 

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

But fltk GUI is an option now; are you saying that scons is trying to build it
even with a plain 'scons' (no options)?

At 12:23 11/01/2007, you wrote:
>scons with word64=1 and usedouble=1 fails to build as it crashes in
>building fltk_gui just like when in my usual format.
>
>as a matter of interest, where is numBuffersInput declared?
>
>==John ff
>
>On Thu, 11 Jan 2007, Victor Lazzarini wrote:
>
> > changed SConstruct to default to mininal system. Can you try scons with no
> > options
> > and see if it builds?
> >
> >
>
>-------------------------------------------------------------------------
>Take Surveys. Earn Cash. Influence the Future of IT
>Join SourceForge.net's Techsay panel and you'll get the chance to share your
>opinions on IT & business topics through brief surveys - and earn cash
>http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
>_______________________________________________
>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 


-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

At last some progress

I found that there were two versins of fluid on teh machine, 1.1.6 and 
1.1.7.  Removing 1.1.7 version and adding the /usr/X11R6/bin diretory to 
my $PATH gets a lot further.  Now it stops later with

g++ -o frontends/fltk_gui/CsoundGlobalSettings.o -c -fexceptions -Wall -g 
-gstabs -fPIC -DLINUX -DPIPES -O2 -fmessage-length=0 -D_FORTIFY_SOURCE=2 
-O2 -fmessage-length=0 -D_FORTIFY_SOURCE=2 -DHAVE_LIBSNDFILE=1016 
-DHAVE_FLTK -DBETA -DUSE_DOUBLE -DHAVE_SOCKETS -DHAVE_FCNTL_H 
-DHAVE_UNISTD_H -DHAVE_STDINT_H -DHAVE_SYS_TIME_H -DHAVE_SYS_TYPES_H 
-DHAVE_TERMIOS_H -DHAVE_SOCKETS -DHAVE_DIRENT_H -I. -IH 
-I/usr/local/include -I/usr/include -I/usr/X11R6/include -Iinterfaces 
frontends/fltk_gui/CsoundGlobalSettings.cpp
/usr/X11R6/include/FL/Fl_Image.H: In constructor 
'Fl_RGB_Image::Fl_RGB_Image(const uchar*, int, int, int, int)':
/usr/X11R6/include/FL/Fl_Image.H:95: warning: dereferencing type-punned 
pointer will break strict-aliasing rules
frontends/fltk_gui/CsoundGlobalSettings.cpp: In constructor 
'CsoundGlobalSettings::CsoundGlobalSettings()':
frontends/fltk_gui/CsoundGlobalSettings.cpp:47: internal compiler error: 
output_operand: invalid expression as operand
Please submit a full bug report,
with preprocessed source if appropriate.
See  for instructions.
scons: *** [frontends/fltk_gui/CsoundGlobalSettings.o] Error 1
scons: building terminated because of errors.

It does build is the -O2 is removed but i am not sure how to do that as I 
have removed the -O2 everywhere in SConstruct (else it wouldl have failed 
earlier)

So really the problem I was having was the dependence on fltk 1.1.7 which 
did not build from source.

On Thu, 11 Jan 2007, John ffitch wrote:

> scons with word64=1 and usedouble=1 fails to build as it crashes in 
> building fltk_gui just like when in my usual format.
> 
> as a matter of interest, where is numBuffersInput declared?
> 
> ==John ff
> 
> On Thu, 11 Jan 2007, Victor Lazzarini wrote:
> 
> > changed SConstruct to default to mininal system. Can you try scons with no 
> > options
> > and see if it builds?
> > 
> > 
> 
> -------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share your
> opinions on IT & business topics through brief surveys - and earn cash
> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel
> 
> 
> 

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

CsoundPerformanceSettingsPanel_FLTK.hpp


At 12:23 11/01/2007, you wrote:
>scons with word64=1 and usedouble=1 fails to build as it crashes in
>building fltk_gui just like when in my usual format.
>
>as a matter of interest, where is numBuffersInput declared?
>
>==John ff
>
>On Thu, 11 Jan 2007, Victor Lazzarini wrote:
>
> > changed SConstruct to default to mininal system. Can you try scons with no
> > options
> > and see if it builds?
> >
> >
>
>-------------------------------------------------------------------------
>Take Surveys. Earn Cash. Influence the Future of IT
>Join SourceForge.net's Techsay panel and you'll get the chance to share your
>opinions on IT & business topics through brief surveys - and earn cash
>http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
>_______________________________________________
>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 


-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Yes that is what i am saying.

Are you trying to tell be you have changed SConstrct since I started this 
saga?


On Thu, 11 Jan 2007, Victor Lazzarini wrote:

> But fltk GUI is an option now; are you saying that scons is trying to build it
> even with a plain 'scons' (no options)?
> 
> At 12:23 11/01/2007, you wrote:
> >scons with word64=1 and usedouble=1 fails to build as it crashes in
> >building fltk_gui just like when in my usual format.
> >
> >as a matter of interest, where is numBuffersInput declared?
> >
> >==John ff
> >
> >On Thu, 11 Jan 2007, Victor Lazzarini wrote:
> >
> > > changed SConstruct to default to mininal system. Can you try scons with no
> > > options
> > > and see if it builds?
> > >
> > >
> >
> >-------------------------------------------------------------------------
> >Take Surveys. Earn Cash. Influence the Future of IT
> >Join SourceForge.net's Techsay panel and you'll get the chance to share your
> >opinions on IT & business topics through brief surveys - and earn cash
> >http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> >_______________________________________________
> >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 
> 
> 
> -------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share your
> opinions on IT & business topics through brief surveys - and earn cash
> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel
> 
> 
> 

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Do you really need Csound5GUI? The problem with this code is that no one
knows about it, as it was a fruit of Istvan's imagination. I would like to 
consider
it deprecated, and take David Akbari's code into Csound5, since at least he
is around and can maintain it.

Victor

At 12:39 11/01/2007, you wrote:
>At last some progress
>
>I found that there were two versins of fluid on teh machine, 1.1.6 and
>1.1.7.  Removing 1.1.7 version and adding the /usr/X11R6/bin diretory to
>my $PATH gets a lot further.  Now it stops later with
>
>g++ -o frontends/fltk_gui/CsoundGlobalSettings.o -c -fexceptions -Wall -g
>-gstabs -fPIC -DLINUX -DPIPES -O2 -fmessage-length=0 -D_FORTIFY_SOURCE=2
>-O2 -fmessage-length=0 -D_FORTIFY_SOURCE=2 -DHAVE_LIBSNDFILE=1016
>-DHAVE_FLTK -DBETA -DUSE_DOUBLE -DHAVE_SOCKETS -DHAVE_FCNTL_H
>-DHAVE_UNISTD_H -DHAVE_STDINT_H -DHAVE_SYS_TIME_H -DHAVE_SYS_TYPES_H
>-DHAVE_TERMIOS_H -DHAVE_SOCKETS -DHAVE_DIRENT_H -I. -IH
>-I/usr/local/include -I/usr/include -I/usr/X11R6/include -Iinterfaces
>frontends/fltk_gui/CsoundGlobalSettings.cpp
>/usr/X11R6/include/FL/Fl_Image.H: In constructor
>'Fl_RGB_Image::Fl_RGB_Image(const uchar*, int, int, int, int)':
>/usr/X11R6/include/FL/Fl_Image.H:95: warning: dereferencing type-punned
>pointer will break strict-aliasing rules
>frontends/fltk_gui/CsoundGlobalSettings.cpp: In constructor
>'CsoundGlobalSettings::CsoundGlobalSettings()':
>frontends/fltk_gui/CsoundGlobalSettings.cpp:47: internal compiler error:
>output_operand: invalid expression as operand
>Please submit a full bug report,
>with preprocessed source if appropriate.
>See  for instructions.
>scons: *** [frontends/fltk_gui/CsoundGlobalSettings.o] Error 1
>scons: building terminated because of errors.
>
>It does build is the -O2 is removed but i am not sure how to do that as I
>have removed the -O2 everywhere in SConstruct (else it wouldl have failed
>earlier)
>
>So really the problem I was having was the dependence on fltk 1.1.7 which
>did not build from source.
>
>On Thu, 11 Jan 2007, John ffitch wrote:
>
> > scons with word64=1 and usedouble=1 fails to build as it crashes in
> > building fltk_gui just like when in my usual format.
> >
> > as a matter of interest, where is numBuffersInput declared?
> >
> > ==John ff
> >
> > On Thu, 11 Jan 2007, Victor Lazzarini wrote:
> >
> > > changed SConstruct to default to mininal system. Can you try scons 
> with no
> > > options
> > > and see if it builds?
> > >
> > >
> >
> > -------------------------------------------------------------------------
> > Take Surveys. Earn Cash. Influence the Future of IT
> > Join SourceForge.net's Techsay panel and you'll get the chance to share 
> your
> > opinions on IT & business topics through brief surveys - and earn cash
> > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> > _______________________________________________
> > Csound-devel mailing list
> > Csound-devel@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/csound-devel
> >
> >
> >
>
>-------------------------------------------------------------------------
>Take Surveys. Earn Cash. Influence the Future of IT
>Join SourceForge.net's Techsay panel and you'll get the chance to share your
>opinions on IT & business topics through brief surveys - and earn cash
>http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
>_______________________________________________
>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 


-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

cvs update to get new SConstruct, removed versions of portmidi that were 
no-longer compatible and now it stops with 


g++ -o libvirtual.so -Wl,-Bdynamic -shared 
InOut/virtual_keyboard/FLTKKeyboard.os 
InOut/virtual_keyboard/FLTKKeyboardWindow.os 
InOut/virtual_keyboard/FLTKKeyboardWidget.os 
InOut/virtual_keyboard/virtual_keyboard.os InOut/virtual_keyboard/Bank.os 
InOut/virtual_keyboard/KeyboardMapping.os 
InOut/virtual_keyboard/Program.os InOut/virtual_keyboard/SliderBank.os 
InOut/virtual_keyboard/SliderData.os -L. -L. -L/usr/local/lib -L. -L. 
-L/usr/local/lib64 -L/usr/X11R6/lib64 -lsndfile -lfltk_images -lpng -lz 
-lfltk_jpeg -lfltk -lpthread -lm -lXext -lX11 -lsupc++ -lstdc++ -lpthread 
-lm
/usr/lib64/gcc/x86_64-suse-linux/4.1.2/../../../../x86_64-suse-linux/bin/ld: 
cannot find -lfltk_jpeg
collect2: ld returned 1 exit status
scons: *** [libvirtual.so] Error 1
scons: building terminated because of errors.

So I am inching towards a working system, but I really need to go to work 
and do some stuff.

==John


-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

For Csound5GUI you need 1.1.7 because of the widgets introduced in that
version.

Victor

At 12:39 11/01/2007, you wrote:


>So really the problem I was having was the dependence on fltk 1.1.7 which
>did not build from source.

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


-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

I have changed it this morning. Csound5GUI only builds if you
explicitly tell scons

At 12:41 11/01/2007, you wrote:
>Yes that is what i am saying.
>
>Are you trying to tell be you have changed SConstrct since I started this
>saga?
>
>
>On Thu, 11 Jan 2007, Victor Lazzarini wrote:
>
> > But fltk GUI is an option now; are you saying that scons is trying to 
> build it
> > even with a plain 'scons' (no options)?
> >
> > At 12:23 11/01/2007, you wrote:
> > >scons with word64=1 and usedouble=1 fails to build as it crashes in
> > >building fltk_gui just like when in my usual format.
> > >
> > >as a matter of interest, where is numBuffersInput declared?
> > >
> > >==John ff
> > >
> > >On Thu, 11 Jan 2007, Victor Lazzarini wrote:
> > >
> > > > changed SConstruct to default to mininal system. Can you try scons 
> with no
> > > > options
> > > > and see if it builds?
> > > >
> > > >
> > >
> > >-------------------------------------------------------------------------
> > >Take Surveys. Earn Cash. Influence the Future of IT
> > >Join SourceForge.net's Techsay panel and you'll get the chance to 
> share your
> > >opinions on IT & business topics through brief surveys - and earn cash
> > >http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> > >_______________________________________________
> > >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
> >
> >
> > -------------------------------------------------------------------------
> > Take Surveys. Earn Cash. Influence the Future of IT
> > Join SourceForge.net's Techsay panel and you'll get the chance to share 
> your
> > opinions on IT & business topics through brief surveys - and earn cash
> > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> > _______________________________________________
> > Csound-devel mailing list
> > Csound-devel@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/csound-devel
> >
> >
> >
>
>-------------------------------------------------------------------------
>Take Surveys. Earn Cash. Influence the Future of IT
>Join SourceForge.net's Techsay panel and you'll get the chance to share your
>opinions on IT & business topics through brief surveys - and earn cash
>http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
>_______________________________________________
>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 


-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

We do need something like WinSound or Csound5GUI to work and to be a  
part of the distribution.
When it worked - Csound5GUI (on the Mac) was very very nice.  It did  
let me see/set ALL the options
for the program and set/run all the utilities.  It just didn't have  
good defaults.

-dB

On Jan 11, 2007, at 7:46 AM, Victor Lazzarini wrote:

> Do you really need Csound5GUI? The problem with this code is that  
> no one
> knows about it, as it was a fruit of Istvan's imagination. I would  
> like to
> consider
> it deprecated, and take David Akbari's code into Csound5, since at  
> least he
> is around and can maintain it.
>
> Victor
>
> At 12:39 11/01/2007, you wrote:
>> At last some progress
>>
>> I found that there were two versins of fluid on teh machine, 1.1.6  
>> and
>> 1.1.7.  Removing 1.1.7 version and adding the /usr/X11R6/bin  
>> diretory to
>> my $PATH gets a lot further.  Now it stops later with
>>
>> g++ -o frontends/fltk_gui/CsoundGlobalSettings.o -c -fexceptions - 
>> Wall -g
>> -gstabs -fPIC -DLINUX -DPIPES -O2 -fmessage-length=0 - 
>> D_FORTIFY_SOURCE=2
>> -O2 -fmessage-length=0 -D_FORTIFY_SOURCE=2 -DHAVE_LIBSNDFILE=1016
>> -DHAVE_FLTK -DBETA -DUSE_DOUBLE -DHAVE_SOCKETS -DHAVE_FCNTL_H
>> -DHAVE_UNISTD_H -DHAVE_STDINT_H -DHAVE_SYS_TIME_H -DHAVE_SYS_TYPES_H
>> -DHAVE_TERMIOS_H -DHAVE_SOCKETS -DHAVE_DIRENT_H -I. -IH
>> -I/usr/local/include -I/usr/include -I/usr/X11R6/include -Iinterfaces
>> frontends/fltk_gui/CsoundGlobalSettings.cpp
>> /usr/X11R6/include/FL/Fl_Image.H: In constructor
>> 'Fl_RGB_Image::Fl_RGB_Image(const uchar*, int, int, int, int)':
>> /usr/X11R6/include/FL/Fl_Image.H:95: warning: dereferencing type- 
>> punned
>> pointer will break strict-aliasing rules
>> frontends/fltk_gui/CsoundGlobalSettings.cpp: In constructor
>> 'CsoundGlobalSettings::CsoundGlobalSettings()':
>> frontends/fltk_gui/CsoundGlobalSettings.cpp:47: internal compiler  
>> error:
>> output_operand: invalid expression as operand
>> Please submit a full bug report,
>> with preprocessed source if appropriate.
>> See  for instructions.
>> scons: *** [frontends/fltk_gui/CsoundGlobalSettings.o] Error 1
>> scons: building terminated because of errors.
>>
>> It does build is the -O2 is removed but i am not sure how to do  
>> that as I
>> have removed the -O2 everywhere in SConstruct (else it wouldl have  
>> failed
>> earlier)
>>
>> So really the problem I was having was the dependence on fltk  
>> 1.1.7 which
>> did not build from source.
>>
>> On Thu, 11 Jan 2007, John ffitch wrote:
>>
>>> scons with word64=1 and usedouble=1 fails to build as it crashes in
>>> building fltk_gui just like when in my usual format.
>>>
>>> as a matter of interest, where is numBuffersInput declared?
>>>
>>> ==John ff
>>>
>>> On Thu, 11 Jan 2007, Victor Lazzarini wrote:
>>>
>>>> changed SConstruct to default to mininal system. Can you try scons
>> with no
>>>> options
>>>> and see if it builds?
>>>>
>>>>
>>>
>>> -------------------------------------------------------------------- 
>>> -----
>>> Take Surveys. Earn Cash. Influence the Future of IT
>>> Join SourceForge.net's Techsay panel and you'll get the chance to  
>>> share
>> your
>>> opinions on IT & business topics through brief surveys - and earn  
>>> cash
>>> http://www.techsay.com/default.php? 
>>> page=join.php&p=sourceforge&CID=DEVDEV
>>> _______________________________________________
>>> Csound-devel mailing list
>>> Csound-devel@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>>
>>>
>>>
>>
>> --------------------------------------------------------------------- 
>> ----
>> Take Surveys. Earn Cash. Influence the Future of IT
>> Join SourceForge.net's Techsay panel and you'll get the chance to  
>> share your
>> opinions on IT & business topics through brief surveys - and earn  
>> cash
>> http://www.techsay.com/default.php? 
>> page=join.php&p=sourceforge&CID=DEVDEV
>> _______________________________________________
>> 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
>
>
> ---------------------------------------------------------------------- 
> ---
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to  
> share your
> opinions on IT & business topics through brief surveys - and earn cash
> http://www.techsay.com/default.php? 
> page=join.php&p=sourceforge&CID=DEVDEV
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel


-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Hurrah!  Well actually fltk-config was for 1.1.6 and the libraries were 
1.1.7
  SuSE seem to have managed to build this version, but it crashed all over 
the place when i tried, and the bug report was "try the latest rc" which 
also failed to build.

So maybe I am back as long as i avoid the C++ components.  Hum...I was 
thinking of working on winsound.  But now I am going to work.

==John ff



-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

OK, but the problem is that the developer is gone and unless someone
steps in to learn the code, maintenance is not going to happen.

Victor

At 13:10 11/01/2007, you wrote:
>We do need something like WinSound or Csound5GUI to work and to be a
>part of the distribution.
>When it worked - Csound5GUI (on the Mac) was very very nice.  It did
>let me see/set ALL the options
>for the program and set/run all the utilities.  It just didn't have
>good defaults.
>
>-dB
>
>On Jan 11, 2007, at 7:46 AM, Victor Lazzarini wrote:
>
> > Do you really need Csound5GUI? The problem with this code is that
> > no one
> > knows about it, as it was a fruit of Istvan's imagination. I would
> > like to
> > consider
> > it deprecated, and take David Akbari's code into Csound5, since at
> > least he
> > is around and can maintain it.
> >
> > Victor
> >
> > At 12:39 11/01/2007, you wrote:
> >> At last some progress
> >>
> >> I found that there were two versins of fluid on teh machine, 1.1.6
> >> and
> >> 1.1.7.  Removing 1.1.7 version and adding the /usr/X11R6/bin
> >> diretory to
> >> my $PATH gets a lot further.  Now it stops later with
> >>
> >> g++ -o frontends/fltk_gui/CsoundGlobalSettings.o -c -fexceptions -
> >> Wall -g
> >> -gstabs -fPIC -DLINUX -DPIPES -O2 -fmessage-length=0 -
> >> D_FORTIFY_SOURCE=2
> >> -O2 -fmessage-length=0 -D_FORTIFY_SOURCE=2 -DHAVE_LIBSNDFILE=1016
> >> -DHAVE_FLTK -DBETA -DUSE_DOUBLE -DHAVE_SOCKETS -DHAVE_FCNTL_H
> >> -DHAVE_UNISTD_H -DHAVE_STDINT_H -DHAVE_SYS_TIME_H -DHAVE_SYS_TYPES_H
> >> -DHAVE_TERMIOS_H -DHAVE_SOCKETS -DHAVE_DIRENT_H -I. -IH
> >> -I/usr/local/include -I/usr/include -I/usr/X11R6/include -Iinterfaces
> >> frontends/fltk_gui/CsoundGlobalSettings.cpp
> >> /usr/X11R6/include/FL/Fl_Image.H: In constructor
> >> 'Fl_RGB_Image::Fl_RGB_Image(const uchar*, int, int, int, int)':
> >> /usr/X11R6/include/FL/Fl_Image.H:95: warning: dereferencing type-
> >> punned
> >> pointer will break strict-aliasing rules
> >> frontends/fltk_gui/CsoundGlobalSettings.cpp: In constructor
> >> 'CsoundGlobalSettings::CsoundGlobalSettings()':
> >> frontends/fltk_gui/CsoundGlobalSettings.cpp:47: internal compiler
> >> error:
> >> output_operand: invalid expression as operand
> >> Please submit a full bug report,
> >> with preprocessed source if appropriate.
> >> See  for instructions.
> >> scons: *** [frontends/fltk_gui/CsoundGlobalSettings.o] Error 1
> >> scons: building terminated because of errors.
> >>
> >> It does build is the -O2 is removed but i am not sure how to do
> >> that as I
> >> have removed the -O2 everywhere in SConstruct (else it wouldl have
> >> failed
> >> earlier)
> >>
> >> So really the problem I was having was the dependence on fltk
> >> 1.1.7 which
> >> did not build from source.
> >>
> >> On Thu, 11 Jan 2007, John ffitch wrote:
> >>
> >>> scons with word64=1 and usedouble=1 fails to build as it crashes in
> >>> building fltk_gui just like when in my usual format.
> >>>
> >>> as a matter of interest, where is numBuffersInput declared?
> >>>
> >>> ==John ff
> >>>
> >>> On Thu, 11 Jan 2007, Victor Lazzarini wrote:
> >>>
> >>>> changed SConstruct to default to mininal system. Can you try scons
> >> with no
> >>>> options
> >>>> and see if it builds?
> >>>>
> >>>>
> >>>
> >>> --------------------------------------------------------------------
> >>> -----
> >>> Take Surveys. Earn Cash. Influence the Future of IT
> >>> Join SourceForge.net's Techsay panel and you'll get the chance to
> >>> share
> >> your
> >>> opinions on IT & business topics through brief surveys - and earn
> >>> cash
> >>> http://www.techsay.com/default.php?
> >>> page=join.php&p=sourceforge&CID=DEVDEV
> >>> _______________________________________________
> >>> Csound-devel mailing list
> >>> Csound-devel@lists.sourceforge.net
> >>> https://lists.sourceforge.net/lists/listinfo/csound-devel
> >>>
> >>>
> >>>
> >>
> >> ---------------------------------------------------------------------
> >> ----
> >> Take Surveys. Earn Cash. Influence the Future of IT
> >> Join SourceForge.net's Techsay panel and you'll get the chance to
> >> share your
> >> opinions on IT & business topics through brief surveys - and earn
> >> cash
> >> http://www.techsay.com/default.php?
> >> page=join.php&p=sourceforge&CID=DEVDEV
> >> _______________________________________________
> >> 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
> >
> >
> > ----------------------------------------------------------------------
> > ---
> > Take Surveys. Earn Cash. Influence the Future of IT
> > Join SourceForge.net's Techsay panel and you'll get the chance to
> > share your
> > opinions on IT & business topics through brief surveys - and earn cash
> > http://www.techsay.com/default.php?
> > page=join.php&p=sourceforge&CID=DEVDEV
> > _______________________________________________
> > Csound-devel mailing list
> > Csound-devel@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/csound-devel
>
>
>-------------------------------------------------------------------------
>Take Surveys. Earn Cash. Influence the Future of IT
>Join SourceForge.net's Techsay panel and you'll get the chance to share your
>opinions on IT & business topics through brief surveys - and earn cash
>http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
>_______________________________________________
>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 


-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Looks like not a lot of people are prepared for 64-bit systems.
We have lived for so long on a 32-bit world that everyone made
assumptions that are not universal.

Victor

At 13:14 11/01/2007, you wrote:
>Hurrah!  Well actually fltk-config was for 1.1.6 and the libraries were
>1.1.7
>   SuSE seem to have managed to build this version, but it crashed all over
>the place when i tried, and the bug report was "try the latest rc" which
>also failed to build.
>
>So maybe I am back as long as i avoid the C++ components.  Hum...I was
>thinking of working on winsound.  But now I am going to work.
>
>==John ff
>
>
>
>-------------------------------------------------------------------------
>Take Surveys. Earn Cash. Influence the Future of IT
>Join SourceForge.net's Techsay panel and you'll get the chance to share your
>opinions on IT & business topics through brief surveys - and earn cash
>http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
>_______________________________________________
>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 


-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

I am not saying that we should maintain it at all.  Actually,
it is a copy of John ffitch's WinSound design with some
extra features.  I would love John to look it over to give
him some ideas for his new WinSound cross-platform GUI.

Rick

On Jan 11, 2007, at 8:18 AM, Victor Lazzarini wrote:

> OK, but the problem is that the developer is gone and unless someone
> steps in to learn the code, maintenance is not going to happen.
>
> Victor
>
> At 13:10 11/01/2007, you wrote:
>> We do need something like WinSound or Csound5GUI to work and to be a
>> part of the distribution.
>> When it worked - Csound5GUI (on the Mac) was very very nice.  It did
>> let me see/set ALL the options
>> for the program and set/run all the utilities.  It just didn't have
>> good defaults.
>>
>> -dB
>>
>> On Jan 11, 2007, at 7:46 AM, Victor Lazzarini wrote:
>>
>>> Do you really need Csound5GUI? The problem with this code is that
>>> no one
>>> knows about it, as it was a fruit of Istvan's imagination. I would
>>> like to
>>> consider
>>> it deprecated, and take David Akbari's code into Csound5, since at
>>> least he
>>> is around and can maintain it.
>>>
>>> Victor
>>>
>>> At 12:39 11/01/2007, you wrote:
>>>> At last some progress
>>>>
>>>> I found that there were two versins of fluid on teh machine, 1.1.6
>>>> and
>>>> 1.1.7.  Removing 1.1.7 version and adding the /usr/X11R6/bin
>>>> diretory to
>>>> my $PATH gets a lot further.  Now it stops later with
>>>>
>>>> g++ -o frontends/fltk_gui/CsoundGlobalSettings.o -c -fexceptions -
>>>> Wall -g
>>>> -gstabs -fPIC -DLINUX -DPIPES -O2 -fmessage-length=0 -
>>>> D_FORTIFY_SOURCE=2
>>>> -O2 -fmessage-length=0 -D_FORTIFY_SOURCE=2 -DHAVE_LIBSNDFILE=1016
>>>> -DHAVE_FLTK -DBETA -DUSE_DOUBLE -DHAVE_SOCKETS -DHAVE_FCNTL_H
>>>> -DHAVE_UNISTD_H -DHAVE_STDINT_H -DHAVE_SYS_TIME_H - 
>>>> DHAVE_SYS_TYPES_H
>>>> -DHAVE_TERMIOS_H -DHAVE_SOCKETS -DHAVE_DIRENT_H -I. -IH
>>>> -I/usr/local/include -I/usr/include -I/usr/X11R6/include - 
>>>> Iinterfaces
>>>> frontends/fltk_gui/CsoundGlobalSettings.cpp
>>>> /usr/X11R6/include/FL/Fl_Image.H: In constructor
>>>> 'Fl_RGB_Image::Fl_RGB_Image(const uchar*, int, int, int, int)':
>>>> /usr/X11R6/include/FL/Fl_Image.H:95: warning: dereferencing type-
>>>> punned
>>>> pointer will break strict-aliasing rules
>>>> frontends/fltk_gui/CsoundGlobalSettings.cpp: In constructor
>>>> 'CsoundGlobalSettings::CsoundGlobalSettings()':
>>>> frontends/fltk_gui/CsoundGlobalSettings.cpp:47: internal compiler
>>>> error:
>>>> output_operand: invalid expression as operand
>>>> Please submit a full bug report,
>>>> with preprocessed source if appropriate.
>>>> See  for instructions.
>>>> scons: *** [frontends/fltk_gui/CsoundGlobalSettings.o] Error 1
>>>> scons: building terminated because of errors.
>>>>
>>>> It does build is the -O2 is removed but i am not sure how to do
>>>> that as I
>>>> have removed the -O2 everywhere in SConstruct (else it wouldl have
>>>> failed
>>>> earlier)
>>>>
>>>> So really the problem I was having was the dependence on fltk
>>>> 1.1.7 which
>>>> did not build from source.
>>>>
>>>> On Thu, 11 Jan 2007, John ffitch wrote:
>>>>
>>>>> scons with word64=1 and usedouble=1 fails to build as it  
>>>>> crashes in
>>>>> building fltk_gui just like when in my usual format.
>>>>>
>>>>> as a matter of interest, where is numBuffersInput declared?
>>>>>
>>>>> ==John ff
>>>>>
>>>>> On Thu, 11 Jan 2007, Victor Lazzarini wrote:
>>>>>
>>>>>> changed SConstruct to default to mininal system. Can you try  
>>>>>> scons
>>>> with no
>>>>>> options
>>>>>> and see if it builds?
>>>>>>
>>>>>>
>>>>>
>>>>> ------------------------------------------------------------------ 
>>>>> --
>>>>> -----
>>>>> Take Surveys. Earn Cash. Influence the Future of IT
>>>>> Join SourceForge.net's Techsay panel and you'll get the chance to
>>>>> share
>>>> your
>>>>> opinions on IT & business topics through brief surveys - and earn
>>>>> cash
>>>>> http://www.techsay.com/default.php?
>>>>> page=join.php&p=sourceforge&CID=DEVDEV
>>>>> _______________________________________________
>>>>> Csound-devel mailing list
>>>>> Csound-devel@lists.sourceforge.net
>>>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>>>>
>>>>>
>>>>>
>>>>
>>>> ------------------------------------------------------------------- 
>>>> --
>>>> ----
>>>> Take Surveys. Earn Cash. Influence the Future of IT
>>>> Join SourceForge.net's Techsay panel and you'll get the chance to
>>>> share your
>>>> opinions on IT & business topics through brief surveys - and earn
>>>> cash
>>>> http://www.techsay.com/default.php?
>>>> page=join.php&p=sourceforge&CID=DEVDEV
>>>> _______________________________________________
>>>> 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
>>>
>>>
>>> -------------------------------------------------------------------- 
>>> --
>>> ---
>>> Take Surveys. Earn Cash. Influence the Future of IT
>>> Join SourceForge.net's Techsay panel and you'll get the chance to
>>> share your
>>> opinions on IT & business topics through brief surveys - and earn  
>>> cash
>>> http://www.techsay.com/default.php?
>>> page=join.php&p=sourceforge&CID=DEVDEV
>>> _______________________________________________
>>> Csound-devel mailing list
>>> Csound-devel@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>
>>
>> --------------------------------------------------------------------- 
>> ----
>> Take Surveys. Earn Cash. Influence the Future of IT
>> Join SourceForge.net's Techsay panel and you'll get the chance to  
>> share your
>> opinions on IT & business topics through brief surveys - and earn  
>> cash
>> http://www.techsay.com/default.php? 
>> page=join.php&p=sourceforge&CID=DEVDEV
>> _______________________________________________
>> 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
>
>
> ---------------------------------------------------------------------- 
> ---
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to  
> share your
> opinions on IT & business topics through brief surveys - and earn cash
> http://www.techsay.com/default.php? 
> page=join.php&p=sourceforge&CID=DEVDEV
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel


-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

you can access the tables of an instance through the API. It might
be possible to add mechanisms for import and exporting table
locations.

Victor

At 14:31 11/01/2007, you wrote:
>One wish I have is for multiple instances of csound to share memory (ftables).
>I guess this might be a complicated task,
>but it would greatly enhance the possiblilities for writing multi-CPU
>csound setups.
>
>Oeyvind
>
>2007/1/10, Steven Yi :
> > Hi All,
> >
> > It being a new year I thought I'd query the list to see what everyone
> > thought about Csound's current status as well as seeing about things
> > we would all like to achieve with where to take Csound.
> >
> > Regarding the current release of Csound, I think that the fix that
> > Anthony suggested and that I checked in regarding paths on Windows
> > seems like it should get out to the public as quickly as possible and
> > I'd like to request that at least a new Windows build be released and
> > better if a new release all around was to happen.  I don't think it
> > would have to be a major point release, just a minor mostly bug fix
> > release so maybe 5.04.1.  It seems that the bug has caused a number of
> > problems for people either using the GUI's or API.  Any thoughts?
> >
> > Also, I don't remember the status of the problem David Akbari posted
> > about and if that was ever resolved.
> >
> > Regarding where Csound is going, I realized that in the past when
> > there was heated ranting by a user or users that it often spurred a
> > lot of quick (if stressful!) changes.  Rather than waiting for a
> > heated rant, shall we poll the main list for user thoughts on where
> > they see deficiencies in the current Csound releases?
> >
> > As for personal work, I've taken a long break from the new parser but
> > I think will resume work on that next week.  Rather than continue to
> > work on that in a separate branch I'd like to integrate that back into
> > the HEAD branch as well as do as I mentioned a month or so ago, which
> > is to set up two layers of options to use: one in SConstruct that
> > would build in the new parser or not, and second a commandline flag to
> > enable using the new parser.  Both of those would default to no,
> > meaning if you just checked out from CVS and didn't turn on to build
> > the parser, nothing would change for you.  Even if you built with the
> > new parser, it wouldn't be used unless explicitly told to via
> > commandline, so again nothing would change for normal usage.  The code
> > is encapsulated into its own files so does not affect the current use
> > of Csound even when compiled in, so I think this is very safe to
> > integrate.  If everyone is okay with this, I'll go ahead on Monday to
> > integrate and start working from there.
> >
> > Thanks!
> > steven
> >
> > -------------------------------------------------------------------------
> > Take Surveys. Earn Cash. Influence the Future of IT
> > Join SourceForge.net's Techsay panel and you'll get the chance to share 
> your
> > opinions on IT & business topics through brief surveys - and earn cash
> > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> > _______________________________________________
> > Csound-devel mailing list
> > Csound-devel@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/csound-devel
> >
>
>-------------------------------------------------------------------------
>Take Surveys. Earn Cash. Influence the Future of IT
>Join SourceForge.net's Techsay panel and you'll get the chance to share your
>opinions on IT & business topics through brief surveys - and earn cash
>http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
>_______________________________________________
>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 


-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

I have changed SConstruct to deal with these issues but it is completely
untested.  Please test it if you are able and let us know how it works!!

:)

Anthony

David Akbari wrote on 1/10/07 8:43 PM:

> * Endianness definitions fixed in SConstruct to allow getPlatform() ==
> 'darwin' && sys.byteorder == 'little'; as well as getPlatform() ==
> 'linux' && sys.byteorder == 'big' so that Linux PPC and Intel Macs can
> be used right out of the box. Previously the SConstruct had assumed if
> Darwin then it is big endian or if Linux it is little endian byte
> order  --- I think Anthony has already fixed this in SConstruct.


-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Steven Yi wrote on 1/10/07 11:45 AM:

> Regarding the current release of Csound, I think that the fix that
> Anthony suggested and that I checked in regarding paths on Windows
> seems like it should get out to the public as quickly as possible and
> I'd like to request that at least a new Windows build be released

YES !! I cringe everytime that I see another person struggling with this as
I think it probably was somehow my fault ...

> As for personal work, I've taken a long break from the new parser but
> I think will resume work on that next week.  Rather than continue to
> work on that in a separate branch I'd like to integrate that back into
> the HEAD branch as well as do as I mentioned a month or so ago, which
> is to set up two layers of options to use: one in SConstruct that
> would build in the new parser or not, and second a commandline flag to
> enable using the new parser.

This all sounds wonderful, Steven.  Make it so!

And if it is not too much trouble, maybe you could commit the output of
Bison as well for now so that I could try building the new parser without
struggling with Bison on MacOS 9 (although I will eventually try to get it
working).

Thanks.

Anthony


-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

It's OK with me to do a bugfix release. The manual also has many
improvements.

Cheers,
Andrés

Steven Yi wrote:
> Hi Andres and all,
>
> I was thinking of a quick release now with the fix for Windows paths
> as it's sort of a showstopper.  I imagine the simple cross-platform
> editor/front-end would be great for the next major point release
> (5.05) but I have some feelings that it won't be something that will
> be ironed out quickly and probably *should* have some rounds of beta
> testing, feedback, etc.  Also, I think we've had a few emails here
> about things to have, but I think it might be best if we drafted a
> requirements doc; nothing overly formal, but I think if the past has
> shown anything, someone programs something thinking this is what
> everyone wants, then everyone tells them what they really want, then
> there's time lost and no one's the better for it.  Also, there's a lot
> of code in csound5gui and winsound that could probably be gathered
> from.
>
> BTW: My take on a cross-platform GUI would be something like MacCsound
> but without the GUI parts.  Dave's syntax code editor could be the
> main area, parts of csound5gui and winsound could be used to fill in
> the rest of the functionality.  (Matt probably doesn't hear it enough
> from me, but MacCsound is A+ on usability in my book. =) )
>
> steven
>
>
>
> On 1/11/07, Andres Cabrera  wrote:
>   
>> Hi,
>>
>> I would also like to see a new release soon. What I would most love to
>> see in the next release:
>> - Simple cross-platform editor/front-end particularly to ease running
>> and editing examples, that newbies can easily step into.
>>
>> Cheers,
>> Andres
>>
>> Steven Yi wrote:
>>     
>>> Hi All,
>>>
>>> It being a new year I thought I'd query the list to see what everyone
>>> thought about Csound's current status as well as seeing about things
>>> we would all like to achieve with where to take Csound.
>>>
>>> Regarding the current release of Csound, I think that the fix that
>>> Anthony suggested and that I checked in regarding paths on Windows
>>> seems like it should get out to the public as quickly as possible and
>>> I'd like to request that at least a new Windows build be released and
>>> better if a new release all around was to happen.  I don't think it
>>> would have to be a major point release, just a minor mostly bug fix
>>> release so maybe 5.04.1.  It seems that the bug has caused a number of
>>> problems for people either using the GUI's or API.  Any thoughts?
>>>
>>> Also, I don't remember the status of the problem David Akbari posted
>>> about and if that was ever resolved.
>>>
>>> Regarding where Csound is going, I realized that in the past when
>>> there was heated ranting by a user or users that it often spurred a
>>> lot of quick (if stressful!) changes.  Rather than waiting for a
>>> heated rant, shall we poll the main list for user thoughts on where
>>> they see deficiencies in the current Csound releases?
>>>
>>> As for personal work, I've taken a long break from the new parser but
>>> I think will resume work on that next week.  Rather than continue to
>>> work on that in a separate branch I'd like to integrate that back into
>>> the HEAD branch as well as do as I mentioned a month or so ago, which
>>> is to set up two layers of options to use: one in SConstruct that
>>> would build in the new parser or not, and second a commandline flag to
>>> enable using the new parser.  Both of those would default to no,
>>> meaning if you just checked out from CVS and didn't turn on to build
>>> the parser, nothing would change for you.  Even if you built with the
>>> new parser, it wouldn't be used unless explicitly told to via
>>> commandline, so again nothing would change for normal usage.  The code
>>> is encapsulated into its own files so does not affect the current use
>>> of Csound even when compiled in, so I think this is very safe to
>>> integrate.  If everyone is okay with this, I'll go ahead on Monday to
>>> integrate and start working from there.
>>>
>>> Thanks!
>>> steven
>>>
>>> -------------------------------------------------------------------------
>>> Take Surveys. Earn Cash. Influence the Future of IT
>>> Join SourceForge.net's Techsay panel and you'll get the chance to share your
>>> opinions on IT & business topics through brief surveys - and earn cash
>>> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
>>> _______________________________________________
>>> Csound-devel mailing list
>>> Csound-devel@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>>
>>>
>>>       
>> -------------------------------------------------------------------------
>> Take Surveys. Earn Cash. Influence the Future of IT
>> Join SourceForge.net's Techsay panel and you'll get the chance to share your
>> opinions on IT & business topics through brief surveys - and earn cash
>> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
>> _______________________________________________
>> Csound-devel mailing list
>> Csound-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>
>>     
>
> -------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share your
> opinions on IT & business topics through brief surveys - and earn cash
> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel
>
>   


-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

I think for what you want it would be necessary to add
a way of exporting and importing tables (by their memory
addresses).

Victor

At 14:02 12/01/2007, you wrote:
>Thanks,
>I've accessed tables via the API,
>but only to read or write single values.
>
>I was thinking of allocating one large table for e.g. live sampling in
>one instance of csound,
>and then be able to use that table for playback in another csound
>instance (e.g. same audio data being used by two csound instances).
>Am I being silly in thinking that this would be possible somehow ?
>
>Oeyvind
>
>2007/1/11, Victor Lazzarini :
> > you can access the tables of an instance through the API. It might
> > be possible to add mechanisms for import and exporting table
> > locations.
> >
> > Victor
> >
> > At 14:31 11/01/2007, you wrote:
> > >One wish I have is for multiple instances of csound to share memory 
> (ftables).
> > >I guess this might be a complicated task,
> > >but it would greatly enhance the possiblilities for writing multi-CPU
> > >csound setups.
> > >
> > >Oeyvind
> > >
> > >2007/1/10, Steven Yi :
> > > > Hi All,
> > > >
> > > > It being a new year I thought I'd query the list to see what everyone
> > > > thought about Csound's current status as well as seeing about things
> > > > we would all like to achieve with where to take Csound.
> > > >
> > > > Regarding the current release of Csound, I think that the fix that
> > > > Anthony suggested and that I checked in regarding paths on Windows
> > > > seems like it should get out to the public as quickly as possible and
> > > > I'd like to request that at least a new Windows build be released and
> > > > better if a new release all around was to happen.  I don't think it
> > > > would have to be a major point release, just a minor mostly bug fix
> > > > release so maybe 5.04.1.  It seems that the bug has caused a number of
> > > > problems for people either using the GUI's or API.  Any thoughts?
> > > >
> > > > Also, I don't remember the status of the problem David Akbari posted
> > > > about and if that was ever resolved.
> > > >
> > > > Regarding where Csound is going, I realized that in the past when
> > > > there was heated ranting by a user or users that it often spurred a
> > > > lot of quick (if stressful!) changes.  Rather than waiting for a
> > > > heated rant, shall we poll the main list for user thoughts on where
> > > > they see deficiencies in the current Csound releases?
> > > >
> > > > As for personal work, I've taken a long break from the new parser but
> > > > I think will resume work on that next week.  Rather than continue to
> > > > work on that in a separate branch I'd like to integrate that back into
> > > > the HEAD branch as well as do as I mentioned a month or so ago, which
> > > > is to set up two layers of options to use: one in SConstruct that
> > > > would build in the new parser or not, and second a commandline flag to
> > > > enable using the new parser.  Both of those would default to no,
> > > > meaning if you just checked out from CVS and didn't turn on to build
> > > > the parser, nothing would change for you.  Even if you built with the
> > > > new parser, it wouldn't be used unless explicitly told to via
> > > > commandline, so again nothing would change for normal usage.  The code
> > > > is encapsulated into its own files so does not affect the current use
> > > > of Csound even when compiled in, so I think this is very safe to
> > > > integrate.  If everyone is okay with this, I'll go ahead on Monday to
> > > > integrate and start working from there.
> > > >
> > > > Thanks!
> > > > steven
> > > >
> > > > 
> -------------------------------------------------------------------------
> > > > Take Surveys. Earn Cash. Influence the Future of IT
> > > > Join SourceForge.net's Techsay panel and you'll get the chance to share
> > > your
> > > > opinions on IT & business topics through brief surveys - and earn cash
> > > > 
> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> > > > _______________________________________________
> > > > Csound-devel mailing list
> > > > Csound-devel@lists.sourceforge.net
> > > > https://lists.sourceforge.net/lists/listinfo/csound-devel
> > > >
> > >
> > >-------------------------------------------------------------------------
> > >Take Surveys. Earn Cash. Influence the Future of IT
> > >Join SourceForge.net's Techsay panel and you'll get the chance to 
> share your
> > >opinions on IT & business topics through brief surveys - and earn cash
> > >http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> > >_______________________________________________
> > >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
> >
> >
> > -------------------------------------------------------------------------
> > Take Surveys. Earn Cash. Influence the Future of IT
> > Join SourceForge.net's Techsay panel and you'll get the chance to share 
> your
> > opinions on IT & business topics through brief surveys - and earn cash
> > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> > _______________________________________________
> > Csound-devel mailing list
> > Csound-devel@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/csound-devel
> >
>
>-------------------------------------------------------------------------
>Take Surveys. Earn Cash. Influence the Future of IT
>Join SourceForge.net's Techsay panel and you'll get the chance to share your
>opinions on IT & business topics through brief surveys - and earn cash
>http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
>_______________________________________________
>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 


-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Great!  If it is not too much trouble for you to email me the Bison output,
that would be wonderful.

Just this one time ... I will attempt to get Bison working at a later date,
but I do want to try out the new parser.

Anthony

Steven Yi wrote on 1/12/07 9:16 AM:

> I haven't heard any dissent so have scheduled myself to integrate the
> new parser stuff on Monday.  I don't know about committing the Bison
> output; I understand where that would help to compile for once, but
> it'll get in the way for everyone doing CVS commits as it'll more
> often than not say there was a change and mark as needing to commit.
> I can email off list though no problems and would prefer to do it that
> way at least initially.


-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net