So my son started to do casual work and one of the job hes been doing is mistery shopping. Recently the company asked him to do video recording and as always I wanted to buy something that is ready to use off the shelf. The problem is that the chinese small "hidden cam" is not reliable and besides the poor quality it also didnt record a single file last time eventhough everything indicated it was up and running... So i decided to use a raspberry pi and convert it to a hidden body cam. Now I am a bit of stuck as there are multiple problems. 1, power. This seems to be alright with the pi4 the pi3b+ just kept giving me the low voltage message... 2, making the pi to record from the moment it powers up, make a 2 minute long loops videos ( this is in case of the battery cuts of or anything not a 10 minute long part is lost and in every2 minutes the pi makes a new file. with this part i dropped the ball as all i found is how to make one long video and start it manually instead of automatically and save the 2 min long files.
so my question if anybody can give me a link where this second problem is detailed like how to make raspi to record automatically till it shuts down or manually stopped?
I am realatively new to the raspberry pi as however I have 2 devices one of them was used to block ads in the network the other one was used to stream videos to the tv. so if i asked something that supposed to be obvius if you are a member here i apologize. Im just getting there.
As far as power, a Pi 0 is more than enough to do video with a lot longer battery life. Run MotionEye OS on it. I haven't looked at it in a while, but adding a start stop/save button should be simple.
First computer 1959. Retired from my own computer company 2004.
Hardware - Expert in 1401, and 360, fairly knowledge in PC plus numerous MPU's and MCU's
Major Languages - Machine language, 360 Macro Assembler, Intel Assembler, PL/I and PL1, Pascal, Basic, C plus numerous job control and scripting languages.
My personal scorecard is now 1 PC hardware fix (circa 1982), 1 open source fix (at age 82), and 2 zero day bugs in a major OS.
@zander hi and thank you for your reply. to be frank I posted this question and didn't see replies I just checked back in now to see as the notification ended up in spam:(
anyway thanks again. I do have an issue with motion eye, as if I run it on pi3b+ I set up correctly yet after starting the system I see 1 file and one file only. and I don't see multiple files regardless of the video file length set up. ( could it be because I have only a 4gb card in it) but I doubt as there is more than half of the storage available)
and motioneye os for some reason doesn't run on raspberry pi 4. I see there are many forums on the subject but I cant get it to work, so I'm still stuck with it.
@huskyg I am running it on a Pi ZERO. From the MotionEye menu choose resolution and then any other settings followed by the button to take a still or take a stream. Click save (top right of the image) as often as you have space for. I didn't know anyone was still using cards, configure a dirt cheap 1TB SSD or NVME (970 or 980) stick and you can shoot lots.
First computer 1959. Retired from my own computer company 2004.
Hardware - Expert in 1401, and 360, fairly knowledge in PC plus numerous MPU's and MCU's
Major Languages - Machine language, 360 Macro Assembler, Intel Assembler, PL/I and PL1, Pascal, Basic, C plus numerous job control and scripting languages.
My personal scorecard is now 1 PC hardware fix (circa 1982), 1 open source fix (at age 82), and 2 zero day bugs in a major OS.
@huskyg See issue 2925 re Pi4. The last entry will take you to issue 2953.
NOTE: Somewhere in those two issues it is mentioned that MotionEye is built for specific hardware configurations, so a 1GB memory Pi4B is different from a 2GB etc. Match up your Pi model to the correct image.
First computer 1959. Retired from my own computer company 2004.
Hardware - Expert in 1401, and 360, fairly knowledge in PC plus numerous MPU's and MCU's
Major Languages - Machine language, 360 Macro Assembler, Intel Assembler, PL/I and PL1, Pascal, Basic, C plus numerous job control and scripting languages.
My personal scorecard is now 1 PC hardware fix (circa 1982), 1 open source fix (at age 82), and 2 zero day bugs in a major OS.