Kenku FM - How To Use Output Of Chrome
Routing the audio output of a Google Chrome tab directly into Kenku FM allows tabletop roleplaying game masters to stream web-based soundboards, ambient generators, and music through Discord without capturing desktop system sounds. Achieving this requires configuring virtual audio routing software to capture the specific Chrome process and designating that virtual cable as the input source inside Kenku FM.
System Prerequisites and Virtual Audio Prerequisites
Streaming web audio smoothly into an online virtual tabletop session via Kenku FM requires specific architectural software components. Because web browsers like Google Chrome do not natively expose individual tab audio streams as discrete microphone inputs, an intermediate virtual audio routing layer is necessary.
- Essential Software Tools: Kenku FM desktop application, Google Chrome browser, and a virtual audio cable solution such as VB-Audio Virtual Cable, SteelSeries Sonar, or VoiceMeeter.
- Prerequisite Knowledge: Basic understanding of Windows or macOS audio device configuration, output routing principles, and Discord bot permission management.
- Estimated Setup Duration: 15 to 20 minutes for first-time virtual device configuration and software linking.
Step-by-Step Audio Routing Configuration
Step 1: Install and Configure a Virtual Audio Cable
Download and install a virtual audio routing driver on your operating system, ensuring your computer restarts if required by the installer package. Once installed, open your operating system sound settings and verify that a new playback device named Virtual Cable, Sonar Media, or equivalent appears in your list of audio endpoints. Do not set this virtual cable as your default system playback device, as you only want targeted applications to route audio through it.
Pro-Tip: If you use Windows 10 or 11, use the advanced sound settings or volume mixer panel to explicitly view per-application audio outputs.
Step 2: Route Google Chrome Audio to the Virtual Output
Launch Google Chrome and navigate to the web page hosting your desired audio, such as an ambient soundscape generator, YouTube playlist, or web-based soundboard. Open your operating system sound settings and navigate to the App Volume and Device Preferences or Volume Mixer panel. Locate Google Chrome in the active application list and change its output destination from Default to your newly installed Virtual Audio Cable. Play a test track in Chrome and verify through your hardware mixer or virtual cable control panel that audio signal meters are registering activity exclusively on that virtual line.
Step 3: Configure Kenku FM Input Settings
Open the Kenku FM application on your desktop and navigate to the settings menu located in the interface. Locate the input device selection dropdown menu, which dictates how the application listens for external audio sources. Select the Virtual Audio Cable input or the specific monitoring channel corresponding to the virtual cable that is currently receiving the output from Google Chrome. Save your changes and ensure the input meter within Kenku FM visualizes movement when you play audio inside your Chrome browser tab.
Warning: Avoid routing your entire system default playback device into Kenku FM, or you will accidentally broadcast private operating system notification sounds, Discord call chimes, and microphone feedback to your players.
Step 4: Stream Audio to Your Discord Voice Channel
Connect Kenku FM to your designated Discord server voice channel using the built-in bot integration or the desktop client connection method. Within Kenku FM, enable the external input or microphone stream so that the audio captured from your virtual cable is transmitted directly into the Discord voice channel. Adjust the volume sliders inside Kenku FM and ask your players to confirm that the audio level coming from the browser tab is balanced against voice chat volumes.
Audio Routing Parameter Comparison
| Routing Method | Setup Complexity | CPU Overhead | Multi-Tab Isolation | Best Use Case |
|---|---|---|---|---|
| VB-Audio Cable | Low | Minimal | No (All Chrome) | Simple web soundboards |
| SteelSeries Sonar | Medium | Low-Moderate | Yes (Per-App) | Advanced stream mixing |
| VoiceMeeter Banana | High | Low | Yes (Advanced Bus) | Complex multi-source mixing |
| Native Browser Cast | Very Low | Minimal | Yes | Direct casting without bot |
Common Audio Failures and Field Fixes
- Root Cause: No audio signal registers inside Kenku FM despite playing music in Google Chrome.
- Actionable Fix: Verify that the Windows or macOS application volume mixer still points Google Chrome to the virtual cable, as browser updates or restarts occasionally reset application routing defaults back to the primary sound card.
- Root Cause: Players in Discord report hearing a loud, high-pitched screeching feedback loop.
- Actionable Fix: Ensure that Kenku FM is not monitoring its own output or sending the virtual cable input back into your default listening speakers while you have headphones disconnected. Use closed-back headphones and mute the virtual cable monitoring channel in your system sound control panel.
- Root Cause: Google Chrome audio is missing entirely from both the browser and Kenku FM.
- Actionable Fix: Restart the Windows Audio service or reboot your computer to clear hung virtual audio driver states, then re-select the virtual cable device in both the operating system volume mixer and Kenku FM settings.
Frequently Asked Questions
Can I route multiple Chrome tabs to different audio channels in Kenku FM?
Standard virtual audio cables capture the entire Google Chrome process, meaning all tabs play through the same output line. To isolate individual tabs, you must use advanced routing software like SteelSeries Sonar or run separate instances of different web browsers routed to distinct virtual cables.
Why is there a noticeable audio delay between Chrome and Discord?
Audio buffering across virtual cables, web browsers, and Discord streaming servers naturally introduces a latency of 100 to 300 milliseconds. This delay is normal for streaming operations and rarely impacts ambient soundscapes or background music during roleplaying sessions.
Do my players need to install any special software to hear the Chrome audio?
No, your players do not need any plugins or extra software installed on their computers. Because Kenku FM streams the processed audio directly through the Discord voice channel, your players will hear the audio using their standard Discord client.
Can I use this method on macOS as well as Windows?
Yes, macOS users can achieve the exact same workflow by utilizing Rogue Amoeba Loopback, BlackHole, or similar virtual audio routing drivers compatible with Apple silicon and Intel processors.
Enhance your tabletop roleplaying game sessions today by seamlessly integrating dynamic web soundboards and atmospheric music directly into your online campaigns.
