Focus stacking drive duration Is not precise

[lore76b]

Focus stacking drive duration for pressing Is not precise.
You set 0.5 and It doesn't. Move enough, of you set a valute highet Is too much.

Suggest modify with Number of pression

[Staacks]

If you have a suggestion on how to do it :)

The problem is that the camera does not react immediately to the keypress. On my camera it will not drive while the immediate preview of the taken picture is visible. To dismiss it as fast as possible I am sending a short half press, but the preview image still takes up a fraction of a second. Could you try if disabling the immediate preview changes the issue for you?

[lore76b]

Hello, preview is disabled. the camera react, but (i don't know how to explain). If i set 4 it does 4, if i set 5 it does 5, if i set 6 it does 10 (number for explain). Il giorno gio 30 apr 2026 alle ore 16:39 Sebastian Staacks < ***@***.***> ha scritto:

…

*Staacks* left a comment (Staacks/alpharemote#27) <#27 (comment)> If you have a suggestion on how to do it :) The problem is that the camera does not react immediately to the keypress. On my camera it will not drive while the immediate preview of the taken picture is visible. To dismiss it as fast as possible I am sending a short half press, but the preview image still takes up a fraction of a second. Could you try if disabling the immediate preview changes the issue for you? — Reply to this email directly, view it on GitHub <#27 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/CC5NPJ562QFMZ5ZD3G44NKT4YNQSHAVCNFSM6AAAAACYMCZILSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DGNJTGM4TGNBXHE> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. You are receiving this because you authored the thread.Message ID: ***@***.***>

[Staacks]

I did some testing and I think I know what you mean.

First of all, for the case of long focus drive times, there is no issue, right? For reference, here are 5 second steps (which of course are way too long for any practical use):

https://github.com/user-attachments/assets/b07f27f2-6e4b-4959-aa43-54a5bda3969b
(0s interval timer, 5s focus move time)

Now, if I try to go with 1 second intervals, the moving time of the focus seems less consistent and there is actually a case where you can hear that the shutter is triggered earlier:

https://github.com/user-attachments/assets/cdcd87bb-da66-4d6a-a720-88badfeb0c43
(0s interval timer, 1s focus move time)

I think what's happening is that the camera cannot quite keep up until the point where the exposure has not yet started before my app checks if the exposure has already finished. You can see this also from the shutter state shown in the app, which flashes shorter and shorter until the hickup occurs. The solution for this is adding an additional second to the intervalometer setting. With this, the timing remains stable even for half second focus drive durations:

https://github.com/user-attachments/assets/72205c9e-0c3d-4027-b797-d9e5f7c5ff71
(1s interval timer, 0.5s focus move time)

However, at that point I find it hard to tell just how consistent the focus moving is at these short times. If this setting is not precise enough, I could try to change the order of the two time intervals, i.e. make the intervalometer pause before the focus bracket drive. This could help by allowing the camera to settle before simulating the focus-move button..?

(Sorry for the poor video quality. With my a6400 and my phone in the shot I had to resort to a GoPro, which is designed for pretty much the opposite of close-up narrowly framed shots in poor light.)

[lore76b]

Hello, i've read yourIn the meantime, I've created some code with Tasker that relies on your app.
I've done some testing, but I thought the values ​​you entered were (or are) in steps, not seconds (but I'm not entirely sure).

I noticed (in the case of my a7r3) that it started working when I inserted a micro-pause (about 300 ms) after the simulated button press.
But especially with my camera, I had to set a minimum base time of 4 seconds to allow the camera to write the photo to the card and be ready to accept the command that simulates pressing the focus advance button.

Essentially, the Tasker code works as if I were pressing the focus movement button (press and release, not hold).

I chose steps of 0.5 (I believe 0.1 and 1 are available as single movements).

For the code (you must have your a-remote app open and connected).

Then it asks you the number of shots, the number of pulses (AF button presses forward) between shots, and then asks how much delay (the default is "0," but it corresponds to a minimum of 4 seconds; if you leave it at zero, it's 4 seconds; if you need more for bulbs or other reasons, enter the time and it's added to the 4 seconds).

Once the cycle is complete, it returns the focus to its starting point.

If you'd like, I'd be happy to share it.

At 24mm, it works well. I haven't had time to try it at other focal lengths yet (like 70mm, where the pressure should have a greater shift).

PS: Your app is very good.
If you could, you could create an app like the exposure calculator (all you need is the shutter speed, ISO, and aperture, then you set the stops to add, and it gives you the shutter speed). Then, with a press of a button, you can trigger the camera with the calculated shutter speed.

That would be fantastic. It calculates and the bulb starts.

Especially with cameras like mine that don't have a built-in timer. answer.

START_STACK.tsk.xml

ne ho fatto anche uno per annullare

ma prova quello che ho mandato se vuoi, ciao

[Staacks]

Ah, I did not even think about the time the camera takes to write to the card. I rarely shoot RAW and with the smaller sensor resolution of my a6400, a fast SD card and a rather large cache size in the a6400 (compared to the sensor, I think) mine is usually ready immediately.

So, I have refine the focus bracketing sequence by switching the intervalometer pause and the focus movement. Setting the intervalometer interval now allows the camera to settle before doing the next focus movement.

I have just published it for F-Droid and Google Play, but it will be a few days before it is available (Google's review will probably be done on Monday and on F-Droid it depends on when the next build cycle starts, but it should also be available within the next days).

Let me know what you think when you received the update. (Version 1.3).

[lore76b]

Ok i Will test It. Have you analized my tasker code? And regarding the exposure calculator in the app, you think you can add the feature? Il ven 22 mag 2026, 01:10 Sebastian Staacks ***@***.***> ha scritto:

…

*Staacks* left a comment (Staacks/alpharemote#27) <#27 (comment)> Ah, I did not even think about the time the camera takes to write to the card. I rarely shoot RAW and with the smaller sensor resolution of my a6400, a fast SD card and a rather large cache size in the a6400 (compared to the sensor, I think) mine is usually ready immediately. So, I have refine the focus bracketing sequence by switching the intervalometer pause and the focus movement. Setting the intervalometer interval now allows the camera to settle before doing the next focus movement. I have just published it for F-Droid and Google Play, but it will be a few days before it is available (Google's review will probably be done on Monday and on F-Droid it depends on when the next build cycle starts, but it should also be available within the next days). Let me know what you think when you received the update. (Version 1.3). — Reply to this email directly, view it on GitHub <#27 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/CC5NPJ43PA42J3O55RJDLCD436EE3AVCNFSM6AAAAACYMCZILSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DKMJTGQ4TCMBYGA> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. You are receiving this because you authored the thread.Message ID: ***@***.***>

[Staacks]

Have you analized my tasker code?
I had a look at it and I am really excited to see the that the broadcast intents are actually used for something as complex as this :) For the focus bracketing feature, it is a sequence of triggers, focus moves and pauses. I think that the important part for this issue here is the delay (plus 4 seconds?) is happening after the trigger, which is now also the case with the new update. The thing missing in the new version is the delay that you set after the focus move. What problem occurs if you do not do that?

Asside from these, I do not think that I can simply take those values and use them as presets in the app, because these depend heavily on the lens, the camera and the settings. For example, I can run a focus sequence much faster on my camera (or maybe rather the settings I use).

And regarding the exposure calculator in the app, you think you can add the
feature?

It should not be to hard, but realistically I do not have the time to add larger things to the app any time soon :(