-
Notifications
You must be signed in to change notification settings - Fork 323
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Capture time is extremely long (~16 minutes) #914
Comments
I think you have built against libusb 0.1 and not libusb 1.x. libusb 0 specifically will not work well for Sonys. |
Thanks Marcus. I'll recompile and look for this. |
Here's what I see with a fresh install of Octopi:
So I made sure to remove the 0.1-4 version and install 1.0-0:
I then installed both packages, and I unfortunately got the "libgphoto2_port" line showing "no USB". I then tried to re-install libusb-dev, and it seems to continue pointing at 0.1.x versions:
If I try to force libusb-1.0-0 to be installed, I see this:
So I think I'm kinda stuck here. I can't get USB to work at all without libusb-dev, which seems to install the 0.1 version of libusb alongside the 1.0 version. And then if I do that, libgphoto2 seems to not interact well with my A7iii (unsurprisingly getting the endless single capture symptom again after repeating these steps). For another datapoint: I also have an A7iv, and using --trigger-capture I was able to get it to work. So there's something different about the A7iii with this setup that appears problematic. |
try to install libusb-1-dev or libusb-1.0-dev or libusb-1.0-0-dev |
libusb-1.0-0-dev worked, and I got this octopi install to this state:
Then I reconfigured and remade libgphoto2... but unfortunately I'm getting the same result. When I try to take a photo the camera is just endlessly looping on that 1 photo, and it's stuck. I can't recover the camera unless I turn it off and take out the battery. Something about that USB command is really knocking it into the weeds... Just for sanity:
Any other ideas? I'm only trying to initiate a capture trigger here with the a7iii (record to memory card). And I'm using:
Thanks! |
Earlier Sony Alpha only could capture to SDRAM. Perhaps yours can also capture to card, this needs to be set to be going to the card. Is it still taking 16 minutes? |
The A7iii is still relatively new. And is widely popular, which is why I'm a bit confused as to why I appear to be the only one hitting these issues. Makes me all but convinced that I'm doing something fundamentally wrong. But yes, with --trigger-capture it took over an hour before I gave up and unplugged the camera. I'm a bit confused by your question though... this is a mirrorless SLR with a very large buffer. Pretty sure the camera always writes to the buffer no matter what (there are no options that I've ever seen) and then this buffer drains to the SD card (FIFO). Is there a certain setting I should be applying in gphoto? Again all I'm looking for here is a trigger- I don't need to transfer the image itself. It can stay on the camera. |
can you get a fresh debuglogfile from the current build with --trigger-capture --debug --debug-logfile=capture.log ? |
That's a good idea. I have a large print going, but I'll do this as soon as the printer is free again. |
Here's a log with
Note that I had to copy/paste with --debug above because the --debug-logfile=FILENAME switch doesn't work for me with this latest build (I just get no file and no error message along with it). It definitely worked before (when I was using the apt-get packaged version). If I want to just trigger capture and record everything in-camera, |
You could try At least seems to work on some Canon cameras. |
Describe the bug
Capture time is extremely long (~16 minutes). During this period, the camera appears to be communicating with the computer, as the camera's red "busy" light is solidly on, and the icon representing the memory card in the upper left hand corner is continually pulsing with a number 1 (indicating 1 shot is being buffered).
https://imgur.com/a/q4eUWV1
Note that I do appear to successfully get a single image out of this command on my camera's SD card. It just takes too long to be practical.
If I try running with --debug, I see a continuous output, mostly with raw data. It looks like this:
The tail of the console output looks like this:
If I try dumping a log with
--debug-logfile=debug_file.log
I don't ever get a log file. I assume it's because it's too big.Name the camera
libgphoto2 and gphoto2 version
To Reproduce
gphoto2 --capture-image
The text was updated successfully, but these errors were encountered: