Description
I use the 'im' command to capture an image file in the scheduler settings at a particular time of day.
This only works if a timelapse capture is not active also.
Steps to Reproduce
- Make sure a timelapse is not shown running on the main preview screen.
- In the RPi_web_cam_interface, go to "Edit Schedule Settings".
- Now set up a command to use the "im" command in the currently active "Period Start" action.
- Push "Save Settings", which will cause the "im" command to execute.
- Click the top link back to the main preview page.
- Click "Download Video and Images".
- Look for the latest Image file and it should be the picture that was just captured in step 4 above.
- Now, go back to the main screen and start a timelapse capture running.
- go to "Edit Schedule Settings".
- Verify that the im command is still present for the active period.
- Push "Save Settings", which will cause the "im" command to execute.
- Go back to main preview screen and click "Download Video and Images" again.
- You will see that this time the image has not been added. Instead, it will have been erroneously saved as an additional timeslice file in the timelapse sequence.
Expected Behavior
If an 'im' command is executed during a timelapse capture, it should save a separate image file and not interfere with the timelapse sequece of images that are being captured.
Additional Information (Optional)
Viewing the python code shows that the capture_still_image function behaves differently based on a state flag that indicates a timelapse is being captured.
But this behavior is only relevant when capture_still_image is called by the timelapse logic, not when processing the 'im' or 'ix' commands.
Pi Model
5
Operating System
Any Raspbian (9.x or older)
Checks
Description
I use the 'im' command to capture an image file in the scheduler settings at a particular time of day.
This only works if a timelapse capture is not active also.
Steps to Reproduce
Expected Behavior
If an 'im' command is executed during a timelapse capture, it should save a separate image file and not interfere with the timelapse sequece of images that are being captured.
Additional Information (Optional)
Viewing the python code shows that the capture_still_image function behaves differently based on a state flag that indicates a timelapse is being captured.
But this behavior is only relevant when capture_still_image is called by the timelapse logic, not when processing the 'im' or 'ix' commands.
Pi Model
5
Operating System
Any Raspbian (9.x or older)
Checks