Page 1 of 1

Non_timeline to non-mixer osc messages.

Posted: Sat Sep 22, 2018 1:45 pm
by Arthurx
Hi All,
Thanks in advance,

I use non-timeline to record and non-mixer for live jamming and performances.
Now i want to automate the volume (gain).
So i created a control track from the audio track.
In the manual it shows that I can choose a path to the mixer in:

http://non.tuxfamily.org/timeline/doc/M ... .1.12.1.2.

I can not find that roll-out menu.
What am I missing?

thanks Arthur :roll:

Re: Non_timeline to non-mixer osc messages.

Posted: Sat Sep 22, 2018 2:11 pm
by tavasti
I don't know how to connect non-mixer and non-timeline by hand, but if you start them with non-session-manager, they will be connected. If non-session-manager is not an option you most likely need to ask in non mailing list.

Re: Non_timeline to non-mixer osc messages.

Posted: Sat Sep 22, 2018 2:14 pm
by Arthurx
hi thanks tavasti,

I will try with the non-session-manager.

Re: Non_timeline to non-mixer osc messages.

Posted: Sat Sep 22, 2018 3:44 pm
by tavasti
tavasti wrote:If non-session-manager is not an option you most likely need to ask in non mailing list.
I asked this on mailing list just for own curiosity :-)

Re: Non_timeline to non-mixer osc messages.

Posted: Sat Sep 22, 2018 6:22 pm
by Arthurx
I also subscribed to the mailing list. great idea :D

Tomorrow I give it another try to get session manager in my workflow.

I have a script to start everything and in the end when i am finished. I rename the work dir to the date. ( a script to copy and rename)
and create a new work dir with empty timeline etc.

So i do not need the session manager for that part.

Re: Non_timeline to non-mixer osc messages.

Posted: Sat Sep 22, 2018 8:54 pm
by tavasti
tavasti wrote:
tavasti wrote:If non-session-manager is not an option you most likely need to ask in non mailing list.
I asked this on mailing list just for own curiosity :-)
Answer:

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.

Re: Non_timeline to non-mixer osc messages.

Posted: Sat Sep 22, 2018 9:09 pm
by Arthurx
Thanks again :D

Re: Non_timeline to non-mixer osc messages.

Posted: Sun Sep 23, 2018 12:33 pm
by Arthurx
HI travasti,

yes, it now works the osc coupling.
And also with my presets. Just replaced the empty non-mixer with my preset.
Same for the non-timline.

Thanks Arthur :wink: :D