Inspired by SthephanShi's and psubscirbe's players, but not forked from any player.
Planned to be made with vanilla HTML/CSS & TypeScript (no libraries other than CodeMirror).
No. Don't even open an issue about that. The library issue tag is for mistakes, not requests.
- Clone the repo (no instructions for this. if you don't know how to Google this, please don't fork)
- npm install
Any changes relating to CSS (i.e. styling) are in src/index.css (CSS).
Any changes relating to the website structure itself are in index.html (HTML).
Any changes relating to the bytebeat processor (audio handling, running the bytebeat, etc.) are in public/bytebeat-processor.js (JavaScript).
Any changes relating to any other code are in src/index.ts (TypeScript).
Any changes relating to configuration of the process of bundling (turning the website into HTML/CSS/JS that the browser can run) are in vite.config.ts (TypeScript).
If you're forking into your own project, CHANGE THE NAME AND LOGO, AND CHANGE THE COPYRIGHT STATEMENT IN LICENSE.
No. Get out.
Check out the dev console. If it says something about forks, well... :P
If it's something else then you definitely broke something. The first thing I'd check is if you're hosting on HTTPS or not.
Browsers are stupid and decided AudioWorklets are high security and should only be on "secure contexts" (aka. HTTPS
and localhost). In fact that's exactly why you need self-signed certs when locally testing (don't worry, the repo
provides a self signed SSL cert for you. It expires in 44 years so I don't think you need to worry about that)
Get SSL certs. You can get free ones from Let's Encrypt. If you wanna be "edgy" then get one of the paid providers.
Learn how to make websites.
Open an issue on the GitHub repo and I'll review it!
Never.
hi artifish
:3
:3
In human terms:
Google it.
In monkey terms:
funny code do funny math. funny math do funny sound. funny sound go boom boom boom. boom boom boom do good sound. good sound do woaaaaa
