Built-in enumerated values in Live, such as device on-off status, automatically snap to either "on" or "off" when they are being edited in an automation lane.
In M4L, if you automate an enum-valued property (such as the carrier waveform "CarrierWave" in the FM synthesis tutorial), it shows up as a continuous float-valued curve in the automation editor. Should it instead snap to the enum values?
I suspect that this is a feature request rather than a bug.
While I'm referring to the FM synth tutorial, here is a simple question: can anyone explain to me how the live.menus are initialized with the names of the waveforms? This is probably just my own ignorance of Max programming; I don't see anything in the inspector except an enum range from 0. to 6.
automating enum valued properties
Re: automating enum valued properties
Speculating on my own question: I think that the enum display in the parameters window of the FM synth tutorial is broken for some reason. When I manually copy the attribute values from the live.menu, I see the enum values in the text-formatted persistent data. However, if I examine the menu's backing data in the parameters window, all I see is floating point numbers.
If I create my own menu, the parameter storage and display of the enum values works fine. So whatever is wrong appears to be intrinsic only to the tutorial.
If I create my own menu, the parameter storage and display of the enum values works fine. So whatever is wrong appears to be intrinsic only to the tutorial.
Re: automating enum valued properties
Thanks. I'll check that.
_M
_M