Richard Benjamin Allen
Richard Benjamin Allen
When I look at the first 128 bytes for an NEF file from a Nikon D5300 I get the following: `49 49 2A 00 08 00 00 00 1A 00...
I am encountering the same issue, multiple Nikon D5300s, if I turn off the cameras, invalid ports or old ports get assigned to the camera that is still on despite...
When you specify `--camera` even though they are all the same, it is able to detect that the port is no longer valid. I am going to implement something which...
I've found that the problem goes away if I specify `camera` and `port`, but only when the cameras are triggered in sequence i.e. distinctly after each other. If one tries...
Update: Using a desktop PC with Ubuntu it fails. However, using a RaspberryPi 4 with Raspbian (Buster) with a camera on three individual USB ports, parallel triggering works for longer...
I have just tried again with the Raspberry Pi but this time escaping the camera param in the cmds list, and it works a lot better. ```python cmds = [['gphoto2',...
I'm not associated with this repository, but I have the same problem. So I use regex in something like the code below: ```python import re from typing import Pattern keys_regex:...
That seems to have fixed this, huge thanks for the quick response!
That's my issue. It is caused by Mirador. I have had this error in the console for several years in Mirador 3. I previously thought it was an OSD issue...
I used the config setting `subPixelRoundingForTransparency: 2` to get around this in my Mirador viewer implementation (which uses OSD), it removed the white lines.