we are developing a narrative VR experience for which is going to run on Quest stand-alone
the experience will integrate modeled environments along with volumetric video of the “narrator” of the story
i wonder which mirrorless should we shot with - a full frame like A7S\R or Aps-c such as a6400
i guess we are going to compress the video file deamatically in each cases and i wonder if the difference between the files will be notable at all
secondly - if we want to shot a full shot of a seated person - what lens should we use
@user2 Depthkit Cinema works with many different types of cameras and lens systems. We have successfully tested full-frame 35mm, Super-35, APS-C, and Micro Four-Thirds cameras.
For highest quality, you should always use the lens which most closely matches the field-of-view of the depth sensor, then move the sensor and camera closer/further from the subject to ensure they fill up as much of the frame as possible without clipping any part of them in either depth or color frame. When using the Azure Kinect, the lens focal length which most closely corresponds to the narrow (NFOV) raw depth mode for full-frame 35mm is ~16-17mm; The focal length which most closely matches on APS-C is ~10-11mm. In my opinion, there aren’t any huge advantages to using one sensor size over the other, except perhaps that the APS-C system may provide a wider depth of field, making it easier to keep your subject in focus.
our experience is being built to run on a Quest stand alone
we are uncertain whether to shot with a mirrorless full frame or to limit ourselves to Apc-s since we afraid the full frame files will be too heavy for the quest
what do you advise us to do?
is there really no difference in quality if we chose Aps-c over full frame as you stated above?
do you have any recommendations for a a certain video file that we should use (codec wise) that would be best to compress and optimize in order to run the volumetric video on a Quest stand alone?
@user2 The codec used to record Cinema footage can be either of the following:
If you are going to import it into Depthkit directly, use a Windows Media Foundation-compliant codec - We recommend H.264 MP4.
If you are going to be color-correcting, scaling, or transcoding the Cinema footage, you can record using whichever codec you want, but once you create the color-corrected/transcoded versions, they must be encoded in Windows Media Foundation-compliant codec like H.264 MP4, and this same process should be applied to your calibration samples as well as the footage which will be linked to your recordings.
All assets come out of Depthkit as H.264 MP4 videos, which work perfectly in standalone playback on Oculus Quest.
@user2 - A quick update for this thread: One of the new features found in Depthkit v0.7.0 is an export settings preset for Meta Quest, which leverages the HEVC (H.265) codec, TV color range, and other settings to generate Combined Per Pixel videos optimized for playback on the Meta Quest platform.