Camera Problems: Symptom, Cause, Solution

Published · Updated
HOW TOEvent Settings → Camera

Symptom-cause-solution guide for camera not connecting to the photo booth kiosk, no preview, error during shooting and DSLR/GoPro/virtual camera (OBS) specific problems. All error texts are taken from the real Turkish source file of the application (SettingsResource.tr.resx).


Additional supported Canon cameras

AI Photo Booth Pro also supports the following Canon models.

ModelCanon EDSDK
Canon PowerShot V1013.17.10
Canon EOS R5 Mark II13.18.30
Canon EOS R113.18.40
Canon EOS R50 V (EOS R50V)13.19.0
Canon EOS R6 Mark III13.20.10
Canon EOS R6 V (EOS R6V)13.20.20

EDSDK versions below identify the Canon SDK reference, not the AI Photo Booth Pro app version. Use the current app and camera firmware; available controls depend on the model and platform. Support does not mean every device has been physically tested by our team.

EOS R6 V: Canon added EDSDK/CCAPI support in firmware 1.1.0. Use firmware 1.1.0 or later. Canon

i
Version note

On Windows, the Canon SDK needed to support these models was added to the app in version 3.6.1. In older versions these cameras may fail to connect even if they appear in the camera list, update your app.

Full camera compatibility list

Cameras seen in use in the field

The following models were connected in our customers' booths and used in the app in the last 30 days (September 2026). A model missing from this list is not necessarily unsupported; if you use a Canon or Nikon that is not listed, do a test shot before the event.

ModelPlatform seen on
Canon EOS 5D Mark IVWindows, iPad / iPhone
Canon EOS 5DSWindows
Canon EOS 7D Mark IIWindows, Mac
Canon EOS 60DWindows
Canon EOS 70DWindows
Canon EOS 77DWindows
Canon EOS 80DWindows
Canon EOS 200DWindows
Canon EOS 250D (Rebel SL3)Windows
Canon EOS 500DWindows
Canon EOS 550DWindows
Canon EOS 600DWindows
Canon EOS 650DWindows, iPad / iPhone
Canon EOS 700DWindows
Canon EOS 750DWindows
Canon EOS 800D (Rebel T7i)Windows, iPad / iPhone
Canon EOS 850DWindows
Canon EOS 1100DWindows
Canon EOS 1200DWindows
Canon EOS 1300D (Rebel T6)Windows, Mac
Canon EOS 2000DWindows, iPad / iPhone
Canon EOS 4000DWindows
Canon EOS M6 Mark IIWindows
Canon EOS M50Windows
Canon EOS M50 Mark IIWindows, iPad / iPhone
Canon EOS R6iPad / iPhone
Canon EOS R6 Mark IIWindows
Canon EOS R6 Mark IIIWindows
Canon EOS R8Windows
Canon EOS R10Windows, iPad / iPhone
Canon EOS R50Windows
Canon EOS R100Windows, iPad / iPhone
Canon EOS RPWindows
Nikon D3400Windows
Nikon D3500Windows
Nikon D5100Windows
Nikon D5200Windows
Nikon D5300Windows
Nikon D5600Windows
Nikon D7000Windows
Nikon Z 6IIWindows
Nikon Z 50Windows

Sony cameras may appear in the camera list, but they currently do not work over USB.

i
Before you start
  1. Troubleshooting is mostly done in Settings → Event Settings → Camera tab (live preview + Select Camera window is here)
  2. The camera you want to use must be physically connected: USB for webcam/DSLR, Bluetooth for GoPro (Windows only), source application must be open and streaming for virtual camera (OBS)
  3. GoPro and Virtual Cameras appear only on Windows (on Mac, in 3.5.4 and later the OBS virtual camera is listed in the USB Cameras group); 'Camera permission' issues can occur on Android, iPad/iPhone and Mac, and in 3.4.2 and later also in the installed Windows app; a DSLR (Canon/Nikon) connects via USB on Windows, Mac, iPad/iPhone and Android (the supported models vary by platform). Sony cameras may appear in the list but do not work over USB; Fujifilm (Fuji) and Kodak are not supported
  4. First update your app to the latest version: many of the problems below were fixed in versions 3.4.2-3.6.1 (the version with the fix is noted under each symptom)

Step by step

Symptom: Camera shows 'Offline', no preview and 'Searching for camera...' returns

Settings → Event Settings → 'Camera' (connected camera card)

Cause: Selected camera physically disconnected (USB plug removed, GoPro turned off/gone away, DSLR went to sleep). The app enforces a 'sticky camera' policy, it doesn't AUTOMATIC jump to another camera, it sticks to the operator's chosen device and runs a reconnect watcher in the background. The monitor tries to turn on the same device again at increasing intervals (500ms → 1s → 2s → 4s → 8s, up to 10s); If it's a GoPro target, it also performs a Bluetooth scan every round. Solution: (1) Check the USB cable and port, unplug and plug back in if necessary. (2) If it is a GoPro, turn on the camera and move it closer to the kiosk. (3) The preview continues automatically when the device comes back, no manual action required. (4) If you want to leave this camera and switch to another camera, select another camera from the Select Camera window (this will cancel the pending tracker).

🔎 Items on the screen: Orange dot + Offline on the connected camera card; spinner + Searching for camera...

The connected camera card is offline: text Offline with orange dot and spinning spinner + Searching for camera... .
The connected camera card is offline: text Offline with orange dot and spinning spinner + Searching for camera....

Symptom: 'Another app is using the camera. Close to continue.'

Settings → Event Settings → 'Camera' (toast/warning)

Cause: Another application (Zoom, Microsoft Teams, Windows Camera app, Skype, etc.) is keeping the webcam in 'exclusive' mode; Windows gives the camera to only one application (MediaFrameReader status is ExclusiveControlNotAvailable). This error really means 'using another app'. Solution: (1) Completely close the other application using the camera (it may be running in the background, check the taskbar/system tray). (2) Open the Select Camera window and press Refresh or select the camera again. Note: If the webcam gives this error during an active shooting (session), the application keeps the booth alive by moving it to the next camera in the added list, or if it is not available, to the Desktop Arrangement.

🔎 Items on the screen: Warning message 'Another app is using the camera. Close it to continue.'

Symptom: 'Camera unavailable. Make sure it is connected and not removed.'

Settings → Event Settings → 'Camera' (toast/warning)

Cause: The device is inaccessible, physically broken/removed or there is a driver/port problem (MediaFrameReader status is DeviceNotAvailable or UnknownFailure). This is NOT 'using another app'; A different message is deliberately shown. Solution: (1) Check the USB cable and port; try another USB port (back/motherboard port if possible). (2) Unplug it and plug it in again after a few seconds. (3) Connect directly instead of USB hub. (4) Refresh the list with Select Camera → Refresh. If the problem persists, try changing the cable/camera.

🔎 Items on the screen: Message 'Camera unavailable. Make sure it is connected and not removed.'

Symptom: 'Camera could not start: the device ran out of hardware resources.' (Windows, webcam)

Settings → Event Settings → 'Camera' (toast/warning)

Cause: On Windows, the hardware resources the computer reserves for the camera ran out while the webcam was being opened. This is NOT 'another app is using it', in older versions the same situation was wrongly shown as 'Another app is using the camera', and operators tried to close an app that was not running at all. Solution: (1) Unplug the camera from USB and plug it back in. (2) Select the camera again with Select Camera → Refresh and try again.

🔎 Items on the screen: Message Camera could not start, the device ran out of hardware resources. Unplug and reconnect the camera, then try again.

Symptom: On Windows, photos taken with a webcam come out yellow/orange or pixelated, and the shot is delayed

Shooting screen / Camera tab (Windows, webcam)

Cause: In versions before 3.6.0, on webcams without a separate photo pipeline the photo was taken from the first frame after restarting the camera stream. Because it was taken before white balance and exposure had settled, colors could come out yellow/orange, on some cameras the image stayed at low resolution (pixelated), and the shot was delayed by about 2-3 seconds. The live preview, however, looked normal. Solution: update your app to 3.6.0 or later, from this version on, the photo is taken from the live preview frame, the colors match the preview and the shot happens instantly.

i
Version note

This problem was fixed in 3.6.0; update your app.

Symptom: Virtual camera (OBS/ManyCam/XSplit) is selected but no image appears: 'Virtual camera is installed but not broadcasting.'

Settings → Event Settings → 'Camera' (Virtual Cameras)

Cause: The virtual camera driver appears in the 'Virtual Cameras' list because it is registered in Windows, but the source application is NOT streaming (e.g. 'Start Virtual Camera' is off in OBS). The application cannot open the device (OpenCV/DirectShow does not produce a stream) and reports this specific situation with a separate message. Solution: (1) Open the source application (OBS/ManyCam/XSplit). (2) In OBS, press the 'Start Virtual Camera' button at the bottom right; Enable virtual camera output in ManyCam/XSplit. (3) Make sure the scene/source is selected and there is an image in the preview. (4) In the app, select Select Camera → virtual camera again. Note: The virtual camera still appears in the Windows list even when the source application is closed, so check 'is it streaming' rather than 'is it connected'.

🔎 Items on the screen: Group Virtual Cameras (detail Virtual camera (OBS, etc.)); message 'Virtual camera is installed but not broadcasting. Open the source application (e.g. OBS) and start the virtual camera ("Start Virtual Camera"), then try again.'

Symptom: Camera does not open: Camera Permission window or 'Camera permission denied: the camera will not work…' warning

Settings → Event Settings → 'Camera' (Camera Permission window)

Cause: Camera permission has not been granted to the app, or it was denied. In 3.4.2 and later, permission is also checked on Windows (in the installed app); on Windows a webcam needs both Camera and Microphone permission turned on (DSLR and GoPro are not affected by this permission). Without permission the camera does not open: the Camera Permission window appears when you open the Camera tab, when you select a webcam and when a shot starts; if permission is permanently blocked, the window has an Open Settings button. If permission is blocked in the booth, the countdown does not start at all; the session closes and returns to the start screen. If the default camera cannot open because of permission during first setup, the app switches to Desktop Editing so that the booth keeps running. Solution: (1) Press the Open Settings button in the window, the app's own permission page opens (on Windows: Settings → Apps → Installed apps → the app → Advanced options; on Mac: System Settings → Privacy & Security → Camera; on Android and iPad/iPhone: the app's settings page). On Windows, the general switch on the 'Privacy & security → Camera' page may not be enough; turn on the permissions on the app's own Advanced options page. (2) Turn on Camera and Microphone permission. (3) Select your camera again under Settings → Event Settings → Camera tab; if necessary, close and restart the app.

i
Version note

The Camera Permission window and Open Settings arrived with 3.4.2; the permission check on Windows also started with this version. In older versions there was no way back from inside the app once permission was denied, and on Windows the camera might not open while showing a wrong message such as a cable error, even though the real problem was the permission, update your app.

🔎 Items on the screen: Camera Permission window; message Camera access was not allowed, so the camera will not work. Please allow camera access to take photos. (denied, closes with OK) or Camera access is blocked for this app, so the camera will not work. Open Settings and turn on Camera and Microphone access for this app, the camera does not start unless both are allowed. (permanently blocked) + Open Settings; warning when the camera opens Camera permission denied, the camera will not work. Allow camera access for this app, then pick your camera again under Settings → Camera. (in versions older than 3.4.2: 'Camera permission denied. Switched to Desktop Editing mode.')

Symptom: Camera does not appear at all in the 'Select Camera' window / newly attached device does not appear in the list

Settings → Event Settings → 'Camera' (Add Camera window)

Cause: The device is not yet enumerated (USB just inserted, driver is being installed), the source application of the virtual camera is closed, or the list comes from a short-term cache. Solution: (1) Press the Refresh button at the bottom of the Select Camera window, the cameras will be scanned again. (2) If it is not visible, unplug the device and plug it in again, then Refresh again. (3) For the virtual camera, first start broadcasting in the source application (OBS Start Virtual Camera). (4) For DSLR, keep the camera on and in 'PC connection/PTP' mode; Scan for Bluetooth with Connect a New GoPro for GoPro. The official tip in the app is the same: 'If it doesn't appear, try unplugging it and plugging it in again.'

🔎 Elements on the screen: Add Camera window; Refresh and Cancel buttons on the bottom bar; group headers Built-in Cameras / USB Cameras / Virtual Cameras / Desktop Editing / GoPro

Add Camera window is open; The camera group list appears with the Refresh button highlighted at the bottom.
Add Camera window is open; The camera group list appears with the Refresh button highlighted at the bottom.

Symptom: A Sony camera appears in the list but there is no live image / a Fujifilm or Kodak camera does not appear at all

Settings → Event Settings → 'Camera' (Add Camera window)

Cause: The app can recognize the brand of Sony cameras connected over USB and show them in the list, but Sony cameras currently do not work over USB: no live image comes in, the test shot shows the Camera not ready warning and no photo is taken. Fujifilm (Fuji) and Kodak cameras are not supported. Solution: Use a supported Canon or Nikon DSLR or a webcam (for connecting Canon/Nikon, see the DSLR connection guide).

Symptom: Pressing 'Take Test Photo' but no shot is taken: 'Camera not ready' warning or 'No Camera Selected' on the card

Settings → Event Settings → 'Camera' (Camera Settings)

Cause: There is no active (selected + open) camera, no camera has been added yet, or the selected camera is offline. A test shot works only while there is an active camera; if there is no active camera, the button silently does nothing. Solution: (1) In the Add Camera section, press Select Camera. (2) CLICK a camera in the list, the click both adds that camera and makes it active (a camera that only has the Added badge is not active and does not appear in the preview). (3) Take a Test Shot works once the camera name appears on the connected camera card and the Ready badge appears in the preview. If a camera is selected but the live image is not coming in yet (the camera is starting, the connection dropped), the button does not start the shot and shows the Camera not ready warning, try again once the image appears in the preview.

🔎 Items on the screen: No Camera Selected on the card in the empty state; Take a Test Shot button; in the ready state, the Ready badge with a green dot in the preview; while there is no live image, the warning Camera not ready

Symptom: Camera disconnected during recording (session): 'Camera disconnected. Check USB cable and camera.' fashionable

Shooting/Session screen (booth)

Cause: Camera physically disconnected in the middle of active shooting (cable pulled, DSLR shut down, GoPro WiFi dropped). To prevent the underlying uncancellable native call from blocking forever, the application runs a break-protection: when the break signal arrives (or a hard time limit of 70 seconds at the latest), it stops shooting, shows the break modal to the user, and clears the session. Solution: (1) Check the USB cable and camera, reconnect if necessary. (2) Check battery/card status on DSLR. (3) Keep the GoPro on and close. (4) Press confirm in the modal (session cleared) and restart shooting after camera comes back.

🔎 Items on the screen: Error title Camera Error; message 'Camera connection lost. Check the USB cable and camera.' (on a built-in camera, tablet/laptop, 'The camera connection was lost. Please try again.'); generic shooting error text 'An error occurred while shooting. Please try again or choose a different camera.'

Symptom: On the shooting screen the live image freezes, turns blurry with a spinning icon on top, or the app restarted by itself

Shooting screen (booth)

Cause: No new frames are coming from the camera, usually the USB cable was pulled out/came loose or the camera is not responding. In 3.6.1 and later the app detects this: if the live image stops unexpectedly, the image turns blurry and a spinning icon appears on top; when the connection recovers, the image comes back by itself. On Windows, if a connection drop leaves a Canon DSLR permanently locked (no response at all for about 20 seconds), the app restarts itself automatically and goes straight back to the booth; if the camera is still not ready at that point, Settings opens directly on the Camera tab. To avoid an endless loop, this automatic restart happens at most once every 3 minutes. Solution: (1) Check the USB cable and the camera, and plug the cable in firmly. (2) If the image does not come back within a few seconds, turn the camera off and on. (3) If the app restarted, check that the camera is on and connected; if Settings opened on the Camera tab, select the camera again and start the booth.

i
Version note

The freeze indicator and the automatic restart arrived with 3.6.1. In older versions, pulling the USB cable during a shoot could lock up the app without any warning on screen, update your app.

Symptom: DSLR capture fails: 'The camera couldn't start recording…' (in older versions 'Camera busy or preparing.') or 'The photo could not be received in time.'

Shooting screen / Camera tab (DSLR)

Cause: The DSLR body rejected the shooting or recording request (Canon/Nikon 'busy' codes, e.g. 81 / 8D03 / 2019) or the photo could not be transferred in time (slow SD card, full buffer, high resolution/RAW). In 3.6.1 the 'busy' message was rewritten: The camera couldn't start recording. Check the camera's screen for the reason. Common causes: the memory card is too slow for the selected video quality, the card is missing or faulty, or the camera needs to be turned off and on. The old text ('Camera busy or preparing. Wait a few seconds and try again.') suggested waiting; however, in the measured cases this error did not go away by waiting, and the cause was usually the memory card. The error code also appears at the end of the message (e.g. '(kod: 81)'). Solution: (1) Look at the camera's own screen, the body usually shows the reason there. (2) Check the memory card: is it inserted, is it faulty, is it fast enough for video; if necessary, replace it with a fast, reliable card. (3) Turn the camera off and on. (4) If a process such as mirror lock/sensor cleaning/long exposure is running on the body, wait for it to finish. (5) For 'The photo could not be received in time': if the transfer is slow, lower the resolution (Small) or choose JPEG instead of RAW (see the high resolution warning below).

🔎 Items on the screen: The camera couldn't start recording. Check the camera's screen for the reason. Common causes: the memory card is too slow for the selected video quality, the card is missing or faulty, or the camera needs to be turned off and on. (3.6.1; in older versions 'Camera busy or preparing. Wait a few seconds and try again.'); 'The photo could not be received in time. Please try again. If the problem persists, check the camera connection.'

Symptom: 'No lens is attached to the camera…', 'The camera's flash is still charging…' or 'The camera won't shoot in its current state. Set the mode dial…' (Canon)

Shooting screen / Camera tab (DSLR)

Cause: The Canon body rejected the shot and reported why: no lens is attached or it is not seated properly; the flash has not finished charging; or the body won't shoot in its current state (mode dial in a scene/auto position, no memory card inserted, etc.; since 3.9.0 a rejection in the video position comes with a separate message, see the symptom below). New 'shot rejected' codes that the camera reports but the app does not recognize are also shown with this last message. Solution: (1) Lens: remove the lens, attach it again and make sure it is fully seated. (2) Flash: wait a few seconds and try again. (3) Shot rejected: set the mode dial to M, Av or Tv (not scene/auto or movie) and check that a memory card is inserted. If you pass the code at the end of the message (e.g. '(kod: 8D0E)') to the support team, the exact cause can be identified.

i
Version note

These three messages were added in 3.4.2. In older versions these situations could show a generic error that did not state the cause ('There was a problem connecting to the camera. Check the USB cable and the camera, then try again.') and wrongly pointed to the cable, update your app.

🔎 Items on the screen: No lens is attached to the camera, or it isn't seated properly. Attach the lens and try again.; The camera's flash is still charging. Wait a few seconds and try again.; The camera won't shoot in its current state. Set the mode dial to M, Av or Tv (not a scene/auto or movie position), make sure a memory card is inserted, then try again.

i
If your external flash does not fire

In 3.7.0 and later no separate setting is needed: on a Canon DSLR with a mirror, the photo is always taken outside live view and the external flash fires on its own (the preview pauses briefly at each shot). The External flash trigger switch existed only in versions 3.6.2-3.6.4; if the flash still does not fire, update the app.

Symptom: On a Canon R series camera (e.g. EOS R10, R50) the live image never opens

Settings → Event Settings → 'Camera' / Welcome and shooting screen

Cause: In versions before 3.5.4, some Canon R series bodies rejected a focus setting that the app sent when starting the live image; even if the live image opened on the camera's screen, no frames reached the app. Also, once starting the live image had failed, it was not retried, so the preview stayed permanently empty. Solution: update your app to 3.5.4 or later, from this version on, the app no longer forces this setting and retries several times if starting fails. If the problem persists on the current version, turn the camera off and on and check the USB cable.

i
Version note

This problem was fixed in 3.5.4; update your app.

Symptom: Photos taken with a Canon DSLR with a mirror come out blurry (e.g. EOS 2000D, 4000D, 1300D, 1200D)

Shooting screen (DSLR)

Cause: In versions 3.5.4 and 3.6.0, on Canon the app itself ran focusing during live view and cut it off after at most about 1.5 seconds to press the shutter. Mirrorless (R/M series) bodies lock focus within this time, but on DSLRs with a mirror, focusing in live view takes longer, so it was cut off halfway and photos came out blurry. Solution: update your app to 3.6.1, in this version, bodies with a mirror shoot with the camera's own focusing again. If the blur persists on the current version, check the lighting, subject distance and focus setting (see the 'Camera failed to focus' symptom below).

i
Version note

This problem was fixed in 3.6.1 (it existed in 3.5.4 and 3.6.0); update your app.

Symptom: DSLR cannot focus / blank frame: 'Camera failed to focus.' or 'The camera failed to take a photo. Remove the lens cap...'

Shooting screen / Camera tab (DSLR)

Cause: Autofocus failed to lock (low light, no contrast/flat surface, subject too close) or the body accepted the shot but did not produce a new image (lens cap attached, lens obstructed, did not hold focus). Solution: (1) Back off a bit and try again; If the environment is dark, increase the light. (2) Remove the lens cover and any obstacles in front of it. (3) If the problem persists, move the lens to MF (manual focus). (4) Adjust the focus distance (move away if the subject is too close).

i
Version note

In versions before 3.5.4 (e.g. 3.5.1), when focus failed on a Canon the camera could lock up and give a 'busy' error on every following shot, and the live image did not come back until the camera was turned off and on. In 3.5.4 the app tries to recover from this state by itself and, if focus fails, tries once to take the photo without focus, update your app.

🔎 Items on the screen: 'The camera could not focus. Please step back a bit and try again; If the environment is dark, increase the light. If the problem persists, move the lens to MF (manual focus).'; 'The camera could not take a photo. Remove the lens cap, remove anything obstructing the lens and make sure it can focus, then try again.'; 'The lens cover is closed. Open the door and try again.'

Symptom: DSLR memory card error: card missing / full / write protected

Shooting screen / Camera tab (DSLR)

Cause: There is no memory card in the DSLR body, the card is full or the card is write protected/faulty (Canon/Nikon code mapping: NoCard/StoreNotAvailable, StoreFull, CardProtect/DiskError). Most DSLRs also reject the shutter release without a card. Solution: (1) 'No card' → insert a working SD/CF card into the body. (2) Fill → free up space on the card or replace it with a blank card. (3) 'Write protected' → turn the physical lock switch on the side of the card to the on position; If it is faulty, replace the card. (4) You may need to turn the camera off and on after the card. For video recording (Canon) a card is required: the video is recorded to the camera's card; without a card, recording does not start and the warning There is no memory card in the camera. Insert a card and try again. appears (3.6.0 and later, older versions waited about 40 seconds while processing the video and then showed a generic camera error). On bodies with two card slots (e.g. EOS R6 Mark III), versions before 3.6.1 could report 'no card' when the card was in the second slot, update.

🔎 Items on the screen: There is no memory card in the camera. Insert a card and try again.; 'The camera memory card is full or cannot be written to. Free up space on the card or replace it.'; 'The memory card is write protected or defective. 'Unlock or replace card.'

3.7.0 and later: if the camera refuses to save the photo to the card, capturing does not stop; the warning 'The camera rejected saving to the memory card (missing, full or locked). Photos are now saved to the computer only. To save to the card again, free up space or replace the card and reconnect the camera.' appears only in a yellow card in the Settings → Camera tab; nothing is shown to the guest on the booth screen. Photos keep arriving in the app; there is just no backup on the card.

Symptom: the 'The camera is in an automatic mode…' card or 'The camera's mode dial is in the movie position, and this camera doesn't take photos there…'

Camera tab / capture screen (DSLR, 3.7.0 and later)

Cause: the mode dial is in fully automatic / scene mode (the camera may raise its built-in flash by itself and lock up with Err 05; a red card appears in the Camera tab), or it is in the video position and the body doesn't take photos in that position (e.g. EOS R100; the message appears at the moment of capture, 3.9.0 and later). Most bodies with a mirror also take photos in the video position and show no warning. Solution: turn the mode dial to M, Av, Tv or P; the automatic-mode card disappears by itself. In the same place, a red card can also report that live view was refused (e.g. 'The camera is too hot for live view. Turn it off and let it cool down.'); follow the instruction on the card.

🔎 Items on the screen: 'The camera's mode dial is in the movie position, and this camera doesn't take photos there. Set the mode dial to M, Av, Tv or P, then try again.'; 'The camera is in an automatic mode ({0}). In automatic modes the camera may raise its built-in flash by itself and lock up (Err 05). Set the mode dial to M, Av, Tv or P.'

Symptom: in Video mode, 'This camera can't record video from the app…' at the start of the session

Booth capture screen (3.9.0 and later)

Cause: the connected camera cannot record video from the app (some DSLR bodies). Solution: use photo modes with this camera, or connect a camera that supports video recording.

🔎 Items on the screen: 'This camera can't record video from the app. Choose Photo mode, or connect a camera that supports video recording.'

Symptom: DSLR battery low / shot rejected: 'Camera battery too low.'

Shooting screen / Camera tab (DSLR, Advanced Settings)

Cause: DSLR battery level is critical; 'Camera battery too low' error appears while shooting. In the Advanced Settings heading in the Camera tab, the battery percentage badge blinks red and warns when low. Solution: (1) Charge the battery or replace it with a charged battery. (2) Connect the camera to the power adapter (AC adapter / dummy battery) if possible, recommended for long events. (3) After replacing the battery, refresh the settings/battery status with Read Status. Note: If the camera is connected to a power adapter and the battery badge shows '19%' with a 'Camera battery low' warning, this is a false warning seen on Canon in older versions (before 3.4.1), it has nothing to do with the battery; update your app. In the current version, the battery badge and warning are not shown for a camera on a power adapter.

🔎 Items on the screen: Error 'Camera battery is too low. Charge it or connect it to the power adapter.'; Battery badge + warning 'Camera battery low (%{0}%), charge or replace before shooting' in Advanced Settings

Symptom: High resolution/RAW warning on DSLR and photos are very slow to arrive

Settings → Event Settings → 'Camera' (Camera Settings DSLR)

Cause: High resolution or RAW format is selected on the DSLR; Large files take a long time to transfer from the camera, creating a countdown/inter-shot wait. A permanent yellow warning card appears at the top of the settings panel. Solution: (1) Lower the Image Quality/resolution from Advanced Settings (Small recommended), then press Apply. (2) Choose JPEG instead of RAW. (3) Don't forget to write the change to the camera with Apply (otherwise it will remain in the draft). The warning card remains visible until low resolution/JPEG is selected.

🔎 Elements on the screen: Yellow warning card: 'High resolution selected. Images may take longer to transfer from the camera due to the large file size. Low resolution (Small) is recommended for faster transfer.'; 'RAW format is selected. ... JPEG format is recommended for faster transfer.'

High resolution/RAW alert card with yellow background above the Adjustments panel in DSLR Camera Settings.
High resolution/RAW alert card with yellow background above the Adjustments panel in DSLR Camera Settings.

Symptom: The dial/ISO/mode on the DSLR body is rotated but the value on the screen is not updated (consumer Nikon)

Settings → Event Settings → 'Camera' (Advanced Settings)

Cause: Some consumer-grade DSLR bodies (e.g., entry-level models such as the Nikon D3500) do not report a dial/mode change on the body as an event to the application (MTP does not issue a DevicePropChanged). So when you rotate the value from the body, the drop-down menus on the screen show the old value. Solution: (1) Press the Read Status button on the Advanced Settings toolbar, the values ​​are refreshed from the camera. (2) Turn on the Auto Read switch for continuous sync, auto-refreshes every few seconds. Note: Since professional bodies (Nikon D5/D850/Z9 etc.) broadcast this event, they generally do not need a manual refresh.

🔎 Elements on the screen: Advanced Settings toolbar: Read Status button; Auto Read key; Reading status... layer in preview while reading

DSLR Advanced Settings toolbar: the Read Status button and the Auto Read switch, together with the ISO/Shutter…
DSLR Advanced Settings toolbar: the Read Status button and the Auto Read switch, together with the ISO/Shutter Speed/Aperture drop-down menus.

Symptom: 'Set Settings with AI' button is inactive or 'Not enough credits for AI analysis'

Settings → Event Settings → 'Camera' (Camera Settings DSLR)

Why: The AI ​​setting recommendation button activates only when (a) a supported DSLR is active and (b) a test photo has just been taken; Additionally, each call costs 2 credits. If the credit is insufficient, the analysis does not start and the credit purchase screen opens. Solution: (1) First take a frame with Take a Test Shot in the preview, the button appears below Retake. (2) If your credit is insufficient, get a loan from the credit paywall. (3) AI recommendations are not automatically applied; It appears as a draft in the menus, review it and write it to the camera with Apply.

🔎 On-screen elements: Set Settings with AI button + '(2 Credits)' label; Analyzing settings… during analysis; warning if credit is insufficient Not enough credits for AI analysis (2 credits needed)

Symptom: GoPro not connecting (Windows only): 'Failed to establish BLE connection.' / 'WiFi connection could not be established.' / 'GoPro is not responding'

Settings → Event Settings → 'Camera' (Add Camera · GoPro)

Why: GoPro connection is two-step, first Bluetooth (BLE) pairing, then connecting to the GoPro's WiFi hotspot. If one of the steps fails (GoPro off/remote, Bluetooth off, hotspot failed, camera unresponsive) the connection cannot be established. The colored status label on the GoPro section and the live log below indicate at what stage it was installed. Solution: (1) Turn on the GoPro and move it closer to the kiosk. (2) Turn on the computer's Bluetooth. (3) Start new scan with 'Connect New GoPro'; If the connection is lost, press 'Reconnect'. (4) Watch the log dump ('Pairing Bluetooth...', 'Connecting to GoPro WiFi...', GoPro not responding etc.), which step it got stuck on is visible here. (5) If it fails constantly, turn GoPro off and on, reset previous WiFi pairing. Note: GoPro is only supported on Windows; On other platforms, the GoPro section is not visible.

🔎 Items on the screen: the GoPro group (detail GoPro · Bluetooth); initial status label Disconnected; the Connect a New GoPro and conditional Reconnect buttons; live log lines; error texts BLE connection failed., WiFi connection failed., GoPro WiFi hotspot could not be opened., GoPro not responding, Connection failed

GoPro section in Add Camera window: colored status label, Connect a New GoPro / Reconnect buttons and live log dump…
GoPro section in Add Camera window: colored status label, Connect a New GoPro / Reconnect buttons and live log dump with dark background at the bottom.

Symptom: Shot with GoPro but photo/video not coming to kiosk: 'Failed to download photo. Footage on GoPro memory card: auto retrying.'

Shooting screen / GoPro (Windows)

Cause: The GoPro shutter worked and the shot was recorded on the GoPro's memory card, but the transfer of the file to the kiosk over WiFi was interrupted (WiFi was weak/cut out, GoPro went away). Solution: (1) The camera automatically tries again, wait briefly (Waiting...). (2) Press Retry Nowto try it now. (3) Keep the GoPro close to the kiosk and turned on; Do not allow walls/metal obstacles in between. (4) If you want to skip that frame, use Skip This Shot. Note: Since the footage is safe on the GoPro card, it is usually transferred automatically once the connection is restored.

🔎 Elements on the screen: Title GoPro Connection Issue; message 'Failed to download photo. Footage on GoPro memory card, auto retrying.' ('Failed to download video...' for video); buttons 'Try Again Now', 'Skip This Shot', 'Reconnect'; 'Waiting...'

i
Tips

Preview and active shooting behave differently: If the camera selected in settings/preview breaks, the application will NOT jump to another camera (sticky) and waits for it to come back with Offline + Searching for camera...; If the webcam/DSLR fails in the middle of an active session, it will be transferred to the next camera in the added list, or if it is not available, it will be transferred to Desktop Arrangement.

Don't confuse two different 'unavailable' messages: 'Another application is using the camera' = another program is holding the webcam (close that program); 'Camera unavailable' = device broken/inaccessible (check cable/port).

Critical distinction in virtual camera (OBS) problems: although the device appears 'connected', no image will appear unless streaming has started in the source app, 'Start Virtual Camera' in OBS first.

If the device is not in the list, the first reflex is: Select Camera → Refresh; then unplug it; then Refresh again.

High resolution/RAW on a DSLR slows down the transfer; for fast streaming, set Image Quality to Small/JPEG and press 'Apply'.

On some DSLR bodies, such as the consumer Nikon, the physical dial change is not immediately reflected on the screen, refresh with Read Status or turn on Auto Read.

GoPro is only supported on Windows; If the connection is stuck, the live log dump in the GoPro section shows which stage (BLE/WiFi) is the problem.

During long events, connecting the DSLR to the power adapter prevents 'Camera battery too low' blackouts.

Note the '(kod: XXXX)' part at the end of the error message (in 3.5.4 and later it is also shown for the test shot in the settings); the support team can see the exact cause from this code.

!
Common mistakes

Trying again without closing the other app holding the webcam (Zoom/Teams/Windows Camera), the 'Another app is using the camera' message will not disappear.

Selecting OBS/virtual camera and forgetting Start Virtual Camera in the source application, 'Virtual camera is installed but not broadcasting' warning appears.

In case of Offline/Searching for camera..., panicking and choosing another camera, due to fixed policy, the preview returns automatically when the cable/GoPro comes back; What really needs to be done is to fix the physical connection.

Leaving the camera at Added and not making it active, camera with badge Added will not appear in preview; Click on the line to activate it.

Changing Image Quality/resolution on DSLR and not pressing 'Apply', change stays in draft, slow transfer issue persists.

Denying camera permission (on mobile, Mac or Windows) and then being surprised that the camera doesn't open, the camera does not open until permission is given; grant it with Open Settings in the Camera Permission window, and on Windows also turn on Microphone permission.

Not checking the physical write-protect lock of the card when receiving a DSLR card error ('card missing/full/protected').

Calling Set Settings with AI without taking a test photo, the button is activated only after a test shot and with 2 credits.

Retrying again and again with the same card on the 'The camera couldn't start recording…' message, the cause is usually the memory card; look at the camera's screen and replace the card if necessary.

Chasing a problem on an old version that has since been fixed, update the app first; many symptoms on this page were fixed between 3.4.2 and 3.6.1.

Setting up with a Sony, Fujifilm (Fuji) or Kodak camera, even though Sony appears in the list, it does not work over USB, and the others are not supported.

Related topics

Event Settings → camera Camera & OBS Setup Session Settings Event Settings → Kiosk

Was this article helpful?

Not sure where to start? We can help.

Tell us about your project. Our team will help with the next step.

By submitting, you agree to our Terms and Privacy Policy.