You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is a minor complaint but it looks like it takes a frame or two for the LED to turn on once the recording has been triggered by an external source, so the first frame is black. Currently I can work around this by manually turning on the LED via the GUI slider after enabling external triggering.
The text was updated successfully, but these errors were encountered:
I hadn't thought about this but makes sense. New commands sent to a Miniscope are only executed at the end of each frame. The software toggles on recording and sends the command to turn on the LED at the same time. The first recorded frame is sent from the Miniscope before the Miniscope executes the command to turn on the LED.
I will modify the code to throw out received frames before the LED command is sent and executed. Does this seem like a good solution?
Another reason for the delay is the DAQ only sends the external trigger state to the software at the end of each frame acquisition.
I guess the proper way of handling all this is to handle triggering the LED and recording in the DAQ hardware and not in the software. This is a little bit trickier to implement but I will try to get around to it sometime soon.
Either of those sound like fine solutions, though the second one sounds ideal. It is also not a huge deal because I can similarly throw out the first frame during post-processing.
This is a minor complaint but it looks like it takes a frame or two for the LED to turn on once the recording has been triggered by an external source, so the first frame is black. Currently I can work around this by manually turning on the LED via the GUI slider after enabling external triggering.
The text was updated successfully, but these errors were encountered: