Back to Laboratory

Launch MegaOke

Select your interface. Compile custom songs, use your main PC as the audio Host, or connect your smartphone as the wireless Remote.

The Architecture of Web Karaoke

Traditional karaoke systems rely on heavy desktop software, external hard drives, or expensive proprietary hardware. The TYF MegaOke Suite was engineered to bring that exact cinematic experience directly into your web browser using modern client-side technologies.

How the Dual-System Works

To ensure zero audio latency and maximum performance, the suite is split into two distinct applications:

Strict BYOC (Bring Your Own Content) Policy

Tristan's Digital Lab provides the playback engine only. We do not host, sell, or distribute copyrighted music, MIDI files, karaoke tracks (.kar), or proprietary SoundFonts. All media processing happens locally on your machine. You are strictly responsible for providing your own legally obtained files to utilize this software.

Client-Side Privacy Guarantee

When you load your personal song collection into the MegaOke Host, those files are read securely via the browser's FileReader API. Your personal files never touch a cloud server, and your listening habits are not tracked or uploaded. This ensures immediate load times and total data privacy.

Frequently Asked Questions

How do I link the Mobile Remote to the Desktop Host?

When you launch the Host Machine (`krk.html`), it will generate a unique session ID or WebSocket IP. Simply open the Mobile Remote (`mobile.html`) on your phone, ensure you are on the same local network, and input the host's ID to establish a connection.

Why is there no sound when I load a .mid or .kar file?

MIDI files contain sheet music data, not actual audio waves. You must first load a SoundFont (.sf2 file) into the Host engine. The SoundFont acts as the instrument library that the WebAssembly synthesizer uses to generate the audio.

Does MegaOke work offline?

Yes. Once the core application assets (HTML, CSS, JS, and Wasm binaries) are cached by your browser, the actual processing of audio files and lyric parsing happens entirely offline via client-side rendering.