Re: [xine-user] Can xine play from a buffer ?

[Michel C. <mc...@ma...>]

Thank you for your information.
As you recommend I start reading the xine hacker's guide and I find it
very useful.

I like your recommendation to do a plug-in, however the company where I
work for, they want me to develop our company client, using xine to
render the media. Our client will get a list of media names that user
can select to play.

We will sell the server and give for free the Linux client.

Also I'm planning to do something that can be very useful for the xine
community. A C++ interface or a C++ wrapper for xine library.
I already post a message in the xine user list asking if a C++ interface
already exists. If not I will create one :)

Michel Cunha

Le jeu 27/02/2003 =C3=A0 15:49, Michael Roitzsch a =C3=A9crit :
> Hi Michel,
>=20
> > The functionality of this client player is to open a UDP socket,
> > receive the media stream data from the server, put the data in a
> > queue, send control messages back to the server if necessary (for
> > example, to ask the server to resend a package) and tell xine
> > libraries to render the queued data.
> >
> > Since I have never to program with xine,can somebody guide me, while
> > saying to me which header files and xine methods I should use ?
>=20
> The job you describe is the typical use of a xine input plugin. A good=20
> start for reading is the xine hacker's guide on the website. It is a=20
> bit outdated, but still should give you some ideas about the internal=20
> architecture of xine.
> The benefit of using an input plugin for this is: it will work with any=
=20
> xine-lib frontend available. The drawback is: You are not coding a=20
> client to xine-lib, but a plugin for xine-lib. This makes you a bit=20
> more dependent of xine-lib's internal APIs, which can still change from=
=20
> time to time.
>=20
> There was a rtp input plugin, that could handle a udp://host:port/ styl=
e=20
> MRL (that is, you could start xine with 'xine udp://somewhere:42/'),=20
> but this plugin has never been ported to xine's new internal APIs. You=20
> could start from there. The code is still there is=20
> xine-lib/src/input/input_rtp.c.
>=20
> Michael