Advertisement
Guest User

Untitled

a guest
May 14th, 2014
365
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 10.18 KB | None | 0 0
  1. If you intend to make secure rips using linux or UNIX, please use morituri instead of rubyripper.
  2.  
  3. It is often recommended that Linux users try to get EAC working with Wine. However, this doesn't always work.
  4.  
  5. When Wine and EAC don't want to cooperate, Rubyripper, with its test-and-copy layer on top of cdparanoia's oft-bemoaned correction, is the next best thing.
  6.  
  7. Installation (Linux)
  8. Method 1: install via your distro's package manager
  9. This is the most convenient way, but it won't always give you the most up-to-date version, even if Rubyripper is in your distro's repositories
  10.  
  11. Ubuntu / Debian-based distros: GetDeb.net Deb
  12. • GetDeb.net now offers the latest Deb installer of rubyripper for Ubuntu.
  13.  
  14. Method 2: install from the tarball
  15. 1. Download the tarball from http://code.google.com/p/rubyripper/downloads/list (0.5.5 is the current version at the time of writing)
  16. 2. untar it in ~/local (or the directory of your choice): tar -xjvf rubyripper-0.5.5.tar.bz2
  17. 3. Install the dependencies listed in the README. (if you're using this method because the distro-provided version is out of date, you can still use the package manager to install these)
  18. 3.1 Ubuntu-specific: Install the following packages: cdparanoia ruby-gnome2 libgettext-ruby1.8 ruby-full flac cd-discid eject vorbis-tools vorbisgain mp3gain.
  19. 4. Follow the installation instructions in the README file.
  20.  
  21. Method 3: run it from your home directory
  22. 1. Download the tarball from http://code.google.com/p/rubyripper/downloads/list (0.5.5 is the current version at the time of writing)
  23. 2. untar it in ~/local (or the directory of your choice): tar -xjvf rubyripper-0.5.5.tar.bz2
  24. 3. Install the dependencies listed in the README. (if you're using this method because the distro-provided version is out of date, you can still use the package manager to install these)
  25. 3.1 Ubuntu-specific: Install the following packages: cdparanoia ruby-gnome2 libgettext-ruby1.8 ruby-full flac cd-discid eject vorbis-tools vorbisgain mp3gain.
  26.  
  27. Installation (Mac)
  28. Check out resipsa's Rubyripper: OS X installation and usage tutorial. Then come back to this tutorial to complete the configuration. The commandline menu system will look different, but the options should be the same.
  29.  
  30. Alternatively, use XLD, an open source, native OSX GUI app with similar test-and-copy verification and more advanced secure ripping features.
  31.  
  32. Configuration
  33. Launch Rubyripper
  34.  
  35. Click the Preferences button in the upper left corner of the window
  36.  
  37. Secure Ripping
  38. http://i.minus.com/ibfzcAfKNO9Zpf.png
  39.  
  40. 1. Look up your CD drive's read offset in the AccurateRip database.
  41. (One way to identify your CD drive is to issue the command: lshw. Another way is: dmesg|grep CD-ROM).
  42. 2. Copy the read offset value into the Cdrom offset field
  43.  
  44. Recommended Ripping Options:
  45. • Match all chunks: 2 times
  46. • Match erroneous chunks: 3 times
  47. • Maximum trials: 20
  48.  
  49. You can probably leave the Ripping options at their defaults, however:
  50. • it doesn't hurt to bump the Match erroneous chunks value up to 3.
  51. • If you don't set the Maximum trials, a badly scratched CD could cause Rubyripper to keep trying for hours before randomly getting matches on bad chunks. (note: if this happens, please do not upload your rip)
  52.  
  53. Ripping related:
  54. • Pass cdparanoia options: -Z
  55. · This disables cdparanoia's built-in correction and leaves you relying entirely on Rubyripper's test-and-copy method. The speed benefit of this might be worth it, given cdparanoia's reputation of not having very secure correction on its own.
  56.  
  57. TOC Analysis
  58. https://i.minus.com/iou68LCvpwmhf.png
  59.  
  60. Codecs
  61. https://i.minus.com/ibi76ZPGJ5NdAF.png
  62.  
  63. FLAC
  64. • --best -V
  65. · This will produce the smallest files, but encoding may take a little longer (recommendation, equal to -8).
  66. • -5 -V
  67. · This is the default compression level, slightly larger than the highest compression, -8, but the encoding will go faster.
  68.  
  69. Vorbis
  70. (note: many/most Linux distributions ship the official xiph.org encoder. The tweaked and tuned aoTuV beta 5 encoder is recommended as superior by HydrogenAudio. If your distro doesn't ship this version, you may wish to check out the section on aoTuV Oggenc under Other codecs)
  71. • -q 8
  72. · 256kbps nominal bit rate. Again, actual ABR can vary greatly.
  73.  
  74.  
  75. Lame Mp3
  76. • -V2 --vbr-new
  77. · V2 is the lowest quality VBR preset allowed on the tracker.
  78. • -V0 --vbr-new
  79. · This is the highest quality VBR preset. Many people prefer this.
  80. • -b 320
  81. · This will give you the maximum possible constant bit rate of 320kbps. Many view this to be overly wasteful compared to V0 (which can hit 320kbps when it needs to) and not necessary, but some people appreciate that extra little bit.
  82.  
  83. Note: The switch --vbr-new, which enabled a superior VBR mode in LAME 3.97 and some previous versions, is no longer needed with LAME 3.98 as it is now the default VBR mode. However, if you're still using LAME 3.97 or older, you have to add --vbr-new to your commandline to use that mode.
  84.  
  85. Other
  86. This is where you would put settings for other codecs, such as updated versions of the above codecs that your distribution doesn't yet include.
  87.  
  88. Another option is to use it for a second LAME encoding. For example, to have Rubyripper rip to V0 and 320 in one run use the "Lame Mp3" option with -V0 --vbr-new and use the "Other" option with lame -b 320 -h --add-id3v2 --ignore-tag-errors --ta "%a" --tt "%t" --tg "%g" --tl "%b" --ty "%y" --tn "%n" %i %o.mp3.
  89.  
  90. FAAC
  91. <This section has yet to be written>
  92.  
  93. aoTuV Oggenc
  94. 1. If your distribution does not already ship a version of oggenc with Aoyumi's tunings, download it from http://artfwo.googlepages.com/oggenc-aotuvb5.bz2 and uncompress it somewhere where you can run it.
  95. 2. Disable the Create m3u playlist option in the Codec related section at the bottom of the window
  96. 3. Include the following line in the Other field of Rubyripper's codec settings: ~/local/bin/oggenc-aotuvb5 -q 7 -d %y -N %n -t "%t" -l "%b" -a "%a" -G "%g" -o "%o.ogg" %i
  97. 3.1. Replace ~/local/bin/ with the directory where you placed the executable
  98. 3.2. Replace -q 7 with your desired quality preset.
  99.  
  100. Normalization and Replay Gain
  101. ReplayGain and peak normalization are two ways of making music from different sources play back at the same volume without manual tweaking of the volume nob.
  102.  
  103. Normalization is a lossy process and doesn't change the perceived loudness very effectively. Do not normalize
  104.  
  105. Replay Gain, however, calculates the perceived loudness of a track or album and adds tags to the files so that supporting audio players (such as Foobar2000, Amarok with the replaygain script, and the Rockbox DAP firmware, among others) can be set to change the volume automatically upon playback or just ignore the tags altogether if the user so chooses.
  106.  
  107. ReplayGain has two modes, album/audiophile and track/radio. The former is preferred when listening to entire albums at once; the latter is good for listening to tracks out of context from their albums, such as with random playlists.
  108.  
  109. FLAC and Ogg Vorbis
  110. • Choose Use replaygain on audio files
  111. · Select Album / Audiophile modus
  112.  
  113. ReplayGain is perfectly acceptable for these formats and is in fact highly encouraged. Applying replay gain in Album/Audophile modus will cause both album and track gain to be written to the tags.
  114.  
  115. MP3
  116. You can still apply replay gain to mp3 rips, but there are some caveats that must be mentioned:
  117.  
  118. With the way Rubyripper invokes the mp3gain utility, it alters the actual audio data. This is a lossless process, since the scanner adds an APEv2 tag to the end of the file with information necessary to revert the change. Supporting players can still switch between album and track modes, and other players will play the altered audio with the mode chosen when the scan was done.
  119.  
  120. However, the original volume may be unobtainable in some players without first altering the audio again. Also, there is a risk of the APEv2 tags being corrupted or erased by poorly implemented or configured id3 taggers.
  121.  
  122. This leaves you with three options:
  123. • Do not apply ReplayGain to mp3 rips
  124. · Choose Don't standardize volume
  125. • Revert the changes made by the scanner, leaving only the tags, which can still be used by supporting players.
  126. · Choose Use replaygain on audio files
  127. · use the following command in a terminal window: mp3gain -u <rip directory>/*.mp3
  128. • Apply ReplayGain manually without passing the -a or -r switches
  129. · Choose Don't standardize volume
  130. · use the following command in a terminal window: mp3gain <rip directory>/*.mp3
  131.  
  132. Freedb
  133. The defaults should be sufficient here.
  134.  
  135. https://i.minus.com/i5GgCVrAbxrlL.png
  136.  
  137. However, if you would prefer to use Musicbrainz' FreeDB gateway (which often has better data but doesn't have quite so many albums in its database), change the Freedb server to the following:
  138. freedb.musicbrainz.org.
  139.  
  140. Other
  141. http://i.minus.com/ibm6flEFsRvQrq.png
  142.  
  143. Filenaming schemes must include, at the very least, Artist and Album in the directory name and Tracknumber and Trackname in the filename.
  144.  
  145. • Base directory: this can be wherever you want the resulting files to be.
  146. • The following are decent settings but can be tweaked so long as all the appropriate data remains.
  147. · Standard: %a - %b (%y)/%n - %t
  148. · Various artists: %a - %b (%y)/%n - %va - %t
  149.  
  150. Click the arrow by Show options for "Filenaming scheme" for a list of variables that can be used.
  151.  
  152.  
  153. The Programs of choice and Debug options are matters of personal preference and do not actually have any effect on the rip.
  154.  
  155. Troubleshooting
  156. Rubyripper freezes after ripping the first track (Rubyripper 0.5.3 or earlier)
  157. Set Preferences > Codecs > Number of extra encoding threads to 0.
  158.  
  159. Explanation: This is apparently a bug introduced with version 0.17 of the ruby gnome bindings. As a work-around, Rubyripper 0.5.4 no longer uses extra threads for encoding.
  160. Issue 221 on Rubyripper's code.google.com issue tracker
  161. This bug is fixed in Rubyripper 0.5.7 and later.
  162.  
  163. Rubyripper doesn't find the CD drive.
  164. Try the following in a terminal window:
  165.  
  166. $ ls -l /dev/cdrom*
  167.  
  168.  
  169. You should get output something like the following:
  170.  
  171. lrwxrwxrwx 1 root root 4 2008-10-08 16:56 /dev/cdrom -> scd0
  172.  
  173.  
  174. In Preferences > Secure Ripping > Cdrom device, replace "cdrom" with the device name shown after the arrow.
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement