Hydrogenaudio Knowledgebase - User contributions [en]

Rubyripper

2021-11-13T18:46:36Z

Pohli: /* External links */ Category Software added

{{Infobox Software
| name = Rubyripper
| logo =
| screenshot = [[File:Rubyripper-screenshot.png|100px]]
| caption = Screenshot of legacy version 0.2
| maintainer = Bouke Woudstra
| stable_release = 0.6.0
| preview_release = 0.6.2
| operating_system = GNU/Linux, Mac OS/X (CLI)
| use = Digital Audio Extraction
| license = GPL
| website = [https://github.com/bleskodev/rubyripper github.com/bleskodev/rubyripper]
}}

'''Rubyripper''' is a secure digital audio extraction application ("cd ripper") for Unix-like operating systems.
It uses [[cdparanoia]] error correcting power and its own secure ripping algorithm to make sure that a CD rip is done successfully and accurately. It is very similar to and inspired by [[EAC]]. Rubyripper is written in the ruby programming language.

It's currently available for GNU/Linux, BSD should work but is untested. Mac OS/X is supported for the CLI version. For GNU/Linux systems it may be the most mature native secure ripping application available.
The source (same as executable) is published as Free Software under the terms of the GPL version 3.

== Features ==
* Sophisticated error correction mechanism
* Direct read offset support
* Detection of pregaps
* Detection of pre-emphasis
* Create disc images with [[cue sheet]]s
* Create m3u playlists
* A GTK2 user interface
* A command line interface (CLI)
* Metadata (CDDB-info) is fetched via the ''cd-discid'' module. Data can be edited after fetching
* The codecs supported are FLAC, Vorbis, MP3, WAV, and arbitrary command line encoders
* Multiple codecs can be used in one run
* Detailed logfile creation
* A detailed overview of hard-to-correct positions

=== Error correction mechanism ===
Rubyripper correction mechanism goes beyond that of [[cdparanoia]]. Every track gets ripped at least twice and is byte compared with the <code>Ruby cmp</code> feature. If any differences are found, each of the 1,000 bytes of the two files is compared. The next trial run looks to see if differing positions or a match can be found. ''(1,000 bytes is about 0.006 seconds)''. The main underlying Philosophy is that an erroneous read of an underlying ripper will produce random results. This seems so far to be correct. A possibility still exists that with random results the same result will be wrong.

In theory if the full 1,000 bytes are erroneous, then a false repair seems to be highly unlikely since there are <math>256^{1000} = 1.73 * 10^{2408}</math> combinations. (As a byte consists of 8 bits, <math>2^8 = 256</math>). The main principle however is, the more trials that are needed, the higher the chance of a false repair. Suppose only 3 bytes in a sample of 1,000 bytes give random information. This would still mean <math>256^3 = 16.7M</math> possibilities for these bytes; really 2 bits in each byte could be a problem. This reduces the possibilities to <math>2^{3*2} = 64</math>. A correct repair at this point may be possible. One has to wonder though: can 3 bytes actually be heard in a wav file that produces 180.000 bytes per second?

In conclusion: Rubyripper won't guarantee a consequent ''MD5 checksum hash'' on tracks that needed correction. However it will repair any files so that it's impossible to successfully blind-test with the original via an [[ABX]] test for example. The log file will optionally report any position that needed more than 3 trials, so you can check the position yourself.

== Installation ==
=== General Installation from Source ===
Make sure to have <code>cd-discid, ruby-libglade2, libglade2-ruby</code> and [[cdparanoia]] installed as a minimum. You can optionally choose for Lame, Vorbis or FLAC, and others via command-line configurations depending upon which codecs you want to encode with i.e Wavpack or Nero AAC (See the official Ubuntu forums for more information).

Then download Rubyripper:
http://code.google.com/p/rubyripper/downloads/list

See the README file for installation instructions or just type: <code>$sudo make install</code>

If Rubyripper doesn't start make sure the dependencies are ok. When launched from the terminal window Rubyripper should tell you which dependency it's missing.

=== Automatic Installation on Ubuntu/Debian ===
[http://www.getdeb.net/ GetDeb] has recent versions of Rubyripper packaged for Ubuntu systems. After teaching your system to use the GetDeb software repositories you can conveniently install using your favourite package manager frontend. Read their [http://www.getdeb.net/updates#how_to_install instructions] on how to easily install their package repositories.

You can alternatively use the Debian "Sid Marrilat" repositories.

* [http://linuxappfinder.com/package/rubyripper Rubyripper 32-bit and 64-bit] The latest releases for i386 and x86_64 architecturess.

=== Automatic Installation on Fedora/Red Hat ===
Starting with Fedora 20 Rubyripper, is no longer packaged with Fedora/Red Hat repositories due it no longer being updated. The easiest way to install it is to build it from the source above. This requires downloading the source code from the Rubyripper code archive on the Google Code website or the GitHub repository fork listed at the end of the wiki.

=== Older Manual Installation on Ubuntu/Debian ===
'''It is strongly recommended you use Ubuntu 10.04 (Lucid Lynx) or greater when compiling from the source! ''' 
'''These instructions were tested with Ubuntu 9.04 ("Jaunty Jackalope“), Gnome 2.26.1, and Rubyripper 0.5.7.'''

#Make sure Rubyripper has these dependencies as a bare mininum. They can be installed by typing in the terminal window: <code> $ sudo apt-get install cd-discid cdparanoia</code> as a bare mininum or <code> $ sudo apt-get install cd-discid cdparanoia flac lame mp3gain normalize-audio ruby-gnome2 ruby vorbisgain</code> to get the most out of the currently available distros. For internationalization: instead of the mentioned <code>ruby-gettext</code> install <code>gettext</code> and <code>libgettext-ruby1.8</code>.
#Download the Rubyripper archive (see above) from the official website.
#Extract the files in the Rubyripper archive (bzipped tarball) into a temporary directory.
#Navigate to the directory in which you extracted the Rubyripper archive (Most likely which will be your desktop) or the directory in which you extracted the archive in, e. g. by typing in terminal window: <code> $ cd /home/USERNAME/Desktop/rubyripper-0.x.x/</code>
#Rubyripper needs to know what features need to be installed. Install both the GUI and command-line version for to get the most out of the application by typing in the terminal window: <code> $ ./configure --enable-lang-all --enable-gtk2 --enable-cli</code> Note: This only prepares/configures installation.
#In order to install the application, type in the terminal window: <code> $ sudo make install</code>
#Rubyripper should now be installed with your applications under <code>Applications -> Sound & Video</code>
#If it runs according to your needs you may remove the temporary directory.

'''Notes:'''
* If you have CD-ROM drive problems it is recommended you read [http://ubuntuforums.org/showpost.php?p=5529611&postcount=16 this] thread
* You can add or drop dependencies as you see fit depending upon what packages you need or already have '''
* Substitute 'x' above with the latest version of Rubyripper'''
* You can run the command-line version of Rubyripper be navigating to the source directory and typing in <code>./rubyripper_cli.rb</code> into the terminal (This is useful if you want to use it conjunction with shell scripts like BASH and KSH to automate the ripping process for instance)'''

=== Setup ===
To point to the correct cdrom drive, you will need to specify both the Cdrom device & Cdrom offset.
* Cd rom device
** To print a list of installed drives:
<nowiki>$ cd-drive | grep Drive</nowiki>

*Cd rom offset
** Click the [http://accuraterip.com/driveoffsets.htm List with offsets] link to lookup the required Correction Offset
** To print a list of installed drives:
<nowiki>$ cd-drive | grep Model</nowiki>

'''Example'''

''Terminal:''

<nowiki>[user@name ~]$ cd-drive | grep Drive
Drivers available...
Drive: /dev/cdrom
Drive: /dev/sr1
[user@name ~]$ cd-drive | grep Model
Model : DVDRW LH-20A1L
Model : iHAS324 W </nowiki>
''Retrieved from the website 3/31/2014:''
{| style="text-align:left"
! CD Drive
! Correction Offset !! Submitted By !! Percentage Agree
|-
| LITE-ON - DVDRW LH-20A1L
| +6
| 706
| 100%
|-
| ATAPI - iHAS324 W
| +48
| 19
| 100%
|}

''Option 1:''

<tt>

Cdrom device: /dev/cdrom

Cdrom offset: 6

</tt>

''Option 2:''

<tt>

Cdrom device: /dev/sr1

Cdrom offset: 48

</tt>

== Known bugs & new features ==
Add an issue in the bugtracker to discuss any new feature requests:
* [http://code.google.com/p/rubyripper/issues/list Known bugs and new features]

== Development API ==
This section will give some technical information, which should be useful for interested developers. It will outline how the code is structured and what the API of Rubyripper codebase is for adding new user interfaces. Since version 0.2 it is quite simple to add new frontends to the current codebase. Currently there are CLI and GTK2 frontends. A Qt frontend or a Cocoa Mac OS frontend, should not be terribly difficult to implement. The developer won't implement this himself though, due to the fact that he is more interested in fine tuning the Rubyripper logic codebase.

== Becoming a Rubyripper developer ==
To become a developer you should have:
* Some basic knowledge of the Ruby programming language. Read for instance the [http://www.ruby-doc.org/docs/ProgrammingRuby/ free online book], at least until the chapter "Until Trouble Strikes". This is a somewhat dated version, but still perfectly usable. The lead developer doesn't use any new features, therefore it should be fine.
* Some basic knowledge of a GUI-toolkit in case you want to add a new frontend.

SVN Checkout now possible. 
Use: <code>$svn checkout http://rubyripper.googlecode.com/svn/trunk/ rubyripper </code> to get the latest source code.

If you're interested in becoming a developer, please contact him at ''rubyripperdev@nospam@gmail.com''. You can leave out the @nospam part.

== Data files and class structures ==
The 0.5 release has three ruby files and one glade file included:
* <code>rr_lib.rb.</code> This contains the Rubyripper codebase. It consists of five classes:
** <code>Gui_Support.</code> This class handles all feedback communication with the user interface and is used a lot by the other classes (except Cddb). This is were log file is generated and the error analysis takes place.
** <code>Cddb.</code> This class handles the freedb fetching. It uses the Freedb class (dependent on ruby-freedb) to get info about the disc. The server contact is handled in the Cddb class itself. Some problems of the Freedb class made it impossible to rely on it. The biggest problem with using Freedb class is that, it's using an old contact protocol and never gives away any information on the current year. This is the main reason why the Cddb class handles all server contact.
** <code>Secure_rip.</code> As might be expected, all error correction logic is put in here.
** <code>Encode. </code> As might be expected, this handles the encoding of the different formats supported.
** <code>Rubyripper.</code> Handles the usage of the different classes. It also performs some logical checks before starting at all.
* <code>rubyripper_cli.rb.</code> It has one class that contains the code for the command line interface frontend.
* <code>rubyripper_gtk.rb.M</code> It has one class that contains the code for the GTK2 user interface frontend.
* <code>rubyripper.glade.</code> This is a help file for the GTK interface. It's made with Glade, a program for designing user interfaces for GTK2.

== Adding a new frontend ==
New frontends are encouraged and aren't difficult to make, once you know your GUI toolkit. Take for instance, the current GTK2 frontend, which consists of only 350 lines of code ''(+ the glade file, but this code is automatically created)'''. From a starting point it would be best to use the current GTK2 or CLI code and just plainly rewrite it for the other toolkit. The basic ideas should be more or less the same.

The basic idea is that the GUI first presents the info of a Cddb instance. When the user wants to start, a new Rubyripper instance is started with all the settings in a Hash as a parameter. You can copy most of the code from the other user interfaces. The user interface should also have an update function. The update function is used as a communication channel for the Rubyripper instance.

# Using a new thread for launching instances is an effective way of getting a responsive GUI.

== External links ==
* [https://github.com/bleskodev/rubyripper Rubyripper] The next best repository since Google Code closed down.
* [http://www.hydrogenaudio.org/forums/index.php?showtopic=38418 Hydrogenaudio forum thread] the first public release of Rubyripper.
* [https://plus.google.com/communities/103961841006414793555 Google Plus] Google Plus community group for questions related to older releases of Rubyripper.
* [http://ubuntuforums.org/showthread.php?t=799621 Ubuntu Forums] a thread that's consistently updated for installing Rubyripper in Ubuntu including troubleshooting.

[[Category:CD Rippers]]
[[Category:Software]]

EAC and Lame

2006-12-17T12:24:32Z

Pohli: /* Configuration */ Config added

===Software Needed===
* [http://exactaudiocopy.org/eac6.html Exact Audio Copy]
* [http://wiki.hydrogenaudio.org/index.php?title=Recommended_LAME Recommended LAME version]

===Installation===
'''Note:''' This guide assumes that EAC has been configured for secure ripping, if not please follow [[EAC_Drive_Configuration | this]] guide.
* Unzip the chosen LAME version into the same directory as EAC.
* If you would like to tag with APEv2 tags please download [http://www.saunalahti.fi/cse/files/wapet.zip wapet.zip] and unzip it into the '''same folder'''.

===Configuration===

* Open EAC and insert a CD into the drive.
* Click the '''EAC''' menu and select '''Compression Options'''.
* Click the '''External Compression''' Tab, and put a check box in '''Use external program for compression'''.
* Change '''Parameter passing scheme''' to '''User Defined Encoder'''.
* Change '''Use file extension''' to '''.mp3'''.
* Click the '''Browse''' button and locate the '''lame.exe''' that you unzipped into the EAC directory earlier.
'''Note:''' If you want to tag with APEv2 tags using Wapet please locate '''wapet.exe''', not lame.exe.
* Remove the ticks from '''Use CRC check''', '''Add ID3 tag''' and '''Check for external programs return code'''.
* Don't worry which bit rate is shown in the '''Bit rate''' drop down box, as this will not have any effect on the resultant MP3 file (See Note 4 at the bottom of this page).

* In the '''Addtional command line options''' box, copy and paste one of the strings below, based on the tag format you prefer.

'''No Tags:'''

'''-V 2 --vbr-new''' '''%s %d'''

'''ID3v1:'''

'''-V 2 --vbr-new''' --id3v1-only --ta "%a" --tt "%t" --tg "%m" --tl "%g" --ty "%y" --tn "%n" '''%s %d'''

'''ID3v2:'''

'''-V 2 --vbr-new''' --id3v2-only --pad-id3v2 --ta "%a" --tt "%t" --tg "%m" --tl "%g" --ty "%y" --tn "%n" '''%s %d'''

'''ID3v1 and ID3v2:'''

'''-V 2 --vbr-new''' --add-id3v2 --pad-id3v2 --ta "%a" --tt "%t" --tg "%m" --tl "%g" --ty "%y" --tn "%n" '''%s %d'''

'''Automatic:'''

'''-V 2 --vbr-new''' --ta "%a" --tt "%t" --tg "%m" --tl "%g" --ty "%y" --tn "%n" '''%s %d'''
''Automatic'' means that by default only ID3v1 will be created. In case the length of at least one of the entries exceeds the permitted length of ID3v1, ID3v2 will be created in addition.

'''APEv2: (This requires [http://www.saunalahti.fi/cse/files/wapet.zip wapet.exe]. Remember to browse for wapet.exe instead of lame.exe as the external encoding program.)'''

'''%d''' -t "Artist=%a" -t "Title=%t" -t "Album=%g" -t "Year=%y" -t "Track=%n" -t "Genre=%m" LAME.exe '''-V 2 --vbr-new''' '''%s %d'''

'''Note 1:''' lame.exe needs to be in the same directory as wapet.exe.

'''Note 2:''' If you wanted to change the [[LAME#Encoder_Presets| LAME preset]], the green text denotes the part that needs to be altered.

'''Note 3:''' The '''%s''' and '''%d''' at the end of each string are placeholders for EAC. '''%s''' means '''source''' filename and '''%d''' means '''destination''' filename.

'''Note 4:''' The '''%l...%l''' and '''%h...%h''' placeholders are used to add text according to whether the High quality or Low quality radio button is selected, as shown below:

'''%l--preset 128%l%h--preset standard%h''' '''%s %d'''

Therefore, if you select '''Low quality''', EAC will invoke the LAME encoder with the following command line parameters:

LAME.exe --preset 128 '''%s %d'''

..and if you select '''High quality''' EAC will invoke LAME with these command line parameters:

LAME.exe --preset standard '''%s %d'''

You can access the bitrate value in the dropdown list using the '''%r''' placeholder, For Example:

--preset %r '''%s %d'''

So, if you selected '''192 kBit/s''' in the '''Bit Rate''' drop-down list, the command line would be:

LAME.exe --preset 192 '''%s %d'''

It is a generally accepted fact that the bitrate selected in the drop-down list doesn't affect the command line. In essence this is true, as it will not affect the command line ''unless you use the %r placeholder''. However, using ABR or CBR over VBR is not recommended, and therefore you should never have to use the '''%r''' option.

<center>[[Image:EAC_LAME02.png|frame|center|LAME configured with ID3v1 tagging]]</center>

[[Category:Guides]]
[[Category:EAC Guides|LAME & EAC]]

Talk:LAME

2006-09-27T18:22:41Z

Pohli: /* LAME compiles Win32 */

{{talkheader}}

==Page discussion==
I propose a major merging with this page. I don't think information about lame should be scattered all over the wiki. I'll think about it this evening and after the merge I'll add a redirect from all Lame related pages to this one.--[[User:Beto|Beto]] 15:51, 13 September 2006 (CDT)

Finally I ended the revision :)--[[User:Beto|Beto]] 19:14, 14 September 2006 (CDT)

== LAME compiles Win32 ==

http://rarewares.org/dancer/dancer.php?f=1 is linked at this Wiki page. But at http://rarewares.org/mp3.html I can only find http://rarewares.org/dancer/dancer.php?f=107 The two archives contain different lame.exe and lame_enc.dll. Why is that? Here's another compile: http://mitiok.maresweb.org/ This is confusing! --[[User:Pohli|Pohli]] 13:16, 27 September 2006 (CDT)

Talk:LAME

2006-09-27T18:16:07Z

Pohli: LAME compiles Win32

{{talkheader}}

==Page discussion==
I propose a major merging with this page. I don't think information about lame should be scattered all over the wiki. I'll think about it this evening and after the merge I'll add a redirect from all Lame related pages to this one.--[[User:Beto|Beto]] 15:51, 13 September 2006 (CDT)

Finally I ended the revision :)--[[User:Beto|Beto]] 19:14, 14 September 2006 (CDT)

== LAME compiles Win32 ==

http://rarewares.org/dancer/dancer.php?f=1 is linked at this Wiki page. But at http://rarewares.org/mp3.html I can only find http://rarewares.org/dancer/dancer.php?f=107 The two archives contain different lame.exe and lame_enc.dll. Why is that? --[[User:Pohli|Pohli]] 13:16, 27 September 2006 (CDT)

Talk:Recommended LAME

2006-07-30T08:42:24Z

Pohli:

This article is redundant information. It seems to be only a copy of [[LAME#Recommended Encoder Settings|LAME]]. Why is that? --Pohli 11:54, 29 July 2006 (CDT)
:Thank the fools that don't bother to search the wiki before writing guides ;-D. I made an attempt to fix it on the main page so that it just pointed to LAME page. I know it would make sense though to have a recommended lame page and keep everything on there? I usually don't use LAME to much so I leave it up to them. --[[HotshotGG]] 1:33, 29 July 2006 (CDT)
::I don't think we need a whole extra "Recommended LAME" page if there's no new information. An advice on the ordinary LAME page should be enough and we have the [[Lame Compiles]] page, too. --Pohli 03:42, 30 July 2006 (CDT)

Recommended LAME

2006-07-29T17:13:06Z

Pohli: /* Introduction */ link "Lame Compiles" adapted

==Introduction==

This article describes the [[Hydrogenaudio]] recommended settings to be used with [[LAME]] for highest quality [[MP3]] encoding.

These settings require LAME 3.94 or later. LAME 3.97beta2 is the recommended version ([[Lame Compiles|click here to download]]).

Avoid using alpha (a) versions of LAME. More often than not those are exclusively for testing purposes. Use them only if you want to help developers with feedback.

Note: The rule of thumb when considering encoding options: at a given bitrate, VBR is higher quality than ABR, which is higher quality than CBR (VBR > ABR > CBR in terms of quality). The exception to this is when you choose the highest possible CBR bitrate, which is 320 kbps (-b 320 = --alt-preset insane), but this produces very large filesizes for very little audible benefit.

''Note: all modes and settings mentioned in this topic belong to the specifications of the MP3 standard, and the resulting MP3s should be playable by every MP3 decoder that conforms with the standard. If your decoder or device does not play MP3s produced by LAME, blame the manufacturer or developer, and not LAME.''

==VBR (Variable bitrate) settings==
'''[[VBR]]:''' ''variable bitrate mode. Use variable bitrate modes when the goal is to achieve a fixed level of quality using the lowest possible bitrate.''

[[VBR]] is best used to target a specific quality level, instead of a specific bitrate. The final file size of a VBR encode is less predictable than with [[ABR]], but the quality is usually better.

-V(number) where number is 0-9, 0 being highest quality, 9 being the lowest.

{| align=center border="1" cellpadding="4" cellspacing="0"
|+'''List of recommended settings'''
| '''Switch''' || '''Preset''' || '''Target Kbit/s''' || '''Bitrate range kbit/s'''
|-
| -b 320 || --preset insane || 320 || 320 CBR
|-
| -V 0 --vbr-new || --preset fast extreme || 245 || 220...260
|-
| -V 0 || --preset extreme || 245 || 220...260
|-
| -V 1 --vbr-new || || 225 || 200...250
|-
| -V 1 || || 225 || 200...250
|-
| -V 2 --vbr-new || --preset fast standard || 190 || 170...210
|-
| -V 2 || --preset standard || 190 || 170...210
|-
| -V 3 --vbr-new || || 175 || 155...195
|-
| -V 3 || || 175 || 155...195
|-
| -V 4 --vbr-new || --preset fast medium || 165 || 145...185
|-
| -V 4 || --preset medium || 165 || 145...185
|-
| -V 5 --vbr-new || || 130 || 110...150
|-
| -V 5 || || 130 || 110...150
|-
| -V 6 --vbr-new || || 115 || 95...135
|-
| -V 6 || || 115 || 95...135
|-
| -V 7 --vbr-new || || 100 || 80...120
|-
| -V 7 || || 100 || 80...120
|-
| -V 8 --vbr-new || || 85 || 65...105
|-
| -V 8 || || 85 || 65...105
|-
| -V 9 --vbr-new || || 65 || 45...85
|-
| -V 9 || || 65 || 45...85
|}
See also [[Technical data for recommended LAME settings]]

If you need a predictable bitrate (in a streaming application, for example), use ABR or CBR modes, described below.

==ABR (average bitrate) settings==
'''[[ABR]]:''' ''average bitrate mode. A compromise between VBR and CBR modes, ABR encoding varies bits around a specified target bitrate. Use ABR when you need to know the final size of the file but still want to allow the encoder some flexibility to decide which passages need more bits.''

''(128 kbit/s ABR: roughly the same filesize as 128 kbit/s CBR)''

* '''[[ABR]] Setting tuned from 320 kbit/s down to 80 kbit/s'''
** --preset <bitrate>

<bitrate> (desired averaged bitrate in kbit/s) can be any value between 8 - 320 , like eg. 9, 17, 80, 128, 133, 200 etc.

:: Example: --preset 200

==CBR (constant bitrate) settings==
'''[[CBR]]:''' ''constant bitrate mode. CBR encoding is not efficient. Whereas VBR and ABR modes can supply more bits to complex music passages and save bits on simpler ones, CBR encodes every frame at the same bitrate. CBR is only recommended for usage in streaming situations where the upper bitrate must be strictly enforced.''

*'''[[CBR]] Setting tuned from 320 kbit/s down to 80 kbit/s'''
** -b <bitrate>

<bitrate> (bitrate in kbit/s) must be chosen from the following values: 8, 16, 24, 32, 40, 48, 64, 80, 96, 112, 128, 160, 192, 224, 256, or 320.

==Remarks==
The ""--vbr-new"" switch enables the new VBR mode. Lame will encode much faster than the old/default VBR mode. In terms of quality, --vbr-new appears to be better than the old model, but reports of artifacts when using the new model do exist. Despite these possible issues, --vbr-new is currently recommended over the default VBR mode due to both the speed and quality increases afforded by the new algorithm.

===Quick Start===

'''Best Quality : 'archiving''''

-b 320. This is the strongest setting for MP3, with the lowest risk of [[artifact]]s.
With the exception of a few situations, quality is rarely better than the highest [[VBR]] profiles described below. However, 'archiving' music using a lossy format like MP3 is never recommended – no matter how transparent the resulting files might be.
Alternative: [[Lossless]] formats like [[WavPack]], [[FLAC]] etc. allow true archiving bit for bit like on original CD.

'''High Quality : HiFi, home or quiet listening'''

-V3 --vbr-new (~175 kbps), -V2 --vbr-new (~190 kbps), -V1 --vbr-new (~210 kbps) or -V0 --vbr-new (~230 kbps) are recommended.
These settings will produce [[transparent]] encoding (transparent = most people cannot distinguish the mp3 from the original in an ABX blind test).
Audible differences between these presets exist, but are extremely marginal.

'''Portable : background noise and low bitrate requirement, small sizes'''

-V6 --vbr-new (~115 kbps), -V5 --vbr-new (~130 kbps) or -V4 --vbr-new (~160 kbps) are recommended for this use.
-V6 --vbr-new produces an acceptable quality, while -V4--vbr-new should be close to perceptual [[transparency]].

'''Very low bitrate, small sizes:''' eg. for voice, radio, [[mono]] encoding etc.

For very low bitrates, up to 100kbps, [[ABR]] is most often the best solution.

Use '''--abr xx''' (e.g. --abr 80).

[[Image:lame-chart-2.png|frame|center|Here a trial to get a view, how the perceived listening quality improves with settings/averaged filesize]]

'''Hey! What happened to "--alt-preset"?'''

The revolutionary --alt-preset system was introduced in LAME 3.90; it was replaced by the --preset flags in later versions. Starting with version 3.94, the -V x quality system was introduced, which allows finer control over the desired bitrate; the --preset switches were made into aliases to the corresponding -V flags for the sake of backwards compatibility. '''There is no difference between the output you get if you use "-V2" or "--alt-preset standard".''' (Although adding "--vbr-new" is recommended for now, see above for details.)

More encoding options are available under the new system, such as -V1, which provides a level of quality between the old "standard" and "extreme" presets, or -V3, which is between the old "medium" and "standard".

LAME 3.97 features more streamlined command line options, and it's recommended to stick to one of the values described in the text or shown in the tables above. You don't need to worry anymore about quality, settings, arcane combinations of switches, or presets.

For example, the following command lines will all produce the same output:

--alt-preset insane = --preset insane = -b 320 = --preset 320 = --preset cbr 320

(--preset cbr 320 is the exact same thing as --alt-preset insane, etc.)

==Setting up EAC for LAME.exe with tagging==

{{:EAC and Lame}}

==Additional reading==

* [[LAME|More information on LAME]]
* [http://www.hydrogenaudio.org/forums/index.php?act=ST&f=16&t=32288 Forum discussion of the recommended settings]
* [http://www.hydrogenaudio.org/forums/index.php?act=ST&f=15&t=203 Forum discussion of the recommended settings (older)]
* [[Recommended LAME credits|Credits for the recommended settings]]
* [http://www.hydrogenaudio.org/forums/index.php?showtopic=32288&view=findpost&p=327262 Previous recommendations (outdated)]
* [[MP3]]
* [[Exact_Audio_Copy|Exact Audio Copy]]

----
[[Recommended LAME credits|Credits]]

Talk:Recommended LAME

2006-07-29T16:54:07Z

Pohli:

This article is redundant information. It seems to be only a copy of [[LAME#Recommended Encoder Settings|LAME]]. Why is that? --Pohli 11:54, 29 July 2006 (CDT)

Recommended LAME

2006-07-29T16:50:07Z

Pohli: /* Additional reading */ repeated link removed

==Introduction==

This article describes the [[Hydrogenaudio]] recommended settings to be used with [[LAME]] for highest quality [[MP3]] encoding.

These settings require LAME 3.94 or later. LAME 3.97beta2 is the recommended version ([[LAME Compiles|click here to download]]).

Avoid using alpha (a) versions of LAME. More often than not those are exclusively for testing purposes. Use them only if you want to help developers with feedback.

Note: The rule of thumb when considering encoding options: at a given bitrate, VBR is higher quality than ABR, which is higher quality than CBR (VBR > ABR > CBR in terms of quality). The exception to this is when you choose the highest possible CBR bitrate, which is 320 kbps (-b 320 = --alt-preset insane), but this produces very large filesizes for very little audible benefit.

''Note: all modes and settings mentioned in this topic belong to the specifications of the MP3 standard, and the resulting MP3s should be playable by every MP3 decoder that conforms with the standard. If your decoder or device does not play MP3s produced by LAME, blame the manufacturer or developer, and not LAME.''

==VBR (Variable bitrate) settings==
'''[[VBR]]:''' ''variable bitrate mode. Use variable bitrate modes when the goal is to achieve a fixed level of quality using the lowest possible bitrate.''

[[VBR]] is best used to target a specific quality level, instead of a specific bitrate. The final file size of a VBR encode is less predictable than with [[ABR]], but the quality is usually better.

-V(number) where number is 0-9, 0 being highest quality, 9 being the lowest.

{| align=center border="1" cellpadding="4" cellspacing="0"
|+'''List of recommended settings'''
| '''Switch''' || '''Preset''' || '''Target Kbit/s''' || '''Bitrate range kbit/s'''
|-
| -b 320 || --preset insane || 320 || 320 CBR
|-
| -V 0 --vbr-new || --preset fast extreme || 245 || 220...260
|-
| -V 0 || --preset extreme || 245 || 220...260
|-
| -V 1 --vbr-new || || 225 || 200...250
|-
| -V 1 || || 225 || 200...250
|-
| -V 2 --vbr-new || --preset fast standard || 190 || 170...210
|-
| -V 2 || --preset standard || 190 || 170...210
|-
| -V 3 --vbr-new || || 175 || 155...195
|-
| -V 3 || || 175 || 155...195
|-
| -V 4 --vbr-new || --preset fast medium || 165 || 145...185
|-
| -V 4 || --preset medium || 165 || 145...185
|-
| -V 5 --vbr-new || || 130 || 110...150
|-
| -V 5 || || 130 || 110...150
|-
| -V 6 --vbr-new || || 115 || 95...135
|-
| -V 6 || || 115 || 95...135
|-
| -V 7 --vbr-new || || 100 || 80...120
|-
| -V 7 || || 100 || 80...120
|-
| -V 8 --vbr-new || || 85 || 65...105
|-
| -V 8 || || 85 || 65...105
|-
| -V 9 --vbr-new || || 65 || 45...85
|-
| -V 9 || || 65 || 45...85
|}
See also [[Technical data for recommended LAME settings]]

If you need a predictable bitrate (in a streaming application, for example), use ABR or CBR modes, described below.

==ABR (average bitrate) settings==
'''[[ABR]]:''' ''average bitrate mode. A compromise between VBR and CBR modes, ABR encoding varies bits around a specified target bitrate. Use ABR when you need to know the final size of the file but still want to allow the encoder some flexibility to decide which passages need more bits.''

''(128 kbit/s ABR: roughly the same filesize as 128 kbit/s CBR)''

* '''[[ABR]] Setting tuned from 320 kbit/s down to 80 kbit/s'''
** --preset <bitrate>

<bitrate> (desired averaged bitrate in kbit/s) can be any value between 8 - 320 , like eg. 9, 17, 80, 128, 133, 200 etc.

:: Example: --preset 200

==CBR (constant bitrate) settings==
'''[[CBR]]:''' ''constant bitrate mode. CBR encoding is not efficient. Whereas VBR and ABR modes can supply more bits to complex music passages and save bits on simpler ones, CBR encodes every frame at the same bitrate. CBR is only recommended for usage in streaming situations where the upper bitrate must be strictly enforced.''

*'''[[CBR]] Setting tuned from 320 kbit/s down to 80 kbit/s'''
** -b <bitrate>

<bitrate> (bitrate in kbit/s) must be chosen from the following values: 8, 16, 24, 32, 40, 48, 64, 80, 96, 112, 128, 160, 192, 224, 256, or 320.

==Remarks==
The ""--vbr-new"" switch enables the new VBR mode. Lame will encode much faster than the old/default VBR mode. In terms of quality, --vbr-new appears to be better than the old model, but reports of artifacts when using the new model do exist. Despite these possible issues, --vbr-new is currently recommended over the default VBR mode due to both the speed and quality increases afforded by the new algorithm.

===Quick Start===

'''Best Quality : 'archiving''''

-b 320. This is the strongest setting for MP3, with the lowest risk of [[artifact]]s.
With the exception of a few situations, quality is rarely better than the highest [[VBR]] profiles described below. However, 'archiving' music using a lossy format like MP3 is never recommended – no matter how transparent the resulting files might be.
Alternative: [[Lossless]] formats like [[WavPack]], [[FLAC]] etc. allow true archiving bit for bit like on original CD.

'''High Quality : HiFi, home or quiet listening'''

-V3 --vbr-new (~175 kbps), -V2 --vbr-new (~190 kbps), -V1 --vbr-new (~210 kbps) or -V0 --vbr-new (~230 kbps) are recommended.
These settings will produce [[transparent]] encoding (transparent = most people cannot distinguish the mp3 from the original in an ABX blind test).
Audible differences between these presets exist, but are extremely marginal.

'''Portable : background noise and low bitrate requirement, small sizes'''

-V6 --vbr-new (~115 kbps), -V5 --vbr-new (~130 kbps) or -V4 --vbr-new (~160 kbps) are recommended for this use.
-V6 --vbr-new produces an acceptable quality, while -V4--vbr-new should be close to perceptual [[transparency]].

'''Very low bitrate, small sizes:''' eg. for voice, radio, [[mono]] encoding etc.

For very low bitrates, up to 100kbps, [[ABR]] is most often the best solution.

Use '''--abr xx''' (e.g. --abr 80).

[[Image:lame-chart-2.png|frame|center|Here a trial to get a view, how the perceived listening quality improves with settings/averaged filesize]]

'''Hey! What happened to "--alt-preset"?'''

The revolutionary --alt-preset system was introduced in LAME 3.90; it was replaced by the --preset flags in later versions. Starting with version 3.94, the -V x quality system was introduced, which allows finer control over the desired bitrate; the --preset switches were made into aliases to the corresponding -V flags for the sake of backwards compatibility. '''There is no difference between the output you get if you use "-V2" or "--alt-preset standard".''' (Although adding "--vbr-new" is recommended for now, see above for details.)

More encoding options are available under the new system, such as -V1, which provides a level of quality between the old "standard" and "extreme" presets, or -V3, which is between the old "medium" and "standard".

LAME 3.97 features more streamlined command line options, and it's recommended to stick to one of the values described in the text or shown in the tables above. You don't need to worry anymore about quality, settings, arcane combinations of switches, or presets.

For example, the following command lines will all produce the same output:

--alt-preset insane = --preset insane = -b 320 = --preset 320 = --preset cbr 320

(--preset cbr 320 is the exact same thing as --alt-preset insane, etc.)

==Setting up EAC for LAME.exe with tagging==

{{:EAC and Lame}}

==Additional reading==

* [[LAME|More information on LAME]]
* [http://www.hydrogenaudio.org/forums/index.php?act=ST&f=16&t=32288 Forum discussion of the recommended settings]
* [http://www.hydrogenaudio.org/forums/index.php?act=ST&f=15&t=203 Forum discussion of the recommended settings (older)]
* [[Recommended LAME credits|Credits for the recommended settings]]
* [http://www.hydrogenaudio.org/forums/index.php?showtopic=32288&view=findpost&p=327262 Previous recommendations (outdated)]
* [[MP3]]
* [[Exact_Audio_Copy|Exact Audio Copy]]

----
[[Recommended LAME credits|Credits]]

EAC and Ogg Vorbis

2005-12-26T15:52:52Z

Pohli: /* Installation */

==Software Needed==
* [http://exactaudiocopy.org/eac6.html Exact Audio Copy]
* [http://www.rarewares.org/files/ogg/oggenc2.5-SVNP3MOD.zip Oggenc2.5 (P3/AMD Build)]
'''OR'''
* [http://www.rarewares.org/files/ogg/oggenc2.5-SVNP4MOD.zip Oggenc2.5 (P4 Build)]

==Installation==
'''Note:''' This guide assumes that EAC is has been configured for secure ripping, if not please follow [[EAC_Drive_Configuration | this guide]].
* Unzip the chosen Oggenc 2.5 build into the same directory that EAC is in.

==Configuration==

* Open EAC and insert a CD into the drive.
* Click the '''EAC''' menu and select '''Compression Options'''.
* Click the '''External Compression''' Tab, and put a check box in '''use external program for compression'''.
* Change '''Parameter Passing Scheme''' to '''User Defined Encoder'''.
* Change '''Use file extension''' to '''.ogg'''.
* Click the '''Browse''' button and locate the '''OGGENC2.EXE''' that you unzipped earlier.
* Remove the ticks from '''Use CRC check''', '''Add ID3 tag''' and '''check for external programs return code'''.
* In the '''Addtional command line options''' box, copy and paste one of the below strings based on the Tag you would prefer.
'''No Tags:'''

'''-q 6''' %s %d

'''Vorbis Comment:'''

'''-q 6''' -a "%a" -t "%t" -l "%g" -d "%y" -N "%n" -G "%m" %s -o %d

'''Note:''' If you wanted to change the quality setting the green portion is what you would substitute with the new setting e.g. -q 10 or -q 2.
* Do not worry what bit rate is shown in the bit rate drop down box, this will be ignored.

<center>[[Image:EAC_OGG.png|frame|center|Ogg configured with Vorbis Comment tagging]]</center>

==Addtional Reading==
* [[Exact_Audio_Copy|Exact Audio Copy]]
* [[Ogg_Vorbis|Ogg Vorbis]]