Closed sorenhan closed 5 years ago
Since the MRE audio API is now implemented, there seems to be a lot of overlap in the API functionality with the video player (other than the visual part, of course). It may make sense to make the video player just use the audio API, and file type dictates if it should create a video or audio? This also means all future synchronization improvements would be shared between video and audio, and that any future MRE client library/host app could choose to implement video players consistently (currently this is an AltspaceVR-specific extension)
video player is not spatialized and has high volume by default. we need to expose the same options we have in the sound api for falloff curve, volume, spread, etc.