Jesper Stærkær
Jesper Stærkær
@5opr4ni could this be the new bug you mentioned during the TSC meeting?
@ronag this bug seems to track back as a 2.2 regression and does not look to be related to the new routing.
 Tested and confirmed to be the same bug in 2.2 #f0d65d66
Related: #673 an #674
Hi Phil. Sure, it would be awesome. We have discussed this already with several broadcasters. One approach is to have CasparCG Clients which talk AMCP and still maintain control over...
After working with Ember+ integrations for the last week, I really see how it would fit CasparCG well. However, I struggle to see obvious benefits over the current OSC functionality....
`CG [channel]-[layer] INFO` does exactly this. This can be closed, I guess.
`CG [channel]-[layer] INFO` returns synchronously. However, `CG [channel]-[layer] INFO [flashlayer]` is still asynchronously and never sends the relevant result back over AMCP, just traces to console and log. I will...
After discussions with @HellGore I will try and make the TemplateHost return the data directly, as a synchronous operation. I will have @jeansson review this before submitting.
Robert, is the delay/offset predictable and stable?