I found a tool named [Lossless Audio Checker](https://losslessaudiochecker.com) : "A utility to check whether a WAVE or FLAC file is truly lossless or not".
I was so sad that this project is not open-source but their Research papers give some interesting clues about detecting bad quality files.
On my side, I used it through a [Bash script](https://gist.github.com/madeindjs/d5e3949313b141f2e5eea62b98...) to detect bad files in my library. The tool produces a lot of false positives since it triggered on some High Res audio musics I bought on Qobuz.
I personally use MPV to play my music libraries containing mainly FLAC file and I wrote a plugin [1] using JS to send my listens to listenbrainz.org . It's damn simple, but it worked for the past few months!
I thought the same thing. As a Node.js dev, I can quickly create a .mjs file and use a `module.export` to return a JavaScript object who contains the configuration. Thus, i can use template string and/or function to do what I want. I can even load JSON files natively
I made basics bash scripts to do some simple stuffs. Scripts I use more often are:
1. A script who help me to make conventional commits name (ex: `feat(xyz): add some stuff. JIRA-ID`). It add Jira Id at the end using git branch, get scope using path of the folder and ask me the rest
2. Create a markdown file for the day as worklog. An another script create markdown file for the Jira issue that I work on and add a wikilink on the worklog
3. Read scripts in package.json and ask me what I want to execute using fzf
I try to do more and more since it's really useful and I had some fun to made them.
As a developer, I love JavaScript ecosystem for some of theses drawback of this package manager.
I'm be able to quickly publish a library on NPM and this is great IMO. Few years ago, I tried to do it for Maven in Java and it was a nightmare.
> We don't need two million packages. We probably don't even need two thousand.
I don't think so. There are many tools, frameworks and libraries in JS and I love that. I learn from all of them and this is exciting. I don't want an ecosystem with only JQuery to do all I want. Sometimes I may use Vue.js, sometimes Angular or React... and that's great.
This is a really great resource. All of theses tips are implemented in Nest.js framework. I can't recommend enough to give it a try, it'll force you yo have best practices.
With plaintext you can do what you need. For example, with todo.txt context are just prefixed by `@`. You can also add special tag with `key:value`. So for example you can add `location:paris` and retrieve it with whatever search tool.
I was so sad that this project is not open-source but their Research papers give some interesting clues about detecting bad quality files.
On my side, I used it through a [Bash script](https://gist.github.com/madeindjs/d5e3949313b141f2e5eea62b98...) to detect bad files in my library. The tool produces a lot of false positives since it triggered on some High Res audio musics I bought on Qobuz.