New developer's library

[Jeff Glatt]

Hi folks,

This is my first post to the list, and the reason is to announce a new GPL
library
that can be used by Windows and Linux developers to implement Open Sound
Control in their C/C++ applications.

A couple weeks ago, I decided to investigate what OSC was all about, and
perhaps use it in some C apps I wrote. I looked at the various libraries,
and LIBLO appeared to be the most suitable. But there were some things
about it I wanted to change. (For one thing, I use Visual C++ on Windows,
and I needed it to compile cleanly, without any cygwin environment for
p_threads, and stuff like that). I also wanted to reduce memory allocations,
and change other things. In the end, it turned out that there were so many
alterations to the code, that I decided to just create another alternative
code base that was only very loosely based upon LIBLO. The new library
is called SimpleOSC.

I've made a ZIP file containing the sources and binaries (for Windows. For
Linux, there are gcc make files to create the binaries for your distro).
Please look at the README.TXT for a brief overview of changes from
LIBLO. And read INDEX.HTM for the excruciating details on everything
about using SimpleOSC.

You can get the ZIP file at:

http://home.roadrunner.com/~jgglatt/tech/simpleosc.zip

Jeff Glatt
http://home.roadrunner.com/~jgglatt 

_______________________________________________
OSC_dev mailing list
OSC_dev@...
http://lists.create.ucsb.edu/mailman/listinfo/osc_dev

[Stephen Sinclair]

On Sun, Jan 25, 2009 at 11:01 PM, Jeff Glatt <jgglatt@...> wrote:

> about it I wanted to change. (For one thing, I use Visual C++ on Windows,
> and I needed it to compile cleanly, without any cygwin environment for
> p_threads, and stuff like that). I also wanted to reduce memory allocations,
> and change other things.

Hi Jeff,

I'm glad that you took this initiative, but I just wanted to say that
if you did anything that you think could be beneficial to LibLo please
don't be afraid to discuss them with the LibLo list or send patches!
I'd very much like it to cleanly compile with VC++ as well, but no one
has really taken the time to work on the Windows version much.  I
don't use Visual C as much as I used to myself, (any Windows work I've
been doing recently uses MingW), so it's people like you who can
contribute this kind of thing.

Anyways it's always good to have more options, so I'll take a look at
your work when I get the chance.

Steve
_______________________________________________
OSC_dev mailing list
OSC_dev@...
http://lists.create.ucsb.edu/mailman/listinfo/osc_dev

[Uli Franke DWE]

Stephen Sinclair wrote:

> On Sun, Jan 25, 2009 at 11:01 PM, Jeff Glatt <jgglatt@...> wrote:
>
>> about it I wanted to change. (For one thing, I use Visual C++ on Windows,
>> and I needed it to compile cleanly, without any cygwin environment for
>> p_threads, and stuff like that). I also wanted to reduce memory allocations,
>> and change other things.
>
> Hi Jeff,
>
> I'm glad that you took this initiative, but I just wanted to say that
> if you did anything that you think could be beneficial to LibLo please
> don't be afraid to discuss them with the LibLo list or send patches!
> I'd very much like it to cleanly compile with VC++ as well, but no one
> has really taken the time to work on the Windows version much.  I
> don't use Visual C as much as I used to myself, (any Windows work I've
> been doing recently uses MingW), so it's people like you who can
> contribute this kind of thing.
>
> Anyways it's always good to have more options, so I'll take a look at
> your work when I get the chance.
>
> Steve

Hi Jeff

Steve's comment can be applied to WOscLib as well which compiles nicely
on Windows with MinGW/MSYS. Long time ago it was compiled with MSVC but
because of standard conformity issues I moved to gcc based solutions.
Just two weeks ago I moved to automake/configure and dropped the MSVC
support (I don't own a MSVC compiler anymore so I can not test). But I
guess it would be trivial to compile WOscLib with MinGW and use the DLL
with MSVC. The makefile could even create automagically all the .lib
etc. files which MSVC needs.

One of the most important things I learned during the past 10 Years is
that it should be avoided to reinvent the wheel whenever possible.
Contributing to existing solutions - ideas, improvements, whatever -
saves resources for new ideas and improvements. Even WOscLib would fit
in this category and if I'd have to make the same decisions as five
years ago, I wouldn't have written WOscLib. Your and others requirements
could just be new ./configure flags without implementing new priority
queues, callbacklists etc.

Uli

--

 Uli Franke -- R&D Engineer Dude
 WEISS ENGINEERING LTD.
 Professional Digital and Analog Audio Products
 Florastrasse 42, 8610 Uster Switzerland
 phone: [phone], fax: [phone]
 email: uli.franke@... web: http://www.weiss.ch

_______________________________________________
OSC_dev mailing list
OSC_dev@...
http://lists.create.ucsb.edu/mailman/listinfo/osc_dev

[Daniel Holth]

Jeff Glatt wrote:

> Hi folks,
>
> This is my first post to the list, and the reason is to announce a new GPL
> library
> that can be used by Windows and Linux developers to implement Open Sound
> Control in their C/C++ applications.
>
> A couple weeks ago, I decided to investigate what OSC was all about, and
> perhaps use it in some C apps I wrote. I looked at the various libraries,
> and LIBLO appeared to be the most suitable. But there were some things
> about it I wanted to change. (For one thing, I use Visual C++ on Windows,
> and I needed it to compile cleanly, without any cygwin environment for
> p_threads, and stuff like that). I also wanted to reduce memory allocations,
> and change other things. In the end, it turned out that there were so many
> alterations to the code, that I decided to just create another alternative
> code base that was only very loosely based upon LIBLO. The new library
> is called SimpleOSC.
>
> I've made a ZIP file containing the sources and binaries (for Windows. For
> Linux, there are gcc make files to create the binaries for your distro).
> Please look at the README.TXT for a brief overview of changes from
> LIBLO. And read INDEX.HTM for the excruciating details on everything
> about using SimpleOSC.
>
> You can get the ZIP file at:
>
> http://home.roadrunner.com/~jgglatt/tech/simpleosc.zip
>
> Jeff Glatt
> http://home.roadrunner.com/~jgglatt 
>
> _______________________________________________
> OSC_dev mailing list
> OSC_dev@...
> http://lists.create.ucsb.edu/mailman/listinfo/osc_dev
>  

I'm sure your library is great, but it has the same name as this Python
library: http://pypi.python.org/pypi/SimpleOSC/0.2.3
_______________________________________________
OSC_dev mailing list
OSC_dev@...
http://lists.create.ucsb.edu/mailman/listinfo/osc_dev

[Jeff Glatt]

>There's a python OSC package named SimpleOSC

Argh! Ok, it looks like the name EasyOSC isn't taken. So I've renamed it to
that.

The new URL for the ZIP file is:

http://home.roadrunner.com/~jgglatt/tech/easyosc.zip 

_______________________________________________
OSC_dev mailing list
OSC_dev@...
http://lists.create.ucsb.edu/mailman/listinfo/osc_dev

[Andy W. Schmeder-2]

FWIW, I have "reinvented" the osc parsing engine at least three  
times.  Usually for reasons of efficiency (microcontrollers, high  
performance streams).  Slight variations on the wheel, if you prefer. :)

Anyways, not all designs fit into the approach used by the "kitchen  
sink" libraries.



A.

On Jan 26, 2009, at 3:39 AM, Uli Franke DWE wrote:

> One of the most important things I learned during the past 10 Years is
> that it should be avoided to reinvent the wheel whenever possible.
> Contributing to existing solutions - ideas, improvements, whatever -
> saves resources for new ideas and improvements. Even WOscLib would fit
> in this category and if I'd have to make the same decisions as five
> years ago, I wouldn't have written WOscLib. Your and others  
> requirements
> could just be new ./configure flags without implementing new priority
> queues, callbacklists etc.

---

Andy W. Schmeder
andy [at] cnmat.berkeley.edu

Programmer/Analyst II
Research Group
Center for New Music and Audio Technologies
University of California at Berkeley
http://cnmat.berkeley.edu





_______________________________________________
OSC_dev mailing list
OSC_dev@...
http://lists.create.ucsb.edu/mailman/listinfo/osc_dev