liblo-devel Mailing List for LibLO

On Sun, 18 Nov 2007 17:24:26 +0000
Martin Habets <err...@mp...> wrote:

> On Sun, Nov 18, 2007 at 08:39:13PM +0900, Kentaro Fukuchi wrote:
> > Hello,
> > 
> > I wrote small utilities for OSC users familiar with command line tools,
> > sendosc and dumposc. You can send OSC message from command line. From usage:
> 
> These have existed for a long time. Why write them again from scratch?

My answer is, because I didn't know them. No, it's not correct.
Maybe I have ever seen them but I completely forgot them (that could be the
reason why the names of the software are completely same). Thank you for
pointed out.

On the other hand, my reimplementation of sendosc/dumposc are more clear
than the existing programs because mine uses liblo, and it makes them
very simple. I always favor a simple code.

Anyway, they will be released under free software license. It is my
pleasure if you like them.

Thanks,

Kentaro

On Sun, Nov 18, 2007 at 08:39:13PM +0900, Kentaro Fukuchi wrote:
> Hello,
> 
> I wrote small utilities for OSC users familiar with command line tools,
> sendosc and dumposc. You can send OSC message from command line. From usage:

These have existed for a long time. Why write them again from scratch?

http://www.cnmat.berkeley.edu/OpenSoundControl/clients/sendOSC.html
http://www.cnmat.berkeley.edu/OpenSoundControl/dumpOSC.html

Regards,
Martin

Hello,

I wrote small utilities for OSC users familiar with command line tools,
sendosc and dumposc. You can send OSC message from command line. From usage:

Usage: sendosc hostname port address types values...
Send OpenSound Control message using UDP.

Description
hostname: specifies the remote host's name.
port    : specifies the port number to connect to the remote host.
address : the OSC address where the message to be sent.
types   : specifies the types of the following values.
          i - 32bit integer
          h - 64bit integer
          f - 32bit floating point number
          d - 64bit (double) floating point number
          s - string
          S - symbol
          c - char
          m - 4 byte midi packet (8 digits hexadecimal)
          T - TRUE (no value required)
          F - FALSE (no value required)
          N - NIL (no value required)
          I - INFINITUM (no value required)
values  : space separated values.

Example
$ sendosc localhost 7777 /sample/address iTfs 1 3.14 hello

You can download a tarball at
http://megaui.net/misc/sendosc.tar.gz

How about to bundle them to liblo package?

Kentaro Fukuchi

Hi Kentaro,

I have been bugged by that too.I had to access the bundle's internal
structure to free the messages.
I understand it's up to the instantiator of the messages to destroy them
afterwards, so I'd rather make a function like "lo_bundle_messages_free"
that you call before "lo_bundle_free" if you want to.
It would make life a bit easier!


Camille


On Nov 18, 2007 12:25 PM, Kentaro Fukuchi <fu...@me...> wrote:

> Hello,
>
> An lo_bundle object can contains multiple lo_messages, but there is no way
> to
> free those messages if you have no pointers to them after calling
> lo_bundle_add_message(). Why lo_bundle_free() does not free messages in
> it,
> just like the following?
>
> void lo_bundle_free_messages_too(lo_bundle b)
> {
>    int i;
>    if (!b) {
>        return;
>    }
>    for(i = 0; i < b->len; i++) {
>        lo_message_free(b->msgs[i]);
>    }
>
>    free(b->msgs);
>    free(b->paths);
>    free(b);
> }
>
> I think this function is useful. What do you think?
>
> Kentaro Fukuchi
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2005.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> liblo-devel mailing list
> lib...@li...
> https://lists.sourceforge.net/lists/listinfo/liblo-devel
>

Hello,

An lo_bundle object can contains multiple lo_messages, but there is no way to
free those messages if you have no pointers to them after calling
lo_bundle_add_message(). Why lo_bundle_free() does not free messages in it,
just like the following?

void lo_bundle_free_messages_too(lo_bundle b)
{
    int i;
    if (!b) {
        return;
    }
    for(i = 0; i < b->len; i++) {
        lo_message_free(b->msgs[i]);
    }

    free(b->msgs);
    free(b->paths);
    free(b);
}

I think this function is useful. What do you think?

Kentaro Fukuchi

This patch add avahi support to liblo, it introduce a little change in
the way we are creating server to allow changing avahi name of the
server, but it remains api-compatible

The avahi support is enabled by --enable-avahi at the configure command line.

The patch also add a --enable-debug which turn on gcc debugging options.

Regards,
Elthariel.