Ron Kuivila and I have been working on some SC3 code that would allow for remote interpretation of the language across a network.Â Of course, there already exist several options for the SC3 user that provide various advantages (Client/LocalClient, BroadcastServer, oscGroups, PB_UP, etc), but these were way too complicated in their implementation for my needs, and provided features that I simply had no use for.Â The result is very paired-down and simple to use.Â On the local side, there is a window for typing SC3 code, with a header consisting of a smaller text box for the target IP. Â
Entire blocks of SC3 code can be placed into the window and interpreted remotely (also works on loopback) by pressing enter.Â The overall behavior is a lot like the SC3 IDE, although somewhat limited in terms of key-commands.Â However, this allows me to simply write my code in the SC3 system and remain there in order to execute it remotely.Â On the remote side, all that is necessary to run is SC-Lang and an OSCresponder that listens to calls from the local machine.
There are other advantages to this approach over others, namely that each instance of this editor can be used for communication with a different node on a LAN.Â As a result, the process of composing for 4 networked machines has become rather simple, no longer the logistical nightmare it once was.
Despite my naming the paradigm "remote_lang2.0", it is still in the development stage.Â Additions to functionality must be added before I can say this stage has been surpassed.Â For now I have to keep an ssh tunnel into each of those remote machines in order to view post-window data.Â This is in the process of being improved.Â Also, I'd like to see a command-log for each window, so I can save a document of legal SC3 code as a transcript of the commands sent to each server.Â Furthermore, there are some environment access issues that should be solved before I'll be totally happy with it.Â But this is a start, and allows me to actually get back to composing instead of trudging along in emacs.Â For the curious, you can download the code here.