Following suggestion !7 (comment 969769691)
Description
The user is now able to set camera's resolution dimensions in real-time, thanks to the "calibration configuration" panel.
These values as well as the 3D avatar models dimensions are used in the processing of new coordinates into the Blender world space.
Indeed, the coordinates outputted by LivePose are not in the same space and should be calibrated to fit Blender's space of coordinates.
Changelog
-
tweak
-
utils/libmapper.py
-> removed non-used imports. -
utils/install_dependencies.py
-> removed global declaration ofdependencies_installed
. -
ui/ui_dependencies
-> minor presentation changes.
-
-
update
-
utils/livePoseWrapper.py
-> defined new distance constraints setting methods. -
utils/maths.py
-> use calibration config. -
utils/objects.py
-> functions modifications. -
ui/ui_panels.py
-> added calibration config panel.- Useful to modify camera's resolution values used to process coordinates in the Blender's world space with
get_kp_world_location
. - Avatar's 3D mesh dimensions are get through bpy.data.objects.
- Avatar model dimension are updated when picking the avatar.
- Added a yet non-used but functional DepthServerThread processing depth location.
- Useful to modify camera's resolution values used to process coordinates in the Blender's world space with
-
requirements.txt
-> added dependencies versions. -
imports.py
-> minor refactoring.
-
Reliability and efficiency review
- Really depends on the network connection quality.
- Make sure that the frame is clear + captures the whole body.
- Still encountering memory heap issues.
- Occasionally causes crashes when recording animations.
- Causes moves jittering after a while.
- Seems to block or slow down thread closing, when stopping capture.