Inference is slow enough that the resultant FPS of the recording is significantly lower than we probably want it to be. Need to resolve. Solution will probably require a threaded class that owns both the camera capture and the recording that also encapsulates the timelapse mechanics, probably also the mechanics that keep recording on after an event and turn it off after a set period has elapses, and only receives from the high-level detect_track_zoom triggers to initiate full FPS recording stints.
This class can almost definitely use the existing ImageStreamRecorder as an attribute. Maybe it does the same with the Camera class.
It would have to be able to provide frames to the main code for inference as the Camera object does.