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

Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
To: Jeremy Salwen <jeremysalwen@...>
Cc: linux-audio-dev <linux-audio-dev@...>
Date: Tuesday, May 22, 2012 - 5:02 pm

On Tue, May 22, 2012 at 2:25 AM, Jeremy Salwen wrote:

Common sense dictates that this is a bad idea. Input means input.
Here's a relevant quote from the LADSPA documentation:

"Plugin writers should be aware that the host may elect to use the
same buffer for more than one port and even use the same buffer
for both input and output (see LADSPA_PROPERTY_INPLACE_BROKEN).
However, overlapped buffers or use of a single buffer for both
audio and control data may result in unexpected behaviour."

The way API documentation works, unless something is explicitly stated
as being permitted, you can never assume that it is. Even if someone
on the ML tells you it's OK that doesn't matter because everyone else
who read the API doc will have assumed it was *not* OK and coded
accordingly.
_______________________________________________
Linux-audio-dev mailing list
Linux-audio-dev@lists.linuxaudio.org
http://lists.linuxaudio.org/listinfo/linux-audio-dev

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)
Re: [LAD] Can an LV2 plugin legally modify input port values?, J. Liles, (Tue May 22, 5:02 pm)