# Sample-accurate Metasound triggers from game code?

**URL:** <https://forums.unrealengine.com/t/sample-accurate-metasound-triggers-from-game-code/2654065>\
**Category:** Audio\
**Tags:** unreal-engine, question\
**Created:** [September 5, 2025, 5:57pm UTC](https://forums.unrealengine.com/t/sample-accurate-metasound-triggers-from-game-code/2654065 "2025-09-05T17:57:07Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![StapledBattery](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@StapledBattery](https://forums.unrealengine.com/u/StapledBattery)\
**Post date:** [September 5, 2025, 5:57pm UTC](https://forums.unrealengine.com/t/sample-accurate-metasound-triggers-from-game-code/2654065/1 "2025-09-05T17:57:07Z")

</div>

The [MetaSound overview page](https://dev.epicgames.com/documentation/en-us/unreal-engine/metasounds-the-next-generation-sound-sources-in-unreal-engine#sample-accuratecontrolofaudio) claims that “sample-accurate” triggers can be executed from “gameplay events”. How to do this?`UAudioComponent::SetTriggerParameter`is only tick-accurate. **Is there any function (C++ or blueprint) that can run a trigger at a specific (sub-tick) time?**

---

<div class="post-metadata">

**Author:** ![ShadowBr0kerz](https://d1ap1mz92jnks1.cloudfront.net/user_avatar/forums.unrealengine.com/shadowbr0kerz/32/1201558_2.png) [@ShadowBr0kerz](https://forums.unrealengine.com/u/ShadowBr0kerz)\
**Post date:** [September 26, 2026, 8:57am UTC](https://forums.unrealengine.com/t/sample-accurate-metasound-triggers-from-game-code/2654065/2 "2026-09-26T08:57:53Z")

</div>

short answer: not from the game thread, by construction. the game thread ticks at frame boundaries; the audio render thread runs its blocks on its own clock (typically every 1024 or 512 samples). a game thread call can never land inside an audio block, only before it.

what the engine gives you:

1. set trigger parameter (audio component or metasound source): the value is delivered to the render thread by the next block. that is tick accurate plus at most one block of latency, which for 60fps game plus 512-sample blocks is a few milliseconds worst case. this is what most games ship with and what the docs loosely call sample accurate.
2. quartz: when the timing requirement is musical, quartz exists precisely for this. schedule sounds on a clock with beats per minute, and the audio render thread executes the scheduled events on the sample clock. a trigger that must land on a beat or subdivision belongs here, not in tick.
3. the metasound input trick for offset scheduling: pass a time offset (in seconds or beats) as a float input alongside the trigger, and inside the metasound use a delay or scheduled node so the audio graph itself places the event on the sample grid. the game thread only needs to be close; the metasound does the sample accurate math. this is the pattern harmonix uses for beat synced content.
4. true audio-thread callbacks from gameplay code do not exist in blueprint and are limited in c++ (you can write a custom metasound node or DI that talks to the audio render thread directly, but the boundary is strict: no game thread calls from the render side, communication through lock-free queues).  
practical recipe for gameplay to audio tight sync: quartz clock plus a metasound with a beat scheduled envelope or trigger, values set via parameters on the component, one frame of game tolerance absorbed by the metasound’s internal scheduling. if you need single-shot punchy events (impacts, ui), the set trigger next block latency is perceptually transparent below roughly 10ms.
