After conversion I get a new thumbnail tl_0000_0001_20170127_182729.mp4
I always have a gray image with a message on it "no video whose format with the MIME type is managed was found"
Code: Select all
Clone the code from github and enable and run the install script with the following commands:
git clone https://github.com/silvanmelchior/RPi_Cam_Web_Interface.git
cd RPi_Cam_Web_Interface
chmod u+x *.sh
./install.shCode: Select all
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following extra packages will be installed:
apache2-bin apache2-data apache2-utils gpac-modules-base liba52-0.7.4
libapr1 libaprutil1 libaprutil1-dbd-sqlite3 libaprutil1-ldap libavdevice55
libavfilter5 libfreenect0.2 libgpac3 liblua5.1-0 libmysqlclient18 libonig2
libperl4-corelibs-perl libqdbm14 lsof mysql-common php5-common php5-json
php5-readline ssl-cert
Suggested packages:
apache2-doc apache2-suexec-pristine apache2-suexec-custom php-pear
frei0r-plugins mysql-client postgresql-client php5-user-cache
openssl-blacklist
Recommended packages:
ffmpeg
The following NEW packages will be installed:
apache2 apache2-bin apache2-data apache2-utils gpac gpac-modules-base
gstreamer1.0-tools liba52-0.7.4 libapache2-mod-php5 libapr1 libaprutil1
libaprutil1-dbd-sqlite3 libaprutil1-ldap libav-tools libavdevice55
libavfilter5 libfreenect0.2 libgpac3 liblua5.1-0 libmysqlclient18 libonig2
libperl4-corelibs-perl libqdbm14 lsof motion mysql-common php5 php5-cli
php5-common php5-json php5-readline ssl-cert zip
0 upgraded, 33 newly installed, 0 to remove and 0 not upgraded.
Need to get 5,213 kB/11.4 MB of archives.
After this operation, 38.2 MB of additional disk space will be used.
Err http://mirrordirector.raspbian.org/raspbian/ jessie/main mysql-common all 5.5.52-0+deb8u1
404 Not Found [IP: 5.153.225.207 80]
Err http://mirrordirector.raspbian.org/raspbian/ jessie/main libmysqlclient18 armhf 5.5.52-0+deb8u1
404 Not Found [IP: 5.153.225.207 80]
Err http://mirrordirector.raspbian.org/raspbian/ jessie/main php5-common armhf 5.6.27+dfsg-0+deb8u1
404 Not Found [IP: 5.153.225.207 80]
Err http://mirrordirector.raspbian.org/raspbian/ jessie/main php5-cli armhf 5.6.27+dfsg-0+deb8u1
404 Not Found [IP: 5.153.225.207 80]
Err http://mirrordirector.raspbian.org/raspbian/ jessie/main libapache2-mod-php5 armhf 5.6.27+dfsg-0+deb8u1
404 Not Found [IP: 5.153.225.207 80]
Err http://mirrordirector.raspbian.org/raspbian/ jessie/main php5 all 5.6.27+dfsg-0+deb8u1
404 Not Found [IP: 5.153.225.207 80]
Err http://mirrordirector.raspbian.org/raspbian/ jessie/main php5-readline armhf 5.6.27+dfsg-0+deb8u1
404 Not Found [IP: 5.153.225.207 80]
E: Failed to fetch http://mirrordirector.raspbian.org/raspbian/pool/main/m/mysql-5.5/mysql-common_5.5.52-0+deb8u1_all.deb 404 Not Found [IP: 5.153.225.207 80]
E: Failed to fetch http://mirrordirector.raspbian.org/raspbian/pool/main/m/mysql-5.5/libmysqlclient18_5.5.52-0+deb8u1_armhf.deb 404 Not Found [IP: 5.153.225.207 80]
E: Failed to fetch http://mirrordirector.raspbian.org/raspbian/pool/main/p/php5/php5-common_5.6.27+dfsg-0+deb8u1_armhf.deb 404 Not Found [IP: 5.153.225.207 80]
E: Failed to fetch http://mirrordirector.raspbian.org/raspbian/pool/main/p/php5/php5-cli_5.6.27+dfsg-0+deb8u1_armhf.deb 404 Not Found [IP: 5.153.225.207 80]
E: Failed to fetch http://mirrordirector.raspbian.org/raspbian/pool/main/p/php5/libapache2-mod-php5_5.6.27+dfsg-0+deb8u1_armhf.deb 404 Not Found [IP: 5.153.225.207 80]
E: Failed to fetch http://mirrordirector.raspbian.org/raspbian/pool/main/p/php5/php5_5.6.27+dfsg-0+deb8u1_all.deb 404 Not Found [IP: 5.153.225.207 80]
E: Failed to fetch http://mirrordirector.raspbian.org/raspbian/pool/main/p/php5/php5-readline_5.6.27+dfsg-0+deb8u1_armhf.deb 404 Not Found [IP: 5.153.225.207 80]
E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing?
awk: cannot open /etc/apache2/ports.conf (No such file or directory)
awk: cannot open /etc/apache2/ports.conf (No such file or directory)
mv: cannot move ‘etc/apache2/sites-available/raspicam.conf’ to ‘/etc/apache2/sites-available/raspicam.conf’: No such file or directory
ln: failed to create symbolic link ‘/etc/apache2/sites-enabled/raspicam.conf’: No such file or directory
sed: can't read /etc/apache2/conf.d/other-vhosts-access-log: No such file or directory
Failed to restart apache2.service: Unit apache2.service failed to load: No such file or directory.
Your custom raspimjpg backed up at /etc/raspimjpeg.bak
sed: can't read /etc/motion/motion.conf: No such file or directory
sed: can't read /etc/motion/motion.conf: No such file or directory
sed: can't read /etc/motion/motion.conf: No such file or directory
sed: can't read /etc/motion/motion.conf: No such file or directory
sed: can't read /etc/motion/motion.conf: No such file or directory
sed: can't read /etc/motion/motion.conf: No such file or directory
sed: can't read /etc/motion/motion.conf: No such file or directory
sed: can't read /etc/motion/motion.conf: No such file or directory
sed: can't read /etc/motion/motion.conf: No such file or directory
sed: can't read /etc/motion/motion.conf: No such file or directory
sed: can't read /etc/motion/motion.conf: No such file or directory
sed: can't read /etc/motion/motion.conf: No such file or directory
sed: can't read /etc/motion/motion.conf: No such file or directory
sed: can't read /etc/motion/motion.conf: No such file or directory
sed: can't read /etc/motion/motion.conf: No such file or directory
sed: can't read /etc/motion/motion.conf: No such file or directory
sed: can't read /etc/motion/motion.conf: No such file or directory
chown: invalid user: ‘motion:www-data’
chmod: cannot access ‘/etc/motion/motion.conf’: No such file or directory
Thanks for the report. I'll check further. However, I thought the Red stop button was disabled with motion detection on.gigpi wrote:Hello!
I think there is a small bug when "motion_detection true" is set in "/etc/raspimjpeg".
Tested with a vanilla 6.2.29 and external motion.
Steps to reproduce:
- Edit /etc/raspimjpeg and change "motion_detection false" to "motion_detection true"
- Start RPi Cam normally. Now motion detection is working as expected
- Stop camera with red button
- Start camera with red button
- Here is the bug. Motion detection button says stop but Motion Detection is not really working. Looking in "status_mjpeg.txt" there is the right string "md_ready", but no real motion detection.
At this point to get it working, you need to:
- Stop motion detection with blue button
- Start motion detection with blue button
Basically stopping&starting manually the camera break motion detection even if interface says detection is active.
Update now uses fetch rather than pull so mismatches shouldn't occur once it has got this version.Gary Littlemore wrote:I'm running Jessie Lite. I've now got my SSH working, I'm running the ./update.sh and it says it doesn't match and I run ./install.sh reboot and the version number doesn't change and it still says it doesn't match again if I try them again.
Any ideas how I get it updated? I'm currently on v6.2.25
You can update the files without changing the permissions; just use sudo command. E.g. sudo nano /vars/www/html/index.php or sudo cp ~/myindex.php /vars/www/html/index.phppajama wrote:Ahh I'm such a noob. Disregard the problem above. New to Linux. I needed to change permissions for the files in the server folder.
The errors you are getting are not specific to the install of the camera software but are a failure to install some stuff from the raspberry repositories. This can sometimes happen if they are busy or there is a network glitch.saabeirik wrote:I'm recently installed Raspbian with Pixel, and I'm trying to setup this cam web interface.
I think I'm doing this right, but I'm a beginner and it is of course possible I'm doing something wrong.
First of all, is Raspbian Pixel compatible with this? I'm following this instruction:
I have no idea what's wrong, and I'm very grateful for any help.
The stream mode button on the web interface indicates what will happen when you press it. So if the button shows MJPEG then it is actually doing default streaming which is a sequence of jpeg images. When you press the button the label will change to Default Streaming and it will actually be doing MJPEG streaming. You can see the effect of streaming by using browser development tool and looking at network activity. With default streaming you will see a regular sequence of image fetches. With MJPEG streaming they stop as the stream is started once.devsfan1830 wrote:I have this setup and working great and can view my camera with the web interface on my local network. But for the life of me I cannot get an MJPEG stream to connect in iSpy. I use the suggested URL with the IP of the Pi and it shows a not connected symbol and a black screen. The nutton under System in the web interface says MJPEG-Stream so I ammume this means im in MJPEG mode. Am I misisng something? Right now its just the default install and I did set a password (which i did add to iSpy as directed)
Thanks a lot - I had overlooked updating my RPi first, this was the problem. Works fine now!btidey wrote:The errors you are getting are not specific to the install of the camera software but are a failure to install some stuff from the raspberry repositories. This can sometimes happen if they are busy or there is a network glitch.saabeirik wrote:I'm recently installed Raspbian with Pixel, and I'm trying to setup this cam web interface.
I think I'm doing this right, but I'm a beginner and it is of course possible I'm doing something wrong.
First of all, is Raspbian Pixel compatible with this? I'm following this instruction:
I have no idea what's wrong, and I'm very grateful for any help.
Just run the installer again.
This is an issue I keep having on new installs. if you go to http://IPaddress/html/ and all is OK then...chum wrote:I just upgraded to jessie lite and installed using the install script. All seems to be okay until I try on Chrome, I see the Index of / folder view". How do I go from here. I am used to seeing the camera interface with the live video. Can someone help. thanks,
Code: Select all
cd /etc/apache2/sites-available/
ls
sudo nano raspicam.conf
Code: Select all
<VirtualHost *:80>
ServerAdmin webmaster@localhost
DocumentRoot /var/www/html
<Directory /var/www/html>
Options Indexes FollowSymLinks MultiViews
AllowOverride All
Order allow,deny
Allow from all
...The url to use does include the subfolder you install in. So if you choose to use html then the url will be http://ipaddress/htmlMettauk wrote:This is an issue I keep having on new installs. if you go to http://IPaddress/html/ and all is OK then...My guess is one of the /html will be missing, probably <Directory /var/www/html>chum wrote:I just upgraded to jessie lite and installed using the install script. All seems to be okay until I try on Chrome, I see the Index of / folder view". How do I go from here. I am used to seeing the camera interface with the live video. Can someone help. thanks,
I have had the camera software running on all models from Zero up to Pi 3 including B.lohtse wrote:Hi guys
have an odd issue for you..
I have successfully installed Rpi Cam on 2 x Zero, 3 x pi 3 and 1 x pi B+ and they are ALL working perfectly yet when I try to install on out standard Pi B all goes well but I cannot access the web interface at all I just get page not found!!! I can SSH via Putty without issue and SSH with root access using winscp fine too... but I CANNOT connect to the camera via RPi Cam at all not even locally on the Pi.. Any ideas why and how to solve issue??? We want to use the Pi B as an Astro cam on a telescope but are not able to due to this issue!
I can't directly help with your immediate problem here but let me explain what may have happened and what I have done to maybe help in future.GammaScorpii wrote:I have a huge problem perhaps somebody out there can help me with. I've been using this great software to shoot lots of video clips and I have just lost a video file for some mysterious reason. The thumbnail jpg is still there in /var/media but the corresponding mp4/h264 file is nowhere to be found.
According to somebody who was watching the file grow as it was being shot, it disappeared most likely during the mp4 conversion process and never came back.
Any idea on what to do to recover it? It's an extremely important piece of footage and I'm worried now that I have tried using PhotoRec to recover any deleted files and haven't had any luck. PhotoRec did save the unknown data to a huge dd image but I have no idea on how to examine that.
My /var/media folder is an xfs partition if that helps.
Any advice on what to do next would be hugely appreciated and worth a credit on the film we're trying to make
What image format are you using? The gstreamer conversion will only work with ones that are GPU 'friendly' and, in particular, will not work with the high resolution 2592 x 1944. Try a test using 1296 x 972. Using HD video for the image (1920 x 1080) should also be OK.vin100 wrote:Hi
I reinstalled rpi web cam with the new version 6.2.31.
I still have the problem of converting Jpeg images in .mp4 with the command "start convert".
I have installed gstreamer1.0
I did a test with a recording of 3 minutes (Timelapse calculated 3sec)
With Firefox I get an error message "No video with a format or MIME type supported was found"
With Chrome I do not have this message. I have the thumbnail t_0000 ..... .mp4, the viewport is white but there is no video, the file is 0 bytes when I download it.
Thanks
I've done as suggested and I'm now stuck on v6.2.29 and I can't get the latest version to install, any ideas?btidey wrote:Update now uses fetch rather than pull so mismatches shouldn't occur once it has got this version.Gary Littlemore wrote:I'm running Jessie Lite. I've now got my SSH working, I'm running the ./update.sh and it says it doesn't match and I run ./install.sh reboot and the version number doesn't change and it still says it doesn't match again if I try them again.
Any ideas how I get it updated? I'm currently on v6.2.25
I'd suggest deleting the RPi installation folder and git cloning it again. Running ./install.sh will still find all the previous components without installing again. You will also then have the new update.sh script.