SonotaCo.JP

[Vesper]

Hello,

My name is Pierre and I'm an amateur astronomer from France.

I'm currently testing UFOCaptureIP 512 (I tested also v.511). I encounter a problem. First of all my configuration is as follow :

- camera Corona Borealis Fireball IMX 662 : 1920*1080, 60 fps day, 25 fps night.
2Mp Imx662 IP Camera 60Fps Starlight Meteor Detection Night VisionGMN Rtsp Ip66 Outdoor Astrophotography Camera;

- Windows 11 PC Ryzen 5-7430U, 16Go /512Go

Both UFOCapture 511 or 512 run smoothly. The problem is :

UFOCaptureIP stops after a detection has been made and doesn’t resume (neither the detection nor even the “preview,” which remains frozen). To resume detection, I have to click “Preview” again and then “Detect" again. Is this normal? Is this a limitation due to the fact that it’s the demo version, and will it be removed once the license is purchased?

Also, I’ve carried out some very thorough tests and I now believe I can say with certainty that neither the camera nor the RTSP stream is at fault. Unfortunately, it seems that UFOCaptureIP is the problem.

In summary:
1- UFOCaptureIP receives the stream;
2- it detects an event;
3- it records correctly;
4- the recorded video file can be viewed in the “Preview” section;
5- the capture engine stops silently;
6- the preview freezes;
7- the CPU usage of “UFOIP” drops to 0 per cent.
This points to UFOCaptureIP itself, more specifically its handling of the transition:
“end of capture → closing the file → resuming stream analysis”.

After that and among other things, I carried out the following experiment: using an RTSP proxy (MediaMTX) between the camera and UFOCaptureIP. This allowed me to completely decouple the camera from the software and see whether the problem stems from the way UFOCaptureIP handles the RTSP connection after a detection.
The result was that the problem stays the same.


Many thanks in advance for any help.

Clear skies,
Pierre