Microfunguy
For outdoor work and action we typically need a fraction of a ms.
That would be very difficult if not impossible to do with PTP
For general outdoor work with moving people, vehicles,water,foliage, etc just a few ms.
Anything less than 10ms would be very difficult, since there is not (AFAIK) a clock with greater resolution available on the camera. Even 10ms would be very hard, since the clocks on each camera wouldn't be synchronized.
Out of curiosity, how do you measure the accuracy of sync ?
One thing that could help is a script controllable delay where the wait_for_remote code is called.
Incidentally, my
A620 does not return a serial number.
Yes, it appears older cameras don't return it.
D10 does,
A540 does not. If you were using a lot of cameras without, it would probably be useful to store a unique camera ID on the SD card or something...
When you broadcast a message to multiple cameras, how do you handle their replies ?
Loop over all the cameras checking for messages. This doesn't need to happen right away. (mc:wait_status_msg, which is called if you use mc:cmdwait)
So when you do a mc:cmdwait('preshoot') it sends the pre-shoot command to all the cameras, then waits for each one to send a message that indicating that get_shooting is true (or something failed)
So, it is not possible to connect to my two A620's (and maybe other cameras) as they do not return a serial number ?
No, it just won't notice if it connects to a different camera when you use reconnect or reboot. The issue is that the usb dev/bus can change when the camera is (it's not tied to the physical USB port). So if you reboot and try to reconnect, you might end up connected to a different camera.
the mc lib doesn't really care about uniquely identifying the cameras, it just connects to them all and identifies them by the order in which they were connected.
