Hi:

For all I like linux I've never been able to find a linux cli audio CD player that is a descent program. Of course, there is Slack's workbone, a very handy audio CD player and a good example of trade-off between facilities and resource-hunger.

I would be happy (not exaggerating) to find such a cli program with only one extra feature over workbone, which by the way can be instructed to leave the console free for you to use it (it stays running in the background if you like, i.e., not interactively): to start a track from whichever place within the track you wish and being able to specify it by means of an option in the command line, in the way mplayer, e.g., does it ('mplayer //cdda 3 -ss 12.43.70' would be: play track 3 of the CD, starting at 12 min, 43.70 sec). Why not mplayer, then? Only one reason. It's like using an atom bomb to kill an ant.

The question: Can somebody suggest a cli CD player like the one described above?

once you find suitable cli cdplayer you can send it to background with screen

cdcd (command driven cd player) will do this I beieve although I have not used it in a while. guesse I like to make sure my ants are good and dead

Will this , archShade, do for a slackware operating system? It's ArchLinux, but the page enumerates a lot of OSs, including slackware. However, for 32 bits (as well as for 64) they offer only one package.

I have no expriance with arch and do not know if a package from arch will run on slack (someone who knows care to chime in), but I have a feeling it won't. I genrally only look at http://packages.slackware.com/ for slack packages, sadly that route is not gonna cut it this time. If I cannot find it there I look on the project website and somtimes (rarely) there may be a slack package.

This is in no way garanteed.
Else install from source which you may have to do if you want to run this. Is a quite easy instalation (standard ./configure; make; su -c "make install") you will need gcc (or another c compiler), make, and licdaudio installed for this to work.

Latest source can be found herehttp://directory.fsf.org/wiki/Cdcd.

I appreciate that instalation from source can be messy at times but I think its well worth doing if you want a package. Another way would be to create your own slack package (from the source) here is a helpful wiki article on the subject. I am a poor guide for this (having not actually done it) but I'm sure there are plenty round here who have. Then you can upload your file and help other people who want to use cdcd under slack in future.

I'm sorry if this is overly simplistic (I appreciate you are quite an experianced linux user) but it's better to cover as much as possible. (Although if I have missed or glossed over anything please don't be afraid to ask)

1 members found this post helpful.

Ref. post #4

The Arch package cdcd-0.6.6-6-i686.pkg.tar.xz is one file : /usr/bin/cdcd
.. and has few dependencies :
$ ldd cdcd
libcdaudio.so.1
libreadline.so.6
.
libncurses.so.5

.. Should work on any contemporary Linux OS.
32bits http://archlinux.c3sl.ufpr.br/commun...686.pkg.tar.xz
64bits http://archlinux.c3sl.ufpr.br/commun..._64.pkg.tar.xz

.

1 members found this post helpful.

Can you elaborate ?

I got this

cdcd-0.6.6-i486-1sl.tgz*
cdcd-0.6.6-i486-1sl.tgz.asc*
cdcd-0.6.6-i486-1sl.txt*
src/

at http://slackware.org.uk/slacky/slack...ltimedia/cdcd/. And my OS
is slackware 12.0. That is to be lucky (12.2 - 12.0 = only 0.2). Within
src/. there comes a slackbuilds script, but no checksums.

Cdcd is the program suggested in post #3, whose manual I was reading and is versatil enough without pretending to serve me a cup of coffe too.

Thanks for these links, archShade.I have some experience compiling (even compiled the kernel but, slavishly following a third person's instructions). About making packages, I have always wanted to do it, and if I did not it only was for lack of time (an erroneous appreciation as I realize each time I have to compile mplayer).

I will certain do, archShade, and a lot of thanks for your posts. I'm about to begin compilation of cdcd.

I have to ask why are you still using slakware 12.0? is there a reason you cannot upgrade. The current version of slack is 14. This is comming from someone running 13.37 however I use slack as a bit of a toy OS (I'm not saying slack is a toy) that I use to try out little projects such as messing around with kernals or trying to configure stuff manually. Most of the time I use Debian (stable) for the just works factor.

I plan to upgradeafter my next set of exams.

@knudfl: Thanks for your useful remarks.

@Tex: Have you ever heard of utorrent ('u' stands for mu)? They use the fact it is a tiny program to advertise it. Because of that I immediately adopted it. A small program runs faster than a big one on the same machine. And takes less room (RAM/disk). But of course, it's all a matter of taste.

I'll put it this way: some people enjoy using the transistor. I enjoy reinventing it. Sure, you have to reinvent quantum mechanics first, but that is fun too. And, like you, I use several operating systems. One of them is MS-DOS 5.00 (1991).

compleatley off topic but

Although this is a good rule of thumb it's not always true. If there is suffciant RAM a program with a larger footprint can outperform one with a small footprint (which may end up being IO bound to another slower part of the computer). It is also possible to have a program that is desighned in a moduler way to only load the parts needed for a particular task where a smaller non-moduler program loads it's entirity into RAM. Another example is if there is a program that has to derive mathematically an oft used constant from an input before using it it would be more efficiant to calculate it once rather than every time it was called but a program that called the function each time would be less efficient than a program that calculated it once even though the one that called the function many times would use less RAM. Many of these issue are solved by modern optimizeers.

As I said 99.9/100 times you would be correct but it's not always the case, even more true when it comes scientific computing.

Another thing that may limit this (and more relevent to the discssion). Multiple instances of a single tool will often have large sections shared which means that if you have mplayer doing many things it could be more efficiant than having multiple specific tools open at the same time.

All that being said I would have though (but have no evidence) that in this situation the standalone cd player would perform bettter.

# 8

The Slackware 12.2 package cdcd-0.6.6-i486-1sl.tgz
http://slackware.org.uk/slacky/slack...6-i486-1sl.tgz
.. works OK on Slackware 12.0, when you have the dependency libcdaudio
http://slackbuilds.org/result/?search=cdaudio&sv=13.1

Binary package for 12.0 : libcdaudio-0.99.12p2-i486-1_SBo.tgz ( 88 kB )
https://docs.google.com/open?id=0B7S...jFyYjVqTFdBYTg

.

1 members found this post helpful.

Most kind of you, Sir, and thank you very much.