I've seen that before as well, but then after rebooting the Pi and refreshing the browser, it works as expected.rpiatf2f10 wrote:I got 32G usb key attached to the PI; however, it says 'Disk 0.0B Free: 0.0B(0.0%)". Any thoughts?
There's some kind of initial condition issue. If you record a video, or just after a while with a web page reloadrpiatf2f10 wrote:HI Guys,
I got 32G usb key attached to the PI; however, it says 'Disk 0.0B Free: 0.0B(0.0%)". Any thoughts?
It would be nice to have some examples of how people set up installations. If not a wiki then at least some links on therpiatf2f10 wrote:HI YvesG,
thanks for the link. Do you use this in-house or outdoor? I was wondering whether people use these Servos outdoor. In that case, how it's being cased......... It would be nice to have a wiki with a section of showing how people use it in different ways.......
I found a bug affecting the USB disk total/free display.rpiatf2f10 wrote: With regard to 32G usb issue, I tried various , reboot, clear cache, etc; however, it still says "0". ...
I'm not sure what the effect is you are talking about. I have several cameras running but haven't noticed anything. Are you saying that for identical mjpeg_width settings the preview images in the browser are not mjpeg_width for some of them? Or is it that the apparent field of view is different?rpiatf2f10 wrote: In one of my early post, I mentioned that I have 5 same Pi B. With identical setting in PI and Web browser, two of PI's preview picture are a bit larger than rest of 3 PI's . The OSD zone actually is closely related to this Preview picture size. I felt that it might affect the accuracy of detection, though I haven't noticed this yet. I tried Chromium/Firefox, both are same.
The OSD config just has a set of resolutions intended to cover typical use cases. If you want to experiment with various other resolutions, stop pikrellcam, edit the resolution you want in pikrellcam.conf, and restart.Gavinmc42 wrote:What are the video and still resolutions?
Could you request 1640 x 320 and get videos/images around that size?
Am I years too late asking this question and it is in an old post somewhere?
Can you double check the mjpeg_width setting in ~/.pikrellcam/pikrellcam.conf on each of your Pi's?rpiatf2f10 wrote: In order to upload files with smaller size, I reduced file size with lower resolutions of these two screen captures.
You can see, that with all settings of PI and browser equal, one preview is larger than the other one.
Until now you could email the preview jpeg, but I just put an upgrade up that adds the option to email the thumb jpeg instead.nitschkecm wrote: I have just installed and so far it runs like a charm. I was wondering if somebody has implemented an email trigger which is easy to implement. I would like to have and email sent in case of a motion event, if possible with the thumbnail generated.
Many thanks for the hint!
Boxing by itself shouldn't cause large lapses like that unless there's something else going on like memory usage is maxing out and your pi is swapping. Just a guess though. I'll look into it some more to make sure it's not something pikrellcam is doing wrong, but it will be a few days since I'm traveling right now.BerryPicker wrote:If one video recording stops because the time limit is exceeded, the following recording overlapps the previous, and initially replays smoothly, but after about 8 seconds there are lost frames causing the replay to jump ahead by leaps of about 10 seconds. Is this because the pi is busy boxing the first recording whilst trying to capture the second? If so, is it best to turn off boxing, and do it later as needed?
I have seen something like this a few times as well. I haven't investigated what triggers it.BerryPicker wrote:If one video recording stops because the time limit is exceeded, the following recording overlaps the previous, and initially replays smoothly, but after about 8 seconds there are lost frames causing the replay to jump ahead by leaps of about 10 seconds.
Thank you billw. Other follow-on recording funnies I've seen are the thumb showing motion region frames with some motion data, and a post capture time cut short.billw wrote:I'll look into it some more to make sure it's not something pikrellcam is doing wrong.
Do you mean from a larger subnet, or that you want to get in from anywhere on the internet? Normally your router's NAT (address translation) does not make your Pi visible to the world, so first you need to figure out your IP address as seen from the outside, and also if your ISP allows traffic to whatever port you're forwarding to the Pi.boomlikethat wrote: can't seem to be able to get to my PiKrellCam interfaces from outside my local network.