Time for [csound5~]? There is lots of great code in there, but I can't
say I have any interest in going back to .ORCs and .SCOs...
.hc
On Feb 1, 2006, at 6:19 PM, Mathieu Bouchard wrote:
---------- Forwarded message ---------- Date: Wed, 01 Feb 2006 16:03:27 -0500 From: Anthony Kozar anthonykozar@sbcglobal.net Reply-To: The ruccas.org mailing list. list@ruccas.org To: The ruccas.org mailing list. list@ruccas.org Subject: [ruccas.org] Release of Csound 5.00
Dear Ruccas.org music-makers and music-lovers!
Please excuse the rampant cross-posting of this announcement if you
receive multiple copies, but we are trying to get the message of this most
momentous event in computer music history out to as many people in the community
as possible.Rejoice! For Csound 5.00 has been released!
Csound is one of the most complete software-only systems for making
music with a computer. While it tends to have an "academic" or
"experimental" bent, Csound has been used to make music in all styles and genres.
Csound 5 is the major new version that has been in development for three years
and has been thoroughly modernized and greatly expanded.Of special interest to members of this list will probably be the
ability to use versions of Csound that are embedded in other popular music
software, such as PD and VST hosts (e.g. Cubase), or that communicate with other software via protocols like Jack, OSC, and Csound's own external programmer's API.Official announcement and release notes are below.
Questions are very welcome. They will probably get answered faster
and more accurately if posted to the Csound mailing list (see below).Enjoy!
Anthony Kozar anthonykozar AT sbcglobal DOT net
From: jpff@[...] Date: Wed, 1 Feb 2006 15:07:00 +0000 To: csound@lists.bath.ac.uk, csound-devel@lists.sourceforge.net Subject: [Csnd] Release of Csound5.00
After what has seemed a very long time (because it was...) we are releasing csound5.00 The binary, manuals and source files are on http://sourceforge.net/projects/csound and look for the csound5 files. The opportunity has been taken to tidy up the assembly of csound4.23 and earlier files and we are leaving the 4.23 files for a short while. Main message -- everyone should change to csound5. More robust, faster, more facilities, more fun, more music.
==John ffitch
Release Notes for Csound 5.00
The developers are very pleased to be releasing Csound5, for Linux (32 and 64 bit), Mac OSX and Windows, together with an uptodate manual.
The system can be downloaded from
http://sourceforge.net/projects/csoundMore details and further information can be found in the csound-develop mailing list at sourceforge and the main user mailing list ar csound@lists.bath.ac.uk
The changes from version 4.23 are extensive. The internal structure of the code has been radically changed, but the language remains compatible with Csound4, and all old orchestra/scores should run unchanged.
The main visible change is that we are using a plugin style of system. many of the opcodes are now loaded at start-up. This opens the way for private opcode libraries, and opcodes released under other licences than LGPL.
The other major change is a move to the use of external libraries where possible. All the internal code for sound files, realtime audio etc has been replaced. We are now using libsndfile for audio file I/O, and one of ALSA, PortAudio, CoreAudio, MME or ASIO for realtime. MIDI may be handled by PortMIDI as well. The incorporation of Open Sound Control facilities uses the liblo library.
A number of opcodes from csoundAV and csoundVST are now part of the main system.
Another major change is that Csound5 is embeddable in other programming systems, using an API for information linkage. We are including Python, Java and other bindings for the API. Csound5 can also have multiple instances and is re-entrant.
In addition there are a number of new opcodes, and of course bug fixes. We believe that csound5 is faster than csound4, and we encourage all users to move to it.
NOTE: IT MAY BE NECESSARY ON SOME PLATFORMS TO HAVE EITHER ENVIRONMENT VARIABLES OPCODEDIR OR OPCODEDIR64 SET TO POINT TO DIRECTORY WHERE OPCODES LIVE. THE RELEASED FILES ARE BELIEVED TO BE SAFE AND CORRECT IN THIS RESPECT BUT BEWARE!
New features:
Access to multiple ALSA devices FLTK widgets reworked and synchronised with csoundAV User defined gens with names (rather than numbers) --expression-opt command option Information on time for each phase of csound if required Command line options to set ID tags in output soundfile (title/copyright etc) Jack available as output device --sched option now accepts a priority value -+rtaudio option to select output system Many new command line options Utilities to create csd files from orc/score Tcl/TK frontends (cstclsh and cswish) Can use looping structures in WAV files as well as AIFF Increased number of possible input and output audio file formats named channels #ifdef in orchestra removed limitation of only one track in MIDI input files MIDI output can also be written to a file (this is somewhat limited) MIDI-style extra time and release (xtratim, linsegr, etc.) is now also possible with score notes string variables (of type S) automatic conversion of some C-style escape sequences (\n, \r, ASCII code in octal \ooo format, etc) in string constants made internal indexes to orchestra variables 32 bit (was 16 bit in Csound 4), allowing for larger and more complex instruments replaced old PVOC format with PVOC-EX in all related opcodes SADIR SSDIR and INCDIR can now be a colon separated list of directories
New Opcodes:
maxk tab, tabw, and tb0()..tb15() vst4cs plugin opcodes pconvolve ftconv loris opcodes Python opcodes fluid opcodes chani and chano; chnset and chnget (string indexed) GEN43 a number of pvs (streaming phase vocoder) opcodes moogladder statevar fofilter syncgrain miditempo event_i reverbsc (Sean Costello's waveguide reverb) freeverb gentune GEN operation GEN51 GEN52 diskin2 turnoff2 a-rate int() and frac(), and round(), floor(), and ceil() << and >> operators STK (Perry Cook) instruments available from original code k() function Mixer opcodes OSCrecv, OSClisten, OSCsend loop opcodes printf, printf_i string hacking opcodes
Bug Fixes:
Error in tablew fixed Minor fixed in dcblock Include files were confused by sections Improved reading of command line Fixes in dynamic fgen numbers gogobel and vibraphone amplitude fix Arguments to schewhen were wrong Better checking in bqrez minor checking in grain wguide2, wguide1 avoid very low frequencies wgpluck bug fix Some error messages corrected and typos fixed FLsetVal arguments were wrong outo missed out channel 6 fixed bugs and improved error reporting in ^+ and ^- code. kread, kdump and a number of other opcodes will take string arguments from the score bug fix in sinc window (gen20) Added iskip options to moogvcf, vco, bqrez, pareq, tbvcf and rezzy values rounded rather than truncated in deltap, comb, and delay removed spurious initial values from some MIDI opcodes Joystick was upside down lpshold and loopseg changed to agree with csoundAV marimba now allows zero probability of a multiple strike Added skipinit argument to diskin and soundin wave-terrain fixes for phase error accumulation (on long notes) new optional argument to delayr and all deltap opcodes, to allow delay taps to read from any of the nested
delayr/delayw pairs, not just the last new optional argument to distort1 opcode (defaults to zero), to select amplitude scaling mode (0: default, compatible with original version; 1: relative to 0dBFS, same as mode 0 if
0dbfs is 32768; 2: unscaled) valpass fixed parameter overwriting Improved accuracy in some filters Improvements in bowedbarJPff -- 1 Feb 2006
Files on Sourceforge
Sources: Csound5.00_src.tar.gz Csound5.00_src.zip Csound5.00_OS9_src.smi.bin Csound5.00_src_all.tar.gz (including Loris and STK code) Csound5.00_src_all.zip (including Loris and STK code)
Manual Csound5.00_manual_chm.zip Csound5.00_manual_html.zip Csound5.00_manual_pdf.zip Csound5.00_manual_pdf_A4.zip Csound5.00_manual_single_file.zip
OS9: Csound5.00_OS9.smi.bin
OSX: Csound5.00_OSX10.3.tar.gz Csound5.00_OSX10.4.tar.gz
Linux Csound5.00_i686.rpm Csound5.00_x86_64.rpm [Linux for non-root users on X86_64 Csound5.00_x86_64d.tar.gz Csound5.00_x86_64f.tar.gz ]
Windows Csound5.00_win32.i686.zip Csound5.00_win32.exe (with installed)
-- Send bugs reports to this list. To unsubscribe, send email to csound-unsubscribe@lists.bath.ac.uk
The Ruccas.org Mailing List http://mail.ruccas.org/mailman/listinfo/list_ruccas.org
PD-announce mailing list PD-announce@iem.at http://lists.puredata.info/listinfo/pd-announce
"The arc of history bends towards justice."
- Dr. Martin Luther King, Jr.
hi hans,
I read:
Time for [csound5~]? There is lots of great code in there, but I can't
say I have any interest in going back to .ORCs and .SCOs...
but [csoundapi~] already comes with it ;) see: http://lists.puredata.info/pipermail/pd-list/2005-05/028329.html
cheers,
x
Hallo, Hans-Christoph Steiner hat gesagt: // Hans-Christoph Steiner wrote:
Time for [csound5~]? There is lots of great code in there, but I can't
say I have any interest in going back to .ORCs and .SCOs...
_From what John ffitch and Victor Lazzarini showed at last years Linux Audio Conference you won't have to, instead you can write Csound in Python, for example.
Csound5 looks like an amazing upgrade and basically a total rewrite and maybe literally a reinvention.
Ciao
Frank Barknecht _ ______footils.org_ __goto10.org__
hello Frank, i just tried to compile fluid~ (from externals cvs) and Pd39.2 i also compiled fluidsynth1.0.6.
the fluid~ lib loads fine at startup but the creation of the fluid~ object crashes pd (signal 4). would it be related to the flext layer may be? there is a flext-iiwu folder which i did not use at all.
best regards, vincent
Hallo, vincent rioux hat gesagt: // vincent rioux wrote:
i just tried to compile fluid~ (from externals cvs) and Pd39.2 i also compiled fluidsynth1.0.6.
Hopefully you compiled fluidsynth1.0.6 with LADSPA disabled?
the fluid~ lib loads fine at startup but the creation of the fluid~ object crashes pd (signal 4). would it be related to the flext layer may be?
If you could run it under a debugger like gdb and send a backtrace, that would a a lot of help. (How to run gdb was described in the list archives several times.)
Ciao
Frank Barknecht _ ______footils.org_ __goto10.org__
Frank, thanks for your answer,
fluidsynth did not get compiled with LADSPA i think as the summary after ./configure indicates: LADSPA support : no
that's what i got with gdb (as a matter of fact, i am not used to this tool) btw, i struggled a lit bit just to find these simplistic two first lines in the mailing list, may be we should just add them on puredata.info?
gdp pd
(gdb) r Starting program: /usr/local/bin/pd [Thread debugging using libthread_db enabled] [New Thread 1076218336 (LWP 7428)]
Program received signal SIGILL, Illegal instruction. [Switching to Thread 1076218336 (LWP 7428)] 0x40266267 in fluid::fluid_init () from /usr/local/lib/pd/extra/fluid~.pd_linux (gdb) bt #0 0x40266267 in fluid::fluid_init () from /usr/local/lib/pd/extra/fluid~.pd_linux #1 0x40265da5 in fluid::__init__ () from /usr/local/lib/pd/extra/fluid~.pd_linux #2 0x40268339 in flext_obj_single::obj_new () from /usr/local/lib/pd/extra/fluid~.pd_linux #3 0x080a2b6a in pd_typedmess (x=0x8209bd4, s=0x0, argc=1, argv=0x81037e8) at m_class.c:664 #4 0x080a25c4 in new_anything (dummy=0x8220a88, s=0x8209bd4, argc=1, argv=0x81037e8) at m_class.c:530 #5 0x080a27a6 in pd_typedmess (x=0x8209bd4, s=0x0, argc=1, argv=0x81037e8) at m_class.c:749 #6 0x080a5c84 in binbuf_eval (x=0x8220a88, target=0x8209bd4, argc=0, argv=0x0) at m_binbuf.c:574 #7 0x080622c5 in canvas_objtext (gl=0x8227718, xpix=136448648, ypix=136448648, selected=0, b=0x8226088) at g_text.c:94 #8 0x08060639 in canvas_obj (gl=0x8227718, s=0x82136a0, argc=4, argv=0x81037c0) at g_text.c:145 #9 0x080a2b57 in pd_typedmess (x=0x8227718, s=0x0, argc=4, argv=0x81037c0) at m_class.c:665 #10 0x080a5c84 in binbuf_eval (x=0x8220a88, target=0x8227718, argc=0, argv=0x0) at m_binbuf.c:574 #11 0x080a93a3 in binbuf_evalfile (name=0x821fea8, dir=0x821fed0) at m_binbuf.c:1193 #12 0x080a9ba1 in glob_evalfile (ignore=0x8209be0, name=0x821fea8, dir=0x821fed0) at m_binbuf.c:1209 #13 0x080a2960 in pd_typedmess (x=0x8209be0, s=0x0, argc=136445648, argv=0x0) at m_class.c:732 #14 0x080a5c84 in binbuf_eval (x=0x8220a88, target=0x8209be0, argc=0, argv=0x0) at m_binbuf.c:574 #15 0x080ae080 in socketreceiver_read (x=0x821f530, fd=0) at s_inter.c:540 #16 0x080afbbf in sys_domicrosleep (microsec=136448648, pollem=1) at s_inter.c:180 #17 0x080af2e8 in sys_microsleep (microsec=136448648) at s_inter.c:202 #18 0x080aaabf in m_scheduler () at m_sched.c:487 #19 0x080b545b in main (argc=136448648, argv=0x8220a88) at s_entry.c:27
greetings, vincent
ps: strangely enough, i finally managed to run fluid~ and pd39, using an older version of fluid~ i compiled some time ago for pd38.
Frank Barknecht wrote:
Hallo, vincent rioux hat gesagt: // vincent rioux wrote:
i just tried to compile fluid~ (from externals cvs) and Pd39.2 i also compiled fluidsynth1.0.6.
Hopefully you compiled fluidsynth1.0.6 with LADSPA disabled?
the fluid~ lib loads fine at startup but the creation of the fluid~ object crashes pd (signal 4). would it be related to the flext layer may be?
If you could run it under a debugger like gdb and send a backtrace, that would a a lot of help. (How to run gdb was described in the list archives several times.)
Ciao
Hallo, vincent rioux hat gesagt: // vincent rioux wrote:
fluidsynth did not get compiled with LADSPA i think as the summary after ./configure indicates: LADSPA support : no
Yes, that's good.
that's what i got with gdb (as a matter of fact, i am not used to this tool)
... but you did a great job! ;)
btw, i struggled a lit bit just to find these simplistic two first lines in the mailing list, may be we should just add them on puredata.info?
gdp pd
(gdb) r Starting program: /usr/local/bin/pd [Thread debugging using libthread_db enabled] [New Thread 1076218336 (LWP 7428)]
Unfortunatly this backtrace at least to my untrained eyes doesn't offer an immediate solution, I dare not even to guess. Some things you could try would be: It crashes in "fluid::fluid_init", which gets called when the [fluid~] object gets created. You could uncomment this temporarily by putting "//" in front of line 56 as in:
55: AddOutSignal(2); // 2 audio out [ == AddOutSignal(2) ] 56: // fluid::fluid_init(argc, argv); 57:
and recompile with flext's build.sh.
If you then can create a [fluid~] object, you may be able to crash it again by sending a message [init( to [fluid~] which calls the initialization in "fluid::fluid_init" manually. Anyway both of these should give different backtraces.
Another thing you could try would be to use the Pd as it is in CVS currently, unless you already do so. That's what I'm running here and with that and flext and fluid~ from CVS I cannot reproduce the crash.
Program received signal SIGILL, Illegal instruction. [Switching to Thread 1076218336 (LWP 7428)] 0x40266267 in fluid::fluid_init () from /usr/local/lib/pd/extra/fluid~.pd_linux (gdb) bt #0 0x40266267 in fluid::fluid_init () from /usr/local/lib/pd/extra/fluid~.pd_linux #1 0x40265da5 in fluid::__init__ () from /usr/local/lib/pd/extra/fluid~.pd_linux #2 0x40268339 in flext_obj_single::obj_new () from /usr/local/lib/pd/extra/fluid~.pd_linux #3 0x080a2b6a in pd_typedmess (x=0x8209bd4, s=0x0, argc=1, argv=0x81037e8) at m_class.c:664
Ciao
Frank Barknecht _ ______footils.org_ __goto10.org__
There is a csoundapi~ and is included in the Csound 5 release. And yes, you can use Python, Java, TclTk, lua, C, C++ to do stuff.
Victor
At 09:13 02/02/2006, you wrote:
Hallo, Hans-Christoph Steiner hat gesagt: // Hans-Christoph Steiner wrote:
Time for [csound5~]? There is lots of great code in there, but I can't say I have any interest in going back to .ORCs and .SCOs...
_From what John ffitch and Victor Lazzarini showed at last years Linux Audio Conference you won't have to, instead you can write Csound in Python, for example.
Csound5 looks like an amazing upgrade and basically a total rewrite and maybe literally a reinvention.
Ciao
Frank Barknecht _ ______footils.org_ __goto10.org__
PD-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
Victor Lazzarini Music Technology Laboratory Music Department National University of Ireland, Maynooth
Frank Barknecht wrote:
Hallo, Hans-Christoph Steiner hat gesagt: // Hans-Christoph Steiner wrote:
Time for [csound5~]? There is lots of great code in there, but I can't
say I have any interest in going back to .ORCs and .SCOs..._From what John ffitch and Victor Lazzarini showed at last years Linux Audio Conference you won't have to, instead you can write Csound in Python, for example.
That's very nice. If you're intersted, I've made a python module for easy 3d programming using opengl for rendering. It can be useful to develop interfaces or visuals for csound using python:
http://www.cesaremarilungo.com/sw/devachan
Csound5 looks like an amazing upgrade and basically a total rewrite and maybe literally a reinvention.
Ciao
And the scons build system is a breeze. At least on my Slackware 10.2 box.
c.
www.cesaremarilungo.com
-
Cesare Marilungo -
CK -
Frank Barknecht -
Hans-Christoph Steiner -
Victor Lazzarini -
vincent rioux