> 2)Stream access for recording or event detection using ML model
Each stream is individually being encoded for a user depending on his network conditions/resolution/etc. Do you want to access the same video stream or want to have a separate higher latency and (constant) quality one? If second, this will mean additional load on the encoder which will lower your density.
We have a plan to add a spectator mode in the future but this will introduce a second encoded video stream and not reuse the one of the actual player.
Can you provide us more details on what specifically you're looking for?
Hey Srinidhi,
> 1)save and restore game state
Anbox Cloud does not provide explicit support for this and it's on you to implement backup/restore of any userdata you want to preserve from instances. We have lifecycle hooks you can use to implement backup/restore of any data inside the Android data partition. See https:/ /anbox- cloud.io/ docs/ref/ hooks and https:/ /anbox- cloud.io/ docs/howto/ addons/ backup- and-restore
> 2)Stream access for recording or event detection using ML model
Each stream is individually being encoded for a user depending on his network conditions/ resolution/ etc. Do you want to access the same video stream or want to have a separate higher latency and (constant) quality one? If second, this will mean additional load on the encoder which will lower your density.
We have a plan to add a spectator mode in the future but this will introduce a second encoded video stream and not reuse the one of the actual player.
Can you provide us more details on what specifically you're looking for?