Opened 13 years ago

Closed 13 years ago

#297 closed Bug Report (invalid)

Parameter ranges for LV2 plugins can be extended

Reported by: t_w_@… Owned by:
Priority: minor Component: Ingen
Keywords: Cc: t_w_@…


It's now possible to edit the parameter range for LV2 plugins and to e.g. raise the maximum to something the plugin will not handle.

Even for plugins with custom GUIs such as Calf Reverb, this can be done via the context menu of the port. This specific plugin will throw out: CALF DEBUG: instance (nil) data (nil)

Assuming that LV2 plugin authors are not smoking crack, min and max should be enforced. However, the ability to reduce the range within this limits is very welcome.

Change History (2)

comment:1 Changed 13 years ago by kfoltman

The instance (nil) data (nil) is not related to parameter ranges - it's just a debug message that says that instance access and data access extensions are not supported. It will be removed when my plugin framework becomes more complete.

Min/max are not meant to be enforced in core LV2 spec. The fact that my plugins misbehave when dealing with out-of-range values is due to my laziness and is not an Ingen bug). In fact, some values (like effect amounts work with out-of-range values just fine - and they should.

(and no, I'm not smoking crack, pot or ingesting anything illegal except for normal air content in the Dublin area)

comment:2 Changed 13 years ago by t_w_@…

Resolution: invalid
Status: newclosed

Great. Then not having absolute min an max for the range a plugin actually can handle as opposed to a mere suggestion of a range that is nice to use is an oversight in LV2.

Note: See TracTickets for help on using tickets.