... > > same, as I'm calling df_xine to output on CRTC2 in both cases... > > Where can I find an explanation of these layers? I'd like to understand > what that all means.
I think the link http://www.directfb.org/docs/ is not published on the DirectFB homepage, but I just checkt minutes ago and it's still alive. Grab that DirectFB_overview_V0.2.pdf document, I think it will explain at least a few things. > > > BTW, Tony, I read in your older post in this thread you where looking > > for better field parity support in DVB stuff like VDR. Well, I don't > > know if you follewd closely this list but Stefan Lucke seems to have > > found the solution for that in softdevice... > > Yes, I saw that and he sent me a patch for testing. Unfortunately I got > a blank white screen! I think he's obviously making progress though, and > if there is still a problem with the driver and I didn't do something > wrong at my end he should be able to fix it once he gets a chance to > test his G550 with a TV. > > > Then, the only thing I would miss in both softdevice and df_xine would > > be the ability to hardware-blend OSD data on the Matrox > subpicture layer > > when using CRTC2 for the video (I think that is certainly reducing CPU > > usage especially with OSD-intense applications like VDR), just like > > mplayer -vo dfbmga is doing. Stefan Lucke already has a few > > Matrox-specific options in his code, that encourages me to hope that > > such special treating of layers can be implemented even if his DFB > > output in softdevice is generic. > > I didn't notice the OSD's CPU usage being a problem, but it definitely > was when I was using vdr-xine with a P3-700, Radeon and X. Luckily > vdr-xine has an option to disable the alpha blending. Well, I noticed that when I once or twice had VDR+softdevice+text2skin running, with a skin having animated stuff in it. If I understood right (tm), the OSD is software-blended in the rendered video frame before blitting it on the output layer. Again, if I understood right (tm), in Ville's dfbmga mplayer video output driver, the OSD is drawn (on demand, that is, depending on command-line switches) as it's Matrox-specific, when we want TV-output, in the subpicture layer (usualy layer 3) and the video on the primary layer (CRTC2 if you set primary-layer=2), and the blending is done in hardware, by the graphics card. I hope this is not bulshit, what I just said... :-)
