There seems to be a lot of misunderstanding around what H.264 (with a dot) actually is. So, quoting from Wikipedia:
H.264/MPEG-4 Part 10 or AVC (Advanced Video Coding) is a standard for
video compression, and is currently one of the most commonly used
The important part to stretch here is that it's only a standard. That means, videos ...
As of April 2015 GStreamer 1.2 included in Raspbian supports OpenMAX hardware accelerated H.264 encoding through omxh264enc.
I've done some benchmarking comparing:
MacBook Pro (Early 2011) dual-core i7-2620M 2.7GHz (Sandy Bridge) - 4GB RAM
RaspBerry Pi 2 Model B 900MHz quad-core ARM Cortex-A7 CPU - 1GB RAM
Sample file: 60s sample from the movie Alatriste (...
Those are explained here: https://www.raspberrypi.org/documentation/configuration/config-txt/video.md
There is also this: https://www.raspberrypi.org/documentation/configuration/hdmi-config.md -- But if the group 1, mode 16 as above works, you don't have to worry about all that.
From Raspberry Pi 2 - FAQ and collated answers
Do I still need CODEC licences?
Yes, if you want to use the HW decoders. However, the higher speed of
the device MIGHT mean a SW decoder can be used. This will depend on
the resolution of the video you are trying to display.
The best information I can find suggests that it's possible to output 4K resolutions, but at fairly miserable frame rates. The Pi 3 has the same GPU as the Pi 2, so the information should still be valid:
I have managed to get 3840 x 2160 (4k x 2k) at 15Hz on a Seiki E50UY04
That cable is most likely a DisplayPort-to-HDMI cable not a HDMI-to-DisplayPort cable (mind the direction). While there are DP ports able to support HMDI signals (DisplayPort Dual-mode) HDMI does not support DP directly. Since HDMI data transmission is very different from DP there will be no simple (passive) cable that just re-routes some signal lines on the ...
I had a similar problem with my Pi, when I connected it first time to my tv (a Samsung D5000): the tv did not understand an HDMI device was connected. I have raspbmc as the os.
There are a couple of instructions you can add to /boot/config.txt to tell your Pi to activate the hdmi output when you connect a cable, and to force hdmi output mode instead of dvi.
Yes. As far as I can remember, pretty much every Pi I've ever tried to play 1920x1080 video on has worked, up to and including the very first generation boards. You can see a brief sample of the Zero playing back 1080 resolution footage from Big Buck Bunny using Kodi on the KordKutters Youtube channel. Looks fine to me, although the presenter notes a little ...
GStreamer is included in Raspbian and with its OpenMAX plugin it will use the hardware encoding capabilities of the Raspberry Pi.
See this link for a tutorial on doing what you're looking for:
If you're interested in transcoding, I've just posted an answer to another question that might interest you:
It's possible and even encouraged. A nice command line player for the Pi is omxplayer. It might be installed by default in Arch, otherwise it's available in the repositories. Omxplayer is written for the Pi, and uses the GPU for decoding video. It works extremely well and smoothly, provided that the video is in a supported format (h264 and mpeg4). ...
Unfortunately it won't. First of all, flash video does not support MPEG-2 for encoding. Secondly, in order to use RaspberryPi hardware decoding capabilities (and MPEG-2 licence is exactly for this decoding mechanism) you have to use RaspberryPi OpenMAX libraries. This means that only applications with specifically written to support RaspberryPi hardware ...
The article you mention says: "Hardware accelerated video (H.264) encoding became available on 24 August 2012 when it became known that the existing license also covered encoding." It says nothing about the date of the manufacture.
H.264 decoding was available prior to Aug, 2012, and is still available, you don't have to change anything
H.264 encoding ...
If you want to use the PI exclusively as a HTPC or media center, you could use a distribution geared towards such applications. OpenELEC/XBMC /RasBMC seem to be the obvious choice. I did try OpenELEC at one time, but getting WiFi to work reliably on it seemed to be a pain.
Here's how I went about using Raspbian (since I use the RPi for tasks other than ...
It would likely be a 4-pole RCA cable, similar to this one -
However you will need to check pinouts on the cable to make sure it matches with what the Pi is outputting.
I found this blog post - http://www.raspberrypi-spy.co.uk/2014/07/raspberry-pi-model-b-3-5mm-audiovideo-jack/ - that ...
You should look to v4l2loopback in order to allow to open "twice" a V4L2 device.
1 - It will allow to create a virtual video device using :
sudo apt-get install v4l2loopback-dkms
sudo modprobe v4l2loopback video_nr=10
This will add a new device /dev/video10
2 - Next you will need to copy the real device (/dev/video0) to the virtual one (/dev/video10) ...
Most probably, bottle neck in this case is CPU speed to process the feed.
I use Rpi for some basic image processing based automation work and here is what I've noticed.
Rpi 1 hardly gives 5 fps at max @ 640x480. Blame single core @ 700 Mhz
Rpi 2 gives about 14 - 16 fps at 640x480. (Quad core @ 900 Mhz)
I've used Odriod-C1 (SBC mostly similar to Rpi 2 - ...
No, those pins have nothing to do with audio.
The upper two pins are to reset the Pi and are labeled "Run". While we have no schematics of the Pi Zero available yet, we can deduce this from former models of the Pi. According to this article it's a two pin header. The circuit with two clamp diodes, a pull-up resistor, and capacitor connected (at least that's ...
This display (according to the provided datasheet) is capable of communicating over SPI, that would make it a candidate to work with the SPI port that is available on the GPIO pins.
But you said that you did not understand very much of the datasheet itself, that might already answer your question. If you don't have any experience with electronics and do ...
If you know you won't be using the composite output, you can set up the pi to always use the hdmi output, even when no device has been detected. That way it will pick up the screen when it's attached, even if done at a later stage.
In your config.txt add/change the following line:
For more (screen and other) settings, see http://...
This sounds very much like some of your AVI files have video encoded with MPEG-2 or VC1 (or possibly some other unsupported codec) and you don't have the MPEG-2 or VC1 codec installed (only h.264/MPEG-4 content can be played by default). I had exactly the same issue when I first installed RaspBMC and tried to play DVD content (it plays like an audio file, in ...
This seems to be a problem with the noob release - previous versions would default to the composite video if nothing was connected to the HDMI port.
To correct this do the following:
Connect your keyboard and TV to the Pi.
Insert your SD card.
Power on the TV.
Power up the Pi and hold down the SHIFT key, until the green LED stops flickering This will ...
As Qualcuno pointed out yesterday, the RPi (all models) does not have support for hardware acceleration of H.265 video sources. As such, the RPi just doesn't have the raw horsepower needed to decode higher resolution videos on the fly.
Will an MPEG-2 License help?
MPEG-2 is a totally different encoding type, so no it won't help your case.
do I even ...
Here's the relevant part of the official docs.
Min and max:
GPU memory in megabytes, sets the memory split between the CPU and GPU; the CPU gets the remaining memory. The minimum value is 16; the technical maximum value 944 [for the RPi 4]. The default value is 64, values above 512 will not provide increased performance and should not be used.
Raspbmc is a very simple way to get your Raspberry Pi running XBMC.
The installation process is as simple as inserting an SD card into your computer and running the installation script. Once this is done, you simply insert your SD card into your Raspberry Pi and it sets itself up automagically.
I've found the wiki and irc channel (#rasbmc) on Freenode to ...
At the moment, it seems there is still no stable software to encode h264 video using the hardware, even if it has been officially announced that the Raspberry Pi does support h264 hardware-encoding. So, we cannot do a benchmark to compare performances to a regular PC.
I don't know if someone is working on the subject, but a developer from libav seems ...
There are a couple of codecs not shipped with Raspbian. You can do two things.
Buy a license.
Get rid of incompatible files. For instance, use a more powerful computer and run
ffmpeg -i "some video.wmv" -qscale 0 "some video.mkv"
which will convert the video nicely. For Debian derivates (like Ubuntu), ffmpeg comes in a package of the same name.
While you ...