On Freitag 08 September 2006 19:22, Martin Wache wrote: > Stefan Lucke schrieb: > > > Except check conditions are reversed > > if ( videoOut->Initialize() ) -> OK path in LoadSubplugins() > > if ( !videoOut->Initialize() ) -> OK path ??? without subplugins > > > > Fix is in cvs. > > > Ups, I guess that was me... But what really is embarrassing is that I > didn't even notice this when looking at the code :-o
Seems to be a common problem, as the same happend in front of my screen too. > > But this brings to my mind that I wanted to suggest long ago to use the > Initialize() methods to auto-detect the video out methods. Currently, if > all methods are compiled the default is video-vidix. If this is missing > video-fb, then video-dfb and finally video-xv. I think that this is > rather stupid. I won't say it is an intelligent or a sopisticated way, perhaps we should bail out when -vo is not given. I've no preference in that case except that it should be clear what would happen. > I would suggest that, if no options are given to first try > video-xv.Initialize(), if that fails video-dfb.Initialize(), then vidix > and last and least fb. > I think this would make quite a reliable autodetection. > Comments? > -- Stefan Lucke _______________________________________________ Softdevice-devel mailing list [email protected] https://lists.berlios.de/mailman/listinfo/softdevice-devel
