SuperCollider 3.5 Beta Released

After 2 years of Supercollider 3.4, finally the beta version of SuperCollider 3.5 was released yesterday.

I have been compiling SC3 for a while, so that I have known what has been changed. But for the official version users, this might be fresh to experience.

The most noticeable change is the gui. (surely noticeable)

Now this gui is QT based, not cocoa based.

For instance, this is the help brower (Help.gui, or cmd+d in osx)

I personally dislike the white background, but now it can be fixed by correcting css file. This might be very comfortable for a user to search for their need. Especially when searching for a UGen, it also gives you all class definition and examples below, of course together with the description(explanation) of the Ugen itself.

Another nice part of the help browser is the auto-completion. When you type something on the search window, it will show the result of what you are typing in. It might be an easier for a person like me who forgets the name of the ugen or class name very often.

The startup file on ~/Library/Application Support/SuperCollider/ should be changed to ‘startup.scd’ if you have ‘startup.rtf’ file.

I don’t remember by heart what important changes are there for now.

After I use this beta version for a while, I will update the post.

 

Oh, this is the download links and comment from the mailing list.

if you find a bug, please report to the mailing lists and/or file a bug report
at https://sourceforge.net/tracker/?group_id=54622. the better the description
and the easier it is to fix the bug, so providing a simple reproducer or a
minimal test case will help a lot.

source tarballs:
http://sourceforge.net/projects/supercollider/files/Source/3.5beta1/SuperCollider-3.5beta1-
Source-linux.tar.bz2
http://sourceforge.net/projects/supercollider/files/Source/3.5beta1/SuperCollider-3.5beta1-
Source.tar.bz2

osx package (ia32/x86_64, requires at least 10.5):
http://sourceforge.net/projects/supercollider/files/Mac%20OS%20X/3.5beta1/SuperCollider-3.5beta1-10.5.dmg

git repository (3.5 branch):
git://supercollider.git.sourceforge.net/gitroot/supercollider/supercollider

Supercollider and Vim (SCVim) in OSX

After a while struggling with the supercollider editor, which for me has an issue with lots and lots of windows floating around the window, I decided to move to another editing environment to code SuperCollider.There are several options for this, such as using TextMate with sc bundle(https://github.com/sbl/scmate.tmbundle), but I wanted to have a more simple platform.

Then there was ”VIM’ and SCVim. (for more options : http://supercollider.sourceforge.net/wiki/index.php/Systems_interfacing_with_SC)

I will explain a bit how to make a proper install in OSX. (Lion, 10.7.2 at the moment of this posting)
First of all, I normally compile SC from the latest source using git. (for more information about download the latestSC source codes: http://supercollider.sourceforge.net/developers/)
In the source folder, there already is the editor source for SCVIM in the editor folder.
Go to the folder /yourSCSourcedirectory/editor/scvim.
If you want to compile scvim seperate, using those command

cmake ..
make
sudo make install

Then your scvim is located in /usr/local/bin/scvim (to see where your scvim is located: type this in terminal ‘which scvim’)
I assume that your SuperCollider is located in /Applications/SuperCollider, which by default this newly compiled supercollider should be there,
scvim is working by an application called ‘sclangpipe_app,’ which makes possible to run sclang.
When you run scvim, it automatically opens up this sclangpipe_app and this should be able to link all your SCClassLibrary and library files.
In your folder, you see the library files such as libsclang.dylib.
(In the official SuperCollider, you don’t see this so that you can skip this part) and those files should be symlinked to sclangpipe.
To do so, type this in your terminal

cd /usr/local/lib; sudo ln -s <build-dir>/SuperCollider/lib* 

There is another problem with scvim + sclangpipe_app.

When you run scvim on your terminal, your sclangpipe_app is not entirely loading SCClassLibrary, which somehow doesn’t work properly.
So that you need to execute sclangpipe_app seperate from scvim.
In order to do so, I use shell script that automaticallt does this job.
This is the example.

#!/bin/bash
open -a "iTerm.app"
  killall sclang
  /usr/local/bin/sclangpipe_app -l /Applications/SuperCollider&
  sleep 0.5
  open -a "iTerm.app" /usr/local/bin/scvim

I saved this file as ‘scvimsc’ and did ‘chmod +x scvimsc’ to make it executable, and put it into the folder /usr/local/bin/ .
Then what you need to do is in terminal, just type

scvimsc

Then it will automatically open both scvim and sclangpipe_app in a proper way.

 

Optional use of iIerm2 for scvim

I use iTerm2.app(free application) instead of default osx terminal, because I like the way it can do window management.
I wanted to put both ‘post window’ and ‘editing window’ on ‘one window’ so that I do not need to have several windows floating around.
In order to do that, you need to use apple script instead of shell script to set up this.
This is the apple script that I use.

tell application "iTerm"
activate
  -- my project workspace
  set myterm to (make new terminal)
  tell myterm
  launch session "sclang"
  set number of rows to 150
  set number of columns to 40
  tell the last session to write text "killall sclang"
  tell the last session to write text "/usr/local/bin/sclangpipe_app -l /Applications/SuperCollider"
  tell i term application "System Events" to keystroke "d" using command down
  tell the last session to write text "scvim"
  set number of columns to 100
  set number of rows to 10
  end tell

I saved it as an application called ‘iscvim.app’ (from the apple script editor) and put it into /Applications/
So that I can only execute this application to open up iTerms, and scvim, and sclang together in one window!

In theory, this compiling process should be all to make scvim to happen. But surely there is an issue with library links.
But for now all are working fine with some lines on terminal, and can be solved with premade script to make things work.

A nice part of using vim is not only ‘window management’ but also using plugin for VIM. such as snippets for supercollider.
I will get back to this subject some day.
any remarks and commends and questions are welcome.

SuperCollider Symposium, London April 2012: call for participation (deadline 16th Oct)

The SuperCollider Symposium is an international event for musicians,
artists, researchers and coders working with the SuperCollider
software. It features a technical conference, introductory workshops,
and a diverse programme of music and art.

The next SuperCollider Symposium will be April 12th–19th 2012, in London.

http://sc2012.org.uk/

We invite submissions of music, artistic works, talks, and workshops.
Submissions will be peer-reviewed, and should be submitted by:
* Submission date: 16th Oct 2011
* Notification of acceptance: 2nd Dec 2011

The Symposium will be hosted at various venues across East London, by
QMUL Centre for Digital Music, Goldsmiths Digital Studios, City
University Centre for Music Studies, and other partners. All concerts,
performances and exhibitions will be open to the public.

Further details for submissions (plus submission instructions, at the end):

//////////////////
// TALKS

Conference talks are invited on topics of SuperCollider-related
research, technical development, or artistic/musical practice. (Note
that submission is by abstract only, there are no full papers.) Some
examples of subject areas include:
* Audio/music synthesis
* Interactive sound and music
* Machine listening
* Generative sound and music
* Artistic developments
* Teaching and Learning
* Creative Collaborations
* Extending SuperCollider
* Using SuperCollider with other environments

//////////////////
// CLUB MUSIC

The symposium will feature a club night in an East London venue.
Therefore we’re calling for submissions of music for dancing to. Acts
can be any style, but must include some substantial use of
SuperCollider.

//////////////////
// MUSICAL/SOUND WORKS

City University London in partnership with Plus-Minus ensemble
(http://www.plusminusensemble.com) will host an evening concert of
musical/sound works in City University Performance Space.

Works may fall into two categories: 1. purely
electronic/electroacoustic/acousmatic, or 2. instrument/s plus live
electronics. Available instruments are clarinet (doubling bass
clarinet), violin, and piano (doubling accordion). All works must
include some substantial use of SuperCollider.

Technical specs:
8-channel loudspeaker ring with subs, plus on-stage stereo pair.
Alternative loudspeaker configurations may be possible.

//////////////////
// WORKS FOR EXHIBITION

The exhibition programme at the Symposium will be hosted at the Art
Pavilion gallery (Mile End Park, London E3 4QY) and in the adjoining
Arts Park, which features a small lake island. We seek proposals for
works small or large, which may be exhibited in the gallery space
and/or the outside space (lake, island, bridges). Proposals which make
use of the outside area are particularly encouraged. Works must
include some substantial use of SuperCollider.

Exhibition venue information:
* Webpage for the Art Pavilion (inc floor-plans):
<http://www.towerhamlets.gov.uk/lgsl/451-500/461_parks/mile_end_park/mile_end_art_pavilion/about_the_art_pavilion.aspx>
* Map showing the building, the lake and the island:
<http://osm.org/go/euu6whJRk–>
* Photo inside gallery: <http://www.flickr.com/photos/louisejoly/378646724/>
* Photo of the lake+island, with the gallery behind:
<http://www.flickr.com/photos/danstowell/5896781088>

Please ensure that you include information of the space and materials
required for the work.

//////////////////
// WORKSHOP LEADERS

Workshops will be held Sat 14th & Sun 15th April (at Goldsmiths), for
beginner/intermediate-level users. We seek people who would like to
lead a workshop – workshop leaders will be given free admission to the
Symposium. Workshop themes can be general (e.g. Introduction to
SuperCollider) or can cover specific topics, but please target the
beginner/intermediate level. Examples of workshop topics:

* Sound synthesis
* Live coding
* GUI programming
* Interaction with live instruments
* SuperCollider for research

//////////////////
// OTHER

If you would like to propose some other event or feature of the
symposium, please do – giving as much information as possible.

//////////////////
// SUBMISSION INSTRUCTIONS (for all types):

Please email your submission to [hidden email] and include the
following information:

* The type of submission (concert / talk / club / installation /
workshop / other)
* Name
* Title (of piece, of talk, etc)
* A description or abstract (no more than 500 words).
* Any specific resources requested (e.g. materials, performers)
* For music/audio, an audio recording can be submitted to soundcloud
dropbox <http://soundcloud.com/supercollider2012>, or you can provide
a link to an online recording. It is not compulsory to send a media
file, but it will help your submission.

/////////////////
Any questions? please contact [hidden email] or tweet @scsymposium.