What you are talking about is a high impedance path backwards through the offline camera's power supply circuitry.
say it's a 100k impedance - is that reasonable? there'll surely be a resistor network across the output to monitor the feedback voltage. then with 10 cameras connected but not powered off, that would be like a 10k resistor in the circuit which you weren't expecting to be there - wouldn't that kind of value be significant?
I've seen exactly this happen, not with the camera battery terminal / not depending on the camera power supply impedance, but I do have multiple triggers, deriving a 5v signal from the usb output of multiple raspberry pis, and any pi's that are connected but not turned on cause this issue, so I wanted to raise this.
My suggestion here is "try it and see" - you are not going to break anything.
agreed
Regardless, none of the cameras are going to trigger just because they power on - unless maybe you are autostarting their multicam script.
my thinking is, if the camera is set to monitor the battery terminal, then the 1st camera powered on will see a low signal on the battery terminal and so it will shoot, _if_ the mooted impedance and number of connected cameras does indeed cause a problem, of course. This would not need a script to be running for this to happen, if the menu setting is there?
But even then, so what? One extra shot on your SD card that will just be ignored.
from my experience with multicam setups, the ideal, by far, is that the 1st pic across all the cameras is the same generation, the 9th pic is the same generation, and so on and anything else is potentially a major pain. I have almost 80 cameras now, i did a session of about 70 pictures, so we're talking over 5000 pictures to be sorted, I would definitely try to avoid anomalous photos as much as I can. Of course, other setups won't be so extreme, at the beginning anyway.
