Dev questions regarding API implementation

[yjm888]

Hoping crowdsource a little help here! I sent a build to devs recently and they seem to be having problems with event paths, i.e. locating the specific events corresponding to the parameters.

I did provide them with a list of parameters as they correspond to looped regions, but I can’t figure out how to provide them the event paths as they request them.

To clarify, there is one event in the project, within which are all the different regions that correspond to parameters. When I go to the event, and copy path all that pastes is " event:/eventname", but the devs seem to want more “events” than actually exist in the build. Is there an issue with how I packaged the build, a semantics miscommunication (i.e. they say "event: but mean “region”), or some other issue? I’m happy to clarify further if someone wants to jump in…thanks all

[li_fmod]

Hi,

Thank you for sharing the information!

@yjm888

To clarify, there is one event in the project, within which are all the different regions that correspond to parameters. When I go to the event, and copy path all that pastes is " event:/eventname", but the devs seem to want more “events” than actually exist in the build. Is there an issue with how I packaged the build, a semantics miscommunication (i.e. they say "event: but mean “region”), or some other issue?

From what you have described, It sounds like there might be a bit of a terminology mismatch between you and the devs.

In FMOD:

• An event refers to a single asset with all of its instruments, automations, and parameters.
• The “region” inside that event (especially one triggered by a parameter) is not considered a separate event, even though it might feel like a separate “track” or “variation.”

So if you have built all your looping sections into one event using a parameter (e.g. TrackNumber) to select between them, then the event path for all variations will still be something like: event:/music_loop

You might want to provide the devs with a simple mapping that shows how to access each section using parameter values, such as:

Event Path: event:/music_loop
Parameter Name: TrackNumber

Track A = 0
Track B = 1
Track C = 2

In code, the devs can use Studio::EventInstance::setParameterByName to switch between tracks, for example:

eventInstance->setParameterByName("TrackNumber", 1);

To better understand your setup and help further, could you please share:

• A screenshot of the event layout in FMOD Studio
• Which game engine the devs are using (Unity, Unreal, etc.)

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

[yjm888]

Thanks a million for the quick reply! This is already helpful. Is there a private channel or platform where I can share the requested info with you? (it’s sensitive/NDA/high-vis so I don’t want to post the screenshot here). Game engine-wise, they are using the API to integrate into a gamified tool within a website. They aren’t using Unity or Wwwise or any game engine that I know of.

[li_fmod]

@yjm888

Is there a private channel or platform where I can share the requested info with you? (it’s sensitive/NDA/high-vis so I don’t want to post the screenshot here).

Yes, you could upload them to your FMOD Profile.