# Max attribute behaviour is messing with max user expectations in help files

**URL:** <https://discourse.flucoma.org/t/max-attribute-behaviour-is-messing-with-max-user-expectations-in-help-files/2639>\
**Category:** Bug Reports and Issues\
**Created:** [August 23, 2025, 10:03am UTC](https://discourse.flucoma.org/t/max-attribute-behaviour-is-messing-with-max-user-expectations-in-help-files/2639 "2025-08-23T10:03:48Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![rodrigo.constanzo](https://discourse.flucoma.org/user_avatar/discourse.flucoma.org/rodrigo.constanzo/32/12_2.png) [@rodrigo.constanzo](https://discourse.flucoma.org/u/rodrigo.constanzo)\
**Post date:** [August 23, 2025, 10:03am UTC](https://discourse.flucoma.org/t/max-attribute-behaviour-is-messing-with-max-user-expectations-in-help-files/2639/1 "2025-08-23T10:03:48Z")

</div>

> [@1.0.9 pre-release testing](https://discourse.flucoma.org/t/1-0-9-pre-release-testing/2620/2):
>
> sample list test Pd MacOS

Ok went through all of these.

`fluid.dataset~` “audio-descriptor” and “merging” tabs pours off patch size:

 ![Screenshot 2025-08-23 at 10.52.17 AM](https://discourse.flucoma.org/uploads/default/original/2X/2/2337e5ae0b7aa6bd53d04afb5004df38df327978.png)

 ![Screenshot 2025-08-23 at 10.53.12 AM](https://discourse.flucoma.org/uploads/default/original/2X/5/51c28459795230c6adb65b071f6bfb129264d2a7.png)

There’s also some inconsistencies/weirdness with `fluid.noveltyfeature~` / `fluid.noveltyslice~` with `@maxfiltersize`, but I don’t think these are 1.0.9 related.

So it seems like `@maxfiltersize` _cannot_ be changed at all, as an attribute. You need to set it as an argument. I guess that’s a Max quirkiness thing where you want to be able to set it as an argument and an attribute.

A more solvable thing is that the default settings and the attributes set in the `fluid.noveltyfeature~` mean that it is not possible to adjust the `filtersize` `attrui`. This was super confusing and sent me down the rabbit hole of `maxfiltersize`, but looking at the helpfile for `fluid.bufnolvetyfeature~` I can see that more comprehensive attributes have been set, which means you _can_ adjust `filtersize` in that helpfile. So my suggestion with this whole long rant here is to adjust the `@maxfiltersize` in the `fluid.noveltyfeature~` helpfile to be something \> 0, especially if you are going to expose the `filtersize` as an `attrui` for the user to mess with.

---

<div class="post-metadata">

**Author:** ![tremblap](https://discourse.flucoma.org/user_avatar/discourse.flucoma.org/tremblap/32/5_2.png) [@tremblap](https://discourse.flucoma.org/u/tremblap)\
**Post date:** [August 23, 2025, 10:41am UTC](https://discourse.flucoma.org/t/max-attribute-behaviour-is-messing-with-max-user-expectations-in-help-files/2639/2 "2025-08-23T10:41:05Z")

</div>

I’ve moved this to another thread - it is more a ‘bug’ report which is not a bug anyway.

> [@rodrigo.constanzo](#):
>
> So it seems like `@maxfiltersize`

the @max\* attributes were, by design, never changeable post instantiation. The GUI doesn’t let you. It is a hack to get attrui to get them, and we auto-set them so begenning users do not have to think about allocation

at the moment, you can go downwards from the attribute that has a ‘max’ attribute . having 2 values might (or might not) improve the help for users, I’ll ponder.

---

<div class="post-metadata">

**Author:** ![rodrigo.constanzo](https://discourse.flucoma.org/user_avatar/discourse.flucoma.org/rodrigo.constanzo/32/12_2.png) [@rodrigo.constanzo](https://discourse.flucoma.org/u/rodrigo.constanzo)\
**Post date:** [August 23, 2025, 10:55am UTC](https://discourse.flucoma.org/t/max-attribute-behaviour-is-messing-with-max-user-expectations-in-help-files/2639/3 "2025-08-23T10:55:02Z")

</div>

Yeah I figured that it was a Max quirkiness while making the post.

Having `filtersize` be adjustable for `fluid.noveltyfeature~` is something that should be there though as it’s super confusing otherwise (by having a non-`1` value set for it as an attribute in the helpfile).