Feature #1331
openSupport for OpenMAX (Raspberry Pi)
0%
Description
I have seen it in the "planned" section of the project description but, apparently, there is no formal request for it. Here it is.
The support of the OpenMAX API will allow us to run a complete standalone VDR on the now famous Raspberry Pi platform. Today, the only way to run VDR on it is as a backend of XBMC or OpenELEC thanks to the XVDR plugin, but VDR is unable to take advantage of the hardware decompression of the Raspi.
There are only few softwares currently taking advantage of the huge graphic capabilities (compared with its price and size) of this device including XBMC or omxplayer.
Unfortunately I am of no help for developing this, but available for testing with great pleasure.
Updated by psofa over 11 years ago
Iirc johns raised up an issue with the pi:
There is no hardware deinterlacing method so deinterlacing has to be done in software.
However in this topic
http://www.raspberrypi.org/phpBB3/viewtopic.php?t=18096 it is said that simple deinterlacing can be done on the pi using gpu programing (not a dedicated deinterlacer but not the slow cpu either).
Even if it proves hard to port omxplayer functionality it would be interesting even without deinterlacing.For example setting an interlaced mode and let the tv's deinterlacer do the work.In fact personally i wouldnt mind running vdr on interlaced mode all the time since 99% of my received services are interlaced
Updated by leonce over 11 years ago
Thanks psofa for these details. However, if I take a .vdr file (recorded from a sat TV stream) and play it with omxplayer, it is running just smoothly. That's why I thought it would be easy to implement this :-(
Wouldn't it be a good approach to "only" generate a stream compatible with omxplayer then send it to this player ? It is already running quite well with streamdev for example, but omxplayer disconnects as soon as we change the channel because of the stream being interrupted. By integrated the handling of omxplayer directly in softhddevice, we could be able to handle the stream stops and starts and, last but not least, the OSD could be directly muxed in it.
Am I wrong ?
Thanks,
Leonce
Updated by leonce over 11 years ago
Thanks psofa for these details. However, if I take a .vdr file (recorded from a sat TV stream) and play it with omxplayer, it is running just smoothly. That's why I thought it would be easy to implement this :-(
Wouldn't it be a good approach to "only" generate a stream compatible with omxplayer then send it to this player ? It is already running quite well with streamdev for example, but omxplayer disconnects as soon as we change the channel because of the stream being interrupted. By integrated the handling of omxplayer directly in softhddevice, we could be able to handle the stream stops and starts and, last but not least, the OSD could be directly muxed in it.
Am I wrong ?
Thanks,
Leonce
Updated by psofa over 11 years ago
im not familiar with the softhddevice source code, but whatever omxplayer does, softhddevice can also do assuming someone writes the code for it :)
However i doubt deinterlacing done by omxplayer matches in quality that of vdpau.....
Updated by psofa over 11 years ago
by the way , i did a quick google research.One can either do deinterlacing via an openmax component (i suppose implemented in the binary blob) or by getting the frames on opengl textures and then deinterlacing via opengl facilities.
Updated by psofa over 11 years ago
oh and interlaced output seems out of the question :( (there are problems with field syncing) .again these are quick google searches.......
Updated by leonce over 9 years ago
This request can be closed now (and also removed from the Todo list) : there is now a plugin called rpihddevice which does the job very well !