[LAD] Can an LV2 plugin legally modify input port values?

Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
To: linux-audio-dev <linux-audio-dev@...>
Date: Tuesday, May 22, 2012 - 9:26 am

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

It's not clear to me what is legal for an LV2 plugin to do with an input
control port. Once the input port has been read, is it acceptable to use
that location in memory as temporary storage in the "run" method? Is it
the host's responsibility to re-fill the value of the parameter before
every run call? Is it the plugin's responsibility to keep input-ports
bit-exactly the same?

What about transformations of the input which leave the value logically the
same? For example, normalizing boolean inputs the values 0 and 1?

The
documentationis silent on this
matter.

Jeremy

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

It's not clear to me what is legal for an LV2 plugin to do with an inpu=
t control port.=A0 Once the input port has been read, is it acceptable to u=
se that location in memory as temporary storage in the "run" meth=
od?=A0 Is it the host's responsibility to re-fill the value of the para=
meter before every run call? Is it the plugin's responsibility to keep =
input-ports bit-exactly the same?

What about transformations of the input which leave the value logically=
the same?=A0 For example, normalizing boolean inputs the values 0 and 1?The documentation is silent on this=
matter.

Jeremy

--047d7b15aa2da5d39504c09c9b46--

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

Messages in current thread:
[LAD] Can an LV2 plugin legally modify input port values?, Jeremy Salwen, (Tue May 22, 9:26 am)