Judging from this commit, the new behavior is by design: https://github.com/pure-data/pure-data/commit/f0a3a0c621dacc1f617cf07b38d8dc563703d12e

I seem to remember a long discussion where people *did not* like the clipping behavior. The rational was that the min/max values are meant for the UI min and max without enforcing direct clipping which you can do using [clip] explicitly.

Also judging form the commit, you can simply launch pd with an older compatibly mode.

--------
Dan Wilcox
@danomatika
danomatika.com

On Dec 20, 2015, at 4:07 PM, pd-list-request@lists.iem.at wrote:

From: William Huston <williamahuston@gmail.com>
Subject: [PD] Regression Issue/Bug: Range-limited [hsl] responds differently on out-of-range input
Date: December 20, 2015 at 4:06:36 PM MST


Regression Issue/Bug: 

Issue: Range-limited [hsl] responds differently on out-of-range input
PD Versions: 0.43.4-extended vs 0.46.7
OS: Raspbian 

The patch is:

[1000(
|
[hsl] # range limted 0-127 (default setting)
|
[nbx]  

Upon a bang to the message box, 
0.43.4-extended the answer is 127.
On 0.46.7 the answer is 1000.