The bare OSC protocol is insufficient for the kind of interconnection that exists between Non Timeline and Non Mixer. Another layer, known as OSC::Signal is required for those features, and NSM provides a discovery/message bus mechanism for OSC::Signal. So to answer your question more directly, this feature only works under NSM. While it would be theoretically possible to do something similar using DBus, etc., that would hardly be any easier or more "pure OSC" than the current requirement of using NSM.
In order to do it without NSM or some other broadcast/discovery intermediary, it would require the user to manually configure every port number and endpoint name. Believe me, that's something you wouldn't enjoy doing. On Sat, Sep 22, 2018 at 8:59 AM Markku Tavasti <[email protected]> wrote: > Hi! > > Just in curiosity, how non-timeline and non-mixer should be started so > that OSC is available in non-timeline? I know that starting them with > non-session-manager does the trick, but how should they be started on > plain command line to get same effect? > > This question came to my mind when reading this: > https://linuxmusicians.com/viewtopic.php?f=1&t=18994 > > --Tavasti > > > >
