Thanks — I can help explain that phrase, but first I want to make sure I’m addressing the exact situation you’re seeing. Could you tell me where you saw "flush audio emitter due to slow audio generation"? For example: • Is it a log message in your app or server console? • Is it coming from a browser console, mobile SDK logs, or a LiveKit server log? • Any lines above or below the message, a timestamp, or the actions happening at the time (joining a room, starting playback, running TTS, etc.)? If you can paste the exact log snippet (2–5 lines) or describe what you were doing when it appeared, I’ll explain what the message means and suggest next steps to resolve it. If you don’t have that info handy, here’s a brief general explanation to start: • It likely indicates the audio emitter (the component producing or sending audio frames) was flushed because audio frames were being generated more slowly than expected. • "Flush" here usually means queued audio was dropped or forced out to keep the stream timely rather than buffering indefinitely. • Causes can include CPU or network load, slow audio generation (e.g., TTS, audio processing), or the producer not writing frames fast enough. • Next troubleshooting steps would be checking CPU/memory, ensuring the audio source produces frames at the required sample rate and interval, and sharing the related log lines so I can recommend specific fixes. Send the context/log and I’ll walk you through targeted troubleshooting.