Can I read audio CD?

I want to read audio CD and save a track as a file.
I can play audio CD, but I can not read audio CD.
Can you tell me how to read audio CD and save as a file.

“Seung-Won Jeon” <babywon@yahoo.com> wrote in message
news:a1406c$imp$1@inn.qnx.com

I want to read audio CD and save a track as a file.
I can play audio CD, but I can not read audio CD.
Can you tell me how to read audio CD and save as a file.

With QNX6 you cannot, nor can you write a program do to it as
the specification for doing so has not been released.

With QNX4 it would be possible to write a program that does that.
However, I`m not aware of the existance of such a program

Mario Charest <goto@nothingness.com> wrote:

“Seung-Won Jeon” <> babywon@yahoo.com> > wrote in message
news:a1406c$imp$> 1@inn.qnx.com> …
I want to read audio CD and save a track as a file.
I can play audio CD, but I can not read audio CD.
Can you tell me how to read audio CD and save as a file.


With QNX6 you cannot, nor can you write a program do to it as
the specification for doing so has not been released.

Sure can. In fact, I managed to do it just with header-hacking. In
fact, I have three tools (ripper, lame, rip2mp3) that I can use to rip
my personal CD collection into MP3 format.

I plan to make ripper into fs-cdda as a resmgr (since ripper already supports
using CDDB to get track names).

http://qnx.wox.org/qnx/binaries/ has ripper.bz2 and rip2mp3 (perl script).
rip2mp3 assumes an install of lame - but I cannot make a lame package due to
legal restrictions of such software.


chris


Chris McKillop <cdm@qnx.com> “The faster I go, the behinder I get.”
Software Engineer, QSSL – Lewis Carroll –
http://qnx.wox.org/

Chris,

I tried the ripper program. It appears to work, the CD and track info is
extracted but the wav file that is generated has no audible content. Are
there any specific requirements?

Could you, perchance, make the source for this program available so I can
track the problem down.

]{

“Chris McKillop” <cdm@qnx.com> wrote in message
news:a16fjk$9jt$1@nntp.qnx.com

Mario Charest <> goto@nothingness.com> > wrote:


“Seung-Won Jeon” <> babywon@yahoo.com> > wrote in message
news:a1406c$imp$> 1@inn.qnx.com> …
I want to read audio CD and save a track as a file.
I can play audio CD, but I can not read audio CD.
Can you tell me how to read audio CD and save as a file.


With QNX6 you cannot, nor can you write a program do to it as
the specification for doing so has not been released.


Sure can. In fact, I managed to do it just with header-hacking. In
fact, I have three tools (ripper, lame, rip2mp3) that I can use to rip
my personal CD collection into MP3 format.

I plan to make ripper into fs-cdda as a resmgr (since ripper already
supports
using CDDB to get track names).

http://qnx.wox.org/qnx/binaries/ > has ripper.bz2 and rip2mp3 (perl
script).
rip2mp3 assumes an install of lame - but I cannot make a lame package due
to
legal restrictions of such software.


chris


Chris McKillop <> cdm@qnx.com> > “The faster I go, the behinder I get.”
Software Engineer, QSSL – Lewis Carroll –
http://qnx.wox.org/

Kristoph A. Cichocki-Romanov <news4@kristoph.net> wrote:

Chris,

I tried the ripper program. It appears to work, the CD and track info is
extracted but the wav file that is generated has no audible content. Are
there any specific requirements?

Could you, perchance, make the source for this program available so I can
track the problem down.

There is no problem other then your CDROM does not support doing CDDA
transfers. This is a fairly common issue. There is a bug in the released
cam-cdrom.so module where the raw reads are not returning any status. This
has been fixed for the next release and ripper will be able to return some
inteligent level of information instead of giving you a blank file. :wink: I
have been lucky that all of my hardware (4 machines) work fine. Most people
I have gotten feedback have had problems on about 50% of the devices they
have tried. In talking with people on other systems (like BeOS), a lot of
hardware is unable to do CDDA.

Once I have fs-cdda working I will probably release the source to that.

chris

\

Chris McKillop <cdm@qnx.com> “The faster I go, the behinder I get.”
Software Engineer, QSSL – Lewis Carroll –
http://qnx.wox.org/

Chris,

It looks like the AOPEN CD-ROM drives do not work but Sony and Mitsumi.
Everything seems to be working as advertised.

I’ll am looking forward to the fs-cdda resource manager/source.

Thank’s for your efforts.

Kristoph


“Chris McKillop” <cdm@qnx.com> wrote in message
news:a196sa$7pp$1@nntp.qnx.com

Kristoph A. Cichocki-Romanov <> news4@kristoph.net> > wrote:

Chris,

I tried the ripper program. It appears to work, the CD and track info is
extracted but the wav file that is generated has no audible content. Are
there any specific requirements?

Could you, perchance, make the source for this program available so I
can
track the problem down.


There is no problem other then your CDROM does not support doing CDDA
transfers. This is a fairly common issue. There is a bug in the released
cam-cdrom.so module where the raw reads are not returning any status.
This
has been fixed for the next release and ripper will be able to return some
inteligent level of information instead of giving you a blank file. > :wink: > I
have been lucky that all of my hardware (4 machines) work fine. Most
people
I have gotten feedback have had problems on about 50% of the devices they
have tried. In talking with people on other systems (like BeOS), a lot of
hardware is unable to do CDDA.

Once I have fs-cdda working I will probably release the source to that.

chris

\

Chris McKillop <> cdm@qnx.com> > “The faster I go, the behinder I get.”
Software Engineer, QSSL – Lewis Carroll –
http://qnx.wox.org/

Thanks …
The ripper program works well in my machine.
Can you tell me where I can get sources or information about “ripper”
program.

And can I read a part of a track in audio CD?
For example first 10 sec. of 1st track.

And what is the function name which reads and extracts CDDA in cam-cdrom.so.
and tell me how to use that function.

And can you tell me what fs-cdda is and when are you going to release it.

Seung-Won Jeon



“Chris McKillop” <cdm@qnx.com> wrote in message
news:a196sa$7pp$1@nntp.qnx.com

Kristoph A. Cichocki-Romanov <> news4@kristoph.net> > wrote:

Chris,

I tried the ripper program. It appears to work, the CD and track info is
extracted but the wav file that is generated has no audible content. Are
there any specific requirements?

Could you, perchance, make the source for this program available so I
can
track the problem down.


There is no problem other then your CDROM does not support doing CDDA
transfers. This is a fairly common issue. There is a bug in the released
cam-cdrom.so module where the raw reads are not returning any status.
This
has been fixed for the next release and ripper will be able to return some
inteligent level of information instead of giving you a blank file. > :wink: > I
have been lucky that all of my hardware (4 machines) work fine. Most
people
I have gotten feedback have had problems on about 50% of the devices they
have tried. In talking with people on other systems (like BeOS), a lot of
hardware is unable to do CDDA.

Once I have fs-cdda working I will probably release the source to that.

chris

\

Chris McKillop <> cdm@qnx.com> > “The faster I go, the behinder I get.”
Software Engineer, QSSL – Lewis Carroll –
http://qnx.wox.org/

Thanks …
The ripper program works well in my machine.
Can you tell me where I can get sources or information about “ripper”
program.

I will most likly be releasing the sources to fs-cdda when it is finished.
I won’t be releasing the source to ripper.


And can I read a part of a track in audio CD?
For example first 10 sec. of 1st track.

With the current rippper no - it just transfers data on a per-track basis.
It is possible but I have not had the need for it. :wink:

And what is the function name which reads and extracts CDDA in cam-cdrom.so.
and tell me how to use that function.

Poke into /usr/include/sys/cdrom.h. It is all done via devctl()s.

And can you tell me what fs-cdda is and when are you going to release it.

Fs-cdda will be a resource manager that will show a set of virtual files
based on CDDB data in /cdda. So, for example…

/cdda/cd0/the_barenaked_ladies-one_week.wav

…it will tack okn the WAV header so you can rip or cp data right out of
/cdda without making an intermediate file.

chris

\

Chris McKillop <cdm@qnx.com> “The faster I go, the behinder I get.”
Software Engineer, QSSL – Lewis Carroll –
http://qnx.wox.org/

Great stuff Chris. Just a few things (if you’re going a CDDB/freedb route
for the CDs). It’s probably a bit early to ask for “features” of the
resource manager, but I’d toss in some now so you might keep them in mind.

First is to make the lookup capability configurable. One thing is to be
able to change the server it’s performing lookups on (if you’re using real
CDDB (Gracenote), it’s not really possible since they don’t like that, but
with freedb it’s fine).

Another has to do with the layout and naming of files. It’d be great to see
"/cdda/cd0/// - " for the layout, and
be able to do a “cp -R /cdda/cd0/” to some place, where it would
preserve the artist/album/track info heirarchy. The main reason I mention
this is to avoid hitting the QNX filesystem limit on filenames. When you
have Artist - Title, you hit the limit a lot earlier than you’d like.

I noticed with Audio CDs that there’s a cddb file in the .info. directory.
Something like this with some more info could be useful too (like have a
file with a list of information for the cd, like “artist=”, etc).

Just some ideas.
-Ron


Fs-cdda will be a resource manager that will show a set of virtual files
based on CDDB data in /cdda. So, for example…

/cdda/cd0/the_barenaked_ladies-one_week.wav

…it will tack okn the WAV header so you can rip or cp data right out of
/cdda without making an intermediate file.

chris

hey Ron…

First is to make the lookup capability configurable. One thing is to be
able to change the server it’s performing lookups on (if you’re using real
CDDB (Gracenote), it’s not really possible since they don’t like that, but
with freedb it’s fine).

I am using freedb - I am currently using thier re-director. But I will
totally make that a command line option for fs-cdda.

Another has to do with the layout and naming of files. It’d be great to see
"/cdda/cd0/// - " for the layout, and
be able to do a “cp -R /cdda/cd0/” to some place, where it would
preserve the artist/album/track info heirarchy. The main reason I mention
this is to avoid hitting the QNX filesystem limit on filenames. When you
have Artist - Title, you hit the limit a lot earlier than you’d like.

Ahhh…you see, it is only the physical QNX4 filesystem that has limits
on the filenames. Try fs-dos, fs-ext or fs-nfs2 and none of these limits
apply (outside of limits from those particular systems). So I belive my
limit is 1024 characters.

The other reason I am not a fan of doing it in a directory system is that it
really serves no purpose when there is only a single CD at a time. :wink:

I noticed with Audio CDs that there’s a cddb file in the .info. directory.
Something like this with some more info could be useful too (like have a
file with a list of information for the cd, like “artist=”, etc).

Yep - already in the plan…

/cdda/cd0/TRACKINFO

thanks for the feedback,
chris


Chris McKillop <cdm@qnx.com> “The faster I go, the behinder I get.”
Software Engineer, QSSL – Lewis Carroll –
http://qnx.wox.org/

Another has to do with the layout and naming of files. It’d be great to
see
"/cdda/cd0/// - " for the layout,
and
be able to do a “cp -R /cdda/cd0/” to some place, where it would
preserve the artist/album/track info heirarchy. The main reason I
mention
this is to avoid hitting the QNX filesystem limit on filenames. When
you
have Artist - Title, you hit the limit a lot earlier than you’d like.


Ahhh…you see, it is only the physical QNX4 filesystem that has limits
on the filenames. Try fs-dos, fs-ext or fs-nfs2 and none of these limits
apply (outside of limits from those particular systems). So I belive my
limit is 1024 characters.

Since I have no idea what kind of space a resource manager runs in, I
thought the /cdda/ stuff would be running out of a QNX filesystem… but if
it’s in memory, I guess it’d work. I use fs-dos for a FAT32 partition and I
LOVE that I can have longer file names than with Fatfsys in QNX4.

The other reason I am not a fan of doing it in a directory system is that
it
really serves no purpose when there is only a single CD at a time. > :wink:

Good point, /cdda/cd0/ would be one drive, and /cdda/cd1 would be another…

I noticed with Audio CDs that there’s a cddb file in the .info.
directory.
Something like this with some more info could be useful too (like have a
file with a list of information for the cd, like “artist=”,
etc).


Yep - already in the plan…

/cdda/cd0/TRACKINFO

sweet :slight_smile:

thanks for the feedback,
chris


Chris McKillop <> cdm@qnx.com> > “The faster I go, the behinder I get.”
Software Engineer, QSSL – Lewis Carroll –
http://qnx.wox.org/

Ahhh…you see, it is only the physical QNX4 filesystem that has limits
on the filenames. Try fs-dos, fs-ext or fs-nfs2 and none of these limits
apply (outside of limits from those particular systems). So I belive my
limit is 1024 characters.

Since I have no idea what kind of space a resource manager runs in, I
thought the /cdda/ stuff would be running out of a QNX filesystem… but if
it’s in memory, I guess it’d work. I use fs-dos for a FAT32 partition and I
LOVE that I can have longer file names than with Fatfsys in QNX4.

Yeah - see, all of the path space under QNX is virtual. It is up to the
resource manager itself to make the call on what to present and how that
relates to a physical system. So, fs-cdda will register /cdda and then
all accesses from /cdda on will be internally resolved within fs-cdda and
so it can report anything about anything.

chris


Chris McKillop <cdm@qnx.com> “The faster I go, the behinder I get.”
Software Engineer, QSSL – Lewis Carroll –
http://qnx.wox.org/

Chris McKillop <cdm@qnx.com> wrote in article <a16fjk$9jt$1@nntp.qnx.com>…
<…>

rip2mp3 assumes an install of lame - but I cannot make a lame package due to
legal restrictions of such software.

You could download BladeEnc - my favourite mp3 encoder, at
http://www2.arnes.si/~mmilut/
There is version for QNX6.0 (linked with libc.so.1), but I’m going to place there new build for
6.1A :wink:
Eduard.