Skip to main content
Raspberry Pi

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

5
  • I'm not very worried about the udp part nor the client (i don't want to control them by hand, they're controlled by a much larger project) but does compoundpi use something that takes near instant capture or does it also have a delay like raspistill? Commented Oct 6, 2014 at 13:17
  • Dave, it seems you're the author of projects that revolve around what i need, is there any chance we could have a Skype or email discussion? Commented Oct 6, 2014 at 13:18
  • Certainly - do feel free to email me directly (my e-mail address should visible on my GitHub profile) Commented Oct 6, 2014 at 13:21
  • 1
    Oh, and on your other question: it's near instant. When the compoundpi daemon is started it initializes and configures the camera (which is where a lot of delay in raspistill comes from) then awaits a capture command. The capture command can either instantly cause a capture or wait until a specified timestamp before capturing. In the instant case, the delay between receipt of command and capture should be milliseconds. Commented Oct 6, 2014 at 13:27
  • Dave Jones, this idea of initialising the camera before taking the capture, can you give more info? Can we do this from the commandline? Commented Mar 27, 2015 at 6:44