Originally posted by Adam What do you mean?
Whether it's wired or wireless, ideally any API should offer a broad range of functionality.
Ideally yes, and ordinarily I would agree, has been pointing to less function and more automation based on what I've seen on the development side. As the newer cameras came out less and less tethering functions could be made to work. This includes the loss of preview modes and bulb, which kills it for AP...which is what got me posting about this originally. Pentax isn't alone in this remix of communications options, Canon has backstepped their tethering as well. For example, no or not working preview mode in new models due to undocumented protocol changes. Their mirrorless eos-m was a disaster, locked out completely "to protect higher end model sales" according to one representative I talked to. Marcus has newer ones working though...(Boggle)
Wifi access is much slower than usb tethering. 10-12 seconds per shot is pretty slow. This means wifi connections will primarily be useful for instant in the field uploads via cellphone, something which, in my opinion, high end users are less likely to do.
The recently released SDK only included a compiled binary with some rudimentary linking which only works in a few cameras. When I asked Libgphoto2 developer Marcus Meissner about this he said he couldn't use it due to the compiled binary and it would again require reverse engineering to start. - that's not what an SDK is supposed to do.
Support for Pentax K-50 · Issue #31 · gphoto/libgphoto2 · GitHub <--this might require coffee
I'm really only involved because even after getting some older cameras to tether and bulb(a recent breakthrough made by A.Solomon at PkTriggercord) my k-50 was the one camera that wouldn't ... very frustrating after all that research and testing work.
So this is why I disagree that they all support tethering. I hope you can understand my frustration. Enjoying the forum btw. Some nice folks here