johng
Posts: 41
Joined: Thu Apr 23, 2015 10:00 am

Re: RPi Cam Web Interface

Wed May 20, 2015 7:37 pm

btidey wrote:
johng wrote: Many thanks for your help. I think you're right. It's running on one of those BT extender things which is the only way that I can get ethernet outside the house and it had started to run really slowly (ping round trip approx 600ms). Have rebooted everything and now back running at good speed, almost the same as direct ethernet connection.
Having said which, I've left it running this morning saving to the SD card per default to get a comparison and I'll put it onto the windows share later. Will look through logs to get an example of boxing overflow.
I also tried turning off boxing by changing MP4 Boxing Mode to false via the browser. It continued to produce MP4 files rather than h264 but the files were unreadable (Windows media viewer, Quicktime and VLC viewer all rejected them). If I change MPBox4 in raspimjpeg to False does this do the same thing or will I get h264 files (which I can then bulk convert)? Presumably this would also kill the iframe errors?

Thanks again, Johng
Changing Boxing mode should be the same from either browser control or raspimjpeg and seems to work for me. I can chnage in the browser, run a file and change it back again and end up with an h264 file. There was a 'feature' that unboxed files could still get labelled as .mp4 even though they weren't. That has been changed in recent versions after 5th May.

One little trick that might be possible to help in situations like this is to use the macro facility to run a script after capture end commands. This can be done in the scheduler. This way you could always capture locally and then copy with the macro to its final destination.
I must be running a pre May 5th version; renamed the offending files to h264 and boxed them to readable mp4s successfully. I can add the renaming into my conversion batch file so it's all one operation. I'll try the new version (with backups) which should make the renaming unnecessary.

Good idea with the macro trick but probably beyond my competence and would need a bit of research at my end so I'll stick with boxing later on the shared disk.

On the inframe issue, I saved to the SD card all this morning including background boxing and all is clean with no iframe errors. I transferred back to the windows share this evening with boxing turned off and I am getting iframe errors in the log. (Curious; I thought they were connected with the boxing).

So it does look as if, in my case, it's a timing issue caused by the network delay. I am trying to get my head round what happens but presumably it's
1. write h264 to shared drive
2. either keep a copy in memory at the pi or read a copy back to pi
3. box at pi
4. write boxed mp4 to shared drive
5. delete h264 on shared drive.

I gather the new version has additional debugging info logged; I can produce iframe errors at will so if logs would be useful, let me know. I could do with boxing enabled and disabled.

I won't be able to update to the new version until late this evening as I'm currently copying today's mp4s from the SD card (I don't have access to it as it's in a nestbox).

btidey
Posts: 1623
Joined: Sun Feb 17, 2013 6:51 pm

Re: RPi Cam Web Interface

Wed May 20, 2015 8:22 pm

johng wrote: On the inframe issue, I saved to the SD card all this morning including background boxing and all is clean with no iframe errors. I transferred back to the windows share this evening with boxing turned off and I am getting iframe errors in the log. (Curious; I thought they were connected with the boxing).

So it does look as if, in my case, it's a timing issue caused by the network delay. I am trying to get my head round what happens but presumably it's
1. write h264 to shared drive
2. either keep a copy in memory at the pi or read a copy back to pi
3. box at pi
4. write boxed mp4 to shared drive
5. delete h264 on shared drive.

I gather the new version has additional debugging info logged; I can produce iframe errors at will so if logs would be useful, let me know. I could do with boxing enabled and disabled.

I won't be able to update to the new version until late this evening as I'm currently copying today's mp4s from the SD card (I don't have access to it as it's in a nestbox).
Actually that's interesting about iframe dependency on network delay as silvan has a theory on cause of iframe errors and extra delays in writing h264 buffers making the problem worse would fit in with this theory.

On the process for recording and boxing, as far as the Pi is concerned it is all local files as the mount hides the fact that the files are actually somewhere else. So your steps are effectively correct but the Pi process doesn't know its a shared folder elsewhere.

The process is actually (ignoring the circular buffer)
1. Start capture command with camera MMAL
2. Open h264 file
3. Accept callbacks from the camera software each containing a buffer of h264 data and write to the file.
4. Stop capture with Camera MMAL
5. Close h264 file and queue a request to box this h264 file

Separately the foreground loop is checking the box queue and kicking off a command which converts the h264 file to mp4 and deleting the original h264. As soon as this completes the next item in the boxing queue is started if there is one.

So the capturing of the raw data to h264 is time critical, and this is where iframe errors would occur, but the boxing is not particularly time critical unless the network is too slow to allow it to keep up with captures.

johng
Posts: 41
Joined: Thu Apr 23, 2015 10:00 am

Re: RPi Cam Web Interface

Wed May 20, 2015 9:27 pm

btidey wrote:*** Important ***
I have pushed a largish change. It seems OK but be prepared, you may need to revert. One way to do this is just to keep a local copy of the changed files before upgrading. These are (index and config php in www folder, script.js in www/js folder, the raspimjpeg binary in opt/vc/bin, and the raspimjpeg config in /etc..
For the avoidance of doubt, is this index and config.php and script in /var/www or in RPi_Cam_Web_Interface/www? I would have thought that the latter are installation copies and the former active copies. They are both the same on mine but may be different on others...

User avatar
jbeale
Posts: 3498
Joined: Tue Nov 22, 2011 11:51 pm
Contact: Website

Re: RPi Cam Web Interface

Thu May 21, 2015 3:16 am

Thanks for the continued progress on this program! I just updated four Pi's (Model A, Model A+, 2x Model 2) to the latest version and will report if I see any i-frame problems. FWIW, I selected internal motion detection and view motion vectors on one device, then found I was unable to turn off display of motion vectors, turning the feature off from the web page had no effect (tried both Firefox and Chrome). I had to manually edit /var/www/uconfig to restore the original settings.

kevw
Posts: 22
Joined: Wed Aug 27, 2014 1:49 pm

Re: RPi Cam Web Interface

Thu May 21, 2015 8:16 am

btidey wrote:
jbeale wrote:
kevw wrote:I was looking at the sensor region to isolate a area in the frame but it doesn't seem to work as expected. I did a test W & H of 500 x 500 and tried 'moving' this around with the X & Y but I got strange results in that the area didn't move..same for a smaller 100x100 W&H - I was expecting to be able to move the small window around the FOV
I had the same experience; as far as I can tell, the sensor region option has no effect.
This is true. We send the values into the camera interface but I don't think we really know what to expect here.
Thanks for confirming you had the same results - will this be fixed sometime in the whenever or does it make sense to remove the fields from the UI?

Cheers,

Kev

silvanmelchior
Posts: 76
Joined: Mon Nov 25, 2013 5:56 pm

Re: RPi Cam Web Interface

Thu May 21, 2015 8:25 am

kevw wrote:
btidey wrote:
jbeale wrote: I had the same experience; as far as I can tell, the sensor region option has no effect.
This is true. We send the values into the camera interface but I don't think we really know what to expect here.
Thanks for confirming you had the same results - will this be fixed sometime in the whenever or does it make sense to remove the fields from the UI?

Cheers,

Kev
It would be good if somebody knows what should happen and if it works in raspivid/raspistill for example.

ethanol100
Posts: 586
Joined: Wed Oct 02, 2013 12:28 pm

Re: RPi Cam Web Interface

Thu May 21, 2015 8:57 am

I think the Sensor Region works as expected, but I would like to call it digital zoom.

You need to put in values form 0-65536
i.e. if you want to have it only to display the lower right quarter, you would set it to
x=32768 y=32768 w=32768 h=32768
corresponding to 0.5,0.5,0.5,0.5 in raspistill.

We need to be careful about the aspect ratio of the selected image and the selected sensor mode. And I am not sure which FOV is used for what...

We need to select the starting point in the whole frame, i.e. if we want to crop an image of 640x480 out of the full image. Where the upper left corner should start at 300x200 in the Std FOV mode(1920x1080), we would choose:
Video res=640x480
x=(300-(1920-1080*4/3)/2)/1080/4*3*65536= 2731
(By requesting a different aspect ratio, the initial image is a central crop, cutting (1920-1080*4/3)/2 px on each side)
y=200/1080*65536=12136
h=480/1080*65536=29127
w=640/1080/4*3*65536=29127

Hope this helps.

Edit: had subtracted the crop at the wrong place for x...
Last edited by ethanol100 on Thu May 21, 2015 9:32 am, edited 1 time in total.

btidey
Posts: 1623
Joined: Sun Feb 17, 2013 6:51 pm

Re: RPi Cam Web Interface

Thu May 21, 2015 9:20 am

jbeale wrote:Thanks for the continued progress on this program! I just updated four Pi's (Model A, Model A+, 2x Model 2) to the latest version and will report if I see any i-frame problems. FWIW, I selected internal motion detection and view motion vectors on one device, then found I was unable to turn off display of motion vectors, turning the feature off from the web page had no effect (tried both Firefox and Chrome). I had to manually edit /var/www/uconfig to restore the original settings.
The vector preview works for me providing, I use the mjpeg streaming mode. Chrome for some reason cancels the request to fetch the individual vector jpgs in default mode. I think this may be related to the jpegs being quite small; the vector images are around 120 x 68 in size. However, even though it wasn't updating in default mode I could still switch on and off. As it stopped doing that it sounds like raspimjpeg was frozen for some reason. Did the log show anything?

btidey
Posts: 1623
Joined: Sun Feb 17, 2013 6:51 pm

Re: RPi Cam Web Interface

Thu May 21, 2015 9:23 am

ethanol100 wrote:I think the Sensor Region works as expected, but I would like to call it digital zoom.

You need to put in values form 0-65536
i.e. if you want to have it only to display the lower right quarter, you would set it to
x=32768 y=32768 w=32768 h=32768
corresponding to 0.5,0.5,0.5,0.5 in raspistill.

We need to be careful about the aspect ratio of the selected image and the selected sensor mode. And I am not sure which FOV is used for what...

We need to select the starting point in the whole frame, i.e. if we want to crop an image of 640x480 out of the full image. Where the upper left corner should start at 300x200 in the Std FOV mode(1920x1080), we would choose:
Video res=640x480
x=300/1080/4*3*65536-(1920-1080*4/3)/2=13413
(By requesting a different aspect ratio, the initial image is a central crop, cutting (1920-1080*4/3)/2 px on each side)
y=200/1080*65536=12136
h=480/1080*65536=29127
w=640/1080/4*3*65536=29127

Hope this helps.
That is a great help in understanding. I hadn't dug into this much and had assumed the values were pixels. We can now look to a) see if this works anyway, and b) whether we need to adjust callback handling in the light of the changed sizes.

Gary Littlemore
Posts: 327
Joined: Thu Oct 11, 2012 11:52 am
Location: Cheshire, UK

Re: RPi Cam Web Interface

Thu May 21, 2015 11:56 am

I'll give this a try later tonight....
silvanmelchior wrote:For those of you who are testing the new version of motion detection, it would be good if you could give feedback how good it is working for you, so we can develop a better version.

And to those of you who are struggling with the iframe errors: I'm trying to fix the problem for weeks now without success, so if anybody has an idea what could be the problem, please contribute to the discussion on github: https://github.com/silvanmelchior/RPi_C ... /issues/56
The problem is that the occurence of the error is very rare and everytime I made a fix I need to wait many hours until I get a result. So I'm sorry that there is no fix at the moment, but I'm trying.
3b+, 2b, b+, b, Zero & Zero-W

btidey
Posts: 1623
Joined: Sun Feb 17, 2013 6:51 pm

Re: RPi Cam Web Interface

Thu May 21, 2015 12:47 pm

I have pushed a change to the internal motion detection to support the mask file which previously was not activated. That was important for me to start to try to use this for real as I need to exclude traffic motion from a corner of the image.

There are now some basic details on the internal motion detection in the wiki including some info on creating mask files.

One bit that may be useful to anybody experimenting with the internal detection is two new annotation variables. These were already present. They can be included in the annotation string and will then give a live update on what the detector is doing. %f is currently giving a changed frame count and %c is giving the changes within a frame. We will continue to use those variables although their meaning may change as the detection algorithm evolves.

User avatar
jbeale
Posts: 3498
Joined: Tue Nov 22, 2011 11:51 pm
Contact: Website

Re: RPi Cam Web Interface

Thu May 21, 2015 1:58 pm

Here's a log file snippet showing iframe errors using the latest code (as of 10 hours ago anyway). Was it was trying to record a long video around 3 am, during the middle of the night when it shouldn't have been recording anything? The scheduler was set to only record during daytime, it's never had this type of failure before. The full log is attached as a zip file.

Code: Select all

[2015/05/21 02:53:39] Scheduled management tasks. Next at 1432202379
[2015/05/21 02:54:09] New period detected 2
[2015/05/21 02:54:09] Send md0
{2015/05/21 02:54:09} External motion detection stopped
{2015/05/21 02:54:09} DEBUG 3
[2015/05/21 02:54:11] Send md 1
{2015/05/21 02:54:11} External motion detection started
{2015/05/21 02:54:12} DEBUG 3
[2015/05/21 02:54:13] Send em night
{2015/05/21 02:54:13} Change: exposure_mode = night
[2015/05/21 02:54:16] Start capture requested
[2015/05/21 02:59:40] Scheduled management tasks. Next at 1432202740
[2015/05/21 03:05:41] Scheduled management tasks. Next at 1432203101
[2015/05/21 03:11:42] Scheduled management tasks. Next at 1432203462
[2015/05/21 03:17:43] Scheduled management tasks. Next at 1432203823
[2015/05/21 03:23:44] Scheduled management tasks. Next at 1432204184
[2015/05/21 03:29:45] Scheduled management tasks. Next at 1432204545
[2015/05/21 03:35:46] Scheduled management tasks. Next at 1432204906
{2015/05/21 03:36:19} DEBUG 2: 3983, 4226
{2015/05/21 03:36:19} Error: Error in iframe list
{2015/05/21 03:36:19} DEBUG 2: 3984, 4226
{2015/05/21 03:36:19} Error: Error in iframe list
{2015/05/21 03:36:19} DEBUG 2: 3985, 4226
{2015/05/21 03:36:19} Error: Error in iframe list
{2015/05/21 03:36:19} DEBUG 2: 3986, 4226
{2015/05/21 03:36:19} Error: Error in iframe list
{2015/05/21 03:36:19} DEBUG 2: 3987, 4226
{2015/05/21 03:36:19} Error: Error in iframe list
{2015/05/21 03:36:19} DEBUG 2: 3988, 4226
{2015/05/21 03:36:19} Error: Error in iframe list
{2015/05/21 03:36:19} DEBUG 2: 3989, 4226
{2015/05/21 03:36:19} Error: Error in iframe list
{2015/05/21 03:36:19} DEBUG 2: 3990, 4226
{2015/05/21 03:36:19} Error: Error in iframe list
{2015/05/21 03:36:19} DEBUG 2: 3991, 4226
{2015/05/21 03:36:19} Error: Error in iframe list
{2015/05/21 03:36:19} DEBUG 2: 3992, 4226
{2015/05/21 03:36:19} Error: Error in iframe list
{2015/05/21 03:36:19} DEBUG 2: 3993, 4226
{2015/05/21 03:36:19} Error: Error in iframe list
{2015/05/21 03:36:19} DEBUG 2: 3994, 4226
{2015/05/21 03:36:19} Error: Error in iframe list
{2015/05/21 03:36:19} DEBUG 2: 3995, 4226
{2015/05/21 03:36:19} Error: Error in iframe list
{2015/05/21 03:36:19} DEBUG 2: 3996, 4226
{2015/05/21 03:36:19} Error: Error in iframe list
{2015/05/21 03:36:20} DEBUG 2: 3997, 4226
{2015/05/21 03:36:20} Error: Error in iframe list
{2015/05/21 03:36:20} DEBUG 2: 3998, 4227
{2015/05/21 03:36:20} Error: Error in iframe list
{2015/05/21 03:36:20} DEBUG 2: 3999, 4227
{2015/05/21 03:36:20} Error: Error in iframe list
{2015/05/21 03:36:20} DEBUG 2: 4000, 4227
{2015/05/21 03:36:20} Error: Error in iframe list
{2015/05/21 03:36:20} DEBUG 2: 4001, 4227
{2015/05/21 03:36:20} Error: Error in iframe list
{2015/05/21 03:36:20} DEBUG 2: 4002, 4227
{2015/05/21 03:36:20} Error: Error in iframe list
20150521-070855-scheduleLog.zip
log file showing iframe errors
(2.91 KiB) Downloaded 61 times

btidey
Posts: 1623
Joined: Sun Feb 17, 2013 6:51 pm

Re: RPi Cam Web Interface

Thu May 21, 2015 2:13 pm

jbeale wrote:Here's a log file snippet showing iframe errors using the latest code (as of 10 hours ago anyway). Looks like it was trying to record a long video around 3 am, during the middle of the night when it shouldn't have been recording anything. The scheduler was set to only record during daytime, it's never had this type of failure before.
Thanks that helpful.

The scheduler said that it was changing to a new day period just before kicking of motion detection wich then started the recording. A period change at that time sounds weird. Is the clock and scheduler settings correct?

User avatar
jbeale
Posts: 3498
Joined: Tue Nov 22, 2011 11:51 pm
Contact: Website

Re: RPi Cam Web Interface

Thu May 21, 2015 2:32 pm

I don't think the scheduler should have done that, settings were as below

Image
https://lh6.googleusercontent.com/-degN ... 0%2BAM.jpg

...wait, apparently "DAWN START" is -180 minutes, or a rather generous 3 hours before sunrise which would be 2:53 am, and that is indeed when the mode shift happened. Did I enter that number, or is it the default?

btidey
Posts: 1623
Joined: Sun Feb 17, 2013 6:51 pm

Re: RPi Cam Web Interface

Thu May 21, 2015 3:32 pm

jbeale wrote:I don't think the scheduler should have done that, settings were as below

Image
https://lh6.googleusercontent.com/-degN ... 0%2BAM.jpg

...wait, apparently "DAWN START" is -180 minutes, or a rather generous 3 hours before sunrise which would be 2:53 am, and that is indeed when the mode shift happened. Did I enter that number, or is it the default?
180 is the default. Probably a bit generous and more suited to higher latitudes where dawn and dusk are more extended.

The times do look OK now. I had forgotten that the period numbers had moved on by 1 when I put in the all day mode. So 2 is dawn rather than day I thought at first.

With the scheduler set up is turning on motion detect during dawn but not passing through capture commands. You can see a capture request coming into scheduler but it doesn't request a capture.It is the motion detect going on that has made raspimjpeg prone to iframe errors at that point even without a capture as it is is capturing to the buffer in anticipation.

So the log makes sense now. We just have to root out the iframe errors and I think there is at least some ideas on that front.

User avatar
jbeale
Posts: 3498
Joined: Tue Nov 22, 2011 11:51 pm
Contact: Website

Re: RPi Cam Web Interface

Fri May 22, 2015 3:09 am

current version of the software (as of today, 5/21/2015) seems to have a problem on my Model A (although it works OK on a Model A+ and two different Model 2s). My Model A keeps getting locked up, even after a reboot, and even after a power cycle. I haven't physically touched it since it has been working mostly OK for months on older software. I don't think it's a hardware issue specific to this unit.

Code: Select all

{2015/05/21 19:16:40} RaspiMJPEG Version 5.2.1
{2015/05/21 19:16:41} MJPEG streaming, ready to receive commands
{2015/05/21 19:16:41} send smd 9
[2015/05/21 19:17:39] RaspiCam support started
[2015/05/21 19:17:39] Capture Pipe already exists /var/www/FIFO1
[2015/05/21 19:17:39] Scheduler loop is started
[2015/05/21 19:17:39] Reload parameters command requested
[2015/05/21 19:17:39] Scheduler loop is started
[2015/05/21 19:17:40] New period detected 3
[2015/05/21 19:17:40] Send md 1
{2015/05/21 19:17:41} External motion detection started
[2015/05/21 19:17:42] Send em auto
{2015/05/21 19:17:42} Change: exposure_mode = auto
[2015/05/21 19:17:44] Scheduled management tasks. Next at 1432261300
[2015/05/21 19:17:44] Purged 1 Files
[2015/05/21 19:21:39] Start capture requested
[2015/05/21 19:21:39] Send ca 1
{2015/05/21 19:21:40} Capturing started
[2015/05/21 19:21:41] Scheduled management tasks. Next at 1432261541
[2015/05/21 19:21:46] Stop capture requested
[2015/05/21 19:21:46] Send ca 0
{2015/05/21 19:21:46} Error: Could not enable connection splitter -> video converter
{2015/05/21 19:21:47} RaspiMJPEG Version 5.2.1
{2015/05/21 19:21:47} Error: Could not enable camera
[2015/05/21 19:21:48] Start capture requested
[2015/05/21 19:21:48] Send ca 1
{2015/05/21 19:21:48} RaspiMJPEG Version 5.2.1
{2015/05/21 19:21:48} Error: Could not enable camera
{2015/05/21 19:21:49} RaspiMJPEG Version 5.2.1
{2015/05/21 19:21:49} Error: Could not enable camera
{2015/05/21 19:21:50} RaspiMJPEG Version 5.2.1
{2015/05/21 19:21:50} Error: Could not enable camera
{2015/05/21 19:21:52} RaspiMJPEG Version 5.2.1
{2015/05/21 19:21:52} Error: Could not enable camera
{2015/05/21 19:21:53} RaspiMJPEG Version 5.2.1
{2015/05/21 19:21:53} Error: Could not enable camera
{2015/05/21 19:21:54} RaspiMJPEG Version 5.2.1
{2015/05/21 19:21:54} Error: Could not enable camera
{2015/05/21 19:21:55} RaspiMJPEG Version 5.2.1
{2015/05/21 19:21:55} Error: Could not enable camera
{2015/05/21 19:21:56} RaspiMJPEG Version 5.2.1
{2015/05/21 19:21:56} Error: Could not enable camera
{2015/05/21 19:21:57} RaspiMJPEG Version 5.2.1
{2015/05/21 19:21:57} Error: Could not enable camera
{2015/05/21 19:21:58} RaspiMJPEG Version 5.2.1
{2015/05/21 19:21:58} Error: Could not enable camera
{2015/05/21 19:21:59} RaspiMJPEG Version 5.2.1
{2015/05/21 19:21:59} Error: Could not enable camera
{2015/05/21 19:22:00} RaspiMJPEG Version 5.2.1
{2015/05/21 19:22:00} Error: Could not enable camera
{2015/05/21 19:22:01} RaspiMJPEG Version 5.2.1
{2015/05/21 19:22:01} Error: Could not enable camera
{2015/05/21 19:22:02} RaspiMJPEG Version 5.2.1
{2015/05/21 19:22:02} Error: Could not enable camera

Gary Littlemore
Posts: 327
Joined: Thu Oct 11, 2012 11:52 am
Location: Cheshire, UK

Re: RPi Cam Web Interface

Fri May 22, 2015 7:12 am

Last night I upgraded to 6.0.1 and where the stream should be it just says "LOADING".
3b+, 2b, b+, b, Zero & Zero-W

btidey
Posts: 1623
Joined: Sun Feb 17, 2013 6:51 pm

Re: RPi Cam Web Interface

Fri May 22, 2015 7:57 am

jbeale wrote:current version of the software (as of today, 5/21/2015) seems to have a problem on my Model A (although it works OK on a Model A+ and two different Model 2s). My Model A keeps getting locked up, even after a reboot, and even after a power cycle. I haven't physically touched it since it has been working mostly OK for months on older software. I don't think it's a hardware issue specific to this unit.
I can't think of any difference between A and A_+ that would make any difference here.

As the log first complained about splitter might be worth setting buffer to 0 to start with. Other than that I'd think I do a full apt-get rpi-update cycle to make sure all that is up to date.

btidey
Posts: 1623
Joined: Sun Feb 17, 2013 6:51 pm

Re: RPi Cam Web Interface

Fri May 22, 2015 8:04 am

Gary Littlemore wrote:Last night I upgraded to 6.0.1 and where the stream should be it just says "LOADING".
Loading is the default image on the start screen that gets replaced when it successfully retrieves jpgs or mjpeg stream from server.

DId you 'update' or 'install' when you changed to 6.0.1. A full install should be used here as there were additions to the raspimjpeg config file.

If that doesn't help. look in schedulerLog for any errors reported.

Antor
Posts: 2
Joined: Fri May 22, 2015 10:35 am

Re: RPi Cam Web Interface

Fri May 22, 2015 10:49 am

I have the same SPLITTER error as reported by jbeale. Only for me it only seems to happen when i press the motion start button.

LOG:

Code: Select all

{2015/05/22 10:30:40} External motion detection started
{2015/05/22 10:30:40} Error: Could not enable connection splitter -> video converter
{2015/05/22 10:30:41} RaspiMJPEG Version 5.2.1
{2015/05/22 10:30:41} Error: Could not enable camera
{2015/05/22 10:30:42} RaspiMJPEG Version 5.2.1
ETC...
on the console i get:

Code: Select all

[23299912] Motion 3.2.12 Started
[23299912] Motion going to daemon mode
mmal: mmal_vc_port_enable: failed to enable port vc.ril.video_encode:in:0(I420): ENOSPC
mmal: mmal_port_enable: failed to enable connected port (vc.ril.video_encode:in:0(I420))0xb122d310 (ENOSPC)
mmal: mmal_connection_enable: output port couldn't be enabled
mmal: mmal_vc_component_enable: failed to enable component: ENOSPC
mmal: mmal_vc_component_enable: failed to enable component: ENOSPC
mmal: mmal_vc_component_enable: failed to enable component: ENOSPC
ETC ...
Not sure why it complains about "not enough space" although the error might be erroneous or because the port is already in use?

Gary Littlemore
Posts: 327
Joined: Thu Oct 11, 2012 11:52 am
Location: Cheshire, UK

Re: RPi Cam Web Interface

Fri May 22, 2015 11:32 am

btidey wrote:
Gary Littlemore wrote:Last night I upgraded to 6.0.1 and where the stream should be it just says "LOADING".
Loading is the default image on the start screen that gets replaced when it successfully retrieves jpgs or mjpeg stream from server.

DId you 'update' or 'install' when you changed to 6.0.1. A full install should be used here as there were additions to the raspimjpeg config file.

If that doesn't help. look in schedulerLog for any errors reported.
It was an install, and the 'Loading' just stays there, nothing else happens. I'll try again later this evening
3b+, 2b, b+, b, Zero & Zero-W

User avatar
jbeale
Posts: 3498
Joined: Tue Nov 22, 2011 11:51 pm
Contact: Website

Re: RPi Cam Web Interface

Fri May 22, 2015 2:17 pm

Does the new version use more memory? On my Model A, I had gpu_mem=96 in /boot/config.txt so I changed that to gpu_mem=128 and it is working now...

User avatar
jbeale
Posts: 3498
Joined: Tue Nov 22, 2011 11:51 pm
Contact: Website

Re: RPi Cam Web Interface

Fri May 22, 2015 2:30 pm

It seems the Pi Model 2 is not immune to iframe errors either...

Code: Select all

[2015/05/21 21:16:34] Scheduled management tasks. Next at 1432268554
[2015/05/21 21:22:35] Scheduled management tasks. Next at 1432268915
[2015/05/21 21:28:36] Scheduled management tasks. Next at 1432269276
[2015/05/21 21:34:37] Scheduled management tasks. Next at 1432269637
[2015/05/21 21:40:38] Scheduled management tasks. Next at 1432269998
{2015/05/21 21:42:35} DEBUG 2: 6664, 6858
{2015/05/21 21:42:35} Error: Error in iframe list
{2015/05/21 21:42:35} DEBUG 2: 6665, 6858
{2015/05/21 21:42:35} Error: Error in iframe list
{2015/05/21 21:42:35} DEBUG 2: 6666, 6858
{2015/05/21 21:42:35} Error: Error in iframe list
{2015/05/21 21:42:36} DEBUG 2: 6667, 6858
{2015/05/21 21:42:36} Error: Error in iframe list
{2015/05/21 21:42:36} DEBUG 2: 6668, 6858
{2015/05/21 21:42:36} Error: Error in iframe list
{2015/05/21 21:42:36} DEBUG 2: 6669, 6858
{2015/05/21 21:42:36} Error: Error in iframe list
{2015/05/21 21:42:36} DEBUG 2: 6670, 6858
{2015/05/21 21:42:36} Error: Error in iframe list
{2015/05/21 21:42:36} DEBUG 2: 6671, 6858
{2015/05/21 21:42:36} Error: Error in iframe list
{2015/05/21 21:42:36} DEBUG 2: 6672, 6858
{2015/05/21 21:42:36} Error: Error in iframe list
{2015/05/21 21:42:36} DEBUG 2: 6673, 6858
{2015/05/21 21:42:36} Error: Error in iframe list
{2015/05/21 21:42:36} DEBUG 2: 6674, 6858
{2015/05/21 21:42:36} Error: Error in iframe list
{2015/05/21 21:42:36} DEBUG 2: 6675, 6858
{2015/05/21 21:42:36} Error: Error in iframe list
{2015/05/21 21:42:36} DEBUG 2: 6676, 6858
{2015/05/21 21:42:36} Error: Error in iframe list
{2015/05/21 21:42:36} DEBUG 2: 6677, 6858
{2015/05/21 21:42:36} Error: Error in iframe list
{2015/05/21 21:42:36} DEBUG 2: 6678, 6858
{2015/05/21 21:42:36} Error: Error in iframe list
{2015/05/21 21:42:36} DEBUG 2: 6679, 6859
{2015/05/21 21:42:36} Error: Error in iframe list
{2015/05/21 21:42:36} DEBUG 2: 6680, 6859
{2015/05/21 21:42:36} Error: Error in iframe list
{2015/05/21 21:42:36} DEBUG 2: 6681, 6859
{2015/05/21 21:42:36} Error: Error in iframe list
{2015/05/21 21:42:36} DEBUG 2: 6682, 6859
{2015/05/21 21:42:36} Error: Error in iframe list
{2015/05/21 21:42:36} DEBUG 2: 6683, 6859
{2015/05/21 21:42:36} Error: Error in iframe list
{2015/05/21 21:42:36} DEBUG 2: 6684, 6859
{2015/05/21 21:42:36} Error: Error in iframe list
{2015/05/21 21:42:36} DEBUG 2: 6685, 6859
{2015/05/21 21:42:36} Error: Error in iframe list
{2015/05/21 21:42:36} DEBUG 2: 6686, 6859
{2015/05/21 21:42:36} Error: Error in iframe list
{2015/05/21 21:42:36} DEBUG 2: 6687, 6859
{2015/05/21 21:42:36} Error: Error in iframe list
{2015/05/21 21:42:36} DEBUG 2: 6688, 6859
{2015/05/21 21:42:36} Error: Error in iframe list
{2015/05/21 21:42:36} DEBUG 2: 6689, 6859
{2015/05/21 21:42:36} Error: Error in iframe list
{2015/05/21 21:42:36} DEBUG 2: 6690, 6859
{2015/05/21 21:42:36} Error: Error in iframe list
{2015/05/21 21:42:36} DEBUG 2: 6691, 6859
{2015/05/21 21:42:36} Error: Error in iframe list
{2015/05/21 21:42:37} DEBUG 2: 6692, 6859
{2015/05/21 21:42:37} Error: Error in iframe list
{2015/05/21 21:42:37} DEBUG 2: 6693, 6859
{2015/05/21 21:42:37} Error: Error in iframe list
{2015/05/21 21:42:37} DEBUG 2: 6694, 6860
{2015/05/21 21:42:37} Error: Error in iframe list

btidey
Posts: 1623
Joined: Sun Feb 17, 2013 6:51 pm

Re: RPi Cam Web Interface

Fri May 22, 2015 5:50 pm

jbeale wrote:Does the new version use more memory? On my Model A, I had gpu_mem=96 in /boot/config.txt so I changed that to gpu_mem=128 and it is working now...
The app side itself isn't using significantly more memory and this should be more than offset by not using motion when in internal mode. However, there are changes on the MMAL side to get simultaneous access to the vectors and video and these may raise the requirements on the GPU side of the equation. 128MB was thr raspberry recommended level but it does mean that there is not much left on a Model A.

johng
Posts: 41
Joined: Thu Apr 23, 2015 10:00 am

Re: RPi Cam Web Interface

Fri May 22, 2015 8:26 pm

On the question of iframe errors:-
Using the new version, installed with install, B+, old external motion, motion on, boxing off, previews off, videos saved (as h264) to windows shared drive, scheduleLog writing to the shared drive.

Started at 08.39 on 21st and ran fine until 04.02 today with occasional single iframe errors with debug 2: 0, 1 and a few with 2: 1, 2 Most capture start/capture stop with DEBUG 3 before/after but occasional no debug message and occasional "g started" or "g stopped". Otherwise OK.

At 04.02 this morning I got

Code: Select all

{2015/05/22 04:02:03} Capturing stopped
{2015/05/22 04:02:03} Capturing started
{2015/05/22 04:02:13} DEBUG 3
{2015/05/22 04:02:22} Capturing stopped
{2015/05/22 04:02:27} Capturing started
{2015/05/22 04:02:32} DEBUG 2: 4, 3
{2015/05/22 04:02:33} Error: Error in iframe list
{2015/05/22 04:02:34} DEBUG 2: 5, 3
This continued until error 2.458.3 at which point the watchdog tried to kick in

Code: Select all

{2015/05/22 04:02:46} DEBUG 2: 458, 3
{2015/05/22 04:02:46} Error: Error in iframe list
{2015/05/22 04:02:46} Watchdog detected problem. Stopping{2015/05/22 04:02:46} DEBUG 2: 459, 3
{2015/05/22 04:02:46} Error: Error in iframe list
{2015/05/22 04:02:46} DEBUG 2: 460, 3
{2015/05/22 04:02:46} Error: Error in iframe list
{2015/05/22 04:02:46} DEBUG 2: 461, 3
{2015/05/22 04:02:46} Error: Error in iframe list
{2015/05/22 04:02:46} DEBUG 2: 462, 3
{2015/05/22 04:02:46} Error: Error in iframe list
{2015/05/22 04:02:46} DEBUG 2: 463, 3
{2015/05/22 04:02:46} Error: Error in iframe list
{2015/05/22 04:02:46} DEBUG 2: 464, 3
{2015/05/22 04:02:46} SIGINT/SIGTERM received, stopping
{2015/05/22 04:02:46} Error: Error in iframe list
{2015/05/22 04:02:46} DEBUG 2: 465, 3
{2015/05/22 04:02:46} Error: Error in iframe list
Watchdog didn't cure the problem and the log finally died after continuous incrementing errors 2: xxx, 3 with

Code: Select all

{2015/05/22 04:05:16} DEBUG 2: 7742, 3
{2015/05/22 04:05:16} Error: Error in iframe list
Picture in browser was frozen at 04.02, buttons not working. Installer stop/start didn't free it and I had to reboot after which OK.

I'm going to move the log back to the default on the SD card but leave everything else unchanged and see what happens...

Return to “Camera board”