"It works! (Nobody is more surprised than I am)"

Please use release version 2.2.0 since it actually works... 2.5.X is cursed so we reverted to 2.3.X

A retro CRT-style music player that somehow manages to play tracker modules and MIDI files without completely falling apart. Built with the coding skills of someone who definitely Googled "how to JavaScript" more times than they'd care to admit.

• Tracker Module Support: Plays .MOD, .XM, .IT, .S3M files (thanks to people much smarter than me)
• MIDI Playback: Handles .MID/.MIDI files (again, not my code doing the heavy lifting)
• Retro CRT Interface: Because modern UIs are for people with actual design skills
• Docker Support: Containerized chaos for your convenience
• Drag & Drop: Upload files by dragging them around like a caveman - Sort of...
• Volume Control: Goes from 0 to 100, just like my anxiety while coding this

This project is a masterclass in "just keep adding libraries and loaders until something works." It features:

• 4 different audio libraries because I couldn't figure out how to make one work properly
• A glorious fallback system for when the main system inevitably fails
• Custom loaders for OpenMPT and MidiCube "Install these NPM packages they said, it would be easy they said, it would be fun they said."
• Error handling that mostly consists of console.log("oh no")
• Comments written by someone who clearly forgot what their code does 5 minutes after writing it
• Variable names like thingy, audioStuff, and whyIsThisBroken
• It can play both midi and various mod files! To a certain degree before everything breaks and I cry

Since I'm basically just duct-taping other people's brilliant work together:

• ChiptuneJS by @deskjet - For making tracker modules actually play instead of just making computer noises
• libOpenMPT - The WASM magic that I definitely don't understand but am grateful exists
• WebAudio-TinySynth by @g200kg - For MIDI synthesis that sounds like a dying robot

• Docker - Because "it works on my machine" is a valid deployment strategy
• Node.js & Express - For serving files and pretending to be a real backend
• Web Audio API - The browser API that does all the actual work
• CSS Grid & Flexbox - For layouts that look intentional
• Promises/Async/Await - For handling the chaos asynchronously

# Clone this beautiful disaster git clone https://github.com/SomeShr1mp/FusionPlayer.git cd FusionPlayer # Build the container (pray it works) docker-compose build # Run it (hold your breath) docker-compose up -d --build # Podman also works flawlessly for some godforsaken reason for building & running the project. # Access at http://localhost:3043 # (Port 3043 because 3000 was "too mainstream".... you can use port 3000 when running with npm though)

#Clone this pile of garbadge git clone https://github.com/SomeShr1mp/FusionPlayer.git cd FusionPlayer #Pull the necessary libraries, may need to source your own soundfont, please be sure to be in the root project folder for this curl -L -f -o public/js/libopenmpt.js https://cdn.jsdelivr.net/gh/deskjet/chiptune2.js@master/libopenmpt.js curl -L -f -o public/js/libopenmpt.js.mem https://cdn.jsdelivr.net/gh/deskjet/chiptune2.js@master/libopenmpt.js.mem curl -L -f -o public/js/chiptune2.js https://cdn.jsdelivr.net/gh/deskjet/chiptune2.js@master/chiptune2.js curl -L -f -o public/js/webaudio-tinysynth.js https://g200kg.github.io/webaudio-tinysynth/webaudio-tinysynth.js # Now time for NPM to do it's thing npm i # Hopefully nothing broke, let's start it npm start # Access at http://localhost:3000 # (To appease those that don't enjoy the glory of Docker)

FusionPlayer/ ├── server.js # Express server that somehow works ├── public/ │ ├── index.html # The main page (surprisingly functional) │ ├── index-fallback.html # For when the main page inevitably breaks │ ├── module-test.html # For testing the various modules and making sure various API's work │ ├── wasm-test.html # For testing wasm loading... a lot more useful than expected │ ├── midi-test.html # The first iteration of the page... only go if you like MIDI test chords │ ├── css/styles.css # CRT effects that make bugs look intentional │ ├── music/ # Exactly what it says on the tin, use the provided test files or make your own! │ ├── soundfonts/ # Pretty much just the soundfonts folder, when using docker, the default one is preloaded. NPM users must find their own │ └── js/ │ ├── audio-engine.js # The "main" engine (uses fallback anyway) │ ├── fallback-audio-engine.js # The one that actually works │ ├── ui-controller.js # UI logic held together with hope │ ├── midicube-loader.js # The loader that my audio engines like. PLEASE DO NOT LET THE BREAK I CAN'T TAKE IT ANYMORE │ ├── openmpt-loader.js # PLEASE GOD DO NOT LET THIS BREAK - IT BREAKS EVERYTHING │ └── midi-parser.js # MIDI parsing that mostly works ├── docker-compose.yml # Container config for the brave └── Dockerfile # Multi-stage build because I read it was "best practice" 

1. Upload Files: Drag music files onto the upload area or click to browse - Need to fix file permission issues & upload issues
2. Select Track: Click on a file in the list (revolutionary UX)
3. Play Music: Hit the play button and hope for the best
4. Control Playback: Use the buttons that look like they're from 1985
5. Adjust Volume: Slider goes left and right (groundbreaking) - still not working...

• Tracker Modules: .mod, .xm, .it, .s3m (the classics)
• MIDI Files: .mid, .midi (because who doesn't love GM patches)
• SoundFonts ---- SOOON --- Like really soon!!: .sf2 (for when built-in MIDI sounds aren't terrible enough)

Environment variables you can set (if you're feeling adventurous):

NODE_ENV=production # Hides some of the debugging shame PORT=3000 # Change if you hate yourself HOST=0.0.0.0 # For Docker networking magic AUDIO_ENGINE_VERSION=2.0 # Because versioning makes me look professional MAX_UPLOAD_SIZE=200MB # For those 4-hour epic tracker modules

• Occasional Audio Glitches: Sometimes sounds like R2-D2 having a breakdown
• File Loading: May take a few seconds because WebAssembly is magic - Uploads don't really work due to File permissions
• Browser Compatibility: Works in Chrome, probably crashes in IE, Works in Firefox and it's offspring
• Mobile Support: Exists in theory, works in practice about 60% of the time
• Error Messages: Range from cryptic to completely unhelpful
• Memory Leaks: The browser might get hungry after playing 50+ files

If you're brave enough to dive into this codebase:

1. Fork it (you'll regret this)
2. Create a branch (git checkout -b fix-the-terrible-code)
3. Make changes (try to make it worse, I dare you)
4. Test thoroughly (by which I mean "run it once and hope")
5. Submit PR (prepare for existential crisis during code review)

• Indentation: 4 spaces because I'm not a monster
• Semicolons: Sometimes yes, sometimes no, always inconsistent
• Variable Names: Should be descriptive or entertainingly bad
• Comments: Explain why, not what (mostly "why did I do this to myself")

GPLv3 License - Feel free to copy this disaster and make it your own disaster.

• Stack Overflow - For basically writing 80% of this code
• MDN Web Docs - For explaining Web APIs to someone who clearly didn't listen in CS class
• Letal ammounts of Caffine and Achohol - The real MVP
• Rubber Duck Debugging - My most patient collaborator
• The Chiptune/Demoscene Community - For keeping tracker music alive
• Every Developer who made the libraries that actually work
• My Past Self - For leaving comments that present me could understand
• James Lyerla - Would not have been able to do much of anything on this project with out him

If it breaks (when it breaks), try:

1. Refreshing the page (classic IT solution)
2. Clearing browser cache (modern problems require modern solutions)
3. Restarting Docker (when in doubt, restart everything)
4. Crying softly (therapeutic and realistic)
5. Opening an issue (so we can cry and scream together)
6. Gaze into the void (Most realistic option)
7. When in doubt, apply holy oils to the blessed machine and recite the prayers of repair (When all else fails)

"WAAAAAAAAAAAAAAAAAAAAAAAAAAAAGGH!" - Ghazghkull Mag Uruk Thraka

(This README is longer than some of my actual code files, which probably says something about my priorities)