is it always necessary to modify instrument for don't have error message like: gk_blue_auto18' of type k not allowed when expecting ....
with i(<parameter>) or are they a better way i miss ?
From: Steven Yi <stevenyi@gm...> - 2012-02-28 11:15:17
Usually, this means you've gotten an instrument that has a widget set
for automation that was previously not set to do so, so that it is now
generating as a k-rate sig instead of a constant. Really, it should
be the case that the signal generated by blue will always generate as
k-rate, as generating as a constant really was an optimization and one
that has caused more problems than it's worth. (Actually, it's a
longer story, where it started off as constants, and later became
If I remember correctly, you can set the widget to be not automatable,
and that should force it to generate as a constant. However, it's
probably better to update your code to allow automation, using i().
BTW: I think this may be a longstanding bug. Do you know of any
examples that have this issue or any items on blueShare that cause
this for you? I did check the code and it looks like it is doing the
right thing to default to not automatable when reading older
instruments/effects, but I'd like to look at this further.
Also, were you using the API when rendering?
On Tue, Feb 28, 2012 at 8:52 AM, stephane boussuge <s.boussuge@...> wrote:
> is it always necessary to modify instrument for don't have error message
> like: gk_blue_auto18' of type k not allowed when expecting ....
> with i(<parameter>) or are they a better way i miss ?
> Stéphane Boussuge