Helicon Soft Forum

Hi,

What's annoying after you use Remote to do std is that you end up with lots of frame, that belong to a remote job (focus staking, bracketing, burst etc..). Each job, is in fact one capture, one photo the photographer envisionned.

But, pardon, me if I'm wrong there's no easy way to pile all the job capture, have them separated by job.

1. Simple ide, movie like clapper frame

here's a though, what if remote add an option to fire a dark frame (1/4000s f22) at the end of a job. That way we could seem immediately our job separated by this dark frame.

Firing an extra "clapper" frame wouldn't take a lot of time, especially at this speed.

That's the crude an easy method.

2. Writing in the exif

A better one, would be, if remote could write in exif, to write in the exif a job id, or job details.

Either by uploading the id in a comment area in the custom exif in the camera, like photographer signature. So Remote will set the camera custom exif before capture, and it's the camera that would write the exif.

Or if remote can't customize custom exif part of the camera before capture, remote could perhaps write in the exif of the dark clapper frame.

3. Logging the frame in remote itself

If remote can't write in the exif (but maybe it can because remote offers gps option)

Remote could log either file names of the picture, or timestamp first and last frame, in an internal log with job id. So afterwards, we could use that log with Light Room to identify our frame, via some import export of data.

A database of job id, where each job setting would be stored could be very cool / useful. So when reviewing image we could better grasp our blunders

The log solution seems the easiest to implement. Writing to EXIF might be possible, but only as long as you're pulling images to your computer or Android device. On the other hand, if you're pulling images then Remote can simply create a new folder when you tell it to (press a button). Desktop version has this feature (menu -> Stack -> New Stack), Android doesn't have a UI control for this action, but we can add it.

I don't pull images to android, because it's slow down the capture process.
What about the extra dark frame ?

But log would be great

Do you think it's slow, or have you tested it and found out it's slow? Because our tests show that sometimes there's no preceivable difference, and if there is it's still very small.

Hum, not sure if we're taking about the same thing.

I tested : Copy frame to computer( which is android) against Leave on caera. I shoot raw. Each files is 29 MB.

So after Remote does a capture, it takes a long time to be able to capture again. Of course without copy frame to computer, we can work as soon as the capture finished.

Even with Jpeg, there's a 10-30 second delay after capture is done.
If you've a procedure you want me to test, I'll do it.

10 seconds sounds fair, although a bit on the long side, but 30 seconds is way, way too long. We'll test to see if there's some performance issue and will get back to you.