cyanrip
sqltorrent
| cyanrip | sqltorrent | |
|---|---|---|
| 5 | 5 | |
| 206 | 269 | |
| - | 1.1% | |
| 8.0 | 0.0 | |
| 22 days ago | about 8 years ago | |
| C | C | |
| GNU Lesser General Public License v3.0 only | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
cyanrip
-
BTFS (BitTorrent Filesystem)
Pretty sure AccuRip is only a collections of checksums to validate your rips. http://cue.tools/wiki/CUETools_Database actually improved on it to provide that healing feature (via some kind of parity, I guess?).
Related, I use and recommend https://github.com/cyanreg/cyanrip on modern UNIXes.
- Whipper: Accurate Audio CD Ripping
- audio cd backup!
- cyanrip – fully featured CD ripping program able to take out most of the tedium
-
How to rip audio CDs 2022 – with drive accuracy listing
I’ve been using CyanRip and it’s been working nicely. Has excellent defaults Eg just run cyanrip from cli with a CD in and it rips to flac in the current dir with the most sensible/reasonable defaults (at least it’s opinions have worked for me).
https://github.com/cyanreg/cyanrip
sqltorrent
-
BTFS (BitTorrent Filesystem)
Or even better store data as an sqlite file that is full-text-search indexed. Then you can full-text search the torrent on demand: https://github.com/bittorrent/sqltorrent
- SQLite BitTorrent Vfs
-
How to circumvent Sci-Hub ISP block
"There was that project some guy posted a while back that used a combination of sqlite and partial downloads to enable searches on a database before it was downloaded all the way."
https://github.com/bittorrent/sqltorrent
- Hosting SQLite databases on GitHub Pages (or any static file hoster)
-
Distributed search engines using BitTorrent and SQLite
Interesting question. I looked at the source code to understand that.
SQLite knows where to look for when you open a SQLite database and you run a query, right? It just asks the underlying filesystem to provide N bytes starting from an offset using a C function, then it repeats the same operation on different portions of the file, it does its computation and everybody is happy.
The software relies on sqltorrent, which is a custom VFS for SQLite. That means that SQLite function to read data from a file stored in the filesystem is replaced by a custom function. Such custom code computes which Torrent block(s) should have the highest priority, by dividing the offset and the number of bytes that SQLite wants to read by the size of the torrent blocks. It is just a division.
See: https://github.com/bittorrent/sqltorrent/blob/master/sqltorr...
What are some alternatives?
whipper - Python CD-DA ripper preferring accuracy over speed
sql.js-httpvfs - Hosting read-only SQLite databases on static file hosters like Github Pages
beets - music library manager and MusicBrainz tagger
torrent-net - Distributed search engines using BitTorrent and SQLite
cmus - Small, fast and powerful console music player for Unix-like operating systems.
ipfs - Peer-to-peer hypermedia protocol
picard - A cross-platform music tagger powered by the MusicBrainz database. Picard organizes your music collection by updating your tags, renaming your files, and sorting them into a folder structure, exactly the way you want it.
datasette - An open source multi-tool for exploring and publishing data
ripit - Command line audio CD ripper [latest released version]
IPSQL - InterPlanetary SQL
vinylemulator - Emulate the tactile experience of a vinyl collection through your Sonos system, but with a back end run by Spotify
apsw - Another Python SQLite wrapper