# UE Audio Component vs. FMOD Audio Component - Envelope Followers

**URL:** https://qa.fmod.com/t/ue-audio-component-vs-fmod-audio-component-envelope-followers/23627
**Category:** Unreal Engine
**Created:** [November 11, 2025, 9:07pm UTC](https://qa.fmod.com/t/ue-audio-component-vs-fmod-audio-component-envelope-followers/23627 "2025-11-11T21:07:29Z")
**Posts on this page:** 3
**Page:** 1

<div class="post-metadata">

### Author: ![DrewKski0](https://yyz2.discourse-cdn.com/flex036/user_avatar/qa.fmod.com/drewkski0/32/1775_2.png) [@DrewKski0](https://qa.fmod.com/u/DrewKski0)
#### Post date: [November 11, 2025, 9:07pm UTC](https://qa.fmod.com/t/ue-audio-component-vs-fmod-audio-component-envelope-followers/23627/1 "2025-11-11T21:07:29Z")

</div>

Hi-yeee Friendly Neighborhood FMODders!

My team & I are working out how to set up an envelope follower for a walkie talkie. Specifically, we’re looking to get the walkie to light up relative to the intensity of the audio waveform playing from each walkie-specific dialogue event. One of our engineers figured out a way to do this with the native UE Audio Component but we’re hitting a wall getting the same behavior out of FMOD events.

Chat GPT (and I am sincerely sorry for even bringing it up) suggested metering the bus from the mixer group, but we’re having trouble doing this (or even knowing if this is the right way forward).

We’re using UE 5.6.1 and FMOD 2.03.08. Any suggestions?

(and thank you!)

---

<div class="post-metadata">

### Author: ![jeff\_fmod](https://yyz2.discourse-cdn.com/flex036/user_avatar/qa.fmod.com/jeff_fmod/32/1766_2.png) [@jeff\_fmod](https://qa.fmod.com/u/jeff_fmod)
#### Post date: [November 18, 2025, 5:28am UTC](https://qa.fmod.com/t/ue-audio-component-vs-fmod-audio-component-envelope-followers/23627/2 "2025-11-18T05:28:42Z")

</div>

Yes querying the bus metering info is a good approach. The process would be:

- Find the bus with [`Studio::System::getBus`](https://fmod.com/docs/2.02/api/studio-api-system.html#studio_system_getbus)
- Get the bus’s underlying Core API `ChannelGroup` with [`Studio::Bus::getChannelGroup`](https://fmod.com/docs/2.02/api/studio-api-bus.html#studio_bus_getchannelgroup)
  - If you can’t access it, it’s probably because it hasn’t been created yet, in which case you need to force it into existence with [`Studio::Bus::lockChannelGroup`](https://fmod.com/docs/2.02/api/studio-api-bus.html#studio_bus_lockchannelgroup)

- Get the `ChannelGroup`’s [`DSP_HEAD`](https://fmod.com/docs/2.02/api/core-api-channelcontrol.html#fmod_channelcontrol_dsp_index) with [`ChannelControl::getDSP`](https://fmod.com/docs/2.02/api/core-api-channelcontrol.html#channelcontrol_getdsp)
- Enable metering on the DSP with [`DSP::setMeteringEnabled`](https://fmod.com/docs/2.02/api/core-api-dsp.html#dsp_setmeteringenabled)

Now whenever you want to get the peak or rms levels you can use [`DSP::getMeteringInfo`](https://fmod.com/docs/2.02/api/core-api-dsp.html#dsp_getmeteringinfo) on that DSP object.  
Hopefully that helps!  
EDIT: I noticed someone else happens to be using this same approach for getting metering info, in case you need a code snippet to reference [Clarification on how getMeteringInfo works](https://qa.fmod.com/t/clarification-on-how-getmeteringinfo-works/23649)

---

<div class="post-metadata">

### Author: ![DrewKski0](https://yyz2.discourse-cdn.com/flex036/user_avatar/qa.fmod.com/drewkski0/32/1775_2.png) [@DrewKski0](https://qa.fmod.com/u/DrewKski0)
#### Post date: [December 15, 2025, 6:37pm UTC](https://qa.fmod.com/t/ue-audio-component-vs-fmod-audio-component-envelope-followers/23627/3 "2025-12-15T18:37:14Z")

</div>

I am so sorry for this insanely late reply - this is exactly what we were looking for. Thank you very much @jeff_fmod!
