I’ve had a look at the code and tried to find the problem.
This works for me, for an scsynth on port 56780:
n = Server(\test, NetAddr("127.0.0.1", 56780), clientID:2); // I chose a different client id, but you could try without
n.serverRunning; // false
n.startAliveThread;
n.serverRunning; // true
Synth(\default, target:n); // plays.
> On 21.12.2016, at 20:18, amindfv@xxxxxxxxx wrote:
>
> Anyone know the right way to do this?
>
> Tom
>
>
>> El 19 dic 2016, a las 22:49, amindfv@xxxxxxxxx escribió:
>>
>> So this may have been a bit of a hack, but my sclang workflow used to be:
>>
>> - Boot scsynth or supernova in one terminal window
>> - Run an sclang script in another window, containing "s.waitForBoot". "waitForBoot" was my way of "telling" sclang that scsynth was already running. If I tried to call e.g. "play { SinOsc.ar }" without it, it would incorrectly tell me that the server wasn't running.
>>
>> Commit 165bf6 seems to have changed this, causing "s.waitForBoot" to send "/quit" messages to the running server. How can I (ideally the "right way") tell sclang that scsynth/supernova is already running?
>>
>> Thanks!
>> Tom
>
> _______________________________________________
> sc-users mailing list
>
> info (subscription, etc.): http://www.birmingham.ac.uk/facilities/ea-studios/research/supercollider/mailinglist.aspx
> archive: https://listarc.bham.ac.uk/marchives/sc-users/
> search: https://listarc.bham.ac.uk/lists/sc-users/search/
Attachment:
signature.asc
Description: Message signed with OpenPGP using GPGMail