ghost
commented
6 years ago update: plot thickens! I thought I should widen my scope so jumped on my wife's macbook (13-Inch, Late 2009 // OS X 10.11.6) and that works without a problem, which seems to point to something funny with my machine rather than any general mac issue.
As an experiment I launched a shared session with both computers, and found that my cursor and input was updating on wife machine fine and following that I was able to successfully trigger messages through to SuperDirt on my own.
So it would appear that my problem is only that my troop screen stops updating once I action tidal, I will try some fresh installing and see if that resolves the issue.
First off I'd like to say many thanks for this project, I've been looking for a collaborative live coding environment exactly like this for a while.
However I am having problems with successfully running Troop in Tidal mode on my MacBook Pro (15-inch, Late 2011) running High Sierra (10.13.3). Just to clarify, Tidal runs fine normally through Atom, and also FoxDot and regular SC code are also relaying fine from Troop (and I can switch between the two without a problem). However when I go to select TidalCycles as my language of choice the Troop interface freezes and becomes unresponsive - interestingly, if I am quick I can action a command while it is still booting, which will result in it being successfully relayed to SC3, obviously once everything locks up I can't do much more with it.
Just as an experiment I did find some hit and miss success with opening multiple clients and somehow getting one back to life, but this is obviously not an ideal workflow!
If I launch client with the the '--mode TidalCycles' option I also get an unresponsive window.
Thanks again for the good work, would be interested to hear if anyone has seen anything similar or any suggestions on where to start poking around looking for a fix.