Hello Depthkit Team,
is there a chance to get a different export from a normal 6 azure sensor setup ?
I did lately recordings with DepthKit Studio and used 6 attached Azure Sensors.
I observed for the PNG export I somehow receive first the one RAW PNG file (4512x1184)…
which I then transcode to the two raw PNG sequence RGB + Depth (2256x2366)…
but this PNG file I receive there is somehow half lower quality as each sensor was recording 2560x1440
as the RGB is actually placed next to depth and by that the resolution is halfed.
The multisensory PNG workflow gives (each RGB 592 x 752) definitely higher results as multisensory MPG export gives for each sensor (RGB 320x270) but the original resolution of each RGB is 2560x1440 (minus depth octa corners reduction around 1184x1440) so somehow the quality is on 25% in the PNG and in the MP4 export on 1/8.
I am aware that there is as well the additional external camera solution with replacing paired RGB (what I haven’t tried yet) but it would be already amazing to as well go for the original RGB stream of the Azure and with an option of manual exposure settings plus the option not to reduce the size of the original stream for half in the PNG export.
It would be amazing already to say inside of DepthKit where the program still has access to the original sized sequences that I decide there to export 2(Row)x3(Sensor) sensor positioning and an backdrop of original sized backdrop or with an scale factor 0.9 shrinked or 0.8 / 0.7 / 0.6 / 0.5 shrinked and so on and then later during the ffmpeg process go for the fitting individual chosen shrink factor backdrop size as well noting the shrink factor inside of the meta file … that the in unity the unity plugin can easy know which scalefactor is used for the MP4 file.
Is this maybe on the near future roadmap ?