Mixing camera models

Mixing camera models is not recommended in most cases as we’re looking for consistent results, but there are some situations where there’s an advantage of mixing models to optimize cost or quality. This would be typically a photogrammetry rig with mixed DSLRs and Pi cameras, or a mix of crop/full-frame models in a hybrid full-body/head scan.
Above: Xangle Camera Server with 3 Sony cameras, one Canon and one Android
Above: Xangle Camera Server with 3 Sony cameras, one Canon and one Android

1- Trigger timing

Trigger timing can vary a lot from one manufacturer to another, but even when mixing models that are very similar. In the video below, we’re showing that the SL3 triggers 10ms later than the SL2. Both models are extremely consistent (1ms), but the SL3 always triggers a bit later. This difference becomes way bigger when mixing with Android phones (Android triggers about 300ms later).
Video preview
To help matching the timing, you can add a “delay” per camera group (per camera model). This is adding up to the main delay that you can set in the trigger panel. Click on the camera model to access this setting.
notion image

2- Camera settings

2.1 - changing / syncing settings
Things get a bit more tricky when trying to match camera settings. If you’re mixing T5 and T6 models, you’ll be able to easily sync settings, but if you’re mixing systems (Sony vs Canon shown below), then most settings need to be set manually across all groups. The settings are going to be in sync across all groups as long as the labels are the same (this works if you mix a R5 and a SL3 but not if you mix a SL3 and a a6400). Use the “link” icon to stop synchronizing across settings that are named the same in different groups.
notion image
2.2 - aliases
If you have a mixed rig made of T5 and T6, you might want to see them all in one group. You can do this from Settings / advanced