Discussion:
[non] Proper way to set up NSM session with mididings?
Markku Tavasti
2015-06-27 12:28:07 UTC
Permalink
Hi!

What is correct way to set up session containing (among others)
non-mixer and mididings?

- mididings needs osc port number for non-mixer
- non-mixer osc port can be configured on command-line,
but it needs NSM Proxy, and then some integration is broken?
What has to be defined as save signal? Any other special settings?
--
M. Tavasti / ***@tavasti.fi / +358-40-5078254
Markku Tavasti
2015-07-01 12:30:47 UTC
Permalink
Post by Markku Tavasti
What is correct way to set up session containing (among others)
non-mixer and mididings?
- mididings needs osc port number for non-mixer
- non-mixer osc port can be configured on command-line,
but it needs NSM Proxy, and then some integration is broken?
What has to be defined as save signal? Any other special settings?
Actually, starting non-mixer with command-line options seem to be
problematic. If I specify path_to_project to NSM Proxy, mixer starts,
but closes itself right after loading everything.
--
M. Tavasti / ***@tavasti.fi / +358-40-5078254
J. Liles
2015-07-01 17:14:42 UTC
Permalink
You could create a shell script called non-mixer-fixed-osc-port, which
doesn nothing but "exec non-mixer" + your commandline args. That should
give you a fixed OSC port, while preserving NSM functionality. However,
you'll be limited to one instance of non-mixer in the session this way.
Hi!
What is correct way to set up session containing (among others) non-mixer
and mididings?
- mididings needs osc port number for non-mixer
- non-mixer osc port can be configured on command-line,
but it needs NSM Proxy, and then some integration is broken?
What has to be defined as save signal? Any other special settings?
--
Loading...