From: Niels E. <ne...@lo...> - 2004-09-16 11:01:17
|
Hello list , The OpenSoundControl protocol (http://www.cnmat.berkeley.edu/OpenSoundControl/) would make a great extension to libvisual. Using the OSC would bring a few benefits to libvisual: 1. Flexible (external/remote) control of libvisual plugins 2. Application programmers dont have to hardcode parameter/event handling but can send messages to libvisual actor/plugin instead At audio analyzer level (not needing the visualization plugins): 3. Users can setup OSC messages to be sent to other applications to trigger bangs/events on sound events ( kick, beat, frequency ... ) Looking at the morph sdl example, I can imagine an osc structure for flexible control of libvisual plugins: /visual/morph/setup/ depth dimension pitch duration <in frames> /visual/morph/set/ freeze <num> alpha <float> speed <float> reverse ... (3. Users sets up OSC messages to be sent to other applications) /visual/analyzer/setup destination_host <host> destination_port <port> /visual/analyzer/on kick <message> beat <message> roll <message> vol <message> I guess that the latter (nr. 3) would be most usefull for libvisual ; it would greatly improve interoperability with other applications without needing to implement libvisual in those applications (the user can simply connect them). Best, Niels Elburg (main developer of Veejay, http://veejay.sourceforge.net) |
From: Dennis S. <sy...@yo...> - 2004-09-16 20:06:24
|
On Thu, 2004-09-16 at 13:01 +0200, Niels Elburg wrote: > The OpenSoundControl protocol > (http://www.cnmat.berkeley.edu/OpenSoundControl/) would make a great > extension to libvisual. > > Using the OSC would bring a few benefits to libvisual: > 1. Flexible (external/remote) control of libvisual plugins > 2. Application programmers dont have to hardcode parameter/event handling > but can send messages to libvisual actor/plugin instead Well, generally OSC is 'just another bus system' and a unknown one. I don't really like depending on this. I'm very wary with depending on 'cool' stuff. Since it can easily crack up the lib. Cheers, Dennis (sorry for my somewhat short answer, kinda tired) |
From: salsaman <sal...@xs...> - 2004-09-16 21:18:36
|
Dennis Smit wrote: >On Thu, 2004-09-16 at 13:01 +0200, Niels Elburg wrote: > > >>The OpenSoundControl protocol >>(http://www.cnmat.berkeley.edu/OpenSoundControl/) would make a great >>extension to libvisual. >> >>Using the OSC would bring a few benefits to libvisual: >> 1. Flexible (external/remote) control of libvisual plugins >> 2. Application programmers dont have to hardcode parameter/event handling >> but can send messages to libvisual actor/plugin instead >> >> > >Well, generally OSC is 'just another bus system' and a unknown one. >I don't really like depending on this. I'm very wary with depending >on 'cool' stuff. Since it can easily crack up the lib. > >Cheers, >Dennis > >(sorry for my somewhat short answer, kinda tired) > > > > >------------------------------------------------------- >This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170 >Project Admins to receive an Apple iPod Mini FREE for your judgement on >who ports your project to Linux PPC the best. Sponsored by IBM. >Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php >_______________________________________________ >Libvisual-devel mailing list >Lib...@li... >https://lists.sourceforge.net/lists/listinfo/libvisual-devel > > > > My suggestion was to use a wrapper - rather like the livido wrapper will be for actors. Just have a little routine that is waiting for a kick trigger from libvisual. Then the routine can handle registering hosts and sending the OSC messages. Salsaman. |
From: Dennis S. <sy...@yo...> - 2004-09-17 06:05:23
|
On Thu, 2004-09-16 at 23:33 +0100, salsaman wrote: > My suggestion was to use a wrapper - rather like the livido wrapper will > be for actors. > > Just have a little routine that is waiting for a kick trigger from > libvisual. Then the routine can handle registering hosts and sending the > OSC messages. Agree with this. |