[Csnd] blue 2.4.0
| Date | 2013-02-06 12:33 |
| From | Steven Yi |
| Subject | [Csnd] blue 2.4.0 |
Hi All,
I'm happy to announce a new release of blue is now available at:
http://blue.kunstmusik.com
The main feature of this release is a new Clojure SoundObject.
Clojure (http://clojure.org/) is a Lisp language built upon the Java
Virtual Machine. The Clojure interpreter has been embedded into blue
so projects using Clojure are portable across all platforms and blue
installations without requiring any other things installed. The
SoundObject editor uses syntax highlighting and parentheses matching.
The other new things include a new ScoreNavigator Dialog
implementation (better performance), and new examples of using
AthenaCL within Blue via External SoundObjects. (Many thanks to Menno
Knevel for his contributions and working very patiently with me on bug
reports!)
There are currently two more bugs I am trying to work through in the
bug tracker, and once those are complete I will be releasing a 2.4.1
bugfix release. One other note, I have not yet had time to put a REPL
in for Clojure, but this is high on my list of things to do. I am
also continuing work on a new modulation system for BlueSynthBuilder
instruments, as well as AudioLayers, to come in the next few major
releases.
Thanks!
steven
>Notes for 2.4.0<
[released 2013.02.05]
NEW
* ClojureObject - SoundObject that uses Clojure (http://www.clojure.org) code
for generating notes
* Clojure 1.4.0 is embedded with blue so that user does not have to install
Clojure themselves, as well as guarantees code to run on every platform
* Editor has Syntax Highlighting and Parentheses/brace matching
* Script menu option added to Reinitialize Clojure engine
* clojureSoundObject.blue added to blue/examples/soundObject
* clojure-piano-phase.blue added to blue/examples/general; this is a
translation of reich.cm from Common Music 2.10.0 by Heinrich Taube that
demonstrates phase technique
* RFE #137 - added temp file check when opening projects that searches for
leftover tempCsd*.csd files from previous blue sessions (usually only happens
if blue/csound has crashed). Offers to delete the temp files after opening,
also checks if another project in the same folder is currently open and skips
temp file check
* Added three examples of using AthenaCL with Blue to blue/examples/soundObjects
folder (external_AthenaCL1.blue, etc.); contributed by Menno Knevel
NEW/FIX
* Bug #80/81: Optimized ScoreNavigatorView: introduced new paintNavigatorView
to LayerGroupPanels so that they could paint a simplified view for the
Score Navigator; fixes broken painting and improves issues with time pointer
rendering triggering frequent paints in the navigator view
FIX
* code completion for BSB Widgets would replace all code after cursor location
or up until ")" if found, fixed to behave as Csound ORC completion does
|
| Date | 2013-02-06 12:34 |
| From | Steven Yi |
| Subject | [Csnd] Re: blue 2.4.0 |
One more thing to report, I will be recording a screencast of new features tonight and will release tomorrow. Thanks! On Wed, Feb 6, 2013 at 12:33 PM, Steven Yi |
| Date | 2013-02-06 17:52 |
| From | Justin Smith |
| Subject | Re: [Csnd] Re: blue 2.4.0 |
Some questions about the clojure support: what version of clojure are you including? would it be possible to require .clj files from the classpath, and is there an appropriate place to put .clj files? (for example if I had some clojure utility code I want to have available regardless of the blue project I am using, is there something like .blue/src for this sort of thing?)
On Wed, Feb 6, 2013 at 4:34 AM, Steven Yi <stevenyi@gmail.com> wrote: One more thing to report, I will be recording a screencast of new |
| Date | 2013-02-06 18:18 |
| From | Steven Yi |
| Subject | Re: [Csnd] Re: blue 2.4.0 |
Hi Justin, I've included Clojure 1.4.0 with blue. Regarding clj files, that's a good question. :) I had not thought that part through as I had wanted to get through this first release first. I imagine the best thing would be for me to add support for both ~/.blue/clojure/src and projectDir/src. It seems like it'd be nice to have a standard for scripts, whether it's Python, JavaScript, or Clojure, for where to place external src files. What would you think about using .blue/clojure and projectDir/clojure? There's a precedent to with .blue/pythonLib, so clojureLib could be another option. Thanks! steven On Wed, Feb 6, 2013 at 5:52 PM, Justin Smith |
| Date | 2013-02-06 18:28 |
| From | Justin Smith |
| Subject | Re: [Csnd] Re: blue 2.4.0 |
clojure looks for its files in the classpath, so technically it could go anywhere as long as it gets added to the path so it can be found. I think clojureLib would make sense, for consistency's sake. ~/.blue/clojure/src would be a nice thing too (but that could easily just be .blue/clojure or .blue/clojureLib as well) Thanks for adding clojure support to blue, since I started using it for work I have grown quite fond of the language. On Wed, Feb 6, 2013 at 10:18 AM, Steven Yi <stevenyi@gmail.com> wrote: Hi Justin, |
| Date | 2013-02-06 18:37 |
| From | Justin Smith |
| Subject | Re: [Csnd] Re: blue 2.4.0 |
Also, how hard would it be to include support for "ClojureInstrument" objects in the orchestra? On Wed, Feb 6, 2013 at 10:28 AM, Justin Smith <noisesmith@gmail.com> wrote:
|
| Date | 2013-02-07 11:43 |
| From | Steven Yi |
| Subject | [Csnd] Re: blue 2.4.0 |
Hi All, I've posted a video that covers the 2.4.0 release: http://www.youtube.com/watch?v=RZnLI7yQTgg Thanks! steven On Wed, Feb 6, 2013 at 12:34 PM, Steven Yi |