Failure 70 on USB Webcam Raspberry Pi
See original GitHub issueI’m using USB webcam on my raspberry pi. Tried to run node server-rpi.js
. It’s successfully run the web server. But when I try to click start video button. It showing the error bellow:
Incomming action 'REQUESTSTREAM' raspivid -t 0 -o - -w 960 -h 540 -fps 12 Failure 70
Issue Analytics
- State:
- Created 3 years ago
- Comments:6
Top Results From Across the Web
USB camera interface with raspberry pi
hello there i want to interface usb camera interface with raspberry pi. ... this command sudo apt-get install fswebcam with any usb camera??...
Read more >Using USB webcams - The Raspberry Pi Guide
Setting up and using a USB webcam. You can control a USB webcam both using bash in the terminal and with Python. First...
Read more >RPi-Cam-Web-Interface - eLinux.org
Supports selection from 2 cameras when used with a compute module. IMPORTANT NOTE1: This is for the Raspberry Pi camera only. It does...
Read more >4 USB camera framerate and resolution
This answer is no longer valid! It was related to original Raspberry Pi model A/B, with USB 2.0 and 100 mbit LAN. Raspberry...
Read more >Running Octoprint on Raspberry Pi Zero 2 W - NotEnoughTech
Consider using a powered USB hub if your webcam has LED lights, as this can cause the camera to fail at best and...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Thanks a lot for the explanation! I think I was having issues because I was running it with some outdated dependencies or conflicts, got it working now with a fresh install of ws, raspivid and stream-split!
Failure 70 is due to a second call to the raspivid command while a raspivid process is already running. In the original logic a string “REQUESTSTREAM” is sent from the client as “Start Video” is pressed, and when the server receives the string it will call raspivid. So if you pressed that button twice, no matter from where, Failure 70 will be generated. Interestingly, if you open one tab, start video, open another tab, kill the raspivid process from the server, then start video from that second tab, both tabs will be watching the stream. This makes sense as in _server.js the h.264 data will be send forEach client. I and my roommate are also trying to achieve multiple stream watchers, so we modified the code a bit so that the server will only be starting raspivid once and will not be listening to commands sent from the client side. Now the first to log on is able to watch the stream. However (which confuses us till now), the following clients that connect to the server are unable to display anything, despite that from console.logging we can confirm h.264 data is being sent through websockets to all clients. My current guess is that late loggers may be missing SPS and PPS frames, which puzzles the h264 decoder (Another fact to support this guess: We call raspivid as the first logger connects.). We are still working on this issue.