Re: [ecasound] Confused looking at effect code

From: Jeremy Salwen <jeremysalwen@email-addr-hidden>
Date: Thu Jun 09 2011 - 03:36:54 EEST

Okay, I'm actually working on creating a LV2 host effect.

I'm not really sure what " 'map-ladspa-list' and 'map-cop-list'," are. I
was looking at this code trying to understand it, not trying to fix it, so
I'm not really sure what it's supposed to be like. I'll assume that the
description fields don't matter?


On Wed, Jun 8, 2011 at 6:29 PM, Kai Vehmanen <kvehmanen@email-addr-hidden> wrote:

> Hi,
> On Wed, 8 Jun 2011, Jeremy Salwen wrote:
> Hi All, hopefully a dev can help me with this:
> [...]
> It seems to me that what is happening is
>> for each port {
>> parse parameter => get_parameter_name=> read the n'th element of
>> param_names_rep
>> add the port name taken from plugin_desc->PortNames to the n'th place of
>> param_names_rep
>> }
>> This is why I am confused. It seems that we read the port name from the
>> list (in a roundabout way) before the name is even placed there. Is
> a very good question indeed as that's a bug! If you take a close look at
> output of 'map-ladspa-list' versus that of 'map-cop-list', the param
> description field for LADSPA plugins is indeed empty (there is a name field
> for every param). I'm not sure if anyone is using the param description
> field (for most internal ops, description is short and equals
> to just stating the parameter name only), which explains why nobody has
> noted this before.
> If you have a fix for this, that'd be great.

EditLive Enterprise is the world's most technically advanced content
authoring tool. Experience the power of Track Changes, Inline Image
Editing and ensure content is compliant with Accessibility Checking.

Ecasound-list mailing list
Received on Thu Jun 9 04:15:02 2011

This archive was generated by hypermail 2.1.8 : Thu Jun 09 2011 - 04:15:02 EEST