Re: [Ekiga-devel-list] preliminary patch for X-Video support

[Damien Sandras <dsandras seconix com>]

Le mardi 19 septembre 2006 à 21:02 +0200, Matthias Schneider a écrit :
> --- Gregory Stark <gsstark mit edu> schrieb:
> 
> > 
> > Matthias Schneider <ma30002000 yahoo de> writes:
> > 
> > > Concerning the PIP issue, as Gregory already pointed out correctly every
> > > recent X graphics adaptor driver should support multiple overlays. In case
> > > the second overlay shouldnt be possible, my implementation simply doesnt
> > > display it.
> > 
> > Well sadly that's a bit overoptimistic. I only said that there existed some
> > graphics cards whose drivers provided multiple overlays. There are certainly
> > still cards, even brand new cards, whose drivers don't. Including, for
> > example, my brand new ATI :( It may just be because the driver is relatively
> > new or it may be a hardware limitation, I don't know.
> > 
> > Because the overlay is so much better it may be worth indicating to the user
> > when a window doesn't use an overlay. (preferably not in a popup window
> > though!). Otherwise the user may have no idea that disabling PIP would make
> > his display much smoother. (Or he may just say "ekiga PIP sucks" rather than
> > "my graphics card sucks but at least ekiga is making the most of it")
> > 
> > -- 
> > greg
> > 
> Hi Gregory,
> it seems I was mistaken on the port-issue, I found out that all the systems I saw with multiple
> ports (mine has 33) where systems with the closed-source nvidia driver (I spotted some matrox as
> well if I remember correctly). 
> 
> In the meantime I have made some advances on the virtual PVideoOutputDevice_ekiga, which now
> allows to fall back to the GDK/SDL output in case XV failes to initialize. About an XV PiP window
> I can think of the following fallback options:
>  1) we simply dont display the local picture
>  2) we scale the local picture into the remote one by software and scale the resulting picture in
> hardware
>  3) we fall back to GDK/SDL completely
> 
> Right now my implemention works like 1), which is what I personally prefer, since all the exercise
> was to prevent software scaling. However I would be open to other opinions and suggestions.. I
> dont know how it is possible to signal the state of acceleration by a non popup means, one idea
> would be to put something into the window title in case the video is displayed in an external
> window (e.g. "Video - XV") so it is possible to differ by other means except the resulting
> quality... Any idea how that could be possible in the incrusted modes?
> 

you can also put a warning in the general history window. 1 is ok.

> Well, right now I am working on the integration with the menus of ekiga (fullscreen, 200%, etc)
> and as a last big bite I still have the GDK-incrusted XV window to investigate, which seems to be
> more complicated than it sounds...
> 
> Thats all for now,
> Matthias
> 
> 
> 
> 		
> ___________________________________________________________ 
> Telefonate ohne weitere Kosten vom PC zum PC: http://messenger.yahoo.de
> _______________________________________________
> Ekiga-devel-list mailing list
> Ekiga-devel-list gnome org
> http://mail.gnome.org/mailman/listinfo/ekiga-devel-list
-- 
 _      Damien Sandras
(o-     
//\     Ekiga Softphone: http://www.ekiga.org/
v_/_    FOSDEM 2006    : http://www.fosdem.org/
        SIP Phone      : sip:dsandras ekiga net
                         sip:600000 ekiga net