Currently when a user starts a timed recording the duration is passed to modules as an argument - they then create a recording thread which checks when the duration has elapsed and stops recording.
It might be better to have the controller internally manage the duration and send out a stop_recording command when the duration has elapsed?
Due to internal delays in the module programs, there may be a small amount of discrepancy in when they stop recording. We can control for this to some degree by controlling when we send a start and stop command to all modules.
Currently when a user starts a timed recording the duration is passed to modules as an argument - they then create a recording thread which checks when the duration has elapsed and stops recording.
It might be better to have the controller internally manage the duration and send out a stop_recording command when the duration has elapsed?
Due to internal delays in the module programs, there may be a small amount of discrepancy in when they stop recording. We can control for this to some degree by controlling when we send a start and stop command to all modules.