På Sun, 19 Nov 2017 19:01:45 +0100 Michael Rasmussen <[email protected]> skrev: > On Sun, 19 Nov 2017 18:34:13 +0100 > Anders <[email protected]> wrote: > > > I had a tethred session today, and during the shooting, the cable > > was disconnected from my camera. Putting it in again, darktable was > > not able to make things work again. The camera could be found, but > > pressing at "tethered shooting" button made it say it created a new > > session, but the photos dissapeared. I rekon it may have worked had > > I restarted darktable, but I ended up keeping the photos in the > > camera for the rest of the session - not so nice I believe. > > > When you disconnect your camera the way you describe the session is > never terminated which means the kernel thinks a camera is using the > port meaning the device reference stays in the file system. When you > then connect your camera once again a new session will be created > which creates another device reference in the file system. Since DT > obviously was continuing using the old reference nothing showed up in > DT.
I don't think the kernel have an issue with that, but that is something I can try, I think that would be visible in dmesg. > Possible solutions (I have never used tethering so I do not know > whether my solutions are already implemented in DT): > 1) You should do a complete reset of tethering in DT How? > 2) You should restart DT after creating a new device reference I will test that :) > 3) You should forcefully terminate the broken session in your OS How? > before reconnecting your camera which should drop the device > reference and notifying user land applications like DT about the > termination > ____________________________________________________________________________ darktable user mailing list to unsubscribe send a mail to [email protected]
