Forums > MaxMSP

new csound~ (build date 2006_09_01)

September 12, 2006 | 2:50 pm

Hi all,

About two weeks ago, I uploaded a new version of csound~ and
forgot to tell anyone. My sincerest apologies. The latest
version (2006_09_01) along with improved install instructions
can be found at:

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

The latest version will allow WinXP users to work with Csound
versions 5.02 and later, but is incompatible with earlier versions.
A MacOSX version has also been added for people using MaxMSP 4.6 on
a PPC Mac. An Intel/UB version of csound~ for MacOSX is not available
at the moment.

Relevant entries from the changelog are at the end of this
email. Have fun!

Davis

CHANGES.TXT:

2006_09_01

-> (MacOSX) Compiled a version of csound~ compatible with MaxMSP 4.6.

-> Recompiled WinXP versions to work with Csound 5.02 and 5.03. The
2006_09_01 build is incompatible with Csound 5.01 or earlier.

2006_08_18

-> Replaced RedBlack Tree code with a hash table to store invalue/outvalue
names and values. This will not change the way you used invalue/outvalue
feature. It may improve performance for low k-rate values.

2006_06_15

-> If message output is not enabled, then the command line string
passed to csoundCompile() will not be printed to the window.

-> Added messages "recordStart/recordStop/playStart/playStop".
These messages control the newly added sequencer which can record
all MIDI events, "control" message events, and "event" message
events. It can also play them back.

This feature is intended mainly for non-realtime rendering.
Adding "-oSomeFileName.aif" to the "csound" command will enable
non-realtime rendering and if there are any recorded events, they
will be played back during the rendering.

This feature has not been fully tested and should not be considered
complete. Other than this entry in the change log, there is no
documentation. If you haven’t talked to me about it, then you probably
shouldn’t use it.

2006_06_13

-> Fixed command line parsing so that flags that look like negative
numbers (e.g. "-3") are processed correctly.

-> If rendering to a file and reading from a MIDI file, if the "-T"
flag is not present, then it is added so that the rendering thread
exits when the end of the MIDI file is reached.


September 18, 2006 | 6:18 am

Davis Pyon wrote:
> About two weeks ago, I uploaded a new version of csound~ and
> forgot to tell anyone.
>
> http://www.davixology.com/csound~.html
>
> Have fun!

I have, thanks a lot!!!
Just two minor possible improvements:
Just rename the csound~_demo.mxt into csound~.help, thats what everybody
wants to be loaded when alt-clicking on csound~…
The instructions to edit the environment.plist could be enhanced by
showing the use of the property list editor, which comes (I think) with
the developer tools of OS X.
In my case the environment.plist existed already and you would not want
to overwrite existing entries…

Elsewise everything worked right out of the box, thanks a lot, big
improvement…

Stefan


Stefan Tiedje————x——-
–_____———–|————–
–(_|_ —-|—–|—–()——-
– _|_)—-|—–()————–
———-()——–www.ccmix.com


September 19, 2006 | 4:21 pm

— Stefan Tiedje wrote:

> Just two minor possible improvements:
> Just rename the csound~_demo.mxt into csound~.help, thats what everybody
> wants to be loaded when alt-clicking on csound~…

Actually, that entails a minor change to csound~. I won’t get into the
gritty details, but I will put that in the next release.

> The instructions to edit the environment.plist could be enhanced by
> showing the use of the property list editor, which comes (I think) with
> the developer tools of OS X.
> In my case the environment.plist existed already and you would not want
> to overwrite existing entries…

I wasn’t aware that the Csound5 installer would overwrite pre-existing
entries. I’ll look into it and let the developers know what I find.

> Elsewise everything worked right out of the box, thanks a lot, big
> improvement…
>
> Stefan

You’re welcome. And thanks for the feedback!

Davis


Viewing 3 posts - 1 through 3 (of 3 total)