On the G1X the folder name seems to be correct, even if a new folder is created. Haven't explicitly tested what happens when the file number wraps around at 9999.
What I meant was if the folder changes automatically between shots, i.e. hitting 9999 or 2000 images in the current folder. If the folder updates at the same time as the counter (which seems likely, though I've never logged it), then the tmp file will be created in the old folder, and the path used in rename will be in the new folder.
This is fairly rare in every day shooting, but pretty common for timelapse. It's also annoying to test.
It's a pity we don't have a FAT level move.
Remote capture is trickier. One option might be to use a completely custom naming scheme and store our own next file number in the config file.
I suppose we could just say it's up to the client and take the number out of the protocol. You could also managed numbers from script, or start with the current get_exp_count() number and increment yourself.
In chdkptp I've been meaning to add the substitution strings like imdl, which allows all kinds of time/date numbering, but the camera image numbering is a nice intuitive default.
I guess we could make the pause apply only to remotecap, but it would be even less likely to be well tested and has a substantial performance hit in come cases.
