Kenku FM: How To Use Output Of Chrome For Tabletop Audio
Capturing and routing Google Chrome browser audio into Kenku FM allows tabletop roleplaying game masters to stream ambient sounds, custom soundscapes, and browser-based music players directly into Discord via a virtual audio device. This comprehensive guide covers the technical pipeline required to route Chrome web audio through third-party audio drivers, assign it as an input source within Kenku FM, and achieve seamless audio synchronization for remote TTRPG sessions.
Technical Prerequisites and Audio Routing Framework
Establishing a reliable web audio stream requires bridging browser output with a dedicated tabletop soundboard application. Because modern web browsers do not natively allow individual tab audio to be selected as a direct microphone or line-in source by third-party applications, you must deploy a virtual audio cable or routing utility. This setup ensures that audio playing from platforms like YouTube, Syrinscape web clients, or custom web audio generators is cleanly captured without capturing unwanted system sounds, Discord notifications, or microphone feedback.
- Essential Software Tools: Kenku FM desktop application (latest stable release), Google Chrome browser, and a virtual audio routing driver such as VB-Audio Cable, VoiceMeeter, or BlackHole (for macOS users).
- Mandatory Prerequisite Knowledge: Basic familiarity with Windows or macOS sound control panels, understanding of input/output device mapping, and administrative permissions to install audio driver software.
- Performance Benchmarks: Expect an audio latency overhead of less than 20 milliseconds when using a dedicated virtual audio cable configured to a 48kHz sample rate with a 512-sample buffer size.
Step-by-Step Chrome Audio Integration Workflow
Step 1: Install and Configure the Virtual Audio Driver
Download and install a virtual audio cable utility compatible with your operating system, such as VB-Audio Cable for Windows or BlackHole 2ch for macOS. Restart your computer after installation to ensure the audio drivers register correctly within your operating system's core audio engine. Navigate to your operating system sound settings and verify that the newly installed virtual cable appears as both a playback device (output) and a recording device (input).
Pro-Tip: Set the default sample rate of your virtual audio cable in the Windows Sound Control Panel or macOS Audio MIDI Setup to match your primary playback device, typically 48,000 Hz at 24-bit depth, to prevent audio artifacting and pitch shifting.
Step 2: Route Google Chrome Audio Output
Launch Google Chrome and navigate to the media source or web application you wish to use for your game session. Because Chrome automatically outputs audio to your default system playback device, you must redirect it to your virtual audio cable. On Windows 10 and 11, open the Volume Mixer settings (System Settings > Sound > Volume Mixer), locate Google Chrome in the list of active applications, and change its Output dropdown menu from Default to your virtual audio cable.
Warning: Changing Chrome's system output will route all browser audio—including YouTube videos, Discord web app alerts, and background advertisements—through the virtual cable. Ensure you close non-essential tabs to avoid broadcasting unwanted sounds to your players.
Step 3: Configure Kenku FM to Ingest the Virtual Audio Stream
Open Kenku FM and navigate to the application settings menu to configure your audio sources. Locate the input device selection panel where Kenku FM detects microphones and auxiliary lines. Select your virtual audio cable as the designated input source within Kenku FM. This action allows Kenku FM to listen directly to the audio stream being pumped out of Google Chrome.
Step 4: Test and Stream to Discord
Join your game's active Discord voice channel through Kenku FM or your standard Discord desktop client. Initiate a test playback in Chrome, such as an ambient audio loop or a test track, and monitor the audio meters inside Kenku FM to confirm input levels are registering correctly. Adjust the volume slider within Kenku FM to balance the web audio against your microphone and local soundboard tracks before your players join the session.
Which Kenku Should I Use? , Kumkum: Unveiling the Symbolism and Uses in ...
Audio Routing Infrastructure Comparison
| Routing Method | Setup Complexity | Latency Overhead | CPU Impact | Best Use Case |
|---|---|---|---|---|
| VB-Audio Cable | Low | Ultra-Low (~10ms) | Negligible | Simple Windows routing of a single browser instance |
| VoiceMeeter Banana | High | Low (~15ms) | Low | Complex multi-source mixing (Microphone + Chrome + Soundboard) |
| BlackHole (macOS) | Medium | Ultra-Low (~10ms) | Negligible | Native macOS routing for web-based sound generators |
| OBS Virtual Audio | High | Moderate (~30ms) | Moderate | Advanced streaming setups requiring visual monitoring |
Common Audio Failures and Field Fixes
- Issue: No audio is registering inside Kenku FM.
- Root Cause: The Windows Volume Mixer reverted Chrome's output back to the default system device, or the virtual cable sample rate is mismatched.
- Actionable Fix: Reopen the Windows Volume Mixer while Chrome is actively playing media to re-assign the output to the virtual cable. Check that both Chrome and Kenku FM match the operating system's master sample rate.
- Issue: Echo or feedback loop is audible in the Discord channel.
- Root Cause: Kenku FM is monitoring its own input source and rebroadcasting it back into the voice channel, or Chrome is playing the same audio source as a local tab.
- Actionable Fix: Mute the local monitor output within Kenku FM settings for the virtual audio input device and ensure you are not running a duplicate audio tab inside your local Discord client.
- Issue: Distorted, crackling, or robotic audio playback.
- Root Cause: Buffer underruns caused by mismatched audio buffer sizes between the browser media stream and the virtual audio driver.
- Actionable Fix: Increase the audio buffer size in your virtual cable control panel from 256 samples to 512 or 1024 samples to stabilize the data stream.
Frequently Asked Questions
Can I route multiple Chrome tabs to different virtual audio channels?
Standard Windows audio settings treat Google Chrome as a single unified process for volume mixing, meaning all tabs share the same output assignment. To route separate tabs independently, you must use standalone browser instances, different browser applications (such as Firefox or Edge), or advanced third-party audio routing software like VoiceMeeter.
Does routing Chrome audio through Kenku FM affect my microphone quality?
No, routing Chrome audio utilizes a separate virtual line-in channel within Kenku FM. Your physical microphone remains mapped to its own dedicated input channel, allowing you to speak over background music and ambient soundscapes without interference.
Why is there a noticeable delay between clicking play in Chrome and hearing it in Discord?
Audio latency is typically introduced by mismatched buffer settings or audio driver processing delays. Lowering your virtual cable's buffer size to 256 or 512 samples usually resolves perceptible lag while maintaining stream stability.
Is it possible to use this method on a Mac without third-party software?
macOS does not natively support routing application-specific audio outputs without an intermediate driver. You must install a lightweight virtual audio routing utility like BlackHole or Soundflower to bridge Google Chrome audio into Kenku FM.
Elevate your remote tabletop roleplaying campaigns by integrating dynamic web audio sources into Kenku FM today. Download the necessary virtual audio drivers and configure your Chrome output to deliver professional soundscapes straight to your players.
