Skip to content
This repository has been archived by the owner on Aug 22, 2024. It is now read-only.

The --record-length parameter in k4arecorder does not match the actual length of the recorded video #1959

Open
Kratos-Wen opened this issue Nov 10, 2023 · 0 comments
Labels
Bug Something isn't working Triage Needed The Issue still needs to be reviewed by Azure Kinect team members.

Comments

@Kratos-Wen
Copy link

Hello, when I use the command:

k4arecorder -d NFOV_UNBINNED -c 720p -r [record length] -l 15 --imu OFF /my/output/directory

to record, if I set the recording time to 60, I end up with a video of about 102 seconds. If the recording time is set to 3600, the resulting video is around 6240 seconds. I'm wondering if this discrepancy is related to my hardware, or if the clock that your time calculation is based on is inaccurate.

Expected behavior:
The length of the output video matches the set recording length.

Desktop (please complete the following information):

  • OS with Version: Ubuntu 20.04.6 LTS
  • SDK Version: v 1.4.1
  • Firmware version:
    RGB camera firmware: 1.6.110
    Depth camera firmware: 1.6.80
    Depth config file: 6109.7
    Audio firmware: 1.6.14
    Build Config: Production
    Certificate Type: Microsoft
@Kratos-Wen Kratos-Wen added Bug Something isn't working Triage Needed The Issue still needs to be reviewed by Azure Kinect team members. labels Nov 10, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Bug Something isn't working Triage Needed The Issue still needs to be reviewed by Azure Kinect team members.
Projects
None yet
Development

No branches or pull requests

1 participant