Hi,

As mentioned in the subject, dmp.csound~ is now simply csound~.  Csound 5.01
is required now for 64bit csound~ on WinXP.  All other versions do not have this
requirement.  At the end of this email is a list of new features and changes.
Download it here:

http://www.davixology.com/csound~.html

Big thanks to Matt Ingalls for the name.  Big BIG thanks to Matt and Victor
Lazzarini
for their externals.  Their source code served as my API documentation (csound.h
doesn't really count).  

Davis


CHANGES.TXT:

2006_03_18:

-> If using 64bit csound~ on WinXP, Csound 5.01 (or later) is required.

-> Added the "noscale" flag.  It's used to bypass audio data scaling
   to/from Csound.

2006_03_15:

-> Added another outlet that sends a bang whenever a csd/orc is
   successfully compiled.  It's a useful feature if you have MIDI
   control opcodes that need to be initialized from the Max environment.

-> Added messages "m", "c", and "e" which are equivalent to
   "midi", "control", and "event", respectively.  These new messages
   are intended to save screen space.

2006_03_14:

-> If neither -d or -g is present in the "csound" message, then csound~
   will add -g to allow the user to see the ASCII representation of
   tables.  Either -d or -g must be present to prevent crashing.

-> Added bang method which acts like the "start" message.  Added
   for compatibility with Ingalls' csound~ patches.

2006_03_11:

The following changes were made in order to add features that were in
Matt Ingalls' version of csound~.

-> Renamed dmp.csound~ to csound~.   

-> Added second optional integer argument to specify # of output signals.
   If no arguments are supplied, then there are 2 input/output signals.
   If 1 argument is supplied, then that argument specifies the # of input/output
   signals.  If 2 arguments are supplied, the first is the # of input signals 
   and second is the # output signals.

-> After "start" message is received, if the # of Csound audio channels != the
   # of input or output signals for the external, a warning is displayed.

-> Added "printout" message which works exactly like "message" message. 

-> If csound~ has not received a "path" message to set the current directory,
   relative pathnames in the "csound" will be relative to the directory
   that contains the patch that contains csound~.

-> Added the "sfdir" message.  The "sfdir" has one argument which should be the
   pathname to a directory.  That directory will be used to set the SFDIR, SSDIR, 
   SADIR, INCDIR, and CSSTRNGS global environment variables.  By default, these 
   env variables are set to the defualt directory (see above).  At the moment, 
   I don't know what the INCDIR and CSSTRNGS variables are for, but they were set 
   in Ingalls' csound~ so I set them just in case.

2006_03_07:

-> Changed behavior of "start" message.  When "start" is passed to [dmp.csound~],
   the current directory is reset to the directory that was given as part of the
   last "path" message.  If "path" has not been received yet, then nothing is done.

   This should fix the problem where other instances of [dmp.csound~] have a 
   different directory saved as the current directory.  


 

It's because the 64bit dll is called csound64.dll in 5.01.
In version 5.00, it was called csound.dll.   I felt it was better
to require users to use 5.01 rather than change the name of csound.dll.
The new versions of csound~ use csound32.dll and csound64.dll on WinXP.

Davis

--- Istvan Varga  wrote:

> On Sunday 19 March 2006 08:02, Davis Pyon wrote:
> 
> > Csound 5.01 is required now for 64bit csound~ on WinXP.
> 
> I do not quite understand this requirement, given that there have
> been no incompatible API changes made that I am aware of, nor have
> been new features added to the API. Did I miss something ?
> Also, why does the restriction apply only to 64 bit floats ?
> -- 
> Send bugs reports to this list.
> To unsubscribe, send email to csound-unsubscribe@lists.bath.ac.uk
> 

Oh, you're right.  I meant the 5.01b .exe rather than 5.00 .zip.  If any
WinXP csound~ users are listening, if you install Csound5 with either:

Csound5.00_win32.i686.zip
Csound5.01_win32.i686.zip

then you should be fine.  If you installed Csound5 with:

Csound5.01b-win32.exe

and you're having problems (csound32/64.dll not found), I suggest you download
and install one of the .zip files mentioned above.  I hope that when
Csound5.01-win32.exe is released, it contains csound32/64.dll as well.  

Thanks Istvan,

Davis

--- Istvan Varga  wrote:

> On Sunday 19 March 2006 22:05, Davis Pyon wrote:
> 
> > It's because the 64bit dll is called csound64.dll in 5.01.
> > In version 5.00, it was called csound.dll.
> 
> I assume by '5.01' you mean the .zip package, which in fact always had
> csound64.dll and not csound.dll ? I do not know if the the file name is
> changed in the 5.01 .exe release, since that is apparently not available
> yet; nevertheless, the Feb 25 beta that is still on SourceForge contains
> csound.dll.