# Fluid.noveltyslice~ instacrash

**URL:** https://discourse.flucoma.org/t/fluid-noveltyslice-instacrash/270
**Category:** Bug Reports and Issues
**Created:** [July 10, 2019, 11:27pm UTC](https://discourse.flucoma.org/t/fluid-noveltyslice-instacrash/270 "2019-07-10T23:27:04Z")
**Posts on this page:** 1
**Showing post:** 3

<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: [July 10, 2019, 11:42pm UTC](https://discourse.flucoma.org/t/fluid-noveltyslice-instacrash/270/3 "2019-07-10T23:42:36Z")

</div>

Looks like the reference file says “This cannot be modulated.” for a bunch of parameters.

Is it not possible to lock that out then? For example, the `@latency` attribute in `fluid.ampslice~` is read-only.

Or at minimum, if a user does modulate the value, return a red error and not crash Max.

---

_[View the full topic](https://discourse.flucoma.org/t/fluid-noveltyslice-instacrash/270)._