# Using a parameter to automate another parameter makes it read-only?

**URL:** <https://qa.fmod.com/t/using-a-parameter-to-automate-another-parameter-makes-it-read-only/21114>\
**Category:** FMOD Studio\
**Created:** [January 17, 2024, 9:19pm UTC](https://qa.fmod.com/t/using-a-parameter-to-automate-another-parameter-makes-it-read-only/21114 "2024-01-17T21:19:19Z")\
**Posts on this page:** 1\
**Showing post:** 7

<div class="post-metadata">

**Author:** ![EdGray](https://avatars.discourse-cdn.com/v4/letter/e/bbe5ce/32.png) [@EdGray](https://qa.fmod.com/u/EdGray)\
**Post date:** [January 30, 2024, 5:59pm UTC](https://qa.fmod.com/t/using-a-parameter-to-automate-another-parameter-makes-it-read-only/21114/7 "2024-01-30T17:59:04Z")

</div>

Hi Joseph, the solution I found was this:

 ![image](https://canada1.discourse-cdn.com/flex036/uploads/fmod/original/2X/d/dac05bd3bdaa570a4586633f829f7ef5d522cc6f.png)

The ‘GlideSpeedBoost’ parameter can be set to -100 to 100, and when the event is triggered this param will increment both GlideBoostInc & GlideBoostDec - however their curves are set up such that values of -100 to 0 will only affect GlideBoostDec, and 0 - 100 only GlideBoostInc. Both these params have velocity set to bring them back to 0 over time. This has the behaviour I intended: repeated triggers of this event will increment/decrement by further amounts.

Unfortunately this has now raised a potential bug as mentioned in this thread: [Automating the AHDSR envelope of a parameter with another parameter causes Unity to crash](https://qa.fmod.com/t/automating-the-ahdsr-envelope-of-a-parameter-with-another-parameter-causes-unity-to-crash/21173)

---

_[View the full topic](https://qa.fmod.com/t/using-a-parameter-to-automate-another-parameter-makes-it-read-only/21114)._