Bug with Waveform~ in Max 6.1.1

    Mar 21 2013 | 4:52 pm
    I keep encountering a bug with Waveform in 6.1.1. I've tried to narrow it down to something I'm doing with it but it seems to occur regardless of the rest of my patching, usually when saving a project. The bug seems to be that the Waveform~ object's 'Waveform Offset' attribute keeps getting set to 'nan' prompting the error in the Max window "detected out-of-range float value (inf or nan) when writing JSON file, replacing with 0". The error doesn't crash max or obstruct in any way other than flooding the Max window.
    Is this just happening for me?

    • Mar 23 2013 | 12:07 am
      You're right something like this can happen if the offset message is sent before waveform~ binds to the buffer~. This will be fixed in the next incremental. The warning should be harmless even though it is annoying.