If using my version of software with scheduler then there is a setting there Max_capture (default 30 seconds). Up that to whatever you like. The idea here was to both ensure one didn't get super long recordings in a security situation and it also allows fixed length recordings by setting the off command to nothing and letting the max turn it off.Hix wrote: I fear that I may miss something if the 30 second timeout persists.
0 wasn't infinite but is now. You could set a very large value before, now you can set 0.Hix wrote:Ahhhhh, completely missed the scheduler. Thanks Rob.
Assume 0 is infinite?
Ignore FIFO char means scheduler is receiving unexpected commands, probably because motion is not set up correctly. It should be sending just a 1 for start and a 0 for stop into FIFO1piecam wrote:HI Robert,
Just updated to newest version today. It looks that I can get a few recorded, but some are not.
I can see h264 raw file at time, then it's gone without being converted to MP4. Weird. Here's some log.
[2015/Mar/27 17:18:08] Stop capture request ignored, already stopped
[2015/Mar/27 17:18:08] Ignore FIFO char
[2015/Mar/27 17:18:29] Start capture requested
[2015/Mar/27 17:18:29] Send ca 1
[2015/Mar/27 17:18:32] Ignore FIFO char
[2015/Mar/27 17:18:52] Stop capture requested
[2015/Mar/27 17:18:52] Send ca 0
[2015/Mar/27 17:18:54] Ignore FIFO char
After the first install then all you should need to do is a .sh install followed by a .sh startHix wrote:Thanks dude.
Excuse my ignorance but is the correct way to do updates:
.m4.h264 files exist during and shortly after a recording. The raw .h264 data in them is then converted by MP4Box into a .mp4 file and the .h264 is then deleted. This can take a little while depending on the size of the recording which you will either see as video processing on the main screen if MP4Box is set true, or is done in the background if MP4Box is set to background. Either way you will see these .h264 files until MP4Box has completed processing.piecam wrote:see attached two files indicating that h264 raw file is gone. weird. How come have I got other files before?!
The illegal character log report is a problem with the default motion conf in the installerpiecam wrote:sorry, my mistake, it seems that you pi have this "on_event_start" and "on_event_end" both with FIFO1.
Then, what could be wrong?
It was a problem on the default motion.conf supplied with the install, but as I said it is harmless and just logs the unexpected LF.piecam wrote: Shoud I add manually "-n" into the command in your GUI? Is that something to do with some sort of typo on repo's script or something done by me inadvertently?
If it's typo on script side, then, I can do a git pull after you update your git repo.
please let me know. thanks
There is nothing in the system at the moment detecting and giving special treatment to short captures. There is a schedule setting that automatically stops recordings longer than Max_Capture (default 30 seconds) but that can be increased to give very long recordings. Once a capture stops they all go through the MPBox process if that is set to true, or background, no matter what the size of the video is. If MPBox config is set to false then MPBox is never called and you end up with just the raw .h264 files.piecam wrote:Hi Robert,
With regards to h264 not converting to MP4, I do see a new MP4 in the folder.
Then, I tested briefly by shaking my hand in front of cam, when I did see h264 file and
3112 ? 00:00:00 sh
3113 ? 00:00:01 MP4Box
3114 pts/0 00:00:00 ps
However, then, the h264 file is gone without new mp4 file. weird.
Or, is there a algorithm in script that says, I detect the motion, then, (after x seconds delay, due to current coding,) the recording starts; however, if recording h264 file doesn't have much motion in it, then it's deleted and not converted to MP4. This seems fitting that the brief movement triggers motion, however, after that, there's not much movement any more. This may explain the length of capture is variable to max 30 seconds. If this is true, it may means that algorithm tells raspimjpeg to delete existing h264 file and not bothering to convert to MP4, as there's no movement any more.
Or, once triggered, it will record for defined xxx seconds no matter there's any further motion at all. But, this doesn't match the variable length of time being captured.
Code: Select all
MP4Box -fps 25 -add /var/www/media/test.h264 /var/www/media/test.mp4
The wiki you put together helped me a lot getting going and I appreciate that otherwise it can be tough for people faced with 65 pages plus of material to know how to set things up so it suits them.jarrah31 wrote:Hi Robert,
I'm the guy who set up the wiki page on http://elinux.org/RPi-Cam-Web-Interface many moons ago, and having wondered back onto this thread to set up a new camera, I'm amazed at the fantastic work that you've done to improve the already excellent RPi Cam Web Interface!
I see that you reference the wiki from your github page, but as someone rediscovering this thread I'm unsure what I need to do to make use of your work, along with understanding all the benefits it brings without trawling though all the posts.
As a result, would you mind summarising your work, how to install/use, etc, on a post that I can then copy into the wiki as the first thing people see please? This would help not only myself but many others who see this popular thread to make the most of your brilliant work!
Code: Select all
git clone https://github.com/roberttidey/RPi_Cam_Web_Interface.git