Sorry, Dave. I have no personal experience with x86_64, but in the sc-users archive, Stephan Kersten does say: "you need to build sclang in a 32 bit chroot, some info on how to do that on debian is here: https://alioth.debian.org/docman/view.php/30192/21/debian-amd64-howto.html http://wiki.debian.org/DebianAMD64 scsynth needs to be built separately for 64 bit, passing LANG=0 to scons. sclang can be run directly from the 64 bit environment: http://elists.resynthesize.com/sc-users/2005/11/1542178/" http://www.nabble.com/compile-problem-amd64-tf1376023.html#a3693833 I am using SwingOSC. I chose it for the amount of documentation (relative to SCUM or Puxeddu's GTK bindings) as well as, with the GUI class, being able to run a good deal of stuff done by Mac SuperCollider users. Hanns Rutz has been developing it pretty actively over the fall. He's been very responsive to any questions/problems I've had. He's also looking for developers to help the project move along. http://www.sciss.de/swingOSC/ I built it from sources I downloaded in late July. I have not yet heard from anyone who has tried it in that environment yet, but I'd love for you to be the first :) Not at all. In fact, it requires it at the moment. There are replacements for sclang, such as Rohan Drape's stuff which I mentioned before: http://slavepianos.org/rd/r/ as well as Rutz's jcollider: http://www.sciss.de/jcollider/ I haven't heard of anyone using Psycollider on Linux (an implementation in Python, which is currently used to do SuperCollider stuff in Windows with SwingOSC as the GUI). Unfortunately, the only one of these that might work as an alternative to run my code is Psycollider. The rest would require me to rewrite (which I am somewhat considering, using rsc). Thanks for asking; let me know if I can help/encourage you more to get SCVamp running on your machine: Renick Bell http://the3rd2nd.com/SCVamp http://the3rd2nd.com