Communication issue between PyQt5 and Spinnaker

Answered

Luis Ezequiel Boero

• June 26, 2025 19:00

Hi,

I have been using a custom made GUI built on python for data and video acquisition (using Spinnaker SDK). For a long time I did not have any issues, but eventually I needed to migrate everything to a new computer with windows 11. Despite the GUI works fine, it eventually crashes (it can be after 2 minutes, or 2 hours, it's very stochastic), normally triggered by the GetNextImage function.

The code for my GUI is really long, but I am OK with sharing it. However, before moving there I am curious if there is any sort of incompatibility between my Spinnaker version and PyQt5 (or windows or my processor)

I currently have:
spinnaker-python 2.4.0.144 (with SpinView 4.2.0.83) (I tried having the same version of the spinnaker-python and spinview and still crashes, so I know is not that).

python 3.8.2

pyqt5 5.15.11

pyqt5-qt5 5.15.2

pyqt5-sip 12.15.0

pyqtgraph 0.13.1

qtpy 2.4.1

 

The computer has Windows 11, and the processor is AMD Ryzen 9 3900X 12-Core 64 GB RAM.

 

I don't necessarily believe that the crashing was due to Spinnaker, it can also be a PyQt5 issue, that's the reason why I am trying to disregard any incompatibility first.

 

Best,

 

0

• 

  TDY_Ifeanyi

  Community team

  • June 30, 2025 12:05

  

  

  Hello Luis,

  I wanted to reach out and see if you could provide any additional information regarding the issue. Are there any exception or error messages that occurred before the crash? 

  My understanding is that Spinnaker python wheel does not depend on any pyqt5 version, and I am not aware of any issue related to pyqt5 and spinnaker-python wheel.

  However, based on your previous message, I believe there might be incompatibility when using spinnaker-python 2.4.x with spinnaker sdk version 4.2. As a potential solution, I recommend performing a fresh installation with the spinnaker-python wheel designed for spinnaker sdk 4.2.0.83 and python 3.8 (i.e., spinnaker_python-4.2.0.83-cp38-cp38-win_amd64). This might help resolve the issue.

  If the issue persists, please don't hesitate to open a support ticket at http://flir.custhelp.com/app/ask. We can then schedule a remote session to further investigate and provide assistance.

  Regards,
  Ifeanyi

  0
• 

  Luis Ezequiel Boero

  • December 10, 2025 18:08

  Hi Ifeanyi,

  I updated the sdk version to the actual version and the issue persists, and despite being normally triggered by the camera, I found that it can also happen also in the absence of camera streaming. I'm also running now everything in a new version of ScopeFoundry and it still crashes, so I believe it is something related to the system not being able to cope with streaming and updating other data acquisition parameters at high frequency.

  Nonetheless, something I noticed is that if I use the spinnaker-python 4.2.0.88, when I compress the videos using MJPGOption and a quality of 75, the result is somehow quite pixelated. This also happens if I even try to record with the same parameters directly from spinview. Nonetheless, with the old version of spinnaker (2.4.x), the video does not get pixelated. Do you have an idea of why they are getting pixelated now?

   

  0
• 

  TDY_Ifeanyi

  Community team

  • January 09, 2026 09:04

  

  

  Hello Luis,

  Apologies for the late response. Can you open support ticket at http://flir.custhelp.com/app/ask to take a look on your implementation and provide assistance?

  0

Please sign in to leave a comment.