Xangle FAQ

1. Bullet-time basics

Planning a multi-camera photobooth or camera array? These answers explain the technique, equipment and setup choices. For software operation, licensing, network configuration and troubleshooting, see the detailed Camera Server FAQ.

1.1 - What is bullet-time, or time-slice photography?

Bullet-time uses photographs from multiple cameras positioned around a subject to create the appearance of moving around a frozen moment. It is also called time-slice photography or a freeze-frame effect. Camera spacing and the shape of the array influence the resulting movement.

1.2 - Can I create a Matrix-style freeze-frame effect with XangleCS?

Yes. XangleCS controls supported multi-camera setups and provides capture, calibration and stabilized playback tools for creating bullet-time effects. The result depends on camera placement, timing, lighting and the selected output settings. See the bullet-time photobooth guide for capture and playback options.

1.3 - Do I need a separate trigger box for a bullet-time camera array?

Supported setups can trigger cameras over USB without separate camera trigger cables. Connection requirements and timing vary by camera model and system architecture, so check the camera compatibility guide and test your intended setup.

1.4 - Does XangleCS support Canon EOS camera arrays?

XangleCS supports selected Canon EOS DSLR and mirrorless models. Check the supported-camera list for your exact model and the connection guide for your computer platform. Camera compatibility does not guarantee identical timing or capture modes across models.

1.5 - Is a bullet-time booth the same as a rotating 360 video booth?

No. A multi-camera bullet-time booth captures different viewpoints using several cameras. A rotating-arm 360 video booth moves a camera around the subject. A multi-camera array can cover an arc or a full circle, depending on its physical layout.

1.6 - Where can I get help with setup?

Start with the setup guides and support resources. Scheduled one-to-one training is available through an extended support plan and must be arranged in advance.

2. Software

2.1 - Do I need an internet connection to run Xangle Camera Server?

Camera Server captures and processes locally, but license validation and cloud services have separate internet requirements:

Starter and Basic: internet is required at launch. There is no offline grace after a failed license check.
Pro and Pulse: the license has up to 24 hours of offline grace between successful validations.
Trials: no offline license grace.

Cloud calibration, cloud Splat training, and cloud delivery need internet while in use. Offline QR sharing serves files over a local network; it does not remove the license-validation requirement. Test the intended capture and sharing setup before the event.

See Offline QR sharing.

2.2 - How does the bullet-time calibration work?

For a bullet-time booth, aim the cameras at a central reference pole, mark its position, then remove it before the subject steps into the capture area. Create a reusable calibration recipe from a suitable capture and use it for subsequent captures while the camera positions and optical setup remain unchanged.

After a camera bump, check aiming and focus. If the camera moved, was re-aimed, or its optical setup changed, calibrate a suitable capture taken after the change and check the result. Sometimes only refocusing is needed.

See the calibration and stabilization guide. A scan rig's reconstruction requirements are different from stabilized bullet-time playback; use the calibration process appropriate to the intended output.

2.3 - Do I need to purchase a Xangle Calibration Bar to make this work?

No. The current calibration process does not require a Xangle Calibration Bar or a physical calibration panel. Use a central reference pole to aim the cameras and mark the subject position, remove the pole, then create a calibration recipe from a suitable capture.

Older releases used marker bars or panels, including arrangements with two matching markers and backlit options for full-circle rigs. Follow the instructions for your installed version rather than assuming that an older calibration accessory is required. See the current calibration guide.

2.4 - How often do you release new versions?

So far we’ve been launching at least one version every two months. We are very active at adding features and improving performances

2.5 - Can I use a second monitor with the “basic” version to use as a replay or sharing station?

Yes. Basic and higher can open replay or sharing tiles on a monitor connected to the Camera Server computer, using the dashboard monitor icon.

Browser pages and stations on separate phones, tablets, or computers require Pro or Pulse. A connected second monitor is not a separate browser station. See Devices.

2.6 - Can I remove the Xangle logo from the software?

With Pro or Pulse, use App Branding to replace or hide the header logo and title. This does not grant permission to replace protected branding such as the Windows taskbar title or footer credits. Use the provided controls and follow the terms of your license; modifying protected branding outside those controls is not an approved customization.

3. License & payments

3.1 - How can I upgrade my license?

Contact Xangle before purchasing a replacement so the tier, camera count, seats, and billing change can be reviewed together.

Monthly to yearly: if you are within the first 10 days, ask whether the monthly payment can be credited.
Yearly: ask how the unused time will be credited toward the new license.
Contract: contact Xangle to arrange an upgrade during the commitment.

Confirm the credit and effective date before paying. Do not assume a new checkout automatically applies an upgrade credit or downgrades an existing license. Contact Xangle about options for a lower tier or camera count.

3.2 - Can I use the software on two different computers?

Yes, if the license includes at least two seats. Each seat is for one running Camera Server computer. With one seat, log out on the first computer before signing in on another.

If the first computer crashes, its seat remains reserved until the session expires, normally 24 hours after its last successful issue or renewal. Check Seats at xangleapps.com for the displayed lock time, or contact Xangle if you need a manual reset.

3.3 - Can I split my 24-camera license into two 12-camera setups?

A single seat cannot run two independent Camera Servers, even if each rig uses fewer than 24 cameras. A license with additional seats can run additional server computers; the camera limit and seat count are separate license values, not a pool to divide yourself.

Raspberry Pi or Windows camera nodes distribute cameras connected to one server. They do not create another independent licensed rig. Confirm the required camera count and seats with Xangle before purchasing.

3.4 - Can I have a trial license before purchasing the software?

Yes. Request a trial on xangleapps.com and verify your email address. New Camera Server trials include up to six local cameras for seven days.

3.5 - What are the limitations of the “trial” license?

Trials are for evaluation, not production events. They include up to six local cameras for seven days, with no daily trigger limit.

Local calibration, local Splat training, network nodes, browser stations, app branding, Timeline scripts and Event scripts, backup, custom naming, and serving render-farm jobs are unavailable. Use Xangle Cloud for calibration and Splat training with the trial's Cloud Credits. Cloud jobs still require internet, enough credits, and inputs within the selected service's limits.

3.6 - Can I use the software after my license has expired?

No. An active license is required to use Camera Server. Renew before the event; offline grace is not an extension of the purchased license term.

3.7 - Single vs Contract license?

A prepaid license, previously called a Single license, covers 31 or 365 days and does not auto-renew. The available purchase terms depend on the tier.

A contract has a 12-month commitment with monthly billing. It is not a cancel-anytime monthly plan. Review the purchase terms for cancellation restrictions and contact Xangle about changes during the commitment.

3.8 - How can I renew my license?

Sign in to xangleapps.com with the email address that owns the license. For an eligible prepaid license, open its Cloud Credits page and choose Renew this license. Renewal extends the existing license from its expiry if it is still active, or from the renewal date if it has expired.

You can also purchase a separate license under the same account, but that is not the same as extending the existing one. Contact Xangle if the renewal action is unavailable or you need a different tier or camera count.

Prepaid licenses do not auto-renew. Long-term licenses are eligible for a reminder two weeks before expiry; that reminder is not promised for every purchase term. Check the expiry yourself before an event.

4. Physical configuration

4.1 - What is the best distance between cameras and/or the subject?

There is no single distance for every rig. Camera-to-subject distance determines framing with the chosen lens. Spacing between cameras determines how much the viewpoint changes from one image to the next.

For a bullet-time booth, closer viewpoints make smaller jumps between frames. Spreading the same number of cameras across a wider arc makes larger viewpoint changes and needs a full playback test. Do not move the cameras closer to the subject just to increase the depth effect without checking framing and crop.

Aim the cameras at the intended subject position and check the final result there. For a photogrammetry rig, check overlapping coverage around the subject instead of treating booth spacing as a scan-rig prescription. See Bullet-time booth and 3D scan.

4.2 - What lens or focal length should I use?

Choose a lens that frames the subject at the available distance, with room for the stabilization crop if you need a bullet-time video.

Examples from booth setups include an 18-55 mm kit zoom, a compact 24 mm pancake, and a 10-18 mm wide-angle for tighter spaces. These are examples, not a recommendation for every camera or rig. Check lens compatibility and sensor size: the same focal length does not give the same framing on every camera.

Test focus, framing, and the final crop across all views before choosing a focal length for the whole rig.

4.3 - Is it better to use a straight or a curved bar?

Both layouts can be calibrated, but calibration does not make their physical camera positions equivalent. It uses the captured views to calculate adjustments.

A straight bar can be easier to pack and ship. A curved bar may better suit the appearance of the booth. Choose based on the available space, camera positions, and tested result, not the assumption that calibration makes the shapes interchangeable.

For a six-camera booth, compare the framing and playback from the intended positions before deciding that the bar shape makes no difference.

5. Camera

5.1 - What camera models are compatible?

Check Supported cameras for models, platforms, connection types, and feature limitations. A camera that takes photos may not offer video, live view, or camera-storage access through the same adapter.

Test the exact body, firmware, cable, and capture mode before relying on it at an event.

5.2 - Can I mix camera models?

Mixing camera models is not explicitly blocked, except that PiCam cannot be mixed with USB or Wi-Fi cameras. It is rarely a good choice for a synchronized rig: different models can have different settings, trigger latency, color and brightness.

Test timing with the complete camera array, and expect that color or brightness differences may need correction in post-production. Check the supported models and camera guides before planning a mixed setup.

5.3 - Do I need SD cards in my cameras?

It depends on the camera, capture mode, and storage destination.

Canon photos saved only to the computer: a card is generally not needed.
Canon photos saved to the camera, or to both camera and computer: a writable card is needed.
Canon video: a card is required for recording before transfer.
Other cameras: check their camera-specific guide; do not assume that Canon's computer-only capture behavior applies to them.

If you intentionally capture to camera storage, use Storage to inspect and download the files. See Images not transferring if an expected transfer does not arrive.

6. Raspberry Pi

6.1 - Do I need Raspberry Pis to use Xangle Camera Server?

Not always. A Windows computer can connect multiple cameras directly over USB, subject to its controllers, hubs, power, and rig size.

For the Canon direct-USB path documented in this guide, a Mac supports one camera. Use Raspberry Pi camera nodes on the same network for additional Canon cameras. Pis can also distribute camera connections and transfer work for larger rigs.

Check Supported cameras for platform and adapter limits.

6.2 - Can I mix Raspberry Pi’s and Windows client?

Yes. They can feed cameras to the same server, but differences between hosts, adapters, and cameras can affect timing and transfer speed. Test the mixed rig's captured images rather than assuming that a shared trigger command means identical exposure timing.

See Measure trigger synchronization.

6.3 - Can I mix PiCam and other cameras on the same Raspberry Pi?

6.4 - What’s the difference between the USB-HUB and the Raspberry Pi architecture?

USB hub is simpler and requires less gear. Raspberry Pis scale better, each Pi pulls its cameras in parallel over Ethernet. See the benchmark page.

Compare measured results on the benchmark page.

6.5 - What Raspberry Pi models works?

The documented models include Pi 3B+, Pi 4B, and Pi 5, with different roles and limits:

Pi 3B+: use a standalone microSD image. Its Ethernet runs over USB 2.0, with a specified maximum throughput of 300 Mbps.
Pi 4B and Pi 5: can run standalone or as cardless clients.
Boot server: use a Pi 4 or 5 with at least 4 GB of RAM.

Choose the image and XNN package for the board's architecture. See Raspberry Pi & network.

6.6 - Can I use a mini PC instead of a Raspberry Pi?

Yes, if it runs a supported camera-node package and the required adapters. For a Windows node, plan for installation, firewall configuration, power, and updates.

Pi deployment uses the XangleOS image and XNN packages. A standalone Pi needs its own microSD card; a cardless Pi needs a compatible boot server and a correctly prepared boot network. A Pi is not cardless without that infrastructure.

For a larger installation, compare the work needed to maintain each Windows node with the Pi image and package-management approach. USB bandwidth, power and transfer speed still need testing. Four cameras per Pi is a useful existing rig-layout example, not a hard limit or a guaranteed optimum.

7. Computer

7.1 - What kind of computer is required?

Camera Server runs on Windows and macOS. Choose a fast local SSD and enough CPU, memory, and network capacity for the rig, then test a complete capture and output cycle.

Camera-adapter and local-processing availability differ by platform. For the documented direct-USB Canon path, Mac supports one camera; use Pi camera nodes for additional Canon cameras. Check Supported cameras and each local engine's requirements before choosing the computer.

Check the benchmarks and the 176-camera hardware example for production context, rather than treating one computer specification as a guarantee for every rig.

7.2 - Do I need a fast graphic card?

It depends on what runs locally. Xangle Cloud performs calibration and Splat training remotely, so the computer does not need the cloud processor's GPU.

Local requirements differ by engine. Postshot Splat training requires a compatible NVIDIA GPU and a Postshot Studio license. Check Calibration engines and Splat training for the available processors and their setup requirements.

7.3 - Can I run Xangle Camera Server on a Mac computer?

Yes. Camera Server is available natively for macOS as well as Windows; Parallels is not required to run the Mac version.

Camera-adapter and local-processing support differ by platform. For the documented direct-USB Canon path, Mac supports one camera; use Raspberry Pi camera nodes for additional Canon cameras. Check the platform compatibility and supported-camera list and each processing engine's requirements before choosing your setup.

8. Other gear items

8.1 - Which wireless triggers models can be used?

Use a presenter that sends a keyboard key Camera Server can map, or a gamepad recognized by the computer and app. Not every Bluetooth device sends a usable input.

Open Button Mapping to assign the input, then test it in the app. The default keyboard trigger is B, held for warmup and released to capture; the gamepad B button mirrors it by default. See Trigger shortcuts.

See the required gear guide for equipment planning.