I have a camera plugged into a USB port on my raspberry pi. It is capable of taking about 3-5 pictures before I get this message:
Timed out waiting for frame!
No frames captured.
I have the resolution set at 320x240. I have gotten the camera to work again by turning of the pi and plugging the camera back in. Inevitably though, I get the timing out error again.
How can I fix this??
Related
I am trying to view a video via CVLC on a raspberry pi zero by using this command...
cvlc --no-osd --video-filter=adjust --brightness=2.0 /mnt/flash-drive/16-16-05.mp4
The video plays without any issues when i leave out the "--video-filter=adjust --brightness=2.0" section.
But when i add that section VLC does not show the video.
I looked around on the web on how to adjust image settings like brightness and contrast from command line and that seems to be the way , i just don't understand why it doesn't work on the raspberry pi zero.
Any idea why that doesn't work ?
EDIT :
This function is not supported on the raspberry pi because of its hardware acceleration.
This function is not supported on the raspberry pi because of its hardware acceleration.
VLC BUG REPORT WEBSITE
I have 2 raspberry pis, suddenly yesterday one of them started using the full screen on reboot, now the relations between height and width are wrong. I copied the /boot/config.txt file from the working pi to the other, still same problem! What is going on?!? Please Help!
I have a smart home (node-red) with a Raspberry Pi and a official 7" touchscreen as dashboard.
I now want to turn off the backlight after a certain time and I know how to do that. I also want to turn it back on if I touch the screen at any place.
I have no idea how to do that, as there is no node-red node for touch input or something like that.
Anyone did this before?
We recently launched our Android Wear app Coffee Google Play Link!
Users can launch the app by flicking their wrist. Essentially, when the watch wakes up we register with the accelerometer and start looking for a flick motion and when the watch dims we deregister.
This works on all devices except the Moto 360. When debugging we're finding that the Moto 360 accelerometer amplitude is about 10% of what we're seeing on other devices and we're only getting about 10Hz on the accelerometer.
Has anyone else seen issues like these on the Moto 360?
OK, I figured this out.
The Moto 360 accelerometer is fine. The problem is that whenever you're attached for debugging over bluetooth (which is how I captured the accelerometer data) everything slows down so bad on the Moto 360 that the accelerometer data is useless.
When using the MessageAPI to send the data and not being attached the values are fine.
I added usb touch screen driver to my custom win ce 6.0 OS image. The touch screen works only when there is another USB device(USB flash drive, usb mouse etc.) present in the system and does not work when there is only single usb touch screen is connected. After troubleshooting, I discovered that the USB touch device does not get enumerated. Any help resolving this issue is highly appreciated.