This program will first get the metadata of various songs from metadata providers like musicbrainz, and then search for download links on pages like bandcamp. Then it will download the song and edit the metadata accordingly.
Go to file
2023-07-27 21:01:01 +02:00
.idea Merge branch 'youtube' into experimental 2023-06-21 08:23:16 +02:00
.vscode Added unit test cases 2023-03-12 17:07:22 +00:00
.VSCodeCounter started implementing sponsorblock 2023-06-14 12:38:36 +02:00
assets fixed logo 2023-02-23 12:17:41 +01:00
documentation updated documentation 2023-06-23 13:31:49 +02:00
src fixed crash 2023-07-27 21:01:01 +02:00
website added website 2022-11-30 09:03:14 +01:00
.gitignore updated gitignore 2023-04-17 13:26:32 +02:00
build.sh Added basic pyproject.toml and started on unit tests 2023-03-12 14:16:44 +00:00
contribute.md updated documentation 2023-06-23 13:35:53 +02:00
LICENSE Initial commit 2022-10-14 13:02:01 +02:00
notes.md fixed tests, they pass now 2023-03-24 10:30:40 +01:00
pyproject.toml Added basic pyproject.toml and started on unit tests 2023-03-12 14:16:44 +00:00
README.md updated documentation 2023-06-23 13:31:49 +02:00
requirements.txt updated dependencies 2023-06-29 14:26:21 +02:00
setup.py made obvious which files are used, and which aren't 2023-02-01 16:19:17 +01:00
test.db fixed mutable argument bug in the source dict of SourceAttribute 2023-01-31 13:18:52 +01:00
version ready for build 2022-11-29 12:14:48 +01:00

Music Kraken

music kraken logo

Installation

You can find and get this project from either PyPI as a Python-Package, or simply the source code from GitHub. Note that even though everything SHOULD work cross-platform, I have only tested it on Ubuntu. If you enjoy this project, feel free to give it a star on GitHub.

# Install it with
pip install music-kraken

# and simply run it like this:
music-kraken

Dependencies

You will need to install these two programms.

  • pandoc

Notes for WSL

If you choose to run it in WSL, make sure ~/.local/bin is added to your $PATH #2

Quick-Guide

The Genre you define at the start is the folder, my programm will download the files into, AS WELL as the value of the ID3 genre field.

When it drops you into the shell 2 main things are important:

  1. You search with s: <query/url>
  2. You choose an option with just the index number of the option
  3. You download with d: <options/url>, where the options are comma seperated
  4. You support me by making a pr, or starring my repo.

Trust me it WILL make sense, once you see it.

Query

The syntax for the query is like really simple.

> s: #a <any artist>
searches for the artist <any artist>

> s: #a <any artist> #r <any releas>
searches for the release (album) <any release> by the artist <any artist>

> s: #r <any release> Me #t <any track>
searches for the track <any track> from the release <any relaese>

For a more detailed guid of the downloading shell, see here.

LOVE YALL (except nazis ;-;)


CONTRIBUTE

I am happy about every pull request. To contribute look here.

Matrix Space

I decided against creating a discord server, due to piracy communities get often banned from discord. A good and free Alternative are Matrix Spaces. I reccomend the use of the Client Element. It is completely open source.

Click this link (https://matrix.to/#/#music-kraken:matrix.org) to join.

TODO till the next release

These Points will most likely be in the changelogs.

  • Update the Documentation of the new cli.
  • Migrate away from pandoc, to a more lightweight alternative, that can be installed over PiPY.
  • Update the Documentation of the internal structure. (could be pushed back one release)

Programming Interface / Use as Library

This application is 100\% centered around Data. Thus, the most important thing for working with musik kraken is, to understand how I structured the data.

Quick Overview

---
title: Quick Overview (outdated)
---
sequenceDiagram

participant pg as Page (eg. YouTube, MB, Musify, ...)
participant obj as DataObjects (eg. Song, Artist, ...)
participant db as DataBase

obj ->> db: write
db ->> obj: read

pg -> obj: find a source for any page, for object.
obj -> pg: add more detailed data from according page.
obj -> pg: if available download audio to target.

Data Model

The Data Structure, that the whole programm is built on looks as follows:

---
title: Music Data
---
erDiagram



Target {

}

Lyrics {

}

Song {

}

Album {

}

Artist {

}

Label {

}

Source {

}

Source }o--|| Song : ""
Source }o--|| Lyrics : ""
Source }o--|| Album : ""
Source }o--|| Artist : ""
Source }o--|| Label : ""

Song }o--o{ Album : AlbumSong
Album }o--o{ Artist : ArtistAlbum
Song }o--o{ Artist : "ArtistSong (features)"

Label }o--o{ Album : LabelAlbum
Label }o--o{ Artist : LabelSong

Song ||--o{ Lyrics : ""
Song ||--o{ Target : ""

Ok now this WILL look intimidating, thus I break it down quickly.
That is also the reason I didn't add all Attributes here.

The most important Entities are:

  • Song
  • Album
  • Artist
  • Label

All of them (and Lyrics) can have multiple Sources, and every Source can only Point to one of those Element.

The Target Entity represents the location on the hard drive a Song has. One Song can have multiple download Locations.

The Lyrics Entity simply represents the Lyrics of each Song. One Song can have multiple Lyrics, e.g. Translations.

Here is the simplified Diagramm without only the main Entities.

---
title: simplified Music Data
---
erDiagram

Song {

}

Album {

}

Artist {

}

Label {

}

Song }o--o{ Album : AlbumSong
Album }o--o{ Artist : ArtistAlbum
Song }o--o{ Artist : "ArtistSong (features)"

Label }o--o{ Album : LabelAlbum
Label }o--o{ Artist : LabelSong

Looks way more manageable, doesn't it?

The reason every relation here is a n:m (many to many) relation is not, that it makes sense in the aspekt of modeling reality, but to be able to put data from many Sources in the same Data Model.
Every Service models Data a bit different, and projecting a one-to-many relationship to a many to many relationship without data loss is easy. The other way around it is basically impossible

Data Objects

Not 100% accurate yet and might change slightly

Creation

# needs to be added

If you just want to start implementing, then just use the code example I provided, I don't care.
For those who don't want any bugs and use it as intended (which is recommended, cuz I am only one person so there are defs bugs) continue reading, and read the whole documentation, which may exist in the future xD