Closed mullenba closed 2 years ago
I don't see any issues with your code, but I would suggest you run the PUB / SUB example programs from the examples folder. Docs and links to code are here.
Please try that and let me know what happens. I know that this pair of example programs works. Of course, you'll need to change your TCP address in the receiver appropriately.
The test_4 example works.
Doing more experimenting, it appears to be on the receive side. If I start the sender, then start the receiver with nothing in front of the camera, I see the frame of the empty space. If I then close the receiver and put my hand in front of the camera, restarting shows my hand.
If I let it run for a long time and occasionally move my hand in front of the camera, it does seem to be changing, one frame every few seconds on about a minute delay.
I'm working with a Raspberry Pi and Windows desktop, and happens in both Windows and Ubuntu WSL.
Looks to be an issue with imutils VideoStream. Replacing it with a direct call to picamera and sending that works fine.
Thanks for the update. I have heard other reports of imageZMQ users resorting to direct calls to picamera after having issues with imutils VideoStream. For example see this issue an imagenode / imageZMQ user had with imutils VideoStream: imagenode issue 15.
When I convert the basic demo from the repo's main page to Pub/Sub, the receiving computer shows the first frame, then doesn't change. The demo as written works fine.
I've tested that the loops are running, but the frame image doesn't change.
Sender:
Receiver: