When imaging with variable gain CMOS cameras, exposure times can vary quite a bit depending on the filter. During a given observation night, one could be imaging in a broadband filter with as short as 30s exposures and then switch to a 3nm narrowband filter requiring 300+ secs. In such a scenario, it is common to dither every x minutes to cap session overhead. For example, every 3 minutes, resulting in every 6 frames while in broadband, but every frame when in narrow.
The current implementation requires manual change of the parameter and I also noticed potential for instability when changing the parameters during a session, in the form of dithering not being triggered.
It would be great to have it as a parameter for a given Capture sequence filter Job, or at least have the ability to change the setting programmatically via a script that could be run at job start/end for a given filter.

I second this request.
I think it would be nice to have it dither every X minutes instead of Y frames.

Coming back to this,
a possible workaround that I am trying to implement is to disable automatic dithering, and use DBus to trigger a manual dither after a capture job.
I was able to trigger the dither, but that is not enough because Capture will not be paused waiting for a settle.
The next step would be to implement the following script, and I have the questions indicated in red below for any developer who is so kind as to take a look:
1) Suspend Capture: for this, what's the difference between the Suspend and Pause methods in DBus?
2) DIther
3) Subscribe to the newStatus or newLog signals of Guide and wait for the settle signal, with a timeout similar to the default ekos implemetation. What I am looking for is the "Dithering completed successfully." log. Can you confirm that this corresponds to the variant newStatus with a value of 18? In the guide.cpp I see that these are constants, but I'm having a hard time to find the #ðefines for these.
4) Wait for any additonal amount of time as set in the global KStars guiding settle option (not the Guide one)
5) Resume Capture
Does this sound right?
It would clearly be great if we could at least get the dither every #n frames setting exposed as a DBus property that we can change programmatically: I'm not sure, but it could be easier on the devs than my original request of having the option as a per-job property of a sequence?
Thanks!

Yes, I think this feature could help.
Sometimes I mix long exposures sequences with lucky imaging technique (1-3 seconds of subframe) and if I forget to change the dither setting, I spend more time to dither than imaging

This was added quite recently....



It allows you to override the global dither setting per job.