I came into the gnu/linux world over a year ago, back then there was nothing meeting my needs.

Linuxrip is a secure ripper (test and copy, with autoretry (first a third, then a fourth, etc), 2 matching rips = ok).
It does xml style logging.
Uses cdparanoia or cdda2wav for ripping.
Can encode to flac(also support for flake), wavpack, vorbis, musepack and mp3.
Does (album) replayain for all types (mp3gain for mp3, because i included support for people who might have portables).
It's multithreaded in the sense it can do encoding and ripping at the same time (only one encode at a time currently).
It can retrieve cddb info.
Automaticly adds capital letters to each word (with an exclude list), to make a more unified appearance (it can be disabled).
Supports multiple naming convention (2 by default, custom ones can be added for those not completely alien to bash scripting).
Supports (simple) nfo's with the option to add notes.
It embeds logs into tags for flac and vorbis (which have a readily available commandline tagger).

I think that's most of the major features, one thing it (will probably never) doesn't support is single flac+cuesheet.

Linuxrip has had a little under 25 (mostly private) releases over a period of almost a year (i guess).
The Makefile is not perfect yet.

It has been tested on gentoo linux and arch linux (not the most recent version). Probably runs on other unix like systems if you can meet the dependencies.

I've been working a release ready for the public, consider this a beta.

Please make sure you have some space in /tmp (for a few small files), forgot to put that into readme.

Let me know what you think.

Currently only svn:
linuxrip page

An example log to serve (possible) curiosity.

How does this compare with rubyripper?

Never tried rubyripper, because i already had my own thing when it came out.
I suppose i could try.

Initial impressions(compared to what i did):

pros:
- asks for config settings

cons:
- can't select cddb server (and it doesn't work for me)
- logs are not the way i would do them (plaintext for one)
- less choices for encoding
- lacking all the little bits and finetuning i'm used to

Not meant for me, but then again i wrote my own script which suits me better (how unexpected :-) ).

Rubyripper's dependency on libraries does make it a smaller codebase, the cli ripper was 200-250 lines of code. My efforts required much more code (one reason is the lack of modules for bash), around 2500 lines (although many lines are short).

I'm mainly curious if the ripping method is similar

I've been getting better results with rubyripper + cdparanoia, then any other ripper for Windows even

I would welcome the same/similar method of ripping and comparing w/ more configuration options, especially if it's all CLI

I will give it a shot in a bit, I'm currently running windows so I could update my drives firmware.

Some comments after first look at the sources:

• Is it possible to separate internally used scripts (and put in something like /usr[/local]/lib/linuxrip) from end user scripts (like linuxrip and createnfo)? It will be simple to package such project.
• I have no nano editor at all! I prefer vim. Maybe better to get editor name from $EDITOR and (if it's unset) find (by 'which') available editor from small list? Nano in requirements is nice!
• For simple arithmetics you can use shell $((expression)) instead of 'echo expression | bc' (and one dependencies will go away again).

Anyway it's a great work for shell only program. If my (mainly admin related) code begins grow too quick I'm switching to more high-level language like python.

Real ripper work I'll test later, sorry.

The method seems similar, but the difference is that my script has a load of options for small things. I'm basicly calling cdparanoia with a set of options (which is are definable), it makes md5's after each rip, compares them, does another rip checks if two matches, etc. Then stores them. Very similar approach in terms of ripping

It's the wiki if you want to take a look at the correction mechanism. It's a fairly straightforward approach that makes sense logically. The lead developer did a good job explaining it. It doesn't gurantee an MD5 sum on each rip. The approach is very similar

I will make the text editor an option, thanks for the $(()) advice, i guess i'll slowly start using/converting that.
My attempt to properly intergrate into the filesystem was just a first attempt, i will change that as well (at some point).

this sounds great, i just wish it supported flac images w/ cue sheets... i'll check it out anyway. thanks madman2003!

Find me a console based cue sheet generator or something like that and i might reconsider adding it (the last broken cue sheet handler was a load of code and didn't work very well and i don't want to write it myself atm).

I used cdrdao read-toc + cueconvert before switched to EAC under Wine. To embed later into FLAC as the metadata block it's enough.

There might a problem using $(()), since integer math doesn't always do it for me.

Try to use decimal point in first used operand, something like $((2./3)) or $(($n./3)).

Doesn't work.

mkcue is what abcde uses apparently. i just pulled that link up w/ google... i have no idea if its up-to-date or accurate...

But what about pre-gap info? It can be found only from tracks itself, not from TOC. cdrdao read-toc can read it (and also ISRC).

For the moment i'm using cdrdao with quicktoc option, the base for flac+cue ripping is there. Just no support for tags in cue (which doesn't matter for the built in cue, but does for the external one).

Also added option for text editor.

Will be in the next version.

New version in start post.

Added choosable text editor and initial flac+cue sheet support.

Added version 0.091, which adds cue sheet support for multiple flac file ripping (probably expanded to other codecs in the future, just not yet :-) ). It needs testing, especially on tracks with subtracks or strange pregap tracks (i only tested normal pregaps on one cd).

EDIT: the style is very similar to eac's non-compliant cue sheets

i apologize if this is a very noobish request, but do any of you know of any online how-to's or anything that would teach me how to install things in ubuntu that are not any any repo's, and don't have deb's.

simply put, i'm very interested in linuxrip, but i have no idea how to use it...

There are two ways, making proper debs or just a package with no dependency checking or anything like that (a package just to be able to uninstall it).

(Source: http://ubuntuforums.org/showthread.php?t=2683)

checkinstall: http://www.ubuntuforums.org/showthread.php?t=2356
debian's maintainer guide (meant for developers): http://www.debian.org/doc/maint-guide/

In this case (because it's just a script and just for you) i would use checkinstall.

Here's a somewhat simpler article too:
http://www.debian-administration.org/articles/336


And some source packages (*.tar.gz or *.tar.bz2, usually) are nice enough to come with a "debian" directory. In which case you can build your *.deb by simply doing such in the root directory of the source:

fakeroot debian/rules binary

or, if you want to pass configure options:

DEB_BUILD_OPTIONS="--enable-something --enable-somethingelse" fakeroot debian/rules binary

variables are also possible:

CC=gcc-3.4 DEB_BUILD_OPTIONS="--enable-something" fakeroot debian/rules binary

then to clean:

fakeroot debian/rules clean

and to install:

dpkg -i somepackage.deb


But ofcourse, not all source packages are so well behaved. You can check out CheckInstall as Madman2003 mentioned. But it doesn't always work. But if what it installs won't run; atleast you can simply uninstall what was installed, so it's no hassle.....

[EDIT]
Here's a tutorial on CheckInstall too:
http://www.debian-administration.org/articles/147
And here are mentioned some of it's limitations:
http://asic-linux.com.mx/~izto/checkinstall/faq.php

Personally I recently tried to use it on FAAC 1.25. I could install it by first running "find . -type f -exec dos2unix -f '{}' \;" over the sources to get rid of all the DOS lineendings, then doing "./bootstrap" and then finally "./configure", "make" and "sudo make install". But I first tried "checkinstall" instead of "make install", but it didn't install several files or any of the symlinks, so the program wouldn't run. When using old "make install" I got a functioning program.....
[/EDIT]

If anyone has makefile suggestion's (if something doesn't work), then please recommend. Also keep in mind that this is just a script, so no compiling is needed. The makefile is just to facilitate a normal "way" of installing. I have never used debian or ubuntu, the install is only tested on gentoo.

on more quick question... can it be configured to encode to multiple formats from a single rip (aka WACK, REACT, etc)?

Yes, in settings there are a bunch encodeXXX vars around, ripping can happen to all formats at once. There are a few limitations, cue sheets are only for flac (haven't got around to make it useable for more than one format), embedding log files only happens for flac and vorbis (the others i couldn't find a useable commandline tagger to embed it).

Enabling all formats will make ripping take a bit longer (it rips and encodes parallel, but the encode system uses a queue). So from a speed point of view i wouldn't go beyond 2 codecs (even on a modern computer).

cool, thanks.

Hi Madman2003 and thread participants,

I'v e been trying to use your script but must've missed something on the settings_file:

from ~/linuxrip, where i untarred the arch, i run
./linuxrip and get:

mario@ubuntu02:~/linuxrip-0.091$ ./linuxrip

Ripping to /dev/null

Select drive: (default is 1)
1: Drivename (/dev/cdrom)
2: ASUS (/dev/cdrom1)
2
./linuxrip: line 311: cdspeed: command not found
Select ripper: (default is 1)
1: cdparanoia
2: cdda2wav
1

A rex rip requires the '-X -z' switches for cdparanoia (Drive 2).

although I didn't enable the option nor have it installed 8-|
"rex", as well, is not enabled but linuxrip insists in cdparanoia config. switches.
Could any of you help me on getting this going? - Thanks a lot.

Below is my settings_file (in ~/linuxrip). BTW do I need to copy this settings_file to /etc/linuxrip ? and the "Makefile" ? does one have to run it? or...

#! /bin/bash

### These settings override the default linuxrip settings, uncomment what you want to change

### Base configuration, this needs to be set properly

## cdrom device location
#device[1]='/dev/cdrom'
device[2]='/dev/cdrom1'

## drivename, will only be put in nfo and xml file, array
#drivename[1]='Drivename1'
#drivename[2]='Asus'

## device id, only needed for cue sheet creation, use "cdrdao scanbus" for info
#deviceid[1]='ATA:0,0,0'
deviceid[2]='ATA:0,1,0'

## rippath
#rippath='/dev/null'

### Optional configuration, recommended to look at

## text editor command
texteditor='nano'

## maximum amount of rip attempts before giving up
defaultries='10'

## freedb server
cddbserver='freedb2.org'

## freedb user
cddbuser='linuxrip'

## FreeDB email address
cddbemail='localhost@localhost'

## cddb port number
cddbport='8880'

## interactive mode, 0 = no, 1 = yes
interactive='1'

## rip single file flac
ripsinglefile='1'

## toc read options, add --fast-toc to skip pregap detection
#readtocoptions=""

## generate cue, only for flac atm
generatecuefile='1'

## encode flac, 0 = no, 1 = yes
encodeflac='1'

## reference flac encoder options
flacoptions='-V -6'

## flake flac encoder options
#flakeoptions='-10'

## flake doesn't verify on it's own, so flac -t can be used for that
#flakeverify='1'

## flac encoder, 'flac' and 'flake' are the choices
#flacencoder='flac'

## encode wavpack, 0 = no, 1 = yes
#encodewavpack='0'

## wavpack encode options
#wavpackoptions=''

## encode mpc, 0 = no, 1 = yes
#encodempc='0'

## mpc encode options
#mpcoptions='--quality 8'

## encode ogg vorbis, 0 = no, 1 = yes
#encodevorbis='0'

## ogg vorbis encode options
#vorbisoptions='-q 8'

## encode mp3, i had better not catch you using this for storage purposes :-)
#encodemp3='0'

## mp3 encode options
#lameoptions='-V 2 --vbr-new'

## ripper, either cdparanoia or cdda2wav
#ripper[1]='cdparanoia'
#ripper[2]='cdda2wav'

## remove wav files, 0 =no, 1 = yes
#removewavs='1'

## folder template
#setfoldertemplate='1'

## file template
setfiletemplate='1'

## filetemplate 2: when exceeding 60 character base(xml file for example) filename(excluding extensions), it will switch to just "albumname.extension"
#maxfilenamecharacters='60'

## file tag
#filetag='anon'

## create nfo
#createnfo='1'

## add drivename to nfo and xml logfile, set drivename below
#adddrivename='1'

## add rippername to nfo, use 'none' if it should not be added
#rippername='none'

## track names (and other things) start with capital letters, even if cddb gives a small letter. 1=capital letter, 0=no capital letter.
capitalletter='1'

## noprocess means the tags will not be changed in any way
#noprocess='0'

## use cdparanoia instead of cd-discid to determine amount of tracks (cdparanoia ignores data tracks), 1=yes, 0=no
## note: with this option on the question if the amount of tracks is right will default to yes instead of having no default.
#improvedtrackdetect='1'

## verbose ripping output
verbose='1'

## use cdspeed to set maximum drive speed
#cdspeed='0'
#maximumspeed='15'

### Expert configuration

## script folder (automaticly determined from the current folder if autodetect, but this is the override)
#scriptpath='autodetect'

## set the drive read offset here, array
#driveoffset[1]='0'
#driveoffset[2]='0'

## cdparanoia options, array
#cdparanoiaoptions[1]="-X -z -O ${driveoffset[1]} -d ${device[1]}"
#cdparanoiaoptions[2]="-X -z -T ${driveoffset[2]} -d ${device[2]}"

## cdda2wav options, array
#cdda2wavoptions[1]="--paranoia --paraopts retries=999 -o ${driveoffset[1]} -D ${device[1]}"
#cdda2wavoptions[2]="--paranoia --paraopts retries=999 -o ${driveoffset[2]} -D ${device[2]}"

## some cd's have destructive copy protections, such as cds200, most drives are (probably) not capable of a 100% rip, be sure to listen very carefully to rips with this setting turned on
#allowmismatchingmd5s='0'

## manually edit info send from the cddb server, in case something is messed up a bit and rewriting costs a lot of time, only works for track names
#manuallyeditcddbinfo='0'

## create rips that are in line with the goals of the rex-guide (http://rex-guide.de.vu), rex guide only specifies exact audio copy atm
#rex='0'

## leo stands for Lossless Exact Original and should only be turned when ripping original cd's and rex switch is on
## this switch only affects a tag in the log and in the foldername
#leo='0'

TIA

Mario

Is this disableable, along with the logs? I don't like keeping clutter like that And can I make it run a specified plugin after a full successful rip? (cover downloading)

I'll consider that a feature request for next version.

EDIT: do you mean you want to run a command from the rip folder? does any information need to be input to this command?



A few things, the only config file that exist (besides the script itself) is /etc/linuxrip/settings.
(i'll see if i can implement a per user config file).

If you want to change things from the default, then you must not have a commented (starts with #) option.
Uncomment it.

So edit the file /etc/linuxrip/settings and keep in mind that if you add a drive[2] all the other driverelated things like variable[1] must also have a variable[2].

If you want i can make a config file for you as example. I recommend this, because i have a feeling you are making some mistakes (which will reveal what i cannot assume).

EDIT: normally you shouldn't edit the script itself

Information insofar as the directory names. But yeah, commands from the rip folder.

I'm embarrassed to say that I have still not gotten this working. I'm convinced that there is something simple that I have missed, and please forgive me for my ignorance. I checked to make sure that I had all of the dependencies. I extracted the tar.gz, cd'ed into the directory ran sudo checkinstall; it created and installed the deb happily. I then opened up /etc/linuxrip/settings and edited all of the settings that pertained to me, un-commenting all of the lines that I changed. I then saved it, and opened a new terminal window and ran the command "linuxrip". Ubuntu reminded me... So I tried again... "sudo linuxrip" Here was the output.So basically, nothing worked. I'm sorry guys... Here's the first part of my /etc/linuxrip/settings file, if it helps. If you need the rest of it, let me know, it was just too long to post.My goal is to output flac files (for now; in the future, when I figure out how to split and transcode images, I will do images) and LAME mp3's (-V5).

And just for good measure, I'm running Ubuntu Edgy on a Pentium M Laptop. Thanks

edit: i appologize for the very long original post... i thought because i wrapped my settings file in code tags, it would have been scaled down, and given a scroll bar. i've taken most of the settings file out. if you need the rest of it to diagnose the problem, let me know and i'll put it back up, or send it to you in a pm.

This smells of strange issues, either permission related (a normal user should be able to rip). Or some kind of shell problem. I'm not quite sure without diagnosing the problem myself. So i'm going to be bold and ask if you can create an account for me if you have a ssh server (if and when questions lead nowhere). But first there are one or two things you can try.

What are the permissions of linuxrip? (ls -l /usr/bin/linuxrip)
Do the commands 'bash' and 'sh' work properly? (both should produce shells, looking a bit different)

At worst you can do a debug run of linuxrip and dump it into a file. (sh -x /usr/bin/linuxrip &> ~/linuxripdump.txt) And give me that file. If that reveals nothing, i probably can't help without interactive acces to your system. But let's first try this

Could I include a frontend to this in my in-planning-stages MPD client written with ruby/Qt? I'd make it say "You do not appear to have linuxrip. Click OK to go to a place where you can download it" going to this thread, or I'd bundle it if you'd allow that - I'd give proper credit in the interface, of course.

If the license will be gplv2 you didn't even have to ask. Still i would prefer that you link to this thread (or some other place at a future time). You do know this script was never made to interface with a gui?

Yes, of course

Neither was DOS... and look where windows is now (let's avoid "at the bottom" remarks )

here's what i have."bash" didn't seem to do anything (no error messages, just a new, identical terminal line was entered, just like as if i had hit *enter* with no command).So then, I tried "sudo bash"I then closed my terminal window, and opened a new one, so I would be back to standard user rights, then I entered "sh"Finally, here's what was returned after the debug run of linuxrip.
thanks again!

I have a theory, your bash does not support arrays. Which version of bash do you have?

My package manager reports bash 3.1-5ubuntu3. Its the default in Ubuntu Edgy.

Please ask the ubuntu people if the configure option --enable-array-variables was used or how you can find out.

Ok, I'll get around to that soon, but I just noticed that what I posted in post 38 does not resemble the settings I had previously set in my /etc/linuxrip/settings file. For instance, I has set LAME to use -V5, but the default -V2 is what was returned. Is this to be expected?

You have no execute permission as user, only owner of the file (root) can run it. Try "sudo chmod 755 /usr/bin/linuxrip" and also for others similar executables from the linuxrip bandle. May be it will help.

How can I tell which other files need to be chmod'd?

I chmod'd /etc/linux/settings, then I tried linuxrip again, and it started working. It threw up an error message regarding permissions about /usr/lib/linuxrip/nfowriter and /usr/lib/linuxrip/xmlwriter. So I then ran the chmod command on each of them, and now it's running (apparently) sucessfully! Thanks everyone who has taken the time to read my ignorant questions... lol. So far, I'm very happy about linuxrip. Thanks Madman2003. I'll probably be back with more questions/comments later, after I get to play around with some things.

So far, the only thing that I would have different is the lack of verbose nature of linuxrip's usage of cdparanoia. abcde shows a progress bar of cdparanoia's progress through each track, right inside the terminal. Is there a way to make linuxrip do this? I should look at the settings file more carefully.

edit: typo's

edit2: Oh, and what version of cdspeed do you use? I google'd and came across the source for a version 0.4, and I installed it, but I had a hard time finding anything about it. Is there a more recent version that someone could share?

Currently you have two choices, either you get no feedback or the normal cdparanoia output. It's a verbose something option.

About the lame level, did you uncomment the parameter in settings?

This is the ebuild gentoo uses for cdspeed-0.4

Everything seems to be working excellent for the most part. At the end of the rip process, this was displayed (starting with the successful rip of the last track, track 12):
I haven't been able to test out my cue file yet, but I'm curious what those error's mean.

Also, turning off the "capital letter" settings seems to lowercase all of my letters. I would like to have the files tagged with the same capitalization as the cddb entry, and then have the option to edit the capitalizations just before the rip, if there are any errors. Sorry, that is what the noprocess settings is for... I'm dumb sometimes.

Thanks Madman2003, that was the same version of cdspeed that I found and was using, and the lame settings is fixed, now that I chmod'd the necessary files.

Overall, I'm very happy with linuxrip. I think it will become my primary means of ripping for the time being.

If i had to guess you have cue sheet creation on and don't have cdrdao installed, or i made assumptions that don't work over there. Does the command cdrdao exist?

EDIT: The lack of toc file suggest if there even if is a cue sheet, it's a big mess containing mostly junk (the toc file is used to create the cue sheet).

cdrdao seems to be installed properly...
Here are the contents of my cuesheet.I'm still trying to find a program that can burn cd's from cuesheets, so I don't have any way to test it out, but it looks fine to me...

I can assure you this is very wrong. This doesn't mention start times of tracks or anything like that.
Could you give me the output of 'cdrdao scanbus', i suspect the problem may lie with a improperly chosen drive (which only affects cue creation).