Is your feature request related to a problem?
Yes. Even with captured events, extension sounds still need to be decoded/scheduled/mixed in the offline and native export audio paths.
Describe the solution you'd like
Mix captured extension audio events into final exported audio timeline.
This includes:
- Decoding extension asset files
- Scheduling by event
timeMs
- Applying per-event volume
- Mixing with existing sources (embedded, fallback, audio regions) without regressions
Describe alternatives you've considered
Injecting post-export audio overlay in a separate pass. Rejected for complexity and sync risk.
Additional context
This is the core implementation slice that makes exported output match preview intent.
Acceptance criteria
- Click events produce audible output in exported MP4 at expected times.
- Dense click sequences preserve order and do not drop unexpectedly.
- Existing source audio behavior remains correct.
- Integration tests verify audible signal near expected click timestamps.
Is your feature request related to a problem?
Yes. Even with captured events, extension sounds still need to be decoded/scheduled/mixed in the offline and native export audio paths.
Describe the solution you'd like
Mix captured extension audio events into final exported audio timeline.
This includes:
timeMsDescribe alternatives you've considered
Injecting post-export audio overlay in a separate pass. Rejected for complexity and sync risk.
Additional context
This is the core implementation slice that makes exported output match preview intent.
Acceptance criteria