Please enable javascript in your browser to view this site!

Common Problems


Quicktime Errors

I'm having some errors with needing Quicktime.

Modern installations and fresh installs of Windows don't natively package Quicktime 7, so you'll need to download the latest version of codec here.

Recording Issues

My recordings are dropping frames.

Close any other apps.

Make sure you are plugged into wall power

If writing to an external hard drive make sure it's USB 3.0 or FireWire 800.

This can be caused by using a USB extender for the Kinect that is too long without an inline repeater. Remove the USB extender or use an active USB 3.0 extender.

Calibration Issues

My Kinect is unable to self-calibrate

DepthKit maintains a relatively narrow margin of error when it comes to calibrating the Kinect, so if a Kinect calibrates outside of that range it will fail to calibrate. We're working on a new version that lets you calibrate with the caveat that the Kinect isn't as well-calibrated as it could be, but for now you'll need to either buy a new Kinect or download a prefabricated calibration like the one here. Once you download the file, close the Capture application, and then place that file in you matrices folder. When you open the Capture app again, it should say that your camera has been properly calibrated.

My depth camera's FoV/principal point don't match the figures given in the video. Or I can't calibrate the Depth Camera.

If they are only slightly different, don't worry!

Try the process again from scratch by disconnecting devices and relaunching the application.

Make sure there is information in the scene that falls within the range visible to the sensor (~3'-12').

Check that there is variation in the scene; information in the foreground, middle and background.

I'm getting high error numbers on the calibrate lenses page.

High error may occur when the checkerboard is too close or too far away.

Make sure there is no glare on the checkerboard from lights. Even one hot spot from a nearby light could throw off the reading.

Make sure that the exposure is set properly on the camera - if the whites of the checkerboards are too bright sometimes you need to shoot it again at a slightly darker exposure.

Make sure you refocused on the checkerboard at every stage and that your aperture is no too low, making the depth of field shallow.

While calibrating, my correspondences are not detecting or are way off.

Confirm that you have a low error on the first stage.

Make sure that your set up is totally stable when capturing the correspondence images. A wobbling checkerboard or camera tripod will throw things off.

Often this will happen if there is not enough ambient IR light, get closer to a window

Conversely if there is too much or uneven lighting it'll also blow out your checkerboard

Try different depths from the camera, being wary moving it too close or too far.

I'm unable to drag in my clips for the Calibrate RGB Intrinsics step or the Calibrate Correspondence step.

There is an issue where launching DepthKit Capture "As an administrator" will make it so dropping in clips isn't possible. If you're running into this error, try starting DepthKit normally, without selecting "Run as administrator."

You also need to make sure your clips are the proper codec — XAVC, .R3D, and other file formats will likely not work. You may need to transcode your calibration videos to h264 in order to import them.

The program is unable to find the checkerboard in the IR image in the "Calibrate Correspondence" section.

It's very likely that you printed your checkerboard with an ink that is too glossy. This can be the case if you used a high-end photo printer or something like a Canon Pixima printer. You should try to print instead with a laster printer, or even just photocopy what you initially printed and use the copy instead of the original, as that should make the checkerboard more receptive to IR light.

Visualize Problems

My video doesn't show up in the Visualizer (either the thumbnails or synch preview) or otherwise acts strangely, or the console shows an error that states "Couldn't get static framerate."

This is usually caused by issues with your source videos. Generally there's no issue with simply dropping your files straight into the /color folders, but occasionally you'll need to transcode the videos if your video's native format isn't compatible with Visualize. If you're looking for a tool to transcode your videos you can use ffmpeg (free), Adapter (free), MPEG Streamclip (free), Adobe Premiere/Media Encoder (paid), or Quicktime Pro (paid).

When you transcode, be sure to keep your video's full resolution and change the codec to something Visualize supports like Apple ProRes or h264. Both video wrappers should be .mov. If you are encountering the above error, be sure to make sure there is a keyframe for every frame. 

If you are using ffmpeg, this means passing the "-g 1" flag as part of your transcode command, like this:

ffmpeg -i mySourceVideo.mp4 -c:v libx264 -pix_fmt yuv420p -g 1 output.mov


For Premiere, there is an option at the bottom of the export dialog to manage keyframe intervals (set this to 1):

After transcoding, replace the videos in the .../color folder with your transcoded videos, close the Visualizer and relaunch it. 

If you don't want to set a keyframe every frame, you can try encoding as a .mov (Quicktime) with either h264 or mpeg4 for the codec, which should allow you to playback/seek/export. If you encode as a .mp4 with .h264 codec, you will likely only be able to playback, not seek or export. For this reason, use .mov whenever possible.

My texture alignment is way off.

Try using the X & Y Rotate, Shift or Scale in the Texture Alignment tab to accommodate for slight inaccuracies.

You may want to recalibrate, which is fine to do after you've shot as long as the relationship between camera and sensor is still fixed.

My time alignment/sync is way off.

Delete any markers on the 3rd "Alignment" track on the timeline to start over.

Look for a very decisive temporal moment to align to, meaning that there is a specific fast movement which allows for precisely selecting a depth and video frame from close times. Because the cameras have different frame rates and clocks, the alignment will never be perfect but should not drift over time.

Visualize will not let me track/seek depth frames, and the frame number is stuck at 0 in the depth track.

If you have verified that the depth frames are indeed in the /depth folder, there is likely a problem with your drive permissions and you'll need to change the permissions to allow you to both read and write from the drive. Otherwise move your Take and calibration file to your main drive and try again.

Visualize will not let me select an exact frame in the timeline, making it difficult to sync my depth and color. It is also not allowing me to select or play the end of the clip in the timeline. 

Once you have verified that there is nothing unusual with your depth sequence, you can try removing your sensor video (if you captured one) from your project file. Visualize may be getting thrown off by the sensor video frame rate. Once this video is removed and you restart Visualize, these issues should be resolved. 

My renders stop always stop at a given frame, no matter what my in/out frames are.

DepthKit Visualize has some problems playing back MJPEG codec videos, and if your video is of this type it's worth trying to rewrap it as h264/mp4.

If you try to rewrap your video and it still doesn't work, you may have a problem with the timecode encoding in your video. Try to re-render your video with fresh timecode, which should then fix the issue.

The camera is aimlessly flying off into the ether without input from me.

This often happens if you've held ALT while pressing one of the movement keys (W,A,S,D etc.) Either hold alt again and press the same key or reload the comp.

My depth frames look corrupted in the preview window when trying to sync my TAKES.

This is a known issue when working with depth frames that have been exported from the newer version of the Capture tools (grayscale). If you're unable to sync, closing and opening the Visualize tool should fix the issue, but if not, you can go directly into your sensor/depth folder and find the frame number for the sync depth frame. You can then seek to this depth frame in the Synchronize tab.

My alembic export is failing to open in 3Ds Max (or similar application) or crashing the application on import. 

This is a known issue and the recommended work around is to convert the alembic files. One way to do this is with Houdini's command line, using the alembic converter here. Once converted, you will be able to open the alembic file in 3Ds Max 2018. Please note that this conversion will increase your alembic file size. 


Capture Problems

The preview in my Capture application seems to stutter a bit, freezing for brief moments every few seconds.

    • This is usually caused by using a USB extender for the Kinect that is too long without an inline repeater. If this is happening, either remove the USB extender or use an active USB 3.0 extender.

My depth camera feed is not showing up in the Calibrate Lenses tab.

    • Try disconnecting and reconnecting your depth camera, then restarting the application.
    • Occasionally fully restarting the computer has helped with sensors that fail to pick up.
    • Confirm that you're using the correct version of the app for your sensor – beta is designed to be used with the Kinect v2 on a Windows machine.
    • If you're using a USB extender, remove it and plug the sensor in directly.

The application crashes when I try to load movie files from the HD camera.

    • Make sure your video files are compatible with the toolkit, H.264 or ProRes MOV's.
    • Make sure you have the latest version of Quicktime installed. If you just ran a fresh install of Windows, it's likely that you don't have Quicktime. Download the latest version here.
    • Make sure you are running the application from a location where you have write access

My Capture app crashes when I attempt to the Calibrate Lens step using extra high resolution (3.5k, 4k) videos.

This happens when you try the Calibrate Lens step using the old method of calibration. The program now allows you to drag the folder containing the RGB videos instead of the videos themselves, which should fix the problem.
If you still have problems:

    1. Drag the first five video clips from the camera & drag them into the window.
    2. Find the /_rgbCalibration directory inside .../MediaBin/_calibration/ where the Capture Application saves the converted PNGs.
    3. Copy the PNGs generated for the first five videos into another directory.
    4. Repeat steps 1-3 in sets of five videos until you've processed all the calibration videos.
    5. Gather all the PNGS from the external folder and copy them back into the folder in _calibration. 
    6. Relaunch the app.

Problems with Capture/Visualize

My application will not launch or it crashes.

    • Maybe your system doesn't support the toolkit. You'll need a computer with accelerated graphics no more than 4 or 5 years old.
    • We have also had recent issues with brand new mac laptops with integrated graphics cards. 
    • Make sure you have not moved the data/ folder in relationship to the DepthKitCapture or DepthKitVisualize applications.

I get an error that states "The program can’t start because MSVCP110.dll is missing from your computer"