Skip to content

Relive your nostalgia with the Beatnik Audio Engine (Windows Only)

Notifications You must be signed in to change notification settings

zefie/BeatnikProject2019

Folders and files

NameName
Last commit message
Last commit date
Mar 13, 2024
Mar 13, 2024
Apr 26, 2024
Mar 13, 2024
Jun 28, 2019
Jun 28, 2019
Jul 21, 2019
Nov 27, 2022
Oct 12, 2021
Mar 15, 2024

Repository files navigation

BeatnikProject2019

Relive your nostalgia with the Beatnik Audio Engine (Windows Only)

Status:

  • Beta
    • Basic functionality should work, but glitches or bugs are expected to occur.

Requirements:

  • Windows 7 or newer. (For Windows XP Support please use build v1.1.7955.26414)
    • May have minor graphical issues on Windows XP but functions propertly with older version (tested on Pentium 3 with WinXP and 256MB RAM)
  • .NET Framework 4.8

Features:

  • Play Beatnik RMF, MIDI, MIDI Karaoke Files using classic Beatnik Soundbanks
  • Basic MIDI Controls, such as Transpose, Tempo, Volume, Seeking, Channel Mute
  • Ability to switch soundbanks almost seamlessly
  • 20+ Soundbanks to choose from, including rare Soundbanks from WebTV and Nokia devices.
  • User Configuration Support to retain common settings
  • Drag-n-Drop Support
  • File association support (Use "Open With", then check "Always Open With" after browsing to BXPlayerGUI.exe)

How to use:

  • Unrar archive
  • Run BXPlayerGUI
  • If the Open Button is greyed out, and it says "Current Patch Bank: None", or you want to change the bank
    • Click "Patch Bank Switcher"
    • Choose a patchset and apply it
  • Load MIDI and enjoy!

Note regarding Firewalls:

Opening .kar files runs a internal "HTTP Server" (not standard by any means), because Beatnik won't open a .kar even though its just a .mid. The miniHTTP is used to make Beatnik think its getting a .mid, but we send it a .kar, without having to modify your filesystem or create temporary files. The miniHTTP is also used to send files in which Beatnik chokes on the filename, such as files with [] in them. Therefore, if you get any prompts from your firewall regarding the application listening on a port (should be localhost!), then this is why.

Screenshot