# Ambience values does not scale properly!

**URL:** <https://forum.fxsound.com/t/ambience-values-does-not-scale-properly/6429>\
**Category:** Get Help\
**Tags:** bug-fixed\
**Created:** [April 17, 2026, 1:02am UTC](https://forum.fxsound.com/t/ambience-values-does-not-scale-properly/6429 "2026-04-17T01:02:24Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![AliceInWonderland](https://avatars.discourse-cdn.com/v4/letter/a/57b2e6/32.png) [@AliceInWonderland](https://forum.fxsound.com/u/AliceInWonderland)\
**Post date:** [April 17, 2026, 1:02am UTC](https://forum.fxsound.com/t/ambience-values-does-not-scale-properly/6429/1 "2026-04-17T01:02:24Z")

</div>

i noticed the weird way ambience values work.  
0 = 3 same  
1 = 5 same  
2 = 4 same  
so it goes like this  
0= off  
1= lvl2  
2= lvl1  
3= off  
4= lvl1  
5= lvl2  
6= lvl3  
i think its pretty much how it goes. i don’t know if its intentional or not but it would be nice if it gets fixed. thanks \<3

---

<div class="post-metadata">

**Author:** ![coreywillei](https://avatars.discourse-cdn.com/v4/letter/c/9e8a1a/32.png) [@coreywillei](https://forum.fxsound.com/u/coreywillei)\
**Post date:** [April 29, 2026, 3:14am UTC](https://forum.fxsound.com/t/ambience-values-does-not-scale-properly/6429/2 "2026-04-29T03:14:44Z")

</div>

i’m a bit skeptical with your findings, is there some supported data or info you have on this \[1\]? because you might just been hearing placebo

* * *

1. part of me is curious cuz I wanna know too, but other part feels odd cuz it sounded like you raw-dogging (sorry vulgar is my lastname) the testing with your ears only and come to conclusion

---

<div class="post-metadata">

**Author:** ![bvijay](https://yyz2.discourse-cdn.com/flex030/user_avatar/forum.fxsound.com/bvijay/32/84_2.png) [@bvijay](https://forum.fxsound.com/u/bvijay)\
**Post date:** [May 3, 2026, 8:10am UTC](https://forum.fxsound.com/t/ambience-values-does-not-scale-properly/6429/3 "2026-05-03T08:10:21Z")

</div>

Thanks @AliceInWonderland for reporting this issue. I will take a look.
