Crash with fl.peaks

[Owen Green]

This configuration reliably crashes here, not when audio is turned on, but when I press play on the player (I know it's a silly configuration, but that's the object of the exercise I guess):

<pre><code> ----------begin_max5_patcher---------- 789.3ocsVssbaBCD8Y7WgFxqtdPX.6z252QmNYjAgsRDRTIQrc6j7sWcCBjR bviIOXvZ0Jc18n8rn+tHHbG+DVFB9N3mfff+tHHvZxXHvONHrBcJmhjV2Bqo nyThT8Z3R2rR0YJ1NUqEVSEuQQwJ6JR8VqQp7CD19GD3bkCw0oqhVBfP6yzH yq05mfe4WhaWTmqwN+Ckj8LDMb43+y7qfjqHbFRbNraaHE1viu6wuEuoWPRX swHzar.oP9b2m7Ag4TRcGC0aB8TkDJlgpbY+ib1d54UHRoGhVOdhvbA.pofv MV54.kyqMSF8lobNSgYpGjJjB2FM8wUSLBxdhNq0vuWcvEbV5KTQxeR1k5tX fSo7i6o7cHpBWUy89OvIEoBKUBr9LZro+cChRTm8GC6PRR96AQTgX9yU3pgq tMb6gNLN5cNUwKve59myElxG8I7XQ4PZoR1QLC7xt6pFltVz4PRxPGjzFggO Fe40DMGc43PViwEiSEF4yXKwtqxCjx9TX6zurXQ6e7FcVrOeYwxIJcY3iZMP q.PgOYwJrjtpFidRNYE85OVQmlXEwI1Wo2adFGeIEcqtcb0Jbb05rl6G0xS9 wWAGPLF3tbdUMlI0JO.kvvHwTIE3GSJIasM31X61EGkNAVYT1XTxHdVICRY4 z6rC+r5f3MaWkpy7sq+uTtT2jSR9ic6g5ItNlniJLaSWG3eHHlOD7kSRFNBb m1YWeFPVZ55roRZweVcRLzUtbKj1GJnhtRhadkZRdiHGq4NSR.RhtO6ZK0Lg cIJG26SlWPw4ueQbx7V9AytRVb87pQ0WOP7Lh9J.FEm7EwfYFRAr0doh6ylY 96FJBs6Wno076t0pMGL1GxotRNezzJA.vtvpPeqG8UFd6K4cMXLNM541UgTz TPJ5VQZyDPxT0d6HEOkbBNGHMEfhlAfZ4kKizb.zTOjdq5rhTTy05ces9Fn8 yovn1WQ9QChLmDAUW+LVH8auMnzMXdjKLC2rzNjvbCsWnKTfelz5eh0BRnaK nz8DZDNM5oLW+F6k0ErFhWdpQ9kE+C.4uUTH -----------end_max5_patcher----------- </code></pre>

[Owen Green]

I think this is the same basic crash as the second one attached to my previous issue.

[Alex Harker]

OK - another object level crash. fl.peaks~ is really designed for spectral amplitudes and does a log of the input for spectral peak interpolation that don't play nice with negative input values. For now inputs are clamped to 0 in the peak interpolation if they go negative (meaning the interpolation/refinement step will probably do nothing). I've put in a note to pick this up as a discussion when we get onto objects.