RE: Help reading mixed audio and data CD

Kris Warkentin <[email protected]> Thu, 22 Dec 2005 00:32:04 -0500
Newsgroups gmane.comp.multimedia.grip.user
Message-ID <[email protected]>
Thanks Mike,

I was looking at the cdparanoia source and observed something along the
lines of:
 
if multisession
	lba -= 11500

which I believe might be what you're talking about.  There was something
there about checking a leadout on the track before fixing up the TOC or some
such.  Thanks very much.  I think I see what needs to be done now.

Cheers,

Kris

> -----Original Message-----
> From: Mike Oliphant - DefenseWeb Technologies
> [mailto:[email protected]]
> Sent: Wednesday, December 21, 2005 5:52 PM
> To: Kris Warkentin; [email protected]
> Subject: RE: Help reading mixed audio and data CD
> 
> Hi Kris,
> 
> There is a gap between the last audio track and the data track on data
> CDs. It has been a while since I wrote the code, but from looking at it,
> it seems the gap is 152 seconds long. Hence, you need to subtract 152
> seconds from the length of the track before the data track.
> 
> Mike
> 
> -----Original Message-----
> From: Kris Warkentin [mailto:[email protected]]
> Sent: Wednesday, December 21, 2005 2:36 PM
> To: '[email protected]'
> Cc: '[email protected]'
> Subject: Help reading mixed audio and data CD
> 
> Hi Grip developers,
> 
> My name is Kris Warkentin from QNX Software Systems in Canada.  Part of
> my
> job is actually as a gdb maintainer and we also are the maintainers of
> the C
> development toolkit in the Eclipse IDE.  As a company, we're trying to
> give
> back so I hope you won't mind if I ask you to help enlighten me on a
> problem
> I'm having.
> 
> Given an audio cd with a data track (1-12 audio, 13 data), our driver is
> reading the TOC and giving back the addresses (lba) of each track.  So
> the
> method of calculating the length is simply track[n].length =
> track[n+1].lba
> - track[n].lba.  This in general seems fine but in the case of this
> particular audio cd, the lba of track 13 comes out as quite a bit too
> high
> resulting in the calculation of the song length being over 6 minutes
> instead
> of 3:45.
> 
> Windows calculates this correctly as does your software.  Interestingly,
> the
> Gnome CD player doesn't seem to do it right but you guys have definitely
> got
> it.
> 
> Anyway, sorry to be asking vague and stupid questions but our driver
> developer insists that he just reads the TOC off of the disk with no
> modifications and that there are no further inferences to be made about
> the
> lengths of the tracks.  Even if it isn't something that can be corrected
> in
> the driver, I'd love to be able to correctly figure out the length of
> the
> last track.
> 
> cheers,
> 
> Kris
> 
> --
> No virus found in this incoming message.
> Checked by AVG Free Edition.
> Version: 7.1.371 / Virus Database: 267.14.2/208 - Release Date: 12/20/2005
> 

-- 
No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.1.371 / Virus Database: 267.14.2/208 - Release Date: 12/20/2005
 


-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click