NON-DAW OSC Control Signal

Discussion:

Diego Simak

2012-07-05 12:50:22 UTC

Hello NON-DAW List,
I have a question regarding automation in Non-DAW.
The manual says that it supports control signals using OSC protocol as
output to feed OSC controls in NON-Mixer but I cannot figure out how to
tell DAW which is the OSC server and the path having the controls.

Can somebody explain me how to configure Non-DAW to send out OSC automation
control signals to Non-Mixer?

Control voltage between Non-DAW and Non-Mixer works fine.

Thanks is advance for your help.

Diego

Diego Simak

2012-07-05 16:35:11 UTC

Permalink

send this again seems it not going through the list
it's not present in the archives neither

---------- Forwarded message ----------
From: Diego Simak <***@gmail.com>
Date: 2012/7/5
Subject: NON-DAW OSC Control Signal
To: non-***@lists.tuxfamily.org

Hello NON-DAW List,
I have a question regarding automation in Non-DAW.
The manual says that it supports control signals using OSC protocol as
output to feed OSC controls in NON-Mixer but I cannot figure out how to
tell DAW which is the OSC server and the path having the controls.

Can somebody explain me how to configure Non-DAW to send out OSC automation
control signals to Non-Mixer?

Control voltage between Non-DAW and Non-Mixer works fine.

Thanks is advance for your help.

Diego

J. Liles

2012-07-05 16:35:42 UTC

Permalink

Post by Diego Simak
Hello NON-DAW List,
I have a question regarding automation in Non-DAW.
The manual says that it supports control signals using OSC protocol as
output to feed OSC controls in NON-Mixer but I cannot figure out how to
tell DAW which is the OSC server and the path having the controls.
Can somebody explain me how to configure Non-DAW to send out OSC
automation control signals to Non-Mixer?
Control voltage between Non-DAW and Non-Mixer works fine.
Thanks is advance for your help.
Diego

Currently, this only works when both non-daw and non-mixer are part of the
same NSM session (NSM is used to allow the two programs to discover each
other and avoid using static OSC port numbers). When run this way, a
'Connect To' submenu will appear in the context menu for each control
sequence, containing the names of the module controls in non-mixer.

Diego Simak

2012-07-05 16:37:11 UTC

Permalink

Post by J. Liles

Thanks I will try this, both DAW and Mixer with NSM,

Thank you

Diego Simak

2012-07-05 22:20:27 UTC

Permalink

Post by Diego Simak

Post by J. Liles

Currently, this only works when both non-daw and non-mixer are part of
the same NSM session (NSM is used to allow the two programs to discover
each other and avoid using static OSC port numbers). When run this way, a
'Connect To' submenu will appear in the context menu for each control
sequence, containing the names of the module controls in non-mixer.

Thanks I will try this, both DAW and Mixer with NSM,
Thank you

Hi, I've tried both non-daw and non-mixer in a single NSM but I cannot see
the submeny 'Connect To' in the control sequence in DAW.
I'm missing something here?
Something that needs to be configured in daw or mixer?

Thank you very much.
Diego

Diego Simak

2012-07-05 22:26:06 UTC

Permalink

Post by Diego Simak

Post by J. Liles

Currently, this only works when both non-daw and non-mixer are part of
the same NSM session (NSM is used to allow the two programs to discover
each other and avoid using static OSC port numbers). When run this way, a
'Connect To' submenu will appear in the context menu for each control
sequence, containing the names of the module controls in non-mixer.

Thanks I will try this, both DAW and Mixer with NSM,
Thank you

Sorry but just re opening the session and the 'Connect To' is now
available, it's just great!

Thank you very much!

Diego