Re: OSC control of individual processors?

Len Ovens <[email protected]> Tue, 20 Jun 2017 07:12:46 -0700 (PDT)
Newsgroups gmane.comp.audio.ardour.devel
Message-ID <[email protected]>
  This message is in MIME format.  The first part should be readable text,
  while the remaining parts are likely unreadable without MIME-aware tools.

--296490112-1159662335-1497967966=:2837
Content-Type: TEXT/PLAIN; charset=utf-8; format=flowed
Content-Transfer-Encoding: quoted-printable

On Tue, 20 Jun 2017, J=C3=B6rn Nettingsmeier wrote:

> Excellent, thanks! One question: the addressing of strips seems to rely=
=20
> on the banking? That means an action happens like this:
> tell ardour what banksize i want and select bank N
> use strip SSID relative to bank N to perform an operation.
>
> That means I can set banksize to 0 and basically address all=20
> tracks/buses/vcas from my remote DAW easily, but only as long as I don'=
t=20
> want to use a banked control surface at the same time. Which I could

Not true, each device may have a different banksize, a different set of=20
strips, different fader math, etc. That is why /set_surface is=20
set_surface, the command only affects the surface sending the command.

> Luxury problem: would it be feasible to have Ardour listen to more than=
=20
> one OSC port, with each port having different /set_surface settings? So=
=20
> that I can have my OSC remote app, my physical fader bank, *and* some=20
> other fancy remote control at the same time?

As explained above, this is not needed.

> That is assuming the banking logic is contained in the OSC code - if

Each surface has it's own banksize as well as current bank. Ardour saves=20
each incoming OSC url along with it's set_surface settings.

The GUI settings dialog may give the impression all surfaces must share=20
the same settings, but the GUI only sets the defaults. That is, it sets=20
what settings Ardour will use for a new surface that does not send a=20
set_surface command. A /set_surface command will override those settings=20
for that surface. Ardour's OSC tries to allow both the most rudimentry OS=
C=20
surface to be used like TouchOSC, or a very complex multi-surface setup. =
I=20
am looking at being able to "link" two or more surfaces to share one bank=
=20
(like a 6 strip surface and a 10 strip surface to work as a 16 strip=20
surface) as well.

--
Len Ovens
www.ovenwerks.net

--296490112-1159662335-1497967966=:2837
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
ardour-dev mailing list
[email protected]
http://lists.ardour.org/listinfo.cgi/ardour-dev-ardour.org

--296490112-1159662335-1497967966=:2837--