Friday, April 11, 2008

SuperCollider for Hardy!

Just a quick notice, that I've updated the SuperCollider binaries for Ubuntu 8.04 (Hardy Heron), that's going to be released later this month. This time, the packages are merged with the original 20060416 version as advised by #ubuntu-motu. Also, the supported architectures are extended to powerpc and lpia.

APT sources.list entries:

deb hardy main
deb-src hardy main



  1. Thanks! Works great, although for some reason it doesn't show up in Add/Remove. Still, a huge step up from tar.gz

  2. Yeah, Add/Remove only shows the official repositories, but I'm working on including the package to Universe, you can track the progress through bug 183552.

  3. Thanks a lot for your effort! (It works fine on my i386 machine, don't even need qjackctl anymore.)

    Should I reinstall Hardy in i386 mode on my amd64 laptop in order to use SuperCollider / your package? Kind regards.

  4. Well, SuperCollider (sclang) still does not work on x86_64 architectures. So if you need both scsynth and sclang you'll have to go i386 :( In fact, I had to do this for an amd64 laptop as well...

    But I'm working on an scsynth-only amd64 package, that will be available in the near future (along with a sced package and probably some plugins/quarks). Stay tuned for updates!

  5. (Good to know. Thanks again!)

  6. Thanks - the package works well, but I cannot record anything at the moment. For some reason prepareForRecord command doesn't work at the moment. What might be the problem?

  7. I've had this problem too. To me, it looks like SuperCollider and libsndfile didn't like each other's versions. As someone suggested on the mailing list, it's better to record via JACK for now...

  8. hi there!

    first of all, thanks for a great package. it was long time needed.

    but, there's little thing/problem. i still love to use emacs. i installed supercollider and supercollider-emacs package from your repository and emacs22. it seems like Evaluate Line with M-C-h doesn't work. any clues why?

  9. nova viator, they there was some talk about changing shortcuts on the mailing list, so perhaps there're some new hotkeys? (I don't know 'em myself, because I don't use emacs right now). Also, did the sclang buffer appear for you? If not, try running emacs with -sclang option and post your results. Hope this helps. Artem.

  10. hija,

    thanks for answers.

    well, i used to use C-M-h to mark the whole function and then C-c-C-c send it to server, but now i discovered C-M-h is to switch to 'help browser' (which doesn't really work, neither does C-c C-h (Find help).. however, i discovered C-M-x to directly execute current de/function (what's inside brackets). so that's good.
    what doesn't work is 'evaluate expression', which enables you to quickly write something like "s.freeAll" and Return and it should stop all sound. however emacs/sclang churns this out:

    ERROR: Command line parse failed
    ERROR: Message 'sceld' not understood.

    i'm not sure these bugs are part of changes is supercollider or this particular package.

  11. Yes, that was a bug in the SuperCollider itself, which is now fixed. I will update the package as soon as the new upstream release is available (and that is going to happen real soon I think).

  12. artwo,

    thanks for great work! we need a recent and working version of supercollider in ubuntu.

  13. artfwo

    Thanks for this, nice to see the new release fixing the soundlib bug.

    I was trying this on a ubuntu amd64, bit of a bother to set up with chroot since no supercollider-amd64, but it works fine. Just wondering if you knew of any other way to set this up with ubuntu-amd64?

  14. Hi, Sornen!

    Unfortunately the only way to install SC3 under amd64 is the chroot way...

    But you may find the amd64 builds of scsynth in my PPA as well. I guess you may even try to use those builds with the chroot environment for the ease of installation, but I have not tried this myself yet :)

  15. Hi Artfwo
    Just for others who want to try this. I used your builds for the chroot, and then your amd64 server build. I also used your amd64 gedit build and installed it with
    dpkg --force-depends
    and then removed the pkg dependency in
    and added these links
    sudo ln -s /chroot/hardy-ia32/usr/bin/sclang /usr/local/bin/
    sudo ln -s /chroot/hardy-ia32/usr/share/SuperCollider /usr/share

    This explains it in some more detail:
    but no need to build sc just add artfwo's source.list to the chroot directory and your main ubuntu amd64 build.

  16. Hi Artfwo
    Previous anonymous poster was me Sornen, which I guess just makes it pseudonymous. A couple of other things. In the chroot I also installed the 32 bit supercollider-doc which then makes it accessible from gedit using ctr U.

  17. Ah, so the documentation has to be installed into the chroot, and not into the host system...

    That surely makes sense, now I remember, that the helpfiles are searched by a SuperCollider function, that is envoked from Sced, so everything is working is expected!

    Thank you for the instructions, Sornen! Guess, I shall finally install a 64bit Ubuntu myself after all :)

  18. Yet another thing to add

    export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/chroot/hardy-ia32/usr/lib/:/chroot/hardy-ia32/usr/local/lib/

    to .gnomerc in your home directory or create it if it does not exist.

    Also be weary of deleting chroot/hardy-ia32 without first deleting the entries in fstab and remounting the file system.

    Perhaps I should put all this in a wiki


  19. Yes, I remember once deleting the chroot together with /proc and /dev from my host system by accident... :)

    Surely, a wiki page will be most useful, indeed!

  20. Hi there, I'm running Ubuntu 8.10 64 bits and I'd like to install supercollider and sced using the techniques described above but I am confused about all of this chroot stuff and can't get anything to work. Can anyone help explain how to do this in a step by step way? I'd really appreciate it.

  21. Rockdrigo, the step by step instructions can be found in the wiki.

    You can safely follow them up to the "# download and build" step, and either proceed with compiling or installing the packages as outlined by Sornen here.