Discussion:
[non] How to make non-timeline and non-mixer to connect with OSC?
Markku Tavasti
2018-09-22 15:43:37 UTC
Permalink
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
J. Liles
2018-09-22 17:22:02 UTC
Permalink
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.
Post by Markku Tavasti
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?
https://linuxmusicians.com/viewtopic.php?f=1&t=18994
--Tavasti
Markku Tavasti
2018-09-22 21:00:48 UTC
Permalink
No problems to believe your words :-) Thanks for this.

--Tavasti
Post by J. Liles
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.
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?
https://linuxmusicians.com/viewtopic.php?f=1&t=18994
--Tavasti
Loading...