CasparCG
OSC remote trigger behaves different
when i trigger a group of layers with normal keyboard commands the start sync 99% off the time triggering a group with OSC "/control/#UID#/play" gives a much poor result !
For performance reasons the OSC messages are not immediately propagated to the rest of the application via a signal, but periodically emitted. Maybe an exception should be made for /control/*
Define "much poor result".
What do you mean by "start sync 99% of the time"?
The performance caching in the client is barely noticeable, especially for control commands. You can't expect zero latency, especially when network latency and such is involved.
Hi Zebiolo
I understand that commands are always fired sequential
but there is a difference in timing between the commands rolling in to the server if you trigger a group by OSC or by hand.
when i am behind a machine i will setup a better test to give a more in depth look at the differences.
although casparcg is not designed to do sync start between multiple channels it all is pretty close to do so.
grt Maurice
Check the server logs for time difference when trigger the group through OSC.
@mauricev78 Can you verify this issue as solved thanks to pull request #196?
/Armin
