server
server copied to clipboard
CasparCG
OSC LAYER STATUS
currently you only get osc message for paused via a message like "channel/1/stage/layer/1/paused". I think it will be better if we could have something like "channel/1/stage/layer/1/status" that will return either "paused" or "playing" or "stopped" or "completed" to show the state of the layer. this will make it much easier to implement a playout client, instead of relaying on the position/duration time
Also we absolutely need to see what's loaded in the background of a layer. Currently there is no way to get that information since INFO is gone.
I was tinkering and it seems that OSC will not get updated with the info from the background since it's not currently receiving frames since it's in the background. My work-around was to send the background producers print() information on every foreground frame receive but obviously this is a HUGE hack and delivers the background producer data in a weird string format.
Any word on the layer status will be appreciated, is it that it not an important feature or its not possible to implement. Just having a paused status alone is not helpful
I know @julusian looked into the background producer and IIRC it is not trivial to send out information from there. That's due to the way osc data is gathered every frame, so when a producer is not producing frames it can't "send" or rather "give" any data. What other status report do you need apart from paused / playing for the currently playing producer? I could imagine combining playing / pausing with current frame and seek / length parameters should give you enough info?
currently LOADBG send a response "RES ID 202 LOADBG OK" at load time , but does not send a "RES ID 202 PLAY OK" when its about to play when AUTO is set. is it possible for LOADBG to send RES ID 202 PLAY OK when being played?
Quoting Julusian from an answer to one of your earlier questions:
After a producer is created, there is no knowledge of where it came from, which makes async responses pretty impossible without some large changes.
So no, unfortunately that is technically not possible, let alone if it would be expected / wanted behaviour at all.
@baltedewit my question was not about OSC. technically, i think everything is possible. The code the runs the AUTO play on the LOADBG can easily send that response.
@baltedewit lets assume this statement is entirely true:
After a producer is created, there is no knowledge of where it came from, which makes async responses pretty impossible without some large changes.
how was it possible to report the OSC PAUSED state when the producer had already been created. is that an exception to the rule
technically, i think everything is possible.
awesome, I'd love to see a PR from you then.