On Friday 26 January 2007 16:32, Stefan Lucke wrote: > On Freitag 26 Januar 2007 14:56, Nicolas Huillard wrote: > > Laz a écrit : > > >>Is there anything in DirectFB which has chagned drastically for the > > >>Unichrome driver? > > > > > > Sorted it: I had pixelformat=ARGB instead of AiRGB in /etc/directfbrc. > > > Looks like a check for the pixel format has been added when setting > > > DLOP_ALPHACHANNEL! Not sure quite when I added that, or whether I even > > > need it now! > > > > In my case, ARGB works and AiRGB leads to no video on the screen, except > > when the OSD is openned (softdevice 0.3.1). > > IIRC, this is softdevice change. Not DirectFB. > > For DirectFB cvs version taken past 2006-12-12 you'll softdevice cvs > version from 2007-01-20 or the following diff applied to your > softdevice version: > http://cvs.berlios.de/cgi-bin/viewcvs.cgi/softdevice/softdevice/video-dfb.c >.diff?r1=1.75&r2=1.76
Yep: just added that (didn't want to update softdevice fully because I _think_ it was one of the plugins I had to hack slightly to get it to compile with vdr-1.5.0 (maybe it wasn't: I'll try it later on!). > With this softdevice change, you may use AiRGB as pixelformat even with > DirectFB versions taken before 2006-12-12. The reason for being forced to > use AiRGB is the following change in DirectFB: > http://www.directfb.org/index.php/viewcvs.cgi/DirectFB/gfxdrivers/unichrome >/uc_primary.c.diff?r1=1.2&r2=1.3 Found that too. :) Updating all these bits has not introduced any interlacing artifacts with via TV-out and hardware decoding, which is good! I also have video whether the OSD is showing or not! Cheers, Laz _______________________________________________ Softdevice-devel mailing list [email protected] https://lists.berlios.de/mailman/listinfo/softdevice-devel
