I assume we're talking about raspistill (for images) rather than raspivid (which is for video). Anyway, the timelapse mode in raspistill simply keeps track of a running clock and captures when it reaches the appropriate time. It also knows when it's missed a frame (have a look here for the details).Arp wrote:Hi,
I plan to let raspivid run over the weekend. I want it to directly save the images onto my owncloud server. I would create a folder and mount it as webdav folder so everything goes automatically into the cloud. Now, I dont know how fast the internet connection will be. Could take a couple of seconds. My question is, when raspivid captures an image, does the waiting start after the file is saved, or is this done in parallel.
For example, if I capture every 10 seconds, but it takes 15 seconds to save the file on the remote folder, does it actually wait 15 seconds, or will it start the next exposure while the old one is saving?
Yes, must admit I was assuming the OP was on wifi - but ethernet should handle it.towolf wrote:Well, personally I’ve been writing full 5mp jpegs per second (or rather 1.2s on average) onto NFS for a month or so. But that is on Gigabit Ethernet. That amounts to 120G of jpegs per day that are cooked down to H264 every morning over a few hours. All because the FoV is not wide enough in video mode.
Code: Select all
#!/usr/bin/python import os import time # define constants incomingdir="" targetdir="" # start infinite loop while True: # see if new images have arrived in incomongdir and copy them to targetdir for files in os.listdir(incomingdir): if files.endswith((".jpg", ".JPG")): print files shutil.copy(incomingdir+"/"+files, targetdir+"/"+files) time.sleep(.5)