View source for Talk:RPi-Cam-Web-Interface
- [View source↑]
Hello: I am interested in knowing what coding is used to leave in the file /dev/shm/mjpeg/user_annotate.txt to avoid that in the overprint they leave ??. Thank you.
Hi, I'm using a PI Zero W with Raspbian Stretch Lite and RPi-Cam-Web-Interface is running wonderful! But now I attached a small screen to the Composite Video Connector and would like to see the preview in Real-Time on that screen. How can I make this happen? Omxplayer works with terrible and growing latency. Is there any way to fork the video signal to a local screen with low latency? Any help is appreciated.
I spoke to the developer of MotionEye OS and asked him how to view the stream from RPi-Cam-Web_Interface and he told me to ask here. What I want to accomplish is to be able to view my camera using RPi-Cam-Web_Interface and set the camera position using the Pan Tilt buttons, then be able to see the new image as well in my MotionEye setup. Any help on this would be much appreciated. If I try and set up the RPi-Cam-Web_Interface in MotionEye now I set it as a Network Camera then giving the current IP address, but I always get an error saying not a Network Camera. I have tried other streaming solutions such as Motion and an app call PiCAMIt from a developer from Germany and I can get that stream working as well, but not RPi-Cam-Web_Interface. Thanks
Raspberry Pi Zero W OTG Confirguration for speed & I think I am overheating Pi with the V2 camera
I have been using the Raspberry Pi Zero W a lot more recently because of the cost. The most recent update to my Pi Zero W Camera has been to use it via OTG.
OMG it makes the Raspberry Pi Camera into a really good 'Web Cam' or 'Streaming Camera', to me it is much better than even using Ethernet. Since it is OTG my PC can get the data very fast, I have not run any tests except I think it is the max throughput of the USB-2 port.
Since this set up allows for very immediate interactions I started 'fiddling with the knobs' and found that I could lock it up at times. That led me to try to 'not' lock it up but push it all the way to 11. When I had 'auto' on for any of the settings it seemed to get a bit slower. I was not sure if anyone else has experienced this or not.
Is there a way to 'share' our setting easily, a save feature and load feature? Could we easily share the user.config file or something like that?
Any help on sharing settings easily would be very helpful. I would love to see how far the experimentation on this configuration of the camera could go.
I also noticed that my V2 camera seems to lock up and I checked the temps as I thought that might be it. Has anyone else experienced V2 cameras locking up? Maybe it is a known issue.
Here are the details from the Preview Box "Preview quality (1...100) Default 10: Width (128...1024) Default 512: Divider (1-16) Default 1:"
Here are the details for the parameters of the Preview Qu: 1-100 Wi:1024(max) Di:1(1=every frame of the FPS if possible)
I was able to set the 1024 max to 1920. On my older system it gives me an error. So I think a firmware update occurred and now it is possible. Can anyone confirm that? I updated the system that gave me the error above 1024 using the standard update upgrade and now 1920 is possible on it too so I am still guessing firmware update.
Any chance this could get a port for the Tinker Board. My understating is rudimentary in this topic, but since this is based on the usage raspimjpeg, something that has already been ported, it should be "doable"?
It's possible add in this software a very simply Audio Streaming for ear web cam side from remote connection? i was try a way like this example in a loop : arecord -d 300 plughw:1,0 -f S16_LE -f r8000 /html/stream.mp3
but very bad solution, not is realtime, sometime crash, very hard to ear by VLC and sametime watch webcam with another browser
Hi, With regard to Purging, can someone explain the math, in the documentation?
The scheduler has facilities for removing old files automatically. There are two mechanisms which are both checked and used at each Management_Interval. First the 3 PURGE_HOURS (one per file type) are checked and any file older than this is removed. So if PurgeVideo_Hours is set to 98 then any video captured more than a week ago will be removed. Setting the values to 0 disables this .
- How is the PurgeVideo Hours implemented?
- is it 98 total video hours?
- or example above, is it 7 days * 24 = 168 hours...but 168 hours is significantly more than 98 hours. I don't understand the above statement if a video captured more than a week ago, with the variable set to 98....Wouldn't it be set to 168?
Thanks for the help!
Hi, I want to edit the main html file, but i dont find it, please help me! Thanks
Did you see this note in the installation section:
IMPORTANT NOTE: If you need to change any files then you need to do these in the run time version (e.g. in the /var/www/html folder or /etc/raspimjpeg). Changing files in the RPi_Cam_Web_Interface folder has no immediate effect. These are just copies used during the install.
Ok but I do not find in the / var / www / html folder the file that is displayed when you access the interface from the browser
Can't you just use grep to find some text from the page?
Do something like:
$grep -ri "some string from the webpage that's unique" .
That will turn up any files that contain the string "some string from the webpage that's unique".
All, I have the RPi Cam Web up and working and now moving onto tidying up the install. I installed, configured and verified that ssmtp and mpack are able to send emails/attachments from pi@raspberrypi prompt.
I need a second set of eyes or someone to verify this is the proper approach:
1. nano /var/www/macros/end_vid.sh
list=( $1*.th.jpg )
mpack -s subject /var/www/media/thumb firstname.lastname@example.org
[save and exit nano]
3. sudo chmod a+x /var/www/macros/end_vid.sh
4. sudo chown www-data:www-data /var/www/macros/end_vid.sh
Does this look correct? is there a more elegant way or method that I overlooked?
Guidance and help are appreciated! Brian
Any way to change size of preview on webpage? Any way to make the min/simple the default page?
You do not have permission to edit this page, for the following reasons:
- The action you have requested is limited to users in the group: Users.
- You must confirm your email address before editing pages. Please set and validate your email address through your user preferences.
You can view and copy the source of this page.
Return to Thread:Talk:RPi-Cam-Web-Interface/Any way to change size of preview on webpage? Any way to make the min/simple the default page?.
So, I am having fun with my RPi and cameras, getting the preview from many into a single web page, into a Python script and into OBS. What I cannot seem to do is change the content of the preview to be the same as the captured image. Is there a way to do this. The preview seems to contain only the centre of the image captured by the camera module. Any ideas please.
All the feeds come from http://<RaspberryPi IP>/cam_pic_new.php?
I'm sorry, I don't know. I haven't played with that stuff at all. You should try the RPi forums.
So here it is all along, right in front of me!
Use the Camera Settings option, Resolutions. Setting to any of the Load Presets other than the first or last (HD ...) gives a mode that includes a full size preview - perfect for my needs.
As someone once said - WONDERFUL!
Is there a way to see the amount of changed motion pixels and show the in the camera name(Annotation)?
I use external motion and the manual only describes the internal motion, so %c and %f do not work..... The version that I use is RPi Cam Control v6.0.37
Perhaps it would be also nice for a user setting for change the position of this text. (left right up down in the camera picture)
I cannot get the Cam-Web-interface to work with the latest Debian Jessie with Apache 2. I would appear that Apache 2 looks into /var/www/hmtl/index.hmtl and execute that hmtl file. Replacing the index.hmtl with yout index.php creates just a white screen. Here is a note from Apache 2
Debian's Apache2 default configuration is different from the upstream default configuration, and split into several files optimized for interaction with Debian tools. The configuration system is fully documented in /usr/share/doc/apache2/README.Debian.gz. Refer to this for the full documentation. Documentation for the web server itself can be found by accessing the manual if the apache2-doc package was installed on this server.
The configuration layout for an Apache2 web server installation on Debian systems is as follows: /etc/apache2/ |-- apache2.conf | `-- ports.conf |-- mods-enabled | |-- *.load | `-- *.conf |-- conf-enabled | `-- *.conf |-- sites-enabled | `-- *.conf
• apache2.conf is the main configuration file. It puts the pieces together by including all remaining configuration files when starting up the web server. • ports.conf is always included from the main configuration file. It is used to determine the listening ports for incoming connections, and this file can be customized anytime. • Configuration files in the mods-enabled/, conf-enabled/ and sites-enabled/ directories contain particular configuration snippets which manage modules, global configuration fragments, or virtual host configurations, respectively. • They are activated by symlinking available configuration files from their respective *-available/ counterparts. These should be managed by using our helpers a2enmod, a2dismod, a2ensite, a2dissite, and a2enconf, a2disconf . See their respective man pages for detailed information. • The binary is called apache2. Due to the use of environment variables, in the default configuration, apache2 needs to be started/stopped with /etc/init.d/apache2 or apache2ctl. Calling /usr/bin/apache2 directly will not work with the default configuration.
By default, Debian does not allow access through the web browser to any file apart of those located in /var/www, public_html directories (when enabled) and /usr/share (for web applications). If your site is using a web document root located elsewhere (such as in /srv) you may need to whitelist your document root directory in /etc/apache2/apache2.conf.
The default Debian document root is /var/www/html. You can make your own virtual hosts under /var/www. This is different to previous releases which provides better security out of the box.
Please use the reportbug tool to report bugs in the Apache2 package with Debian. However, check existing bug reports before reporting a new bug.
Please report bugs specific to modules (such as PHP and others) to respective packages, not to the web server itself.
I am not able to move the pi-pan severs from the Cam-web-interface. The servos work fine from the command line and the buttons appear on the web interface but they do not activate the servos from the interface. I am using a safari web browser on a mac and have tried a chrome browser with the same result. It seems related to the script for the pi-pan control. Has anyone had a similar problem and/or solution.
How about adding links to the information pages in the index.html so it's easy to get help...
for example add:
<a href="http://elinux.org/RPi-Cam-Web-Interface">Help on configuring Web Service</a>
<a href="http://www.raspberrypi.org/forum/viewtopic.php?f=43&t=63276">Forum Thread on RPi Cam Web Interface</a>
after and before .