Rendering Error in layout Message/Item: array_keys(): Argument #1 ($array) must be of type array, null given. Please enable debug mode for more information.
Do you want to receive the buffer or just save to disk? 500 ms is indeed quite long for a 20ms exposure. Assuming you're using latest INDI with FAST blob support, you should be getting very quick results. However, I don't think pyindi was actually updated to take. I opened a
new issue
to see if this be supported.
The tutorial needs some updates as well... any volunteers that'd like to edit and maintain it to current standards?
Rendering Error in layout Message/Item: array_keys(): Argument #1 ($array) must be of type array, null given. Please enable debug mode for more information.
Ok, thank you fo the advices.
I'll finish the other parts of the project and then I'll decide if waiting or creating a C++ extension (that could take some time as well ).
Benjamin
I seem to have the same problem, only the blobEvent.wait() doesn't take 500ms for me, but it goes on forever just like an endless loop..
Also, this problem seems to come and go, and I can never understand why, or what has changed for it to suddenly work again.
Were you ever able to fix your long acquisition problem ?
On my side it is long but regular (except for the first acquisition that car take a little bit more, about 20% more time). I do not have, as you, changes in the acquisition time or endless loop.
I didn't resolved this problem, for the moment this is "almost sufficient" for my projet that just need 5 to 10 Hz acquisitions and I reached 3 Hz.
I'm working on a python library that call a c++ client that just take an image and send it to the python software. I hope it will help.
For the acquisition time, I understood that using only python, the only way it to wait for the libindi library to be updated.