[OSC_dev] Adding OSC support to VLC

[Pascal Baltazar]

Hi !

on the question of instances (i.e. here /deck ids), we've been  
considering introducing a new reserved character in our use of OSC in  
Jamoma (modular framework for Max/MSP), by using the dot.

/deck.1/play
/deck.1/pause

which hopefully could help as well humans as machines to distinguish  
between subnodes and instances.

This (and more about requests in Jamoma) is documented on http://www.jamoma.org/wiki/NameSpace/

Hope this helps,

pb


Le 24 nov. 08 à 23:29, Forwind info a écrit :

>
> Good work !
>
> Would it be useful to consider multiple decks ?
>
> /deck/$id/play
> /deck/$id/pause
> /deck/$id/stop
>
> Conor
>
> On Mon, Nov 24, 2008 at 9:26 PM, Nicholas J Humfrey <njh at aelius.com>  
> wrote:
> Hello,
>
> I am thinking about adding OSC support to VideoLan. I did some work on
> using MPRIS (http://www.mpris.org/), which uses D-Bus to communicate
> with with VLC, but I am missing OSC and could do without the hassle of
> running D-Bus.
>
> I previously wrote MadJACK, an MPEG Audio Deck which sends its output
> to Jack:
> http://www.aelius.com/njh/madjack/
>
>
> I tried to design the protocol to be generic, so that it could be used
> by other media players too. There doesn't seem to be very much
> standardisation of OSC messages in the community (apart from the 'SYN'
> namespace).
>
> What do people think about my message format and namespace?
> Is it useful to standardise the messages for inter-compatibility?
> Would it be helpful to change the protocol to be able to address
> multiple decks?
>
>
> My plan is to initially just support the commands that don't need
> replies:
> /deck/play
> /deck/pause
> /deck/stop
> /deck/cue (f)
> /deck/eject
> /deck/load (s)
> /deck/volume (s)
>
> And if playlists were supported:
> /deck/add_track (s)
> /deck/next
> /deck/previous
> /deck/repeat (T/F)
>
>
>
> nick.
>
> _______________________________________________
> OSC_dev mailing list
> OSC_dev at create.ucsb.edu
> http://lists.create.ucsb.edu/mailman/listinfo/osc_dev
>
> _______________________________________________
> OSC_dev mailing list
> OSC_dev at create.ucsb.edu
> http://lists.create.ucsb.edu/mailman/listinfo/osc_dev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.create.ucsb.edu/pipermail/osc_dev/attachments/20081125/81b6c035/attachment.html