Skip to main content

Notice

Please note that most of the software linked on this forum is likely to be safe to use. If you are unsure, feel free to ask in the relevant topics, or send a private message to an administrator or moderator. To help curb the problems of false positives, or in the event that you do find actual malware, you can contribute through the article linked here.
Topic: [OPEN SOURCE] cyanrip (release candidate 1) (Read 7779 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

[OPEN SOURCE] cyanrip (release candidate 1)

Release v1.0.0-rc1
Changelog
For those who don't know cyanrip project, it's a "Fully featured CD ripping program able to take out most of the tedium. Fully accurate, has advanced features most rippers don't, yet has no bloat and is cross-platform."
Features:
  • Automatic tag lookup from the MusicBrainz database
  • Encoded and muxed via FFmpeg (currently supports flac, opus, mp3, tta, wavpack, alac, vorbis and aac)
  • Drive offset compensation and error recovery via cd-paranoia
  • Full pregap handling
  • HDCD detection and decoding
  • CD Deemphasis (TOC + subcode)
  • Multi-disc album ripping
  • ReplayGain v2 tagging
  • Able to encode to multiple formats in parallel
  • Cover image embedding in mp3, flac, aac and opus
  • Automatic cover art image downloading
  • Provides and automatically verifies EAC CRC32, AccurateRip V1 and V2 checksums
  • Accurate ripping verification of partially damaged tracks
  • Automatic drive offset finding

Linux installation: https://github.com/cyanreg/cyanrip#installation
Automated Windows builds
Latest release Windows build
Latest Windows build

If the latest build is broken, you can find older ones in the nightly release page
Hybrid Multimedia Production Suite will be a platform-indipendent open source suite for advanced audio/video contents production.
Official git: https://forart.it/HyMPS/

Re: [OPEN SOURCE] cyanrip (release candidate 1)

Reply #1
Interesting, I'm a whipper user so I'll try this out.
WavPack 5.7.0 -b384hx6cmv / qaac64 2.80 -V 100

Re: [OPEN SOURCE] cyanrip (release candidate 1)

Reply #2
Looking forward to the v1.0.0 Stable release :)



 

Re: [OPEN SOURCE] cyanrip (release candidate 1)

Reply #5
hi @forart.eu
will be released a gui to use it?
thanks




Re: [OPEN SOURCE] cyanrip (release candidate 1)

Reply #9
New release out (the author regressed versioning to 0.9.x):

v0.9.2

Changelog:

  • ReplayGain 2.0 scanning and tagging
  • Preemphasis detection via both TOC and subchannel
  • Automatic deemphasis
  • CUE file writing
  • Repeat ripping mode for affirmation or badly damaged discs
  • Tagging improvements (setting the media_type tag)
  • Logfile reorganization and checksumming
  • Windows compatibility improvements
  • Migration to new FFmpeg 6.0 APIs

https://github.com/cyanreg/cyanrip/releases/
Hybrid Multimedia Production Suite will be a platform-indipendent open source suite for advanced audio/video contents production.
Official git: https://forart.it/HyMPS/

Re: [OPEN SOURCE] cyanrip (release candidate 1)

Reply #10
  • Accurate ripping verification of partially damaged tracks
I quickly browsed their github to get what this is supposed to mean, didn't find it ... anyone?
Sounds like the Accurate Rip that dBpoweramp offers.
"AccurateRip compares results with other peoples rips, a match is a 100% certainty it was without error, no other secure ripping method can get this close to verifying error free rips. Once a month AccurateRip will request to send your results to help populate the database."

Honestly, reading about cyanrip sounds like it's trying to copy most everything dBpoweramp does—but lesser in every way.
Processed audio in java and python.

Re: [OPEN SOURCE] cyanrip (release candidate 1)

Reply #11
Sounds like the Accurate Rip that dBpoweramp offers.
Well maybe it does sound like dBpoweramp's "partial match" feature?

Which from memory works like this: If a track has an AR entry, and upon ripping twice none match and are different, dBpoweramp can sometimes get a match by combining frames from rip#1 with frames from rip#2.