Thanks all for answering.
Let's see now..
1.
@waterwingz : I suspected that your script might work that way (one script on the pc and the other on the camera).But the whole situation process raises a conflict in my eyes.
When i mass-connect to the cameras and they go into "rec mode" , ready to shoot , they kinda start "default" script running.I mean i see the "Default Script <ALT>" at the lower left side.
This goes off when either cameras get disconnected (i suppose , because when they shoot , viewfinder goes black...some bug? but everything is working despite of that and view comes back when i connect cameras back and switch them back to play mode) or i issue a "mass exit" command from chdkptp.
Won't this whole process fail if some other script (yours lets say) is running already on the camera?
2. when i said , take the switch and walk around , i didnt think about "remote" switch , but a wired one.When i say walk around we are talking a distance of 2-3 meters from pc to the "cameras setup" and back..Not big distances.I dont mind to carry a cable with me lets say...but i'd like to have the shooting task in loop forever , go over to the cameras , give instructions to the customer where to stand , what to do , what not to do and when he/she is ready . i press the switch .
3.I see that you quoted two lines i wrote but you left out some others that was the whole point.
I said that i press shoot at chdkptp....shoot task goes into loop...i press switch...cameras diconnect and at the same time shooting occures.All good so far.
When i press switch again , cameras connect to pc again...obviously and then i run my script to download the images from the cameras.chkdptp command tries to connect to each camera and download the images to some predefined folders.
What i said was that at the first running of the script , chdkptp fails to connect to one of the two cameras...the same every time?different?i dont care , i didnt look into it.Its meaningless.Fact is that iof one of the two cameras doesnt connect and images dont get downloaded.
If i run the script a second time..ALL IS GOOD.So i wonder if this a usb-related thing..cameras dont get available fast or something.
As i said i include a "mass connect , mass exit" command in the script prior the download command..just to "wake" cameras up...to make them available...my thoughts..maybe its nonsense.
It works everytime..but as i said...its 2 cameras and the connections and disconnections are fast.I wonder how much time the script will need when it has 64 cameras to handle.
Its obvious that i used a custom build with the hack included. (chdk-shell , downloaded the source , edit kbd.c for my camera model , compile it , "stick" it to the cameras
)
4.
@reyalp : Cameras are using chdk 1.3 r599 .That the version STICK chose for my camera and i dont see a reason not to believe it
First of all all my sync-tests where using an online meter (with milliseconds) and all cameras where focusing on it.I dont have a CRT monitor for some more accurate tests..
With the first method (shooting via chdkptp) as i said 1-2 cameras out of 8 were losing "some" msecs.Not much.Nothing tragic.And if you think that the "objects" getting shot will be mostly static, that wouldn't be a problem.
But i fear that when 64 cameras will be connected , maybe sync will go off for more millisecs.
I have to add at this point that i used syncat parameter for shooting to make shooting a bit more accurate but with not a significant changes at the result.
If there is something else i could tweak/use for this "method" , feel free to enlight me
The second method (usb hacked cable , switch on/off , hacked kbd.c etc) is rumored to be more accurate.With 2 cameras is working very good.I need to test it with 8 cameras now.
In few words...what shooting method is "known" to have good sync with multiple cameras?
Thanks.
