I have version 4.23f07 of the CSound source distribution, downloaded
from SourceForge after September ninth, and I have no problems
building it in my usual way.  I changed wxCSound so it can be compiled
in a mode that interacts with CSound only through the CSound API, as
long as CSound supports the yield callback.  wxCSound uses the yield
callback to implement user initiated aborts of a CSound run.

I have not been able to build a library implementing the CSound API.
Are there instructions on how to do this?  I've replaced jpff_glue.c
with csound.c in my file build list, and I've edited cs.h so that
POLL_EVENTS is defined to be csoundYield.  The resulting system has
serious linking problems.

For one thing, I'm compiling with RTAUDIO undefined to make the
distribution easy to port, but csound.c expects definitions of various
audio functions.  Even if you hack around this problem, functions such
as csoundOpenLibrary are not defined.  I added load_opcodes.c to the
build list, and found conflicts with dl_opcodes.c.  I removed
dl_opcodes from the build list, and then found csoundLoadExternal was
undefined.  This iterative process did not seem to be converging, so I
stopped.  Should I consider these problems subjects for bug reports,
or is there some trick that would fix my problems?

I also loaded MSYS and MinGW on a Windows 2000 laptop.  I compiled and
installed wxWindows using their configure script with just one
problem.  The wx-config script had to be altered to add
-I/usr/local/include to the C and C++ flags it generates.  I
configured wxCSound, and compiled the code I wrote with no problems.
The CSound code generated a few compile time errors.  Once again,
Should I consider these problems subjects for bug reports, or is there
some trick that would fix my problems?  One error I recall is the file
sfont.c:117 redeclares _errno.

Finally, when I compile CSound with GCC and -Wall, I received a number
of warnings, a few of them look scary.  Should I consider the warnings
a subject of a bug report, or is this situation well known?

John

wxCSound source site: http://www.ccs.neu.edu/home/ramsdell/tools/

Hi all, 

I'm not sure if others have checked it out, but wxCsound is pretty
nice.  If Winsound will be making an exit and be replaced with a version
that will use the CsoundAPI, I'd like to suggest we use wxCsound as an
initial code base with the aim to reproduce all of the functionality
that is in Winsound.  It'd be nice to see a consistently laid-out GUI
that is available cross-platform.  (I'm thinking it would particularly
benefit teachers who are teaching Csound whose students would most
likely vary on what platform they are using at home.)

One thing I checked is that license-wise, wxWindows seems to fit fine
with LGPL Csound (http://www.wxwindows.org/newlicen.htm).  It has been
ported to MacOS9, MacOSX, Windows, and Linux, which covers the major
platforms for Csound, and since it uses native widgets it should be
easier to approach for new users.  

On the other hand, FLTK is also license-wise compatible with Csound
(LGPL).  I understand it would be a little strange to have wxWindows and
FLTK in the same build, though the FLTK opcodes could probably be moved
out of the engine and into a plugin.  And since both toolkits are C++, I
can't imagine that it would be too difficult to port John's wxCsound
work to FLTK.


So, what's everyone else think on the issue?  

steven

stevenyi  writes:

> Hi all, 
> 
> I'm not sure if others have checked it out, but wxCsound is pretty
> nice.  If Winsound will be making an exit and be replaced with a
> version that will use the CsoundAPI, I'd like to suggest we use
> wxCsound as an initial code base with the aim to reproduce all of
> the functionality that is in Winsound.

I was hoping to get out a solid Windows version of wxCSound before
this issue was raised.  I also plan to build an installer for it using
the NullSoft Install System .

In any event, I too would very much like to see a consistently
laid-out GUI that is available cross-platform.  

Let me extend my thanks to Steven for helping me find a nasty pointer
bug, and for sending me helpful comments.

John

I released an experimental Windows binary at:

http://www.ccs.neu.edu/home/ramsdell/tools/

It's experimental because it crashes sometimes.  Presumably, the
crashes are only due to the problem I reported yesterday, but I'm not
completely sure.

People not interested in wxCSound may still be interested in this
release.  It is distributed using an NSIS generated installer.  The
NSIS script used to generate the installer is contained in the source
distribution. 

John

Hi John,

Neat!  Just tried it out on windows and the installer worked fine, app 
is looking great, and rendered a scanned synthesis piece I was working 
on without problems.  Didn't try multiple renders so didn't come across 
the crashing bug you posted yesterday. 

The Table viewer is neat, but the white background for the whole panel 
versus just the drawing area sticks out in my point of view. 

Thanks!
steven

John D. Ramsdell wrote:

>I released an experimental Windows binary at:
>
>http://www.ccs.neu.edu/home/ramsdell/tools/
>
>It's experimental because it crashes sometimes.  Presumably, the
>crashes are only due to the problem I reported yesterday, but I'm not
>completely sure.
>
>People not interested in wxCSound may still be interested in this
>release.  It is distributed using an NSIS generated installer.  The
>NSIS script used to generate the installer is contained in the source
>distribution. 
>
>John
>
>
>
>  
>

I would like to fill in wxCSound's AUTHORS file with something
informative about the parts of CSound used to create the version of
libcsound.a I use.  If there is a standard sentence people use for
this purpose, please send it to me.
        
Clearly I have to include Barry Vercoe's name, and I've noticed that
John ffitch is sometimes singled out for being the chief maintainer of
CSound.  I grep'd the sources using the pattern copyright on the files
used to create libcsound.a, excluding any real-time audio files.  I
came up with the enclosed list of contributors.  Should their names be
included?  Did I miss someone?

Alan deLespinasse
Allan S C Lee
Barry Vercoe
Bill Gardener
Dan Ellis
Dave Madole
Dave Philips
Davide Rocchesso
David McIntyre
Eli Breder
Erik Spjut
Fabio P. Bertolotti
Gabriel maldonado
Gabriel Maldonado
Georg Essl
Greg Sullivan
Hans Mikelson
Istvan Varga
Jens Groh
J. Michael Clarke
John ffitch
Keith Henderson
Marc Resibois
Mark Dolson
Matt Gerassimoff
Matt Gilliard
matt ingalls
Michael A. Casey
Michael Clarke
Michael Gogins
Nick Collins
Nicola Bernardini
Paris Smaragdis
Paul Lansky
Perry Cook
Peter Neubäcker
Phil Burk
rasmus ekman
Richard Dobson
Richard Karpen
Robin Whittle
Sean Costello
Sean M. Costello
Tom Sullivan
Trevor Wishart
Victor Lazzarini
Ville Pulkki
William 'Pete' Moss
Willian 'Pete' Moss

Stephen,

I made the change you requested to the background of the plots tab,
and it will appear in the next release.  Thanks for your feedback.

John

steven  writes:

> Hi John,
> 
> Neat!  Just tried it out on windows and the installer worked fine, app
> is looking great, and rendered a scanned synthesis piece I was working
> on without problems.  Didn't try multiple renders so didn't come
> across the crashing bug you posted yesterday. The Table viewer is
> neat, but the white background for the whole panel versus just the
> drawing area sticks out in my point of view. Thanks!
> steven
> 
> John D. Ramsdell wrote:
> 
> >I released an experimental Windows binary at:
> >
> >http://www.ccs.neu.edu/home/ramsdell/tools/
> >
> >It's experimental because it crashes sometimes.  Presumably, the
> >crashes are only due to the problem I reported yesterday, but I'm not
> >completely sure.
> >
> >People not interested in wxCSound may still be interested in this
> >release.  It is distributed using an NSIS generated installer.  The
> >NSIS script used to generate the installer is contained in the source
> > distribution. John
> >
> >
> >
> >

I meant to write 'Steven' not 'Stephen'.  No morning coffee yet...

John

steven  writes:

> Hi John,
> 
> Neat!  Just tried it out on windows and the installer worked fine, app
> is looking great, and rendered a scanned synthesis piece I was working
> on without problems.  Didn't try multiple renders so didn't come
> across the crashing bug you posted yesterday. The Table viewer is
> neat, but the white background for the whole panel versus just the
> drawing area sticks out in my point of view. Thanks!
> steven
> 
> John D. Ramsdell wrote:
> 
> >I released an experimental Windows binary at:
> >
> >http://www.ccs.neu.edu/home/ramsdell/tools/
> >
> >It's experimental because it crashes sometimes.  Presumably, the
> >crashes are only due to the problem I reported yesterday, but I'm not
> >completely sure.
> >
> >People not interested in wxCSound may still be interested in this
> >release.  It is distributed using an NSIS generated installer.  The
> >NSIS script used to generate the installer is contained in the source
> > distribution. John
> >
> >
> >
> >

=)

Not a big deal.  Looking forward to your next release!  BTW: there's one
thing I thought would be nice, and that was the ability to drag and drop
a file onto the main frame and have it become the active file, as long
as csound is currently not in performance, as well as focus the settings
tab to show the new file info.  I was thinking this could work with csd,
orc/sco (if you drop an orc, it'd check to see if a file with the same
prefix.sco is available and vice versa), or csc file.  

steven


On Mon, 2003-10-06 at 07:10, John D. Ramsdell wrote:
> I meant to write 'Steven' not 'Stephen'.  No morning coffee yet...
> 
> John
> 
> 

Steven,

The wxWindows documentation chapter titled "Topic Overviews" has a
section on Drag and Drop, and in particular, there is an object called
wxFileDropTarget.  Thus your suggestion appears to be doable, and I've
placed it on my to do list.  I'm not sure about the level of effort.

The "Topic Overviews" also has a section on wxPython, which, according
to Robin Dunn, "is a blending of the wxWindows GUI classes and the
Python programming language."  wxPython and SilenceVST might make an
interesting combination, given that SilenceVST already embeds Python.

John

stevenyi  writes:

> =)
> 
> Not a big deal.  Looking forward to your next release!  BTW: there's one
> thing I thought would be nice, and that was the ability to drag and drop
> a file onto the main frame and have it become the active file, as long
> as csound is currently not in performance, as well as focus the settings
> tab to show the new file info.  I was thinking this could work with csd,
> orc/sco (if you drop an orc, it'd check to see if a file with the same
> prefix.sco is available and vice versa), or csc file.  
> 
> steven
> 
> 
> On Mon, 2003-10-06 at 07:10, John D. Ramsdell wrote:
> > I meant to write 'Steven' not 'Stephen'.  No morning coffee yet...
> > 
> > John
> > 
> >