![]() Data from the tracking source should start overwriting the values in the camera.This should have been automatically generated by the driver once tracking data started to be received Under the Camera Settings, select tracking source.In the PositionReceiver under Drivers, add the relevant tracking driver and set it up to receive tracking data.In r25 we have made a number of improvements to the camera tracking workflow within Designer. DSOF-24752 - Fixed an issue where d3net session between servers containing different capture card types threw "Unable to create video capture stream" errors and spammed the console continuouslyĭSOF-21756 Support for Invisible: real-time markerless mocap by move.aiįor details on how to use real-time markerless motion capture with Invisible by move.ai, please visit: ĭSOF-23201 Improve lens tracking source workflows.DSOF-24751 - Fixed an issue where camera focus distance and aperture were usable as layers.DSOF-24748 - Fixed lens calibration not being applied when using Object tracking source.DSOF-24734 - Fixed an issue where it was not possible calibrate tracking delay when using object rather than camera tracking source.DSOF-24595 - Fixed an issue where it was not possible to create a group in an existing group.DSOF-24576 - Fixed an Access Violation when stopping uncompressed RenderStream workload on an rx.DSOF-24295 - Fixed an issue where timecode was sometimes ignored when track jumping. ![]() DSOF-24130 - Fixed an issue where the tooltip didn't render text but could grow too tall when you have groups within group.DSOF-23645 - Fixed an issue where Actors and Understudies were not showing frame rate at startup until opening the session widget.DSOF-23458 - Fixed IO stalling due to too many concurrent read operations.New: The r21 release notes now include detailed feature overviews.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |