Difference between revisions of "Timelapsebox"
From Eth0Wiki
(3 intermediate revisions by one other user not shown) | |||
Line 6: | Line 6: | ||
* open source only? so every conference / organisation can build one themselves | * open source only? so every conference / organisation can build one themselves | ||
+ | ** Debian minimal + mplayer | ||
+ | ** http://www.munz.li/?p=48 | ||
== Hardware options == | == Hardware options == | ||
Line 15: | Line 17: | ||
* Ultra low power option? | * Ultra low power option? | ||
* Wifi / lan uplink / rsync interface for an interface to see the timelapse/still image while the event is running | * Wifi / lan uplink / rsync interface for an interface to see the timelapse/still image while the event is running | ||
+ | |||
+ | == Available hardware == | ||
+ | * Failbaitr has a spare via eden mini-itx board 800mhz + 256mb ram |
Latest revision as of 22:05, 4 January 2017
The idea is to have a self contained box that anyone can build, and change that can be setup on a field / in a building before anyone else comes in. Starts taking pictures trough any and all connected webcams/camera's and stores a timelapse on its storage media.
This box would stay online during the entire event and easily and without any extra steering needed create a nice timelapse video for every connected camera.
Software options
- open source only? so every conference / organisation can build one themselves
- Debian minimal + mplayer
- http://www.munz.li/?p=48
Hardware options
- non exotic stuff
- laptop / atom / via mini-itx?
- ups / batteries for power?
Wanna haves
- Ultra low power option?
- Wifi / lan uplink / rsync interface for an interface to see the timelapse/still image while the event is running
Available hardware
- Failbaitr has a spare via eden mini-itx board 800mhz + 256mb ram