Automate local parameter by other local parameter inside event context only

FMOD Studio
1

Hello! So, I trying to setup car engine sound events. I’ve created the automation “turbo” parameter by engine “rpm” and it looks like global dependency. It affects the other events which uses the same parameters.

image
image1924×1480 362 KB

image
image1248×1110 87.5 KB

Is there any way to prevent it, or it’s fmod constraint?

2

Hi,

Thank you for sharing the information and screenshots!

Just to clarify, are you saying that you created a parameter turbo and automated it based on the rpm parameter inside the e36 event, and that this setup unexpectedly affects other nested events (like engine, gearwhine, turbo), whose volumes are automated by their own turbo parameter, even though they are supposed to be independent?

Could you please share a few more details about how your events are structured and what behavior you’re aiming to achieve?

Some additional screenshots or a short video would really help confirm the setup and better understand the issue you’re encountering.

2 Likes
3

Thanks for responding!
Sure. Parameters “turbo” and “rpm” are local and I thought I can automate one with other inside event only. But this automation appears inside other event too (rccp_sport)
In this case turbo works fine, but what if I have to setup different automations for one parameter in many events? :slight_smile:

4

Thank you again for all the details and video! They’ve been super helpful in understanding what’s happening.

I think the issue comes down to how FMOD handles automation on local parameters:

When you automate one local parameter based on another local parameter, that automation becomes part of the parameter definition itself, not just the event.

This means that even if two events use a parameter with the same name (e.g. “turbo”), FMOD treats it as the same parameter definition.

As a result, any automation or modulation added to that parameter will appear in every event that uses it, even though the parameter values themselves are local to each event.

If you want different automation setups in different events, you could consider two options:

1. Use different parameter names

This ensures each parameter has its own definition and automation setup. For example:

  • One event uses rpm
  • Another uses rpm_alt or rpm2

2. Use the same parameter name, but place it in different folders in the Preset Browser

FMOD treats parameters as unique based on their path, not just their name. So you could do:

  • /vehicle/rpm
  • /aircraft/rpm

In this case, both are named "rpm", but FMOD sees them as completely independent parameters, each with its own automation.

Hope this helps, let me know if you have more questions.

1 Like