Re: [Libvisual-devel] Re: Libvisual-devel digest, Vol 1 #193 - 1 msg

[Dennis S. <sy...@yo...>]

On Tue, 2005-03-01 at 04:29 +0100, Jon =C3=98yvind Kjellman wrote:
> Thanks, alsa input works ok now, although still upside down (I only =20
> noticed it on the G-Force text.) What am I doing wrong?

I am not sure, but I see Vitaly using the following within lvdisplay
it's glx driver:

                glMatrixMode(GL_PROJECTION);
                glPixelZoom(1.0f, -1.0f);
                glRasterPos2f(-1.0f, 1.0f);
		glDrawPixels(....

Regarding lvdisplay, it's our in development displaying framework :)

> In my project I want the option to choose random plug-ins. I started =20
> hacking some nasty code to switch plug-in, but noticed =20
> visual_bin_switch_actor_by_name(). How does this work? Will it create a=
 =20
> new actor? ... destroy the old? ... preserve rundepth (8bit -> 24bit) s=
et =20
> during visual_actor_video_negotiate()?

When using a bin, you should use it 'managed', it supports fading=20
between plugins, however there are some serious problems with it.

The whole VisBin will be replaced within this devel cycle to make
place for VisPipeline, we will still have a VisBin but that would
serve as an abstract facade to the VisPipeline stuff.

I think it's wiser to deal with the actor yourself for now, and sit
in there till the new code is there, if you decide otherwise,
check the xmms and bmp plugin out. Also the 'morph' example
(which is outdated[tm]), might proof some basic information. It it
doesn't work out, ask again :)

> Not entirely on the topic of libvisual, but in my project I'm rendering=
 =20
> the plug-in in the background with some other tings in front of it. =20
> However when I tried with the OpenGL based plug-ins it is a royal mess.=
 It =20
> displays, but there are lots of strange artifacts. I'm pretty sure it's=
 =20
> due to me messing up OpenGL buffers and attributes the plug-in uses and=
 it =20
> messing it up for me. The question is (besides any good ideas on how to=
 do =20
> this in a working fassion): are OpenGL plug-ins allowed everything (by =
=20
> convention) or do they adhere to some rules which may make my life simp=
ler?

I am pretty sure this is possible, we had a discussion on this
before. AND we want to support blit overlaying in GL, however=20
honestly, I am not GL master, I think Vitaly has to jump in here
and help you, so, Vitaly, or any other openGL know it all, help him
out! :)

> Are there anyone working on a xine-lib input plug-in?

Nope, and this would be GREATLY appreciated, also native xine support ;)
so they can use lv to render libvisual :)

> > I am very interested in this, I want to work up our state of docs, I
> > also want to startup a wiki as a source of information and the such.
>=20
> I've started writing on a small tutorial and I'll 'bomb' the example wi=
th =20
> relevant comments. I'll post it for review when it's done.

Sounds superb, in what format are you writing the tutorial ? I would
love a docbook, if this is not too hard :) (anything other
would be cool of course)

> > I understand that you're working on some car multimedia project ? do
> > you have urls regarding this, I am very interested about all this! :)
>=20
> No urls at the moment. It isn't release worthy yet. But it'll be =20
> open-sourced and I'll post something here when I unleash it on the net =
=20
> (shouldn't be many weeks.)

Ok keep us updated, this is super!

Cheers,
Dennis