New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Push images via ZMQ #13
base: master
Are you sure you want to change the base?
Conversation
Cool, much better! |
there is no "optional" port.
60918c3
to
d3c01a0
Compare
By the way, are you going to do some benchmarking? I mean just pushing via ZMQ does not make packets fly magically faster over the wire. |
Of course I will. And sure, I don't expect zmq to be much faster. The point is rather that from python I can tell the server to stuff the images down the wire without actually needing to touch them in python. So far, on my laptop I get 4 GB/s with zmq and 5 GB/s with your streams, but I use python to receive the zmq which also slows things down I guess. I will make all kinds of tests later and example experiments in concert. |
there is no "optional" port.
which the client requests by setting number of images to 0.
4b5744b
to
0e6efcc
Compare
6f447b3
to
15e118e
Compare
15e118e
to
6dab21f
Compare
obsolete after letting client setting the endpoints.
* ucad: Add check for potential integer overflow * chore: ucad: Use correct type specifier * ucad: Use long type for number of frames * chore: Use glib types * ucad: Restore formatting consistency
Rationale
So far I have come up with this based on the dicussion here, summary:
handle_push_request
toucad
and re-uses the rest for control of the cameras (I don't see the necessity for a completely newucad-zmq
server)camera = Camera('net')
for controlasync
-basedcamera.grab_push()
, which can be added as a mixin or whatever else extension of the python camera objectUse case