[LV2] Mapping of OSC to LV2 Atoms

David Robillard d at drobilla.net
Thu Oct 15 16:17:34 PDT 2015

On Thu, 2015-10-15 at 13:39 -0600, Spencer Jackson wrote:
> On Thu, Oct 15, 2015 at 12:29 PM, David Robillard <d at drobilla.net> wrote:
> > On Fri, 2015-06-19 at 22:33 +0200, Hanspeter Portner wrote:
> >
> > > * The four exotic OSC types 'T'rue, 'F'alse, 'N'il, 'I'nfinitum have
> > >   no associated data in OSC. Should they be mapped to atoms and
> > >   packed into the arguments tuple or only show up in the message
> > >   format string like in OSC?
> >
> > I don't know about nil and infinitum, but it seems true and false
> > clearly map to Bool.  There is no type string for atom objects, so a
> > true bidirectional mapping shouldn't be missing bits and rely on some
> > external funny thing (a format string) to fill in the gaps, IMO.
> >
> The  OSC spec works this way, with NO bits at all in the data section to
> correspond to these types.

I am aware of that.

>  So I maintain my previous argument. As Hanspeter
> said, it would require a change in any existing logic that handles OSC
> messages...

Apparently I do not understand your previous argument.  The data has to
live somewhere, and there is no format string in LV2 atoms.

How do you propose "/foo tf" be represented as an atom?


More information about the Devel mailing list