Crates.io | listenbrainz-cli-tools |
lib.rs | listenbrainz-cli-tools |
version | 0.2.1 |
source | src |
created_at | 2024-05-31 07:31:52.330536 |
updated_at | 2024-07-08 14:17:38.523835 |
description | A CLI app containing a set of useful tools for Listenbrainz |
homepage | |
repository | https://github.com/RustyNova016/listenbrainz-cli-tools |
max_upload_size | |
id | 1257744 |
size | 12,968,311 |
A collection of CLI based tools for Listenbrainz.
The latest build can be found in the release tab
git clone https://github.com/RustyNova016/listenbrainz-cli-tools.git
cd ./listenbrainz-cli-tools
cargo build --release
Full markdown help can be found under docs/CommandLineHelp.md, but full --help
support exists too.
Usage > Command Line documentation
This will list all your unmapped listens, grouped by similarity. It also gives a link to quickly look up the listen in listenbrainz, and go link it
(1) Paul's Dream (Dune) - Caster
-> https://listenbrainz.org/user/user/?min_ts=1709228551&max_ts=1709228553
(7) Raise Your Weapon - KLOUD
-> https://listenbrainz.org/user/user/?min_ts=1709824520&max_ts=1709824522
Total: 8 unlinked recordings
Note: Listens are grouped by "Messybrainz ID" (MSID). This is the way Listenbrainz recognize similar listens by attributing them the same MSID. Linking a listen will link the others as long as they have the same MSID.
This also means that the same recording can be shown twice in the list. For example: "Panic - Dion Timer" won't have the same MSID as "Panic by Dion Timmer", even if they are the same recording.
Usage > Command Line documentation
This tool allows for easy and faster mapping of recordings. It goes through each unmapped recordings, and give a few suggested recordings for the mapping. This is the exact same as mapping recording in the web UI.
Usage > Command Line documentation
While ListenBrainz have its own statistic page, it only refreshes daily, and is limited to only some entities. Furthermore, bugs in ListenBrainz statitics lead to misleading result.
This calculator aims to be most accurate possible, and will display your top listens for you.
A few radio algorithms have been made to generate playlists for you
Usage > Command Line documentation
This algorithm keep your playlist close to the artists you are listening to. The way it generate is as follow:
There is the option to only get unlistened recordings, making an alternative to ListenBrainz's own discovery playlists.
Usage > Command Line documentation
This radio will create a playlist containing all the tracks that you listen to, but seemingly no one else does.
The mix is made by calculating a score for each listen. This score is composed of two values:
The rank in the user's top 1000 recording of all time (First place get 100 points, second get 999.9, etc...)
The percentage of the recording's listens being from the user (Made with this formula: (user listens / worldwide listens) *100)
[!IMPORTANT]
As of the 2nd of july 2024, a bug in ListenBrainz made all global listen counts frozen. This radio will most likely be extremely inaccurrate by now. See the official status on LB-1590
Usage > Command Line documentation
This algorithm bases itself on your listen rate of recording to get more forgotten tracks. It takes the recordings with the lowest listen rates, and put them into a playlist
Usage > Command Line documentation
Similar to listen rates, this algorithm calculate the average time between listens, and estimate when the next listen will happen. It thens put together a playlist made out of recordings you should have listened by now.
Another mode is the "Overdue factor". Instead of sorting by date, the listens are sorted by how many estimated listens should have happened by now (Time elapsed since last listen / Average time per listens)
Usage > Command Line documentation
Similarly to Listenbrainz, a compatibility calculator is available, using a new algorithm that may provide more accurate results.
The score is calculated as follow:
As an exemple, let's have two users: UserA and UserB. They both only share one listened track in common, being "Exemple Track". UserA has 5 listens on "Exemple Track", and 28 total listens. UserB has 12 listens on "Exemple Track", and 45 total listens.
Since "Exemple Track" is the only shared track, this means that the final score is 17% compatibility
This project is in beta. There's a lot of features I'd like to add, and need a lot of testing before 1.0. If you find a bug, or have a feature request, feel free to create (and spam) a new issue.