Hot answers tagged

7

The problem is that the C922 does not advertise its H264 stream over UVC whereas the C920 does. This is because Logitech did not want to enable general use of the H264 for the C922, but instead wanted you to buy the camera with something like Skype which knows internally how to get hold of the data. The reason for this peculiar setup was to enable the camera ...


2

The correct commands to start an RTSP server on the Raspberry Pi are, for example: uv4l --driver raspicam --auto-video_nr --framerate 30 --extension-presence=0 cvlc v4l2c:///dev/video0:width=640:height=480:chroma=H264 --sout '#rtp{sdp=rtsp://:8554/}' --demux h264 Do not forget to pass --extension-presence=0 to uv4l. On the client side you can then play ...


2

Solved issue. I had to change the Pi's display options in raspi-config to 1024x768.


2

Regarding the official answer on Raspberry Pi forum, it is not possible to include B-Frames into h264 stream since hardware encoder doesn't support it.


2

If you do not specify the default framerate in python then it will be set to 30fps. The players you are using expect a frame rate of 25fps. So your 30 second video should last 30seconds x 30fps/25fps = 36 seconds. See documentation, 10. API - picamera.camera Module, for the default frame rate. Try using camera.framerate=25 Camera must not be recording for ...


1

The author of U4VL is elusive and secretive. I suggest using the contact form on www.linux-projects.org to negotiate a contract for commercial use. The pseudonyms of the author on the Raspberry Pi StackExchange are "prinxis" and "RpiName" on raspberrypi.org - you can try to contact him/her that way too.


1

Issues in Android app visualization were given by a faulty network connection. It is pretty difficult to say what happens in detail because I cannot investigate further on access point configuration and other network settings (including firewalls) active on company network since I've not network admin privileges, This's pretty frustrating. As a matter of ...


1

I would approach this by checking the output of lsof | grep /opt/vc This will list all processes which access videocore libraries. This can be further narrowed down to a specific library you're interested in. For video decoding in general, libbcm_host could be a good start.


1

It seems there are some issues with timestamps in BCM2835 (for instance, Pi Zero) which affect the standard kernel driver for the RPi camera: https://github.com/raspberrypi/linux/issues/1836 The fix should be available on kernel release 5.8.


1

The only way to play H264 video streams with standard web technologies is WebRTC. UV4L has been supporting WebRTC for years now, and the project website is plenty of examples, tutorials and demos made for the Raspberry Pi showing how to run custom web applications with UV4L itself providing H264 hardware-encoded streams in the pages.


1

The OpenGL driver that you can enable in raspi-config seems to be some sort of DRI driver. When it's enabled you have a /dev/dri/card0 device. Turn it off and the device goes away. It seems to generally slow things down on my Pi 3B so I keep it off. I'm only interested in pure (portable?) OpenGL ES 2.0 like the examples in /opt/vc/src. Those work fine ...


1

Try using this command vlc "Humvee_Large.h264":sout=#rtp{sdp=rtsp://:8554/} :sout-keep If you can access GUI, try using VLC's GUI streaming setup.


1

You may have to force the stream mode for your camera. First chek if MPEG or H264 is really available : v4l2-ctl --list-formats Using v4l2-ctl --all you will see the current resolution and pixel Format for your camera. To define another resolution and/or pixelFormat, use this command : v4l2-ctl --device /dev/video0 --set-fmt-video=width=1280,height=960,...


Only top voted, non community-wiki answers of a minimum length are eligible