Julian Rohrhuber
Julian Rohrhuber
I've just made a change, could you check if it fixes your issue?
> Could it be, that the pause action on the server side takes some time on more complex SynthDefs and when this happens, then the client code is not applied...
Just to reduce the possibilities of wrong ordering, I've added a little change.
Thanks for the catch, I am sorry I didn't check carefully enough. Also, I've added a change so that the synth is registered. You should be able to check if...
> Or to be more precise, when I check the synth whether it is playing or running, then the value is always false. I will keep trying it. Yes, this...
This is excellent, thank you for the good analysis. Just one question, what is meant by "synth status: true"? That it is playing (exists on the server), but may be...
So yes, this is clearly a timing issue, the synth is woken up after it is paused explicitl by a message that is already on its way. I have done...
if all works, I'd merge into develop now.
Thank you! I think a code of conduct is not to be "enforced". It is the scale against which we may measure what is appropriate and what is not. So...
Hi @mossheim I have deleted the thread, because I wanted to give everyone (that is everyone who wanted) a chance to reset and start anew. It may have been wrong...