# Property seek limitations and suggestions

**URL:** <https://qa.fmod.com/t/property-seek-limitations-and-suggestions/22638>\
**Category:** FMOD Studio\
**Created:** [February 26, 2025, 9:17pm UTC](https://qa.fmod.com/t/property-seek-limitations-and-suggestions/22638 "2025-02-26T21:17:37Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![Alcibiade](https://yyz2.discourse-cdn.com/flex036/user_avatar/qa.fmod.com/alcibiade/32/4284_2.png) [@Alcibiade](https://qa.fmod.com/u/Alcibiade)\
**Post date:** [March 4, 2025, 11:56am UTC](https://qa.fmod.com/t/property-seek-limitations-and-suggestions/22638/5 "2025-03-04T11:56:36Z")

</div>

Thanks @joseph for the insight.  
Of course this is not only about what my personal use would be. It seems, when I posted [this](https://qa.fmod.com/t/suggestion-seek-speed-on-everything/16947) in 2021, you already had in mind how this feature would have to be designed. And I suspect users showing their interest were especially focused on the diverted use I’m describing, and I also suspect you didn’t fully adapted the development of the feature accordingly. Of course I might be wrong, but that could be interesting to ask users what they were waiting for exactly.  
By the way, I clearly remember thinking, at that time in 2021, “I hope they will correctly map the volume curve”!

> [@joseph](#):
>
> We can’t simply change the mapping curve that the modulator uses for volume properties, because that would make the values displayed for the modulator’s speed properties inaccurate.

This is, in my opinion, clearly the best solution, compared to the other ones. I think nobody cares about the real meaning of the value displayed for the seek modulator. “range/s” didn’t mean anything for me (until you explained, of course) and I didn’t care. I understand if the mapping is changed, they won’t be exact predictability of the seek duration to reach its target anymore, but I think this is way less important than having a smooth audio transition.  
Maybe the best of both worlds (with a little loss of clarity) would be an option to change the mapping (“linear dB”, “linear gain”, “constant power” maybe) of each volume seek modulator. This would ensure retro-compatibility with projects already using the feature.

> [@joseph](#):
>
> I suspect Aaron was actually alluding to a different workaround to the one you’re thinking of. Specifically, I believe he meant to suggest that, rather than automating your volume properties directly on the controlling parameter, you should create one new parameter for each volume property you want to automate, automate each of those volume properties on one of those new parameters, then automate those parameters on the controlling parameter. Then, place the seek modulators on the new parameters, rather than on the controlling parameter or the volume properties.

I’m quite sure Aaron was thinking about the normal method with a unique continuous parameter (“original workflow”, “completely viable workflow”, “particularly good workflow for this type of mixing”).  
That being said, I indeed thought about what you suggested, by using proxy parameters, but never tried yet.

---

_[View the full topic](https://qa.fmod.com/t/property-seek-limitations-and-suggestions/22638)._