Function/line~ output jumping to high number after hitting intended peak

Asher Bay's icon

I have a function object with 3 points stored. One in the bottom left (0, 0), one at a predetermined point near the middle, say (5, 5), & one in the bottom right (10, 0). The function triggers a Line~ object, whose output is captured & displayed by a snapshot~ object. When I bang the function, the Line~ output starts crawling upward like it should, but when it reaches its intended peak (5 in this case), it jumps to a ludicrously high number, like 5822, & stays there.
Has anyone experienced this before? Or know what the cause may be? I hope my description makes sense.

Thanks

Christopher Dobrian's icon

It’s usually best to include a compressed copy of your patch so others can try to replicate the problem and/or see what might be incorrect. Did you try simply removing the function object and replacing it?

Asher Bay's icon

Thank you for the reply.

Max Patch
Copy patch and select New From Clipboard in Max.

This should demonstrate the problem I'm having.
Switching elements out doesn't appear to have any effect on the issue.

Floating Point's icon

click on the function object with patch unlocked, open the inspector, and change "mode" from "curve" to "linear".
this will simplify the list that's output from 3-arguments per break-point to two which is what line~ wants to get

example patch:

Max Patch
Copy patch and select New From Clipboard in Max.

Asher Bay's icon

It worked, thank you very much!

Tim Coomb's icon

I have tweaked this patch to run with Max For Live, however I want it to run over 16 bars. I tried substituting 16.0 for 5000 and 2500 but it doesn't work how I want. Could somebody suggest a solution.

Cheers

Using function and line~.maxpat
text/plain 5.60 KB