Record a performance with your phones, turn it into animation on your computer, and use the motion in Maya.
Follow the Quick start for the complete path. You will prepare the phones, record a calibration and a performance, import the footage, then process and download the motion.
If you already have recordings, go to Import footage. If your footage is imported, start with Create a calibration.
Computer beside the capture area: use Desktop hosting. The desktop controls recording and imports selected takes directly from the phones.
Capture away from the computer: use Phone hosting. Record with the phone rig, then transfer the session when the computer is available.
Both paths use the same calibration and processing steps. The host controls the session; camera phones record their own video. Keep the original recordings until you have verified your desktop copy and backup.
Use this route for your first session. The linked guides explain each stage when you need more detail.
If a camera moves, record a new calibration before continuing. Keep lens, zoom and capture settings fixed for each calibrated setup.
Set up the desktop processor and the capture phones before your first shoot.
Use 64-bit Windows 10 or 11, a compatible NVIDIA RTX graphics card and its current driver. Confirm compatibility against the requirements supplied with your release before installing. Allow space for the app, installation, original footage and processing results; recordings can quickly become larger than the application itself.
Maya is optional for FBX processing. It must be installed and available to ATB Mocap if you want ATB Mocap to generate Maya scene files.
Use the app's Connected Apps area to check available external applications when you need Maya output.
The phone apps require Android 12 or later, or iOS 16 or later. Install the supplied Android app or the iPhone build provided to you. A supported operating system alone does not qualify a camera: run Device Check on each recording phone.
Update the participating devices together so they use compatible session and transfer features. Preserve recordings when updating; do not uninstall an app to resolve an update problem.
Pack secure mounts, charged batteries or power banks, floor markers, cables and a shared network or hotspot. Make sure the camera apps can use their cameras and microphones. Measure the calibration performer's height and leave enough free storage on every recording phone.
Give every camera a name you can recognize, then check that it can record the required profile.
On a fresh installation, Name this device suggests a name. Edit it if needed, then choose Confirm name. Use a different name for every camera in the session, such as Camera A and Camera B. You can change the camera name later in the phone's Settings.
On iPhone, the suggested name may be simply iPhone. Enter a useful name manually when this happens. Confirming or editing it works without access to the custom name in iOS Settings.
Device Check is mandatory before a phone records for the first time. Once it passes the standard check, the phone is ready to use; you do not need to repeat the check for every session. Run it occasionally to verify that recording still meets the required standard, especially after an app or operating-system update or if recording performance changes.
The optional 4K check is separate. You do not need it to use a phone that has passed the standard 1080p60 check.
Open Join as Camera, keep the phone sideways as instructed, and wait for the host. Check charge, storage and full-body framing. Keep the app in the foreground during recording and transfer.
If the check fails, read its result, check permissions and free space, let an overheated phone cool, then repeat it. Use a phone/profile that passes rather than ignoring a failed check.
Good coverage makes the rest of the workflow easier. Set up once, then keep the cameras fixed.
Start with a clear, evenly lit area and mark its edges. Leave enough room for the actors' complete movements. Keep people who are not performing outside the acting area.
Place the cameras around the space facing inward, on stable tripods. Walk the complete area and check every camera: the actors' feet, heads and raised hands should stay visible. Avoid an arrangement where all cameras see the same side of an actor.
Use at least three calibrated cameras for a single actor. Five gives more coverage. For multiple actors, use at least four calibrated cameras and aim for clear views of each actor from several directions throughout the action. Extra cameras help with crossings and close contact, but framing still matters. The multi-person solver can estimate briefly obscured motion; review its warnings and those parts of the result carefully.
For now, plan for up to 12 cameras. This is the current planning limit; larger rigs need separate testing. More cameras can improve motion quality and coverage, but also increase processing time.
Choose the intended lens and recording profile before recording calibration. Check focus and framing, then leave lens, zoom, camera position and capture settings unchanged for the performance takes.
If a camera moves, record a new calibration. A calibration describes the physical camera setup; choosing an old calibration cannot correct a newly moved camera.
Measure the calibration performer's height in metres. Record them walking through the whole area in a cactus pose, upright with elbows bent and hands raised. Include views toward each camera and movement back to the centre. Keep the full body visible.
Ordinary boundary floor markers help keep the performance inside the recorded space. You do not need to enter them when processing calibration.
Use a phone to control the rig when the computer is not beside the capture area.
The host controls recording. Each camera keeps its own original recordings. Check which devices are actually listed as recording cameras rather than assuming the controller is an additional camera.
Record calibration first, then name a new scene for the performance. Follow the same clap and recording steps as desktop hosting. Finish recording before collecting or transferring files.
You can import directly from the phones over Wi-Fi or USB. You do not have to collect every file onto the controller first.
If you want a consolidated phone copy before leaving the location, use Collect to this phone on a saved session. Keep the contributing phones open until copying finishes, then verify what is present. Preserve the session folders and companion metadata when copying them to a computer.
The desktop and phones need to reach each other on the local network. The desktop can use Ethernet while phones use Wi-Fi.
Keep both apps open and check that the devices are on the same reachable network. Avoid guest Wi-Fi that prevents devices from seeing one another. Try Search again or the available refresh control.
Use Connection help to show a connection QR code or desktop address. Scan the code or enter the address on the phone. This helps when automatic discovery fails; it still needs a working network connection.
When Windows asks about the app's network access, allow it on the trusted local network you intend to use. You do not need router port forwarding. If the network prevents communication, use USB or session-folder import for saved footage.
A phone can be connected for file transfer without being qualified to record. Complete Device Check before joining a recording session. Connections shows currently connected devices; transfer progress is shown with the session or import.
Use this workflow when the computer is near your capture area.
The session uses the open library and receives its name automatically. Keep that library open while hosting.
Start with the Calibration scene and follow Record calibration and takes. The desktop begins recording after the required camera acknowledgements; it has no fixed countdown. Wait until recording is confirmed before making the claps.
Click a camera tile to inspect lens and resolution choices before the first take. Those settings lock once the camera holds footage for the session.
On the desktop capture screen, Space or Enter starts or stops recording when you are not editing text or using a dialog. Check the visible recording state after each action.
You can use Exit session while requested imports continue in the background. Local hosted sessions remain available after restarting the desktop.
Record calibration first, keep the cameras fixed, and begin every take with the same clear, asymmetrical three-clap pattern. Leave different gaps between the claps: one short pause, then a longer pause.
The initial Calibration scene is a recording label. The camera calibration itself is created later on the desktop.
With several actors, choose one person to make the claps while the others briefly hold still. Select that person under Actor when processing the take. They can be different from the calibration performer.
Check the take list for missing cameras or an incomplete recording. Keep the phone apps open for any requested transfers. If you move a camera and continue filming, record a new calibration for the new setup.
Bring the recordings into the desktop library before creating calibrations and processing takes.
Open its takes screen and choose Import Videos. Select individual takes, or leave all unchecked to request outstanding footage. Keep phone apps open until the expected clips show Imported.
Alternatively, open a saved session on a phone, choose Upload files, and select the intended desktop and library.
Use the Android or iPhone USB option offered by Import footage and follow its connection prompts. If you already copied the session to your computer, choose A session folder and select the complete session folder.
Keep videos and their companion metadata together. Confirm the destination project and any camera details requested by the importer. When available, choose Go To Session after import.
Confirm that the expected takes and camera recordings are present. Transferred bytes are not the same as a completed library import. Read any missing-file or Needs attention message before processing.
If a transfer stops, reconnect the phone and reopen its app. Pending desktop requests can resume; repeat a phone-initiated upload when needed. Use Retry failed imports after fixing the reported problem. Successful clips are kept. Import does not start a solve automatically.
Keep the phone originals until you have checked the imported footage and made a backup.
Use this when you want a phone to hold copies from the other cameras before returning to the computer.
This copies recordings. It does not change the recording roles or delete the other phones' originals. A camera phone can collect copies; it does not need to become the host.
Choose Stop collecting if needed. Completed copies stay in place; choose Collect to this phone again to continue. Check storage if the app reports that space is low.
Only available participating phones can contribute. A finished copy operation does not prove an offline phone has no additional footage. Check the expected camera roster yourself.
Use Upload files from the collected session, or copy the complete session folder for desktop import. The files keep the original cameras' identities. You can also import directly from the recording phones without collecting first.
Calibration finds the camera arrangement and scene scale for the recordings made with that setup.
The calibration form uses the standard processing defaults. Boundary markers used to show the acting area's edges do not need to be entered.
Check the camera layout and any reported warnings. Make sure the expected cameras are included and the arrangement makes physical sense.
Use this calibration only for takes recorded with those camera positions and settings. If a camera moved, create a new calibration from a recording made after the move.
The calibration performer's height establishes the scene scale. It does not mean every person in later takes has that height. When processing a performance, Actor identifies the person who made that take's claps; it can be someone else.
If calibration fails, first check full-body visibility during the walk, the measured height, the selected recording and the clap range. Read the app's specific warning before deciding whether to record again.
Choose the recording and calibration, then tell ATB Mocap which section of the performance to solve.
One actor uses ATB_SingleSolver. Multiple actors use ATB_MultiSolver. The multi-person workflow requires the corresponding camera coverage.
Set Clap sync (s) around all three claps so the recordings can be aligned. Set Capture range (s) around the action you want to keep. The output range can leave out the claps; keep them in the original recording.
Use the timeline and playhead controls to inspect the recording and set the start/end points. Check that each start is before its end.
Choose Run to start now, or immediately after any currently running work. Choose Queue to hold the item until you start it yourself; it will not start automatically when other work finishes.
Click the run summary at the bottom of the sidebar to open the run queue. Its Run button releases every held item into processing, in order, one at a time. It runs the whole held queue, not only a selected row.
Follow the current stage and messages in the app. Let the app report completion before downloading results.
Read warnings even when a preview is produced. A completed run with warnings may need review. If the result needs a different calibration, actor selection or range, create a new solve with those corrected choices.
Continue with Review and regenerate outputs.
Use Pause to suspend the active run and Resume to continue it. Select the running item and choose Stop to stop it; select waiting items and choose Remove to take them out of the queue. Read the current button label before acting.
Clear Completed removes finished entries from the queue display. It does not delete the stored results or run history. Keep earlier versions while reviewing a replacement solve.
Watch the result against the performance before using it in animation.
Play the complete preview and check body movement, turns, foot contact and actor identity. For multiple performers, watch crossings and close contact as well as the separated parts of the take. Read any warnings attached to the run.
The preview is a way to inspect the motion. Its character proportions and deformation can still need refinement. Foot placement in a preview does not guarantee perfect foot locking after retargeting.
Use Re-Process on an existing solved take when you need to regenerate its delivery files and preview from saved animation. This is useful after a preview-resource update or after making Maya available for a missing Maya scene.
Re-Process does not estimate a new performance from the camera recordings. To change the motion solve, create a new run with the intended inputs and settings.
Open the take and choose Run beneath Versions when you need a new solve with corrected processing choices. Confirm calibration, actor count, clapper and time ranges before starting. Keep earlier versions until you have compared the results.
After checking the result, continue to Download animation.
Download the result that matches the actor and application you will use.
Open the processed take and choose Download.
Each actor has a separate animation file. Multi-actor downloads retain actor numbers; choose the actor you intend to retarget. Keep the original downloaded files alongside your working copies.
Check that Maya is installed and detected in Connected Apps. Read the run's output warning, then use Re-Process to regenerate the delivery files and download again.
Confirm the actor, frame rate, frame range, scale and root movement. Exclude any setup/T-pose frames from the final shot. Follow Use the motion in Maya for character setup, retargeting and baking.
Prepare your character once, then reuse that setup for each performance.
The cactus pose is for recording calibration. The T-pose is for character setup in Maya.
Save a copy before baking. Use Select Controls in the HIK tool, then your rig's baking tool to bake the chosen frame range onto those controls. Play back the baked animation and save the scene.
Studio Library is optional if you want to store the baked controls for reuse. Character-specific retargeting adjustments remain part of reviewing the result on your own rig.
Keep your captures and processing results organized without having to rename camera files by hand.
Use the sidebar and breadcrumbs to move through the collection. Give projects, scenes and takes clear names. Keep camera filenames and companion metadata together when copying recordings.
Open the destination library before starting a desktop session or an import. A hosted session and its transfer requests retain that library destination. Finish the hosted work before switching libraries.
The desktop Host Session page lists saved local capture sessions, including sessions whose footage is still on phones. The library's Sessions area contains imported material ready for calibration and processing.
Open session on the hosted takes page becomes available after at least one take has all expected camera clips imported. It opens the corresponding session in the library.
Preserve earlier processing versions while comparing a new solve. A preview refresh through Re-Process uses saved animation; a new solve creates a new result to review.
Activate the desktop with your own purchase details and keep participating phone apps compatible.
Open Licensing in the desktop sidebar. Enter your license key and the email used for the purchase, then follow the activation prompts. Keep the key private.
Use Check Status when you need to refresh the displayed license state. If activation fails, check the key, purchase email and internet connection, then read the message shown by the app.
A valid desktop activation can be used offline until the locally displayed validity expires. Reconnect before that deadline to refresh it. Your subscription and license must remain valid. Use the date and status shown by the application for your current entitlement.
Close the desktop before running a desktop update. Keep the complete setup download together and retain your library backup. Install phone updates over the existing apps so recordings and settings are preserved.
Use compatible Android and iPhone builds for the same rig. Phone updates do not replace desktop backups or requalify a changed recording setup automatically.
Send the app version and exact license error through the support route provided with your release. Do not post the license key, purchase email or an activation screenshot publicly.
Keep enough working space, verify transfers and back up the library before removing original recordings.
Camera phones keep their recordings locally. Collection adds copies to another phone. Import adds verified footage to the desktop library. Processing creates animation and preview outputs alongside the library's session work.
Do not treat a successful phone-to-phone collection as a desktop backup. Check the expected cameras and takes after import, and play representative footage.
Close active work, then back up the complete library to a separate location, including its database, footage, metadata and processing outputs. Check that the copy is readable. Keep a separate copy of important downloaded animation and Maya working scenes.
Open Storage & Cleanup to review the desktop's storage and cleanup options. Read what the app proposes to remove before confirming. Preserve original footage and the outputs you still need.
On a phone, Clean up transferred is restricted to files the desktop has confirmed. Review the confirmation and your backup before removing anything. Delete This Session is a separate destructive action; it is not a transfer or retry command.
If a transfer reports low space, free space on the destination and retry the failed work. Keep pending transfer files in place so the app can resume them.
Start with the message in the app. These checks cover the problems most likely to interrupt a normal session.
Keep ATB Mocap open on both devices. Check the shared local network and desktop Allow phone connections setting. Avoid isolated guest Wi-Fi. Refresh, then try the QR code or desktop address in Connection help. Use USB import for saved footage if the network is unavailable.
Complete the standard 1080p60 Device Check with camera and microphone permissions granted. Follow the orientation prompt. The preview pauses during the recording check; watch the countdown. An optional failed 4K check does not require repeating a passed standard check.
Check the phone's visible prompt, orientation, charge, free space and Device Check result. Verify that camera names are unique and that the selected lens/profile is supported. Do not begin the performance until recording is confirmed for the intended cameras.
Reopen the phone apps and reconnect them. Confirm the intended session and destination library. Retry the upload or use Retry failed imports after fixing the reported issue. If using a folder, copy the complete session with its metadata. Check the missing camera phone directly before assuming the session is complete.
Listen to the recording and check that Clap sync (s) includes all three clear claps. Microphone access must have been available while recording. Capture range (s) can exclude the claps; the sync range must still include them.
Check the selected recording, calibration performer's height, full-body visibility and calibration walk range. Confirm the camera setup did not move. Read the specific quality warning. Record a new calibration if the setup changed or the recording does not cover the acting space.
Read the run message. Check actor count, calibration, the person who clapped and the chosen ranges. Inspect the source views for missing body parts or blocked actors. For a graphics/runtime error, confirm the supported release requirements and graphics driver, then retain the exact message for support. Use a new solve for corrected inputs; Re-Process only regenerates outputs from saved animation.
Check Maya detection in Connected Apps, then Re-Process the solved take and download again. FBX does not require Maya. In Maya, also verify the intended HumanIK Character/Source, frame range and scale.
Use the website contact forms to report a problem or send feedback. Identify the product as ATB Mocap in your message.
Keep the app version, exact error text, the stage that failed and a screenshot of the relevant screen. Say whether the session was phone- or desktop-hosted and which phone models were involved. Keep originals intact. Share sensitive recordings or license details only through a support route agreed with the owner.