Cole Gerdemann

Actually I think it is a slightly different issue since I'm pretty sure the Picamera2 class isn't meant to be started after being closed, it needs to be re-initialized. But...

Appreciate it, if you have any further questions let me know. I will dig in to the library a bit myself if I have time

That files with a completely different error, probably stemming from the same bug though: ``` [3:10:29.493452382] [4627] INFO Camera camera_manager.cpp:293 libcamera v0.0.0+3866-0c55e522 [3:10:29.524751075] [4628] WARN RPI raspberrypi.cpp:1258 Mismatch between Unicam...

I see. For now we are completely re-initializing the picamera object in between photos but this is not ideal. Are you guys planning to implement this in the future?

Exciting, thank you! If you need any help with anything let me know

That is great news... I took a look at the relevant commits. I'll see if I have time to give it a go this Friday, but if not I'll make...

I can confirm the original test script for this bug report now functions! Additionally, I've also tested a few other cases including taking simultaneous videos (which works!): ```python3 import time...

Were tests introduced to ensure there are no regressions for this in the future? I see this commit https://github.com/raspberrypi/picamera2/commit/86b2981aa196ba3858cf138d7f2318c4269cc247 which I think would test this functionality (multi-threading specifically), but wasn't...

that is extremely helpful. Is there an easy strategy to derive the blue and green color gains for a target colour temperature? I know that math is done internally somewhere...

That actually might be preferable. Goal is to pre-compute this ahead of time without much hardware access.