Alexandre

-> in the filtergraph inspector, go to Constrains MAXIMUM Frequency/Amplitude/ or even Q : set it to "" using delete key

-> now you have Constrains MINIMUM set to and the number that was in the MINIMUM is now in the MAXIMUM...

We just tested that this bug happen in Max 4, 5 and 6...

To reproduce:
in filtergraph.maxhelp :
-> in the filtergraph inspector, go to Constrains MAXIMUM Frequency/Amplitude/ or even Q : set it to "" using delete key
-> save the patch
-> open it again
-> now you have Constrains MINIMUM set to  and the number that was in the MINIMUM is now in the MAXIMUM...

bug-filtergraph-constrains-maximum-mixing-up-when-saving-a-patch

Thanks Alexandre, I can reproduce and we will take a closer look.

[BUG] filtergraph Constrains Maximum mixing-up when saving a patch