Fujifilm X-T5 calibration breaks

[lamosadosa]

When trying to calibrate this is the console output. NegPy gives a "calibration failed" message.

[2026-07-28 08:45:35] INFO     negpy.negpy.infrastructure.capture.gphoto: gphoto2 post-shot drain 0 ms (overlapped)
[2026-07-28 08:45:35] INFO     negpy.negpy.infrastructure.capture.gphoto: gphoto2 captured capture.raf (85.0 MB): assert 64 ms, shot 869 ms, download 95 ms (894 MB/s)
[2026-07-28 08:45:39] INFO     negpy.negpy.infrastructure.capture.gphoto: gphoto2 post-shot drain 0 ms (overlapped)
[2026-07-28 08:45:39] INFO     negpy.negpy.infrastructure.capture.gphoto: gphoto2 captured capture.raf (84.8 MB): assert 66 ms, shot 869 ms, download 94 ms (900 MB/s)
[2026-07-28 08:45:43] INFO     negpy.negpy.infrastructure.capture.gphoto: gphoto2 post-shot drain 0 ms (overlapped)
[2026-07-28 08:45:43] INFO     negpy.negpy.infrastructure.capture.gphoto: gphoto2 captured capture.raf (84.6 MB): assert 47 ms, shot 865 ms, download 94 ms (900 MB/s)
[2026-07-28 08:45:47] INFO     negpy.negpy.infrastructure.capture.gphoto: gphoto2 post-shot drain 0 ms (overlapped)
[2026-07-28 08:45:47] INFO     negpy.negpy.infrastructure.capture.gphoto: gphoto2 captured capture.raf (85.2 MB): assert 41 ms, shot 868 ms, download 93 ms (917 MB/s)
[2026-07-28 08:45:50] INFO     negpy.negpy.infrastructure.capture.gphoto: gphoto2 post-shot drain 0 ms (overlapped)
[2026-07-28 08:45:50] INFO     negpy.negpy.infrastructure.capture.gphoto: gphoto2 captured capture.raf (84.9 MB): assert 42 ms, shot 878 ms, download 93 ms (917 MB/s)
[2026-07-28 08:45:54] INFO     negpy.negpy.infrastructure.capture.gphoto: gphoto2 post-shot drain 0 ms (overlapped)
[2026-07-28 08:45:54] INFO     negpy.negpy.infrastructure.capture.gphoto: gphoto2 captured capture.raf (85.7 MB): assert 75 ms, shot 899 ms, download 100 ms (857 MB/s)
[2026-07-28 08:45:58] INFO     negpy.negpy.infrastructure.capture.gphoto: gphoto2 post-shot drain 0 ms (overlapped)
[2026-07-28 08:45:58] INFO     negpy.negpy.infrastructure.capture.gphoto: gphoto2 captured capture.raf (86.9 MB): assert 75 ms, shot 881 ms, download 95 ms (916 MB/s)
[2026-07-28 08:46:02] INFO     negpy.negpy.infrastructure.capture.gphoto: gphoto2 post-shot drain 0 ms (overlapped)
[2026-07-28 08:46:02] INFO     negpy.negpy.infrastructure.capture.gphoto: gphoto2 captured capture.raf (87.3 MB): assert 55 ms, shot 883 ms, download 101 ms (867 MB/s)
[2026-07-28 08:46:06] INFO     negpy.negpy.infrastructure.capture.gphoto: gphoto2 post-shot drain 0 ms (overlapped)
[2026-07-28 08:46:06] INFO     negpy.negpy.infrastructure.capture.gphoto: gphoto2 captured capture.raf (87.7 MB): assert 64 ms, shot 867 ms, download 95 ms (921 MB/s)
[2026-07-28 08:46:09] INFO     negpy.negpy.services.capture.calibration: calibration response: kR=4876.0 kG=5068.1 kB=6323.8 (spread 0.38 stops)
[2026-07-28 08:46:10] INFO     negpy.negpy.infrastructure.capture.gphoto: gphoto2 post-shot drain 0 ms (overlapped)
[2026-07-28 08:46:10] INFO     negpy.negpy.infrastructure.capture.gphoto: gphoto2 captured capture.raf (84.7 MB): assert 41 ms, shot 867 ms, download 96 ms (878 MB/s)
[2026-07-28 08:46:13] INFO     negpy.negpy.services.capture.calibration: calibrated R → level 244, shutter 1/20 (target 58982, got 58065, clip 0.000%, target)
[2026-07-28 08:46:14] INFO     negpy.negpy.infrastructure.capture.gphoto: gphoto2 post-shot drain 0 ms (overlapped)
[2026-07-28 08:46:14] INFO     negpy.negpy.infrastructure.capture.gphoto: gphoto2 captured capture.raf (85.4 MB): assert 2 ms, shot 861 ms, download 96 ms (885 MB/s)
[2026-07-28 08:46:17] WARNING  negpy.negpy.infrastructure.capture.gphoto: gphoto2 exit: [-1] Unspecified error
[2026-07-28 08:46:17] ERROR    negpy.negpy.desktop.workers.capture_worker: calibration failed
Traceback (most recent call last):
  File "negpy/infrastructure/capture/gphoto.py", line 654, in capture
gphoto2.GPhoto2Error: [-1] Unspecified error

Tried different ports, different cables, ensuring tethering is via "also save on sd card", high performance energy mode on camera on, running as user or as superuser.

Running Fedora.

gphoto2         2.5.28         gcc, popt(m), exif, no cdk, no aa, jpeg, readline
libgphoto2      2.5.33         standard camlibs, gcc, no ltdl, EXIF
libgphoto2_port 0.12.2         iolibs: disk ptpip serial usb1 usbdiskdirect usbscsi, gcc, no ltdl, EXIF, USB, serial lockdev locking

[lamosadosa]

This was probably due to wrong power saving settings on the Fuji

I still have the issue that the camera and its live view as well as the scanning function disappears aber one successful frame - now I have to disconnect and reconnect after each frame

[lamosadosa]

Well the power thing was just a coincidence. Next try on calibration it failed again. Happens on latest NegPy44 version on macos and Linux

[light-sntchr]

/assign

[light-sntchr]

Thanks for the log. The error you are hitting is the camera refusing the shutter, and there are a couple of things I cannot tell from the part you pasted.

Could you send the log from the moment you connect the camera, not just the end? One line matters most: shortly after connecting it says either "capture target set to sdram" or "this body offers no in-memory capture target".

That ties into something you mentioned. You have the camera set to also save to the SD card, while NegPy tries the opposite and asks it to keep the file in memory. Each RAF is about 85 MB, so a dozen shots is roughly a gigabyte written to the card, and a backlog there would explain why it runs fine for a while and then stops. Could you try one calibration with tethering only, no copy to the card, and see if it gets further?

Does it fail at the same point every time? In your log it survives eleven captures and stops right after the red channel finishes, which is worth confirming.

On the second problem you mentioned, where the camera disappears after one frame: the log helps there too. If you see a line saying "camera disappeared from the bus", the camera dropped off USB entirely, which is a different fault from the session breaking, and the fix would be a different one. Does that happen after every single frame, or only sometimes? I would like to look at both problems together, so please keep them in this issue.

For what it is worth, the X-T5 is in gphoto2's camera list with live view and settings support, so this is not a case of an unsupported body.

@rohanpandula, in #652 you describe Fujifilm bodies sticking in a gphoto2 tethered-capture state and refusing to reconnect, which is the reason the Bluetooth route exists. Was that the same failure as the one here? Specifically, did captures run fine for a while and then fail with a bare [-1], or did the body drop off after a single frame the way it does in the second problem above? An error code, or the operation it wedged on, would help a lot. We have two Fujifilm reports open now and no root cause for either, and your GFX 100 II observations are the closest thing to a third data point.

[lamosadosa]

thanks. I did deactivate the raw store on card.

it still fails. here is a ful console log from connecting the camera to calibration fail

[2026-07-29 11:12:28] INFO     negpy.negpy.infrastructure.capture.gphoto: gphoto2 session open: X-T5 (driver 'Fuji Fujifilm X-T5', live view yes, settings yes)
[2026-07-29 11:13:12] INFO     negpy.negpy.infrastructure.capture.gphoto: gphoto2 session open: X-T5 (driver 'Fuji Fujifilm X-T5', live view yes, settings yes)
[2026-07-29 11:13:30] INFO     negpy.negpy.infrastructure.capture.gphoto: gphoto2 captured capture.raf (85.2 MB): assert 59 ms, shot 2869 ms, download 97 ms (881 MB/s)
[2026-07-29 11:13:30] INFO     negpy.negpy.infrastructure.capture.gphoto: gphoto2 post-shot drain 305 ms (overlapped)
[2026-07-29 11:13:30] WARNING  negpy.negpy.infrastructure.capture.gphoto: gphoto2 live view (1/3): [-1] Unspecified error
[2026-07-29 11:13:31] WARNING  negpy.negpy.infrastructure.capture.gphoto: gphoto2 live view (2/3): [-1] Unspecified error
[2026-07-29 11:13:31] WARNING  negpy.negpy.infrastructure.capture.gphoto: gphoto2 live view (3/3): [-1] Unspecified error
[2026-07-29 11:13:31] WARNING  negpy.negpy.infrastructure.capture.gphoto: gphoto2: camera stopped answering, dropping the session
[2026-07-29 11:13:36] INFO     negpy.negpy.infrastructure.capture.gphoto: gphoto2 post-shot drain 0 ms (overlapped)
[2026-07-29 11:13:36] INFO     negpy.negpy.infrastructure.capture.gphoto: gphoto2 captured capture.raf (85.1 MB): assert 51 ms, shot 2685 ms, download 95 ms (899 MB/s)
[2026-07-29 11:13:42] INFO     negpy.negpy.infrastructure.capture.gphoto: gphoto2 post-shot drain 0 ms (overlapped)
[2026-07-29 11:13:42] INFO     negpy.negpy.infrastructure.capture.gphoto: gphoto2 captured capture.raf (84.9 MB): assert 52 ms, shot 2675 ms, download 94 ms (901 MB/s)
[2026-07-29 11:13:47] INFO     negpy.negpy.infrastructure.capture.gphoto: gphoto2 post-shot drain 0 ms (overlapped)
[2026-07-29 11:13:47] INFO     negpy.negpy.infrastructure.capture.gphoto: gphoto2 captured capture.raf (84.9 MB): assert 48 ms, shot 2670 ms, download 96 ms (883 MB/s)
[2026-07-29 11:13:53] INFO     negpy.negpy.infrastructure.capture.gphoto: gphoto2 post-shot drain 0 ms (overlapped)
[2026-07-29 11:13:53] INFO     negpy.negpy.infrastructure.capture.gphoto: gphoto2 captured capture.raf (85.8 MB): assert 52 ms, shot 2699 ms, download 97 ms (888 MB/s)
[2026-07-29 11:13:59] INFO     negpy.negpy.infrastructure.capture.gphoto: gphoto2 post-shot drain 0 ms (overlapped)
[2026-07-29 11:13:59] INFO     negpy.negpy.infrastructure.capture.gphoto: gphoto2 captured capture.raf (85.8 MB): assert 47 ms, shot 2701 ms, download 97 ms (886 MB/s)
[2026-07-29 11:14:05] INFO     negpy.negpy.infrastructure.capture.gphoto: gphoto2 post-shot drain 0 ms (overlapped)
[2026-07-29 11:14:05] INFO     negpy.negpy.infrastructure.capture.gphoto: gphoto2 captured capture.raf (86.1 MB): assert 54 ms, shot 2696 ms, download 99 ms (873 MB/s)
[2026-07-29 11:14:11] INFO     negpy.negpy.infrastructure.capture.gphoto: gphoto2 post-shot drain 0 ms (overlapped)
[2026-07-29 11:14:11] INFO     negpy.negpy.infrastructure.capture.gphoto: gphoto2 captured capture.raf (86.9 MB): assert 51 ms, shot 2724 ms, download 98 ms (887 MB/s)
[2026-07-29 11:14:17] INFO     negpy.negpy.infrastructure.capture.gphoto: gphoto2 post-shot drain 0 ms (overlapped)
[2026-07-29 11:14:17] INFO     negpy.negpy.infrastructure.capture.gphoto: gphoto2 captured capture.raf (87.1 MB): assert 47 ms, shot 2737 ms, download 100 ms (873 MB/s)
[2026-07-29 11:14:23] INFO     negpy.negpy.infrastructure.capture.gphoto: gphoto2 post-shot drain 0 ms (overlapped)
[2026-07-29 11:14:23] INFO     negpy.negpy.infrastructure.capture.gphoto: gphoto2 captured capture.raf (86.7 MB): assert 58 ms, shot 2736 ms, download 99 ms (878 MB/s)
[2026-07-29 11:14:25] INFO     negpy.negpy.services.capture.calibration: calibration response: kR=5268.6 kG=7333.1 kB=6977.3 (spread 0.48 stops)
[2026-07-29 11:14:28] INFO     negpy.negpy.infrastructure.capture.gphoto: gphoto2 post-shot drain 0 ms (overlapped)
[2026-07-29 11:14:28] INFO     negpy.negpy.infrastructure.capture.gphoto: gphoto2 captured capture.raf (84.9 MB): assert 48 ms, shot 2680 ms, download 97 ms (874 MB/s)
[2026-07-29 11:14:31] INFO     negpy.negpy.services.capture.calibration: calibrated R → level 226, shutter 1/20 (target 58982, got 58402, clip 0.000%, target)
[2026-07-29 11:14:34] INFO     negpy.negpy.infrastructure.capture.gphoto: gphoto2 post-shot drain 0 ms (overlapped)
[2026-07-29 11:14:34] INFO     negpy.negpy.infrastructure.capture.gphoto: gphoto2 captured capture.raf (86.1 MB): assert 7 ms, shot 2697 ms, download 99 ms (873 MB/s)
[2026-07-29 11:14:37] WARNING  negpy.negpy.infrastructure.capture.gphoto: gphoto2 exit: [-1] Unspecified error
[2026-07-29 11:14:37] ERROR    negpy.negpy.desktop.workers.capture_worker: calibration failed
Traceback (most recent call last):
  File "negpy/infrastructure/capture/gphoto.py", line 654, in capture
gphoto2.GPhoto2Error: [-1] Unspecified error

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "negpy/desktop/workers/capture_worker.py", line 504, in run_calibration
  File "negpy/services/capture/calibration.py", line 483, in calibrate
  File "negpy/services/capture/calibration.py", line 544, in _verify_channel
  File "negpy/services/capture/calibration.py", line 453, in _shoot
  File "negpy/services/capture/calibration.py", line 598, in _capture
  File "negpy/infrastructure/capture/gphoto.py", line 669, in capture
negpy.infrastructure.capture.gphoto.GphotoError: capture failed: [-1] Unspecified error

[lamosadosa]

i did change setting to allow taking pics without sd-card being present. it did fail again. same errors.
I did change the aperture from f5.6 to f8 and now it did run through the calibration.

trying to scan I get an instant close of the scan/preview window - i have to reconnect and re-power the camera

[2026-07-29 11:30:45] WARNING  negpy.negpy.infrastructure.capture.gphoto: gphoto2 exit: [-1] Unspecified error
[2026-07-29 11:30:46] INFO     negpy.negpy.infrastructure.capture.gphoto: gphoto2 session open: X-T5 (driver 'Fuji Fujifilm X-T5', live view yes, settings yes)
[2026-07-29 11:30:46] WARNING  negpy.negpy.infrastructure.capture.gphoto: gphoto2 live view (1/3): [-1] Unspecified error
[2026-07-29 11:30:46] WARNING  negpy.negpy.infrastructure.capture.gphoto: gphoto2 live view (2/3): [-1] Unspecified error
[2026-07-29 11:30:47] WARNING  negpy.negpy.infrastructure.capture.gphoto: gphoto2 live view (3/3): [-1] Unspecified error
[2026-07-29 11:30:47] WARNING  negpy.negpy.infrastructure.capture.gphoto: gphoto2: camera stopped answering, dropping the session
[2026-07-29 11:30:52] INFO     negpy.negpy.desktop.workers.capture_worker: camera disappeared from the bus — dropping the session
[2026-07-29 11:30:52] WARNING  negpy.negpy.infrastructure.capture.gphoto: gphoto2 exit: [-52] Could not find the requested device on the USB port
[2026-07-29 11:30:58] INFO     negpy.negpy.infrastructure.capture.gphoto: gphoto2 session open: X-T5 (driver 'Fuji Fujifilm X-T5', live view yes, settings yes)
[2026-07-29 11:30:58] WARNING  negpy.negpy.infrastructure.capture.gphoto: gphoto2 exit: [-1] Unspecified error
[2026-07-29 11:30:59] INFO     negpy.negpy.infrastructure.capture.gphoto: gphoto2 session open: X-T5 (driver 'Fuji Fujifilm X-T5', live view yes, settings yes)
[2026-07-29 11:30:59] WARNING  negpy.negpy.infrastructure.capture.gphoto: gphoto2 live view (1/3): [-1] Unspecified error
[2026-07-29 11:31:00] WARNING  negpy.negpy.infrastructure.capture.gphoto: gphoto2 live view (2/3): [-1] Unspecified error
[2026-07-29 11:31:00] WARNING  negpy.negpy.infrastructure.capture.gphoto: gphoto2 live view (3/3): [-1] Unspecified error
[2026-07-29 11:31:00] WARNING  negpy.negpy.infrastructure.capture.gphoto: gphoto2: camera stopped answering, dropping the session
[2026-07-29 11:31:04] WARNING  negpy.negpy.infrastructure.capture.gphoto: gphoto2 exit: [-1] Unspecified error
[2026-07-29 11:31:05] INFO     negpy.negpy.infrastructure.capture.gphoto: gphoto2 session open: X-T5 (driver 'Fuji Fujifilm X-T5', live view yes, settings yes)
[2026-07-29 11:31:05] WARNING  negpy.negpy.infrastructure.capture.gphoto: gphoto2 live view (1/3): [-1] Unspecified error
[2026-07-29 11:31:06] WARNING  negpy.negpy.infrastructure.capture.gphoto: gphoto2 live view (2/3): [-1] Unspecified error
[2026-07-29 11:31:06] WARNING  negpy.negpy.infrastructure.capture.gphoto: gphoto2 live view (3/3): [-1] Unspecified error
[2026-07-29 11:31:06] WARNING  negpy.negpy.infrastructure.capture.gphoto: gphoto2: camera stopped answering, dropping the session

[light-sntchr]

Thanks, that full log answers a lot.

Two things are now clear. Your camera is recognised properly (the log line says live view yes, settings yes), and the shutter side works fine, it moves 85 MB files at 880 MB/s. What fails is only the preview: every attempt returns [-1], and in the second log it fails immediately after connecting, before any capture.

The bad part is what NegPy did with that. After three failed preview frames it assumed the camera was gone and dropped the whole session, which also took down the capture session that was working perfectly. Then it reopened and tried again, over and over, which is what eventually pushed the camera off the USB bus with [-52]. So the window closing instantly and the constant reconnecting were our fault, not your camera's. That part is fixed in #674: a broken preview no longer kills the session, and it is not retried in a loop. Scanning keeps working, without a preview.

On the preview itself I am less optimistic. gphoto2's site lists the X-T5 as supporting live view, but that entry has exactly the same flags as the X-T3 and X-T4 and was carried over when the model was added, so it is a declaration rather than something that was tested. There are open reports of the same thing on other Fujifilm bodies with no root cause found, for example gphoto/gphoto2#671 on the X-T3, which shows both -110 and -1 after a single capture, and gphoto/libgphoto2#603 on the X-S10 where capture-preview returns the same error you get.

Before I accept that, two quick tests would help, and they take a minute:

1. With the camera connected, run gphoto2 --capture-preview in a terminal. If that fails the same way, the problem is in libgphoto2 itself and there is nothing NegPy can do. If it works, we are doing something the command line does not, and I can fix it.
2. If it does work: right after connecting, run gphoto2 --set-config capturetarget=1 and then --capture-preview again. NegPy sets that value when it opens the camera, and Fujifilm bodies have a history of trouble with it, so that is my main suspect on our side.

[lamosadosa]

1: success

gphoto2 --capture-preview
Speichere Datei als capture_preview.jpg

2:error

gphoto2 --set-config capturetarget=1
                                                                               
*** Fehler ***      
capturetarget wurde nicht in der Konfiguration gefunden.
*** Fehler (-1: »Unspezifizierter Fehler«) ***      

Für Debug-Meldungen verwenden Sie bitte die Option »--debug«.
Diese Meldungen können Ihnen helfen, eine Lösung für Ihr Problem zu
finden. Wenn Sie jedoch Fehler- oder Debug-Meldungen an die
Mailingliste <gphoto-devel@lists.sourceforge.net> schicken wollen, 
so starten sie gphoto2 bitte wie folgt:

    env LANG=C gphoto2 --debug --debug-logfile=my-logfile.txt --set-config capturetarget=1

Bitte stellen Sie sicher das die uebergebenen Argument ausreichend gequoted sind

with --debug here are some of the error lines

0.761109 ptp_usb_getresp             (2): Reading PTP_OC 0x1014 (Device Property Beschreibung abfragen) response...
0.761113 gp_port_read                (3): Reading 1024 = 0x400 bytes from port...
0.761156 gp_port_read                (3): Read    12 = 0xc out of 1024 bytes from port: (hexdump of 12 bytes)
0000  0c 00 00 00 03 00 0a 20-11 01 00 00              ....... ....    

0.761162 ptp_usb_getresp [usb.c:495] (0): PTP_OC 0x1014 receiving resp failed: PTP Device Prop Not Supported (0x200a)


0.766102 ptp_usb_getresp [usb.c:495] (0): PTP_OC 0x1014 receiving resp failed: PTP Device Prop Not Supported (0x200a)
0.766109 gp_widget_set_value         (2): Setting value of widget 'PTP Property 0xd17b' to '1'...
0.766115 gp_widget_set_value         (2): Setting value of widget 'ResetSetting' to '4'...
0.766122 gp_widget_set_value         (2): Setting value of widget 'PTP Property 0xd208' to '772'...
0.766130 gp_widget_set_value         (2): Setting value of widget 'PTP Property 0xd21c' to '4'...
0.766148 gp_context_error            (0): capturetarget wurde nicht in der Konfiguration gefunden.

*** Fehler ***      
capturetarget wurde nicht in der Konfiguration gefunden.
*** Fehler (-1: »Unspezifizierter Fehler«) ***  

[light-sntchr]

Thanks, your CLI result was the missing piece. The preview is not broken on the X-T5 as such: it dies the moment a still is taken, which is why a bare --capture-preview on a freshly started camera works. Your capturetarget result is explained too, that setting simply does not exist on this body.

#674 should fix it. The reasoning is in the PR if you want the detail.

Could you test once more after it is merged, a calibration plus two or three frames, and tell us whether live view survives the captures? If it still breaks you will at least not be stuck: the window stays open and scanning keeps working without a preview.

[lamosadosa]

new release (0.45.0) did improve the calibration. it went fine.
but when trying to take scan a frame after that it drops again.
re-power and reconnect worked. for a few frames.

[2026-07-30 18:55:33] INFO     negpy.negpy.infrastructure.capture.gphoto: gphoto2 session open: X-T5 (driver 'Fuji Fujifilm X-T5', live view yes, settings yes)
[2026-07-30 18:55:33] INFO     negpy.negpy.infrastructure.capture.gphoto: gphoto2: this body has no capture-target setting; leaving it alone
[2026-07-30 18:55:43] INFO     negpy.negpy.infrastructure.capture.gphoto: gphoto2 session open: X-T5 (driver 'Fuji Fujifilm X-T5', live view yes, settings yes)
[2026-07-30 18:55:43] INFO     negpy.negpy.infrastructure.capture.gphoto: gphoto2: this body has no capture-target setting; leaving it alone
[2026-07-30 18:56:01] INFO     negpy.negpy.infrastructure.capture.gphoto: gphoto2 captured capture.raf (84.8 MB): assert 58 ms, shot 2889 ms, download 95 ms (894 MB/s)
[2026-07-30 18:56:01] INFO     negpy.negpy.infrastructure.capture.gphoto: gphoto2 post-shot drain 304 ms (overlapped)
[2026-07-30 18:56:02] WARNING  negpy.negpy.infrastructure.capture.gphoto: gphoto2 live view (1/3): [-1] Unspecified error
[2026-07-30 18:56:03] WARNING  negpy.negpy.infrastructure.capture.gphoto: gphoto2 live view (2/3): [-1] Unspecified error
[2026-07-30 18:56:03] WARNING  negpy.negpy.infrastructure.capture.gphoto: gphoto2 live view (3/3): [-1] Unspecified error
[2026-07-30 18:56:03] WARNING  negpy.negpy.infrastructure.capture.gphoto: gphoto2: live view failed but the camera still answers — continuing without a preview
[2026-07-30 18:56:07] INFO     negpy.negpy.infrastructure.capture.gphoto: gphoto2 captured capture.raf (84.5 MB): assert 45 ms, shot 2692 ms, download 100 ms (848 MB/s)
[2026-07-30 18:56:07] INFO     negpy.negpy.infrastructure.capture.gphoto: gphoto2 post-shot drain 304 ms (overlapped)
[2026-07-30 18:56:13] INFO     negpy.negpy.infrastructure.capture.gphoto: gphoto2 captured capture.raf (84.6 MB): assert 50 ms, shot 2683 ms, download 99 ms (855 MB/s)
[2026-07-30 18:56:13] INFO     negpy.negpy.infrastructure.capture.gphoto: gphoto2 post-shot drain 304 ms (overlapped)
[2026-07-30 18:56:19] INFO     negpy.negpy.infrastructure.capture.gphoto: gphoto2 captured capture.raf (85.7 MB): assert 57 ms, shot 2714 ms, download 102 ms (844 MB/s)
[2026-07-30 18:56:19] INFO     negpy.negpy.infrastructure.capture.gphoto: gphoto2 post-shot drain 304 ms (overlapped)
[2026-07-30 18:56:25] INFO     negpy.negpy.infrastructure.capture.gphoto: gphoto2 captured capture.raf (87.2 MB): assert 13 ms, shot 2722 ms, download 98 ms (887 MB/s)
[2026-07-30 18:56:25] INFO     negpy.negpy.infrastructure.capture.gphoto: gphoto2 post-shot drain 304 ms (overlapped)
[2026-07-30 18:56:30] INFO     negpy.negpy.infrastructure.capture.gphoto: gphoto2 captured capture.raf (87.5 MB): assert 61 ms, shot 2748 ms, download 100 ms (874 MB/s)
[2026-07-30 18:56:31] INFO     negpy.negpy.infrastructure.capture.gphoto: gphoto2 post-shot drain 304 ms (overlapped)
[2026-07-30 18:56:33] INFO     negpy.negpy.services.capture.calibration: calibration response: kR=2044.0 kG=2182.8 kB=2938.8 (spread 0.52 stops)
[2026-07-30 18:56:36] INFO     negpy.negpy.infrastructure.capture.gphoto: gphoto2 captured capture.raf (84.5 MB): assert 43 ms, shot 2676 ms, download 93 ms (910 MB/s)
[2026-07-30 18:56:36] INFO     negpy.negpy.infrastructure.capture.gphoto: gphoto2 post-shot drain 305 ms (overlapped)
[2026-07-30 18:56:39] INFO     negpy.negpy.services.capture.calibration: calibrated R → level 231, shutter 1/8 (target 58982, got 60335, clip 0.000%, target)
[2026-07-30 18:56:42] INFO     negpy.negpy.infrastructure.capture.gphoto: gphoto2 captured capture.raf (85.8 MB): assert 2 ms, shot 2698 ms, download 99 ms (866 MB/s)
[2026-07-30 18:56:42] INFO     negpy.negpy.infrastructure.capture.gphoto: gphoto2 post-shot drain 304 ms (overlapped)
[2026-07-30 18:56:48] INFO     negpy.negpy.infrastructure.capture.gphoto: gphoto2 captured capture.raf (85.7 MB): assert 2 ms, shot 2695 ms, download 97 ms (881 MB/s)
[2026-07-30 18:56:48] INFO     negpy.negpy.infrastructure.capture.gphoto: gphoto2 post-shot drain 304 ms (overlapped)
[2026-07-30 18:56:50] INFO     negpy.negpy.services.capture.calibration: calibrated G → level 255, shutter 1/8 (target 58982, got 51658, clip 0.000%, target)
[2026-07-30 18:56:53] INFO     negpy.negpy.infrastructure.capture.gphoto: gphoto2 captured capture.raf (87.4 MB): assert 2 ms, shot 2750 ms, download 102 ms (853 MB/s)
[2026-07-30 18:56:54] INFO     negpy.negpy.infrastructure.capture.gphoto: gphoto2 post-shot drain 307 ms (overlapped)
[2026-07-30 18:56:59] INFO     negpy.negpy.infrastructure.capture.gphoto: gphoto2 captured capture.raf (87.2 MB): assert 2 ms, shot 2748 ms, download 99 ms (882 MB/s)
[2026-07-30 18:57:00] INFO     negpy.negpy.infrastructure.capture.gphoto: gphoto2 post-shot drain 310 ms (overlapped)
[2026-07-30 18:57:02] INFO     negpy.negpy.services.capture.calibration: calibrated B → level 190, shutter 1/8 (target 58982, got 57447, clip 0.000%, target)
[2026-07-30 18:57:05] INFO     negpy.negpy.desktop.workers.capture_worker: live view unavailable: X-T5 accepted the connection but its live view does not work (a known gap in libgphoto2's Fujifilm support). Scanning still works, just without a preview.
[2026-07-30 18:57:18] INFO     negpy.negpy.desktop.workers.capture_worker: run_capture setup 0 ms
[2026-07-30 18:57:21] INFO     negpy.negpy.infrastructure.capture.gphoto: gphoto2 captured Roll001_Frame001_R.raf (84.5 MB): assert 10 ms, shot 2687 ms, download 97 ms (875 MB/s)
[2026-07-30 18:57:21] INFO     negpy.negpy.services.capture.service: channel R: settle 51 ms, capture+download 2848 ms → Roll001_Frame001_R.raf
[2026-07-30 18:57:21] INFO     negpy.negpy.infrastructure.capture.gphoto: gphoto2 post-shot drain 304 ms (overlapped)
[2026-07-30 18:57:21] WARNING  negpy.negpy.infrastructure.capture.gphoto: gphoto2 exit: [-1] Unspecified error
[2026-07-30 18:57:21] ERROR    negpy.negpy.desktop.workers.capture_worker: capture failed
Traceback (most recent call last):
  File "negpy/infrastructure/capture/gphoto.py", line 678, in capture
gphoto2.GPhoto2Error: [-1] Unspecified error

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "negpy/desktop/workers/capture_worker.py", line 276, in run_capture
  File "negpy/services/capture/service.py", line 206, in capture_triplet
  File "negpy/infrastructure/capture/gphoto.py", line 693, in capture
negpy.infrastructure.capture.gphoto.GphotoError: capture failed: [-1] Unspecified error

[2026-07-30 18:59:27] INFO     negpy.negpy.infrastructure.capture.gphoto: gphoto2 captured Roll001_Frame004_B.raf (87.5 MB): assert 11 ms, shot 2775 ms, download 100 ms (872 MB/s)
[2026-07-30 18:59:27] INFO     negpy.negpy.services.capture.service: channel B: settle 51 ms, capture+download 3129 ms → Roll001_Frame004_B.raf
[2026-07-30 18:59:27] INFO     negpy.negpy.infrastructure.capture.gphoto: gphoto2 post-shot drain 304 ms (overlapped)
[2026-07-30 18:59:29] INFO     negpy.negpy.services.rendering.gpu_engine: GPUEngine: VRAM resources released
[2026-07-30 18:59:38] INFO     negpy.negpy.desktop.workers.capture_worker: run_capture setup 0 ms
[2026-07-30 18:59:38] WARNING  negpy.negpy.infrastructure.capture.gphoto: gphoto2 exit: [-1] Unspecified error
[2026-07-30 18:59:38] ERROR    negpy.negpy.desktop.workers.capture_worker: capture failed
Traceback (most recent call last):
  File "negpy/infrastructure/capture/gphoto.py", line 678, in capture
gphoto2.GPhoto2Error: [-1] Unspecified error

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "negpy/desktop/workers/capture_worker.py", line 276, in run_capture
  File "negpy/services/capture/service.py", line 206, in capture_triplet
  File "negpy/infrastructure/capture/gphoto.py", line 693, in capture
negpy.infrastructure.capture.gphoto.GphotoError: capture failed: [-1] Unspecified error

[light-sntchr]

Found the remaining one, and your logs gave it away: both of your sessions failed at exactly the 13th shot. Twelve shots at 85 MB is about a gigabyte. The camera keeps every tethered shot in its internal buffer until the host deletes it, NegPy never did, and once the buffer is full the X-T5 refuses the next trigger. A power cycle empties the buffer, which is why it then worked for exactly four more frames, twelve shots again.

#696 deletes each shot off the camera right after downloading it, so the buffer never fills. There is a decent chance this also brings live view back: your preview dies the moment the first un-deleted shot sits in the buffer and returns after a power cycle, so the pending object may be exactly what blocks it.

Could you test once more when it lands, ideally a calibration plus a dozen frames in one go? If it clears shot 13, we have it.