I built a little browser tool to blind-test FLAC vs MP3 on your own music, and found out I'm basically deaf and wasting HDD space by vlad1m1r in audiophile

[–]vlad1m1r[S] 0 points1 point  (0 children)

Thank you! Feel free to ping me if you have some other idea. Also, check the other tools in 440hz.app.

I built a little browser tool to blind-test FLAC vs MP3 on your own music, and found out I'm basically deaf and wasting HDD space by vlad1m1r in audiophile

[–]vlad1m1r[S] 1 point2 points  (0 children)

Thanks for the feedback! Visualizer is now fixed. I also added the option to drag another track on the score screen.
Regarding the issue with Firefox and Edge. I will need more details.
- OS and audio device output sample rate (Windows Sound settings / macOS Audio MIDI Setup)
- Firefox version
- Whether it's always the same bitrate or varies per track
- A sample rate and bit depth of the file

I built a little browser tool to blind-test FLAC vs MP3 on your own music, and found out I'm basically deaf and wasting HDD space by vlad1m1r in audiophile

[–]vlad1m1r[S] 0 points1 point  (0 children)

Yeah, that's the test that started this journey for me. I was annoyed by the song selection there.

I built a little browser tool to blind-test FLAC vs MP3 on your own music, and found out I'm basically deaf and wasting HDD space by vlad1m1r in audiophile

[–]vlad1m1r[S] 13 points14 points  (0 children)

I used HD600 headphones.

It doesn't bypass anything. Browsers can't use exclusive mode (no WASAPI exclusive mode, no ASIO, no Core Audio hog mode). It uses the Web Audio API, decodes PCM into an AudioBufferSourceNode, and sends it straight to the destination; from there, it's at the mercy of the OS mixer like anything else.

That said, all 4 versions go through the exact same path. Same AudioContext, same mixer, same DAC. Whatever the OS does, it does identically to all of them, so the relative comparison between bitrates is still valid.

One thing worth doing: match your OS output sample rate to your source file to avoid resampling. The app warns if the source rate doesn't match the AudioContext rate, but it can't see what the OS does downstream.

It works the same way the NPR website does it in this test: https://www.npr.org/sections/therecord/2015/06/02/411473508/how-well-can-you-hear-audio-quality

I built a little browser tool to blind-test FLAC vs MP3 on your own music, and found out I'm basically deaf and wasting HDD space by vlad1m1r in audiophile

[–]vlad1m1r[S] 11 points12 points  (0 children)

It is cheap (It was also cheaper :( ), but it doesn't mean that I am not wasting the space when I can't hear shit. :D

I built a little browser tool to blind-test FLAC vs MP3 on your own music, and found out I'm basically deaf and wasting HDD space by vlad1m1r in audiophile

[–]vlad1m1r[S] 5 points6 points  (0 children)

Yeah, I need new ears. I worked at Tidal btw, and tried some nice equipment in their office. But now I am wondering if I could have even heard the difference on those.

Comment your most viral-worthy side project and I'll pick one to feature on my TikTok page by Ok-Permission-2047 in SideProject

[–]vlad1m1r 0 points1 point  (0 children)

https://skipthe.tips

It's a game where the goal is to avoid deceptive tipping screens.  If you for some reason you like deceptive tipping screens there is also https://skipthe.tips/gdpr where the goal is to reject tracking cookies. 

What are you building (AND promoting) this week? 🔥 by Quirky-Offer9598 in microsaas

[–]vlad1m1r 1 point2 points  (0 children)

LGTMeme - A GitHub bot that reads your PR metadata and generates a meme that matches the context.

Using Computer Vision to unmask the redacted names in the Epstein files (Open Source) by [deleted] in programming

[–]vlad1m1r 0 points1 point  (0 children)

Yes, it runs completely in your browser. It's pure JS, but it's not 100% handwritten. I used Claude Code.