libvisual-devel — libvisual mailinglist for developers

Re: [Libvisual-devel] everything is fine

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

Woohoo, I'm so happy to hear that, I already started to
get nightmares about odd distro specific race condition
somewhere nested inside the code! :)

BTW: What are your plans regarding libvisual-xmms (so
we can add that to the roadmap as well)

Cheers,
Dennis

On Thu, 2004-09-02 at 18:52 -0300, Duilio Javier Protti wrote:
> Ok, the problem with some plugins was due to a lack
> of sync with libvisual-xmms module on CVS (which include
> updates corresponding to last libvisual API changes).
> 
> Now I can test my work, so let's go work.
> 
> Bye,
> Duilio.

[Libvisual-devel] gforce 'dist' target working and data get installed right

[Duilio J. P. <dp...@fc...>]

Now the dist target includes data files and headers.
Data files are installed now on
$(prefix)/libvisual/actor/actor_gforce directory.

However, still missing from installation (and distro)
data files whose name contains white spaces. I think
this cannot be handle by automake, probably we will
have to change filenames (Dennis, is that possible?).

Headers needs lot of cleanup to avoid warnings.


Enjoy it!

[Libvisual-devel] Minor problems with compilation

[salsaman <sal...@xs...>]

Hi,
I am looking into making a livido wrapper for the libvisual plugins. 
Livido details can be found at http://livido.dyne.org/codedoc/. This 
will be a new open source architecture for video plugins. Once this is 
done, your plugins will be usable in LiVES, Cinelerra, FreeJ, Veejay, 
effecTV and PDP.

I have compiled libvisual, but an error came up in the process. You need 
to add -I . to the include files, as the headers are in . for a new 
build until make install is run.

Tomorrow I will try to build a livido wrapper. This should not be too 
complicated, I will retrieve a list of plugins and each one will become 
a livido_class in the wrapper library. Each class will construct a 
channel template with 0 in channels and one out channel with whatever 
palettes the plugin allows.

Within livido, each livido_class can be used to create any number of 
livido_instances. each instance in this case representing an instance of 
a libvisual plugin.

OK, quick question, are the plugins threadsafe - ie. can I start up 
several instances of different/the same plugin without problem ?

Currently the only problem I forsee is with the size negotiation, I 
understand that libvisual uses horizontal and vertical block size 
restrictions, whereas livido currently only allows a completely free or 
a fixed channel size. I will suggest to the other livido developers that 
we implement something for block sizes.

I hope you are serious about developing this architecture, because this 
could become a very nice addition to the livido plugin set.

Regards,
Salsaman.

http://lives.sourceforge.net

[Libvisual-devel] everything is fine

[Duilio J. P. <dp...@fc...>]

Ok, the problem with some plugins was due to a lack
of sync with libvisual-xmms module on CVS (which include
updates corresponding to last libvisual API changes).

Now I can test my work, so let's go work.

Bye,
Duilio.

Re: [Libvisual-devel] Re: New plugin system.

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

I have moved it into the plugin specific data structure and I totally
think it belongs here (VisActorPlugin etc etc)

This way generic plugins can be created as well, for libvisual-display
for example.

Cheers,
Dennis


On Wed, 2004-09-01 at 23:28 -0300, Duilio Javier Protti wrote:
> > /**
> >  * The VisPluginInfo data structure contains information about a plugin
> >  * and is filled within the plugin itself.
> >  */
> > struct _VisPluginInfo {
> >
> >         .....
> >
> > 	/* FIXME do we move prefs to the separate plugin structures, or
> > do we move everything (the methods as well) into an union here ? */
> >         union {
> >                 struct {
> >                         int     depth;
> >                 } actor;
> > 
> >                 struct {
> >                         int     depth;
> >                 } morph;
> >         } prefs;
> > 
> > };
> 
> I think would be good to move prefs to _VisPluginData, because it is
> data subject to change on the fly. This way we kept all 'static' info on
> _VisPluginInfo and 'dynamic' plugin info go to _VisPluginData.
> 
> Bye,
> Duilio.

Re: [Libvisual-devel] libvisual working ok

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

That is very strange, I have nothing like this locally, can you make
a screenshot so I've got an idea what is happening ?

Cheers and thanks,
Dennis


On Thu, 2004-09-02 at 00:18 -0300, Duilio Javier Protti wrote:
> Ok, now libvisual works well on my system with
> the last CVS update. However, some plugins, like
> infinite, shows strange colors, it looks like it
> initializes right, but then the palette goes bits
> down and colors are screwed.
> 
> Any idea? I will check this tomorrow.
> 
> Bye,
> Duilio.
> 
> 
> 
> -------------------------------------------------------
> This SF.Net email is sponsored by BEA Weblogic Workshop
> FREE Java Enterprise J2EE developer tools!
> Get your free copy of BEA WebLogic Workshop 8.1 today.
> http://ads.osdn.com/?ad_id=5047&alloc_id=10808&op=click
> _______________________________________________
> Libvisual-devel mailing list
> Lib...@li...
> https://lists.sourceforge.net/lists/listinfo/libvisual-devel

[Libvisual-devel] libvisual working ok

[Duilio J. P. <dp...@fc...>]

Ok, now libvisual works well on my system with
the last CVS update. However, some plugins, like
infinite, shows strange colors, it looks like it
initializes right, but then the palette goes bits
down and colors are screwed.

Any idea? I will check this tomorrow.

Bye,
Duilio.

[Libvisual-devel] Re: problems with xmms plugin (or libivisual)

[Duilio J. P. <dp...@fc...>]

Yes, I have tried, and it doesn't work! The error messages
still exactly the same. (??)

Bye,
Duilio.

> Hmms I can't reproduce this here. Have you tried removing all the
> plugins and rebuilding everything ?
> 
> Cheers,
> Dennis
> 
> 
> On Fri, 2004-08-27 at 20:28 -0300, Duilio Javier Protti wrote:
> > I can't make it work the xmms plugin, the output is:
> > 
> > Message: All plugins enabled
> > libvisual CRITICAL: XMMS plugin: visual_mem_free
> > [(../../libvisual/lv_mem.c,44)]: assertion `ptr != NULL' failed
> > libvisual CRITICAL: XMMS plugin: visual_mem_free
> > [(../../libvisual/lv_mem.c,44)]: assertion `ptr != NULL' failed
> > libvisual CRITICAL: XMMS plugin: visual_mem_free
> > [(../../libvisual/lv_mem.c,44)]: assertion `ptr != NULL' failed
> > libvisual CRITICAL: XMMS plugin: visual_video_free_buffer
> > [(../../libvisual/lv_video.c,172)]: assertion `video->screenbuffer !=
> > NULL' failed
> >  
> > Segmentation fault
> >  
> > You've probably found a bug in XMMS, please visit
> > http://bugs.xmms.org and fill out a bug report.
> > 
> > 
> > And valgrind show this:
> > 
> > ==22202== Invalid read of size 4
> > ==22202==    at 0x44441902: visual_plugin_get_reference (in
> > /usr/lib/libvisual.so.0.0.0)
> > ==22202==    by 0x44441C3F: plugin_add_dir_to_list (in
> > /usr/lib/libvisual.so.0.0.0)
> > ==22202==    by 0x444419EE: visual_plugin_get_list (in
> > /usr/lib/libvisual.so.0.0.0)
> > ==22202==    by 0x44444EC7: visual_init (in /usr/lib/libvisual.so.0.0.0)
> > ==22202==    Address 0x4 is not stack'd, malloc'd or free'd
> >   
> >  Segmentation fault
> >    
> >   You've probably found a bug in XMMS, please visit
> >   http://bugs.xmms.org and fill out a bug report.
> > 
> > 
> > I have tested with infinite and jess plugins, but the 
> > behavior is exactly the same. I think there is a problem 
> > on libvisual core.
> > 
> > Bye,
> > Duilio.

[Libvisual-devel] Re: New plugin system.

[Duilio J. P. <dp...@fc...>]

> /**
>  * The VisPluginInfo data structure contains information about a plugin
>  * and is filled within the plugin itself.
>  */
> struct _VisPluginInfo {
>
>         .....
>
> 	/* FIXME do we move prefs to the separate plugin structures, or
> do we move everything (the methods as well) into an union here ? */
>         union {
>                 struct {
>                         int     depth;
>                 } actor;
> 
>                 struct {
>                         int     depth;
>                 } morph;
>         } prefs;
> 
> };

I think would be good to move prefs to _VisPluginData, because it is
data subject to change on the fly. This way we kept all 'static' info on
_VisPluginInfo and 'dynamic' plugin info go to _VisPluginData.

Bye,
Duilio.

[Libvisual-devel] new plugin system.

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

The new plugin system has landed in CVS and all plugins are updated.

In order to get it working remove all the old plugins from 
%prefix/lib/libvisual first.

>From now on the framework does plugin versioning, and saves
the struct size to check against.

What is left for 0.1.6 is:
Libvisual:
	Timed morph,
	Method to check if a morph needs audio,
	Update lv_bmp.c to support big and little endian right.

Libvisual-plugins:
	Finish the bumpscope plugin.
	Make a new slide morph plugin (from top, bottom, left, right)
	Fix flash plugin on 16 bit.

Libvisual-gforce:
	Fix the source tree so it works with make dist (Our
		automake guru Duilio is working on this one!)


Cheers,
Dennis

Re: [Libvisual-devel] New plugin system.

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

I've changed a few things:


Plugin initializer:
___
        static const VisActorPlugin actor[] = {{
                .requisition = act_infinite_requisition,
                .palette = act_infinite_palette,
                .render = act_infinite_render,
                .depth = VISUAL_VIDEO_DEPTH_8BIT
        }};

        static const VisPluginInfo info[] = {{
                .struct_size = sizeof (VisPluginInfo),
                .api_version = VISUAL_PLUGIN_API_VERSION,
                .type = VISUAL_PLUGIN_TYPE_ACTOR,

                .plugname = "infinite",
                .name = "infinite plugin",
                .author = "Original by: Julien Carme
<jul...@ac...>, Port by: Dennis Smit
<ds...@ne...>",
                .version = "0.1",
                .about = "The infinite visual plugin",
                .help = "This is the libvisual plugin for the infinite
visual",

                .init = act_infinite_init,
                .cleanup = act_infinite_cleanup,
                .events = act_infinite_events,

                .plugin = (void *) &actor[0]
        }};
___

Now the plugin system can load any type of plugin (also non actor,
input, morph) plugins.

[Libvisual-devel] New plugin system.

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

Alright I landed most of the new plugin system, it's based mostly
on the work by Vitaly.

It's not yet completely set in stone, not yet in CVS (have to
finish a few bits tomorrow), and it's open for discussion. Although
with a bit of hurry because I won't have a lot of time upcoming 2 weeks
and the 10th of September I want to release 0.1.6.

The structures:

struct _VisPluginRef {
        char                    *file;
        int                     usecount;
        VisPluginInfo           *info; /* This info is a duplicate
because plugins are closed after the registry is build (I don't like
the idea of having unused plugins dlopened.) */
};

/**
 * The VisPluginInfo data structure contains information about a plugin
 * and is filled within the plugin itself.
 */
struct _VisPluginInfo {
        uint32_t        struct_size; /* Hey isn't that cool, we can now
check for ABI compatability! was about time, thanks vitaly! :) */
        uint32_t        api_version;
        VisPluginType   type;

        char    *plugname;

        char    *name;
        char    *author;
        char    *version;
        char    *about;
        char    *help;

        plugin_init_func_t      init;
        plugin_cleanup_func_t   cleanup;
        plugin_events_func_t    events;

	/* FIXME do we move prefs to the separate plugin structures, or
do we move everything (the methods as well) into an union here ? */
        union {
                struct {
                        int     depth;
                } actor;

                struct {
                        int     depth;
                } morph;
        } prefs;

};

struct _VisPluginData {
        VisPluginRef            *ref;

	/* This info the real plugin info that is retrieved from the
plugin after the plugin is loaded, the ref contains a copy for
closed plugins */
        const VisPluginInfo     *info;

        VisEventQueue           eventqueue;
        VisParamContainer       params;

        int                     plugflags;
        VisSongInfo             *songinfo;

        int                     realized;
        void                    *handle;

        union {
                void            *generic;

		/* These contain plugin specific methods, IMPORTANT
do we rather have a union in VisPluginInfo, or not  ? */
                VisActorPlugin  *actor;
                VisInputPlugin  *input;
                VisMorphPlugin  *morph;
        } plugin;

        void                    *priv;
};

/**
 * The VisActorPlugin structure is the main data structure
 * for the actor (visualisation) plugin.
 *
 * The actor plugin is the visualisation plugin.
 */
struct _VisActorPlugin {
        plugin_actor_requisition_func_t  requisition;   /**< The
requisition function. This is used to
                                                         * get the
desired VisVideo surface size of the plugin. */
        plugin_actor_palette_func_t      palette;       /**< Used to
retrieve the desired palette from the plugin. */
        plugin_actor_render_func_t       render;        /**< The main
render loop. This is called to draw a frame. */
};

/**
 * The VisInputPlugin structure is the main data structure
 * for the input plugin.
 *
 * The input plugin is used to retrieve PCM samples from
 * certain sources.
 */
struct _VisInputPlugin {
        plugin_input_upload_func_t       upload;        /**< The sample
upload function. This is the main function
                                                          * of the
plugin which uploads sample data into
                                                          * libvisual.
*/
};

/**
 * The VisMorphPlugin structure is the main data structure
 * for the morph plugin.
 *
 * The morph plugin is capable of morphing between two VisVideo
 * sources, and thus is capable of morphing between two
 * VisActors.
 */
struct _VisMorphPlugin {
        plugin_morph_palette_func_t      palette;       /**< The plugin
it's palette function. This can be used
                                                          * to obtain a
palette for VISUAL_VIDEO_DEPTH_8BIT surfaces.
                                                          * However the
function may be set to NULL. In this case the
                                                          * VisMorph
system morphs between palettes itself. */
        plugin_morph_apply_func_t        apply;         /**< The plugin
it's main function. This is used to morph
                                                          * between two
VisVideo sources. */
};


______

And the plugin part (get_plugin_info, init, cleanup):

const VisPluginInfo *get_plugin_info (int *count)
{
        static const VisPluginInfo info[] = {{
                .struct_size = sizeof (VisPluginInfo),
                .api_version = VISUAL_PLUGIN_API_VERSION,
                .type = VISUAL_PLUGIN_TYPE_ACTOR,

                .plugname = "infinite",
                .name = "infinite plugin",
                .author = "Original by: Julien Carme
<jul...@ac...>, Port by: Dennis Smit
<ds...@ne...>",
                .version = "0.1",
                .about = "The infinite visual plugin",
                .help = "This is the libvisual plugin for the infinite
visual",

                .init = act_infinite_init,
                .cleanup = act_infinite_cleanup,
                .events = act_infinite_events,

                .prefs.actor.depth = VISUAL_VIDEO_DEPTH_8BIT

        }};

        *count = sizeof (info) / sizeof (*info);

        return info;
}

int act_infinite_init (VisPluginData *plugin)
{
        InfinitePrivate *priv;
        VisActorPlugin *actplug = visual_plugin_actor_new ();;

        visual_log_return_val_if_fail (plugin != NULL, -1);

        plugin->plugin.actor = actplug;

        actplug->requisition = act_infinite_requisition;
        actplug->palette = act_infinite_palette;
        actplug->render = act_infinite_render;

        priv = visual_mem_new0 (InfinitePrivate, 1);
        plugin->priv = priv;

        priv->plugwidth = 32;
        priv->plugheight = 32;

        visual_palette_allocate_colors (&priv->pal, 256);

        _inf_init_renderer (priv);

        return 0;
}

int act_infinite_cleanup (VisPluginData *plugin)
{
        InfinitePrivate *priv;

        visual_log_return_val_if_fail (plugin != NULL, -1);

        priv = plugin->priv;

        _inf_close_renderer (priv);

        visual_palette_free_colors (&priv->pal);
        visual_mem_free (priv);

        visual_mem_free (plugin->plugin.actor);

        return 0;
}


______



So that is that, now do we want things different, what do we want
different ?

Please do your call kinda quick so I can port the other bunch of plugins
over in the evenings after school! :)

After this is done most work for 0.1.6 is done and we're near ready
for a release!

Cheers and thanks a lot,
Dennis

Re: [Libvisual-devel] problems with xmms plugin (or libivisual)

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

Hmms I can't reproduce this here. Have you tried removing all the
plugins and rebuilding everything ?

Cheers,
Dennis


On Fri, 2004-08-27 at 20:28 -0300, Duilio Javier Protti wrote:
> I can't make it work the xmms plugin, the output is:
> 
> Message: All plugins enabled
> libvisual CRITICAL: XMMS plugin: visual_mem_free
> [(../../libvisual/lv_mem.c,44)]: assertion `ptr != NULL' failed
> libvisual CRITICAL: XMMS plugin: visual_mem_free
> [(../../libvisual/lv_mem.c,44)]: assertion `ptr != NULL' failed
> libvisual CRITICAL: XMMS plugin: visual_mem_free
> [(../../libvisual/lv_mem.c,44)]: assertion `ptr != NULL' failed
> libvisual CRITICAL: XMMS plugin: visual_video_free_buffer
> [(../../libvisual/lv_video.c,172)]: assertion `video->screenbuffer !=
> NULL' failed
>  
> Segmentation fault
>  
> You've probably found a bug in XMMS, please visit
> http://bugs.xmms.org and fill out a bug report.
> 
> 
> And valgrind show this:
> 
> ==22202== Invalid read of size 4
> ==22202==    at 0x44441902: visual_plugin_get_reference (in
> /usr/lib/libvisual.so.0.0.0)
> ==22202==    by 0x44441C3F: plugin_add_dir_to_list (in
> /usr/lib/libvisual.so.0.0.0)
> ==22202==    by 0x444419EE: visual_plugin_get_list (in
> /usr/lib/libvisual.so.0.0.0)
> ==22202==    by 0x44444EC7: visual_init (in /usr/lib/libvisual.so.0.0.0)
> ==22202==    Address 0x4 is not stack'd, malloc'd or free'd
>   
>  Segmentation fault
>    
>   You've probably found a bug in XMMS, please visit
>   http://bugs.xmms.org and fill out a bug report.
> 
> 
> I have tested with infinite and jess plugins, but the 
> behavior is exactly the same. I think there is a problem 
> on libvisual core.
> 
> Bye,
> Duilio.
> 
> 
> 
> 
> -------------------------------------------------------
> This SF.Net email is sponsored by BEA Weblogic Workshop
> FREE Java Enterprise J2EE developer tools!
> Get your free copy of BEA WebLogic Workshop 8.1 today.
> http://ads.osdn.com/?ad_id=5047&alloc_id=10808&op=click
> _______________________________________________
> Libvisual-devel mailing list
> Lib...@li...
> https://lists.sourceforge.net/lists/listinfo/libvisual-devel

[Libvisual-devel] problems with xmms plugin (or libivisual)

[Duilio J. P. <dp...@fc...>]

I can't make it work the xmms plugin, the output is:

Message: All plugins enabled
libvisual CRITICAL: XMMS plugin: visual_mem_free
[(../../libvisual/lv_mem.c,44)]: assertion `ptr != NULL' failed
libvisual CRITICAL: XMMS plugin: visual_mem_free
[(../../libvisual/lv_mem.c,44)]: assertion `ptr != NULL' failed
libvisual CRITICAL: XMMS plugin: visual_mem_free
[(../../libvisual/lv_mem.c,44)]: assertion `ptr != NULL' failed
libvisual CRITICAL: XMMS plugin: visual_video_free_buffer
[(../../libvisual/lv_video.c,172)]: assertion `video->screenbuffer !=
NULL' failed
 
Segmentation fault
 
You've probably found a bug in XMMS, please visit
http://bugs.xmms.org and fill out a bug report.


And valgrind show this:

==22202== Invalid read of size 4
==22202==    at 0x44441902: visual_plugin_get_reference (in
/usr/lib/libvisual.so.0.0.0)
==22202==    by 0x44441C3F: plugin_add_dir_to_list (in
/usr/lib/libvisual.so.0.0.0)
==22202==    by 0x444419EE: visual_plugin_get_list (in
/usr/lib/libvisual.so.0.0.0)
==22202==    by 0x44444EC7: visual_init (in /usr/lib/libvisual.so.0.0.0)
==22202==    Address 0x4 is not stack'd, malloc'd or free'd
  
 Segmentation fault
   
  You've probably found a bug in XMMS, please visit
  http://bugs.xmms.org and fill out a bug report.


I have tested with infinite and jess plugins, but the 
behavior is exactly the same. I think there is a problem 
on libvisual core.

Bye,
Duilio.

Re: [Libvisual-devel] Gforce

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

Indeed it has been a while! Can you also look at making sure that the
GForceColorMaps GForceDeltaFields GForceParticles GForceWaveShapes
NotWorkingWaveShapes directories are included as well in the
'make dist' resulting source tree ?

I'll hear what you think about the ROADMAP, and if you'd like you
might want to make a roadmap for the xmms plugin.

I personally work on completing the bumpscope port today, and start
on including the new plugin system.

Cheers,
Dennis

On Fri, 2004-08-27 at 01:55 -0300, Duilio Javier Protti wrote:
> Hi, really has been a while! I have checked the libvisual-gforce
> module, and at a fast look on it I see some headers are missing 
> for the compiler. I will fix that and any other trouble on the 
> build tree. Later I will tell you my opinions about the ROADMAP
> (I'm agree on almost everything).
> 
> Bye,
> Duilio.

[Libvisual-devel] Gforce

[Duilio J. P. <dp...@fc...>]

Hi, really has been a while! I have checked the libvisual-gforce
module, and at a fast look on it I see some headers are missing 
for the compiler. I will fix that and any other trouble on the 
build tree. Later I will tell you my opinions about the ROADMAP
(I'm agree on almost everything).

Bye,
Duilio.

> Heya Duilio,
> 
> It has been a while!!!
> 
> I'm back online and back from vacation, lot's have been checked into CVS
> and I've added a new plugin 'libvisual-gforce' in the 'libvisual-gforce'
> module.
> 
> Would you like to look at the build tree of libvisual-gforce
> and make 'make dist' work as it should ?, your build skills are
> far superior compared to mine :)
> 
> Cheers,
> Dennis

Re: [Libvisual-devel] Going to Evoke!

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

On Thu, 2004-08-26 at 11:46 +0200, Dennis Smit wrote:
> Heya List,
> 
> I'm just being told that I'm going to the Evoke demo scene party
> (www.evoke-net.de), are other people from the list going as well ?
> 
> Cheers,
> Dennis


I recall that... I will not be going to evoke :(

Sucks.

[Libvisual-devel] Going to Evoke!

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

Heya List,

I'm just being told that I'm going to the Evoke demo scene party
(www.evoke-net.de), are other people from the list going as well ?

Cheers,
Dennis

[Libvisual-devel] artsd support ?

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

Heya people, and especially the amarok developers this time!

Gustavo and I were talking about artsd support as input plugin and since
we both don't know anything at all about artsd we wondered if the amarok
developers could shine some light on it, or maybe even implement it for
us ;) *wink wink*

Cheers,
Dennis

Re: [Libvisual-devel] Back home, have connectivity again!

[Gustavo S. B. <gu...@gs...>]

Em Wednesday 25 August 2004 05:36, Mark Kretschmann escreveu:
> Regarding libvisual: Is there an IRC channel where libvisual devels usually
> hang out?

I and Dennis hang in #freevo and others on freenode

-- 
Gustavo Sverzut Barbieri
---------------------------------------
Engenharia de Computacao 2001 - UNICAMP
GPSL - Grupo Pro Software Livre
Cell..: +55 (19) 9165 8010
Jabber: gsb...@ja...
  ICQ#: 17249123
   GPG: 0xB640E1A2 @ wwwkeys.pgp.net

[Libvisual-devel] Gforce also in CVS

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

I've imported the working GForce plugin under the module name
'libvisual-gforce' into CVS.

This requires libvisual from CVS as well

Cheers,
Dennis

[Libvisual-devel] Libvisual CVS updated!

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

Alright, I've managed to put all the stuff in CVS except for 
libvisual-gforce which will follow shortly.

Also I created a ROADMAP for the future, and I would like to have
comments on it: http://libvisual.sourceforge.net/LIBVISUAL_ROADMAP

Now the ChangeLogs for the last month:

Libvisual:
      * TODO: Updates.

        * examples/simplesdl.c, examples/morphsdl.c:
        Random API updates and such.

        * libvisual/lv_audio.c (visual_audio_analyze):
        Added normalized audio freq analyser.

        * libvisual/lv_bmp.c (visual_bitmap_load):
        Updates to api changes and palette support.

        * libvisual/lv_color.c, libvisual/lv_color.h: Added, supports
        for VisColor.

        * libvisual/lv_cpu.c, libvisual/lv_cpu.h: Added, far from
finished.

        * libvisual/lv_event.c, libvisual/lv_event.h: Added support for
        param change events.

        * libvisual/lv_input.c (visual_input_new): Fixed bug, function
was
        always failing.

        * libvisual/lv_libvisual.c: Added global params.

        * libvisual/lv_palette.c, libvisual/lv_palette.h: Updated to
VisColor
        and added some methods to help with colors.

        * libvisual/lv_param.c, libvisual/lv_param.h: Complete parameter
        sub system.

        * libvisual/lv_param.c (visual_plugin_get_params): Added
function.

        * libvisual/lv_songinfo.c: Using VisTime for all timing related
        things.

        * libvisual/lv_video.c (visual_video_color_bgr_to_rgb): Added
rgb, bgr conversion.
        (visual_video_compare): Checks if two VisVideos have the same
        settings.

        * libvisual/lv_time.c, libvisual/lv_time.h: Added time, timer
subsystems.

        * tools/lv-inspect.c: Added more help.


___

Libvisual-plugins:

2004-08-25  Dennis Smit  <ds...@ne...>

        * TODO: Updates.

        * plugins/actor/bumpscope/*: Added, not finished yet.

        * plugins/actor/gdkpixbuf/*: Added, quite ready, some things
todo. (A
        gdkpixbuf image loader).

        * plugins/actor/jakdaw/*: Ported the xmms jakdaw plugin!

        * plugins/actor/plazma/*: Ported the xmms plazma plugin!

        * plugins/actor/xpyre/*: Start port of the xmms Xpyre plugin,
not finished.

        * plugins/*: Small cleanups all around.



___

For the rest there aren't major changes!


Cheers,
Dennis

Re: [Libvisual-devel] Back home, have connectivity again!

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

Everything is going good thank you for asking!, and yes the vacation
rocked!

Do my greets back to Christian!

About the IRC channel, there is not yet an irc channel, maybe it's an
idea to make one!

Cheers,
Dennis


On Wed, 2004-08-25 at 10:36 +0200, Mark Kretschmann wrote:
> On Wednesday 25 August 2004 02:11, Dennis Smit wrote:
> > Well I'm back at home (from vacation) and also have connectivity again!
> >
> > I've got a shitload of changes to checkin and I'll start doing this
> > tomorrow!
> >
> > How is everyone doing ?
> 
> Welcome back Dennis! Hope you had a nice vacation. Greetings from Christian 
> Schaller from GStreamer, who I met at the aKademy KDE conference :) He says 
> he met you at an earlier event some time ago.
> 
> Regarding libvisual: Is there an IRC channel where libvisual devels usually 
> hang out? 
> 
> --Mark

Re: [Libvisual-devel] Back home, have connectivity again!

[Mark K. <ma...@we...>]

On Wednesday 25 August 2004 02:11, Dennis Smit wrote:
> Well I'm back at home (from vacation) and also have connectivity again!
>
> I've got a shitload of changes to checkin and I'll start doing this
> tomorrow!
>
> How is everyone doing ?

Welcome back Dennis! Hope you had a nice vacation. Greetings from Christian 
Schaller from GStreamer, who I met at the aKademy KDE conference :) He says 
he met you at an earlier event some time ago.

Regarding libvisual: Is there an IRC channel where libvisual devels usually 
hang out? 

--Mark

[Libvisual-devel] Back home, have connectivity again!

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

Hello,

Well I'm back at home (from vacation) and also have connectivity again!

I've got a shitload of changes to checkin and I'll start doing this
tomorrow!

How is everyone doing ?

Cheers,
Dennis