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 ...
The license enables you to decode and encode (where applicable) the mentioned media types using the built in hardware encoders/decoders.
H.264 Encode is enabled in the latest version (Included in Pi Price) which is great!
For an extra £2.40 you can watch MPEG2 video, ie DVD's are encoded in MPEG2!
For an extra £1.20 you can decode VC-1 video, ie ...
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.
The images of OpenELEC and Raspbmc I found don't work well yet on my RPI. I have tried them and they either crash or don't boot, etc.
If you want to play around, while waiting for those two distribution to become more mature, you can use the following debian image with xbmc precompiled: http://rpi-developers.com/projects/xbmc/
[UPDATE (Dec 2, 2012)]: I gave ...
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.
The video codecs actually fall into three categories - those supported and enabled by the GPU, those supported by the GPU but not enabled due to licensing restrictions, and those not supported at all.
As for details of what goes where, this blog post gives the info:
Two licensed codecs will be provided at launch, MPEG4 and h.264. Codec licences have ...
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 ...
sudo sh -c "TERM=linux setterm -foreground black >/dev/tty0"
sudo sh -c "TERM=linux setterm -clear all >/dev/tty0"
This will change the font color to black, than clears the screen.
Or in a single line:
sudo sh -c "TERM=linux setterm -foreground black -clear all >/dev/tty0"
And set it back to normal:
sudo sh -c "TERM=linux setterm -foreground ...
The Raspberry Pi foundation has announced that The official Raspberry Pi touchscreen display is now available. This is a ten-point touchscreen, which connects to the DSI connector and has full kernel support, after an upgrade.
Given that this has taken the foundation several years to finish, I doubt it is something that anyone could easily hack together ...
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 ...
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 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 ...
To answer your question, any H.264 encoding will work perfectly on the Raspberry Pi. So you have to select (whatever profile you pick, best high profile or normal) the H.264 option in the tab Video under Video codec. For audio use AAC (supported) and pick stereo (Dolby surround doesn't work).
Using those settings (tested it myself) everything plays nice and ...
Theoretically, you will be able to do so, based on the information on Broadcom's page:
The BCM2835 has 1080p30 Full HD HP H.264 Video Encode/Decode capabilities, the only question is if and when someone will come up with a driver that supports that kind of functionality.
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 ...
Regardless of distribution, if you want a media player then use OMXPlayer.
It is still the only media player that offers full hardware accelleration (as far as I know). Anything else will provide choppy video playback.
Also, it might be useful for you to know that the Debian Wheezy beta has OMXPlayer installed by default.
Firstly make sure you boot straight into X.
For details on this, please see this question:
Auto-start X-windows / gdm on the standard Debian build
Then edit your ~/.xinitrc file. It needs to contain the command that starts your media player:
omxplayer -p -o hdmi /home/oliver/awesome.mp4
This will make the video begin as soon as X does.