Vmeta: Difference between revisions
Jump to navigation
Jump to search
DanielDrake (talk | contribs) (Created page with 'vMeta is a hardware-accelerated multimedia encoding and decoding engine included in the XO-1.75 and XO-4. === Installation and test === Tested on 12.1.0 on XO-1.75. # Install …') |
DanielDrake (talk | contribs) No edit summary |
||
| Line 10: | Line 10: | ||
Note that these packages do include software decoders too (not sure why) so just seeing the video play back doesn't mean that it is being done by the vmeta hardware engine. The best way to be confident that hardware accel is being used is by looking at totem standard output, which should be limited to: |
Note that these packages do include software decoders too (not sure why) so just seeing the video play back doesn't mean that it is being done by the vmeta hardware engine. The best way to be confident that hardware accel is being used is by looking at totem standard output, which should be limited to: |
||
<pre> |
|||
{{{ |
|||
vmetadec istance(0x....) found |
vmetadec istance(0x....) found |
||
At finalizing, Gstvmetadec instance(0x....) DecErroOccured is 0x0 |
At finalizing, Gstvmetadec instance(0x....) DecErroOccured is 0x0 |
||
Gstvmetadec instance(0x....) is finalized. |
Gstvmetadec instance(0x....) is finalized. |
||
</pre> |
|||
}}} |
|||
Also look in <tt>dmesg</tt>, check that there are not any vmeta-related complaints there. |
Also look in <tt>dmesg</tt>, check that there are not any vmeta-related complaints there. |
||
Revision as of 22:13, 2 April 2013
vMeta is a hardware-accelerated multimedia encoding and decoding engine included in the XO-1.75 and XO-4.
Installation and test
Tested on 12.1.0 on XO-1.75.
- Install gstreamer-plugins-marvell and libvmeta-marvell
- Download http://techslides.com/demos/sample-videos/small.mp4 and play it in Totem in GNOME
Note that these packages do include software decoders too (not sure why) so just seeing the video play back doesn't mean that it is being done by the vmeta hardware engine. The best way to be confident that hardware accel is being used is by looking at totem standard output, which should be limited to:
vmetadec istance(0x....) found At finalizing, Gstvmetadec instance(0x....) DecErroOccured is 0x0 Gstvmetadec instance(0x....) is finalized.
Also look in dmesg, check that there are not any vmeta-related complaints there.