[LAD] JACK CV Ports API

Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
To: Linux Audio Developers <linux-audio-dev@...>
Date: Tuesday, April 3, 2012 - 11:24 pm

--f46d0430855a65a26c04bcce9b9f
Content-Type: text/plain; charset=ISO-8859-1

hey lads,
sharing an idea I had here

my (currently in development) host directly exposes plugin ports to jack -
audio as audio, midi as midi, and parameters as a midi port for midi-cc
usage.
while coding for lv2 plugins, I noticed the CV port type, more info here:
http://lv2plug.in/ns/ext/cv-port/

I didn't yet coded support for it, but I'll do soon. Those kind of ports
will be exposed to jack as pure audio ports.
Non-daw and non-mixer also use this kind of ports, and maybe others.
The problem is that users shouldn't connect normal audio and CV ports
together...

so I came up with an idea that is simple and fairly easy to implement - a
new jack port flag.

example:
port = jack_port_register(client, port_name, JACK_DEFAULT_AUDIO_TYPE,
JackPortIsInput|JackPortIsCV, 0);

patchbays can check for this flag and represent the port as a different
type (I've done it here myself as jack keeps any custom port flag values I
set, and works just fine).
in the jack library code we can check for the flag and not allow port
connections.

what do you think?

--f46d0430855a65a26c04bcce9b9f
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

hey lads,sharing an idea I had heremy (currently in development=
) host directly exposes plugin ports to jack - audio as audio, midi as midi=
, and parameters as a midi port for midi-cc usage.while coding for lv2 =
plugins, I noticed the CV port type, more info here:
http://lv2plug.in/ns/ext/cv-p=
ort/
I didn't yet coded support for it, but I'll do soon=
. Those kind of ports will be exposed to jack as pure audio ports.Non-d=
aw and non-mixer also use this kind of ports, and maybe others.
The problem is that users shouldn't connect normal audio and CV ports t=
ogether...so I came up with an idea that is simple and fairly easy =
to implement - a new jack port flag.example:port =3D jack_port_=
register(client, port_name, JACK_DEFAULT_AUDIO_TYPE, JackPortIsInput|JackPo=
rtIsCV, 0);
patchbays can check for this flag and represent the port as a different=
type (I've done it here myself as jack keeps any custom port flag valu=
es I set, and works just fine).in the jack library code we can check fo=
r the flag and not allow port connections.
what do you think?

--f46d0430855a65a26c04bcce9b9f--

Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:
[LAD] JACK CV Ports API, Filipe Lopes, (Tue Apr 3, 11:24 pm)
Re: [LAD] JACK CV Ports API, J. Liles, (Wed Apr 4, 12:45 am)
Re: [LAD] JACK CV Ports API, David Robillard, (Wed Apr 4, 12:20 am)