Not encoding, just decoding (which is all they mention decoding on the specs)
As one of the RPi engineers / moderators mentioned in a post on the official RPi forums here when asked the same question:
Not on the Pi4, it would require changing the SOC (or the SoC being
redesigned to have an encoder).
He then clarifies:
In fact H265 encode in HW is VERY ...
I have tried to do this a few times but never gotten the results I wanted. Just recently I revisited it and found this works to multicast directly from raspivid.
raspivid -a 12 -a "ras2" -t 0 -b 3000000 -fps 20 -w 1920 -h 1080 -o udp://126.96.36.199:1234 -ih -fl -stm -if adaptive -pf main -v -n
Then use this on a linux PC to view:
I would recommend using GStreamer for this.
Check out their tutorials to understand how to play a video file, and this page documents how to apply a text overlay.
You will probably want to test using the gst-launch-1.0 command line tool, but to trigger from a GPIO I expect you'll need to write a program. You can use GStreamer from a wide variety of ...
Strictly speaking, no. The video output of the Pi is under control of the VideoCore, not the ARM CPU.
You can allocate a framebuffer and use low-level memory writes to fill it, but you'll still have to talk to the the VideoCore to get it displayed.
In a less strict sense, you could consider the VideoCore as an equivalent of the VGA adapter hardware. It's a ...
The SD Card Copier has problems with some SD Cards, as it performs file copies and is intolerant of errors.
It MAY be possible to use the SD Card if you format with the SDFormatter.app but it is probable that the SD Card is worn out.
Note: This question isn't Raspberry Pi specific. Please post these kinds of questions in Stack Overflow
This should work:
Remember to replace the ENDOV variable with the time that the video ends
from omxplayer.player import OMXPlayer
from pathlib import Path
import time #for determining the time of playback
import RPi.GPIO as GPIO #for taking signal from ...
And my version of the chromium-browser : 74.0.3729.157 (Official Build)
Chromium 74!? That's very out of date. The latest version has been Chromium-browser 78 for months.
Run this to update your Raspbian:
sudo apt update
sudo apt full-upgrade
After updating, try chrome:gpu again. WebGL should say "Hardware accelerated" by default.
You should not have to ...
The version of Chromium in Raspbian's repo (chromium-browser package) is patched to support hardware decode on the Pi. The patches are here: https://github.com/RPi-Distro/chromium-browser/tree/master/debian/patches
Electron bundles and patches Chromium itself and doesn't use the patched system version. I've looked at producing a patched build of Electron ...
Actually Intel provides a software to utilize a RPi4 as backend, to make your camera available in your network and directly use all API commands: https://dev.intelrealsense.com/docs/open-source-ethernet-networking-for-intel-realsense-depth-cameras
FRAMOS has a similar middleware for their reference models:
D435_Manual_V1.1 - Page 24
@MichaelHarvey wrote in a comment:
The chip supports HDCP and is used on other platforms where the content provider insists, and the content is DRM protected. The Raspberry Pi has no such deals in place, and so HDCP is disabled.