OK, I add a 700MB file only and it says that track size
is > 750MB! It is a constant bug, it happens every time
when my CD size goes beyond the 650MB limit. Why does
it happen and will you fix it?
There's two "tracksizes" to be taken into account when
recording a CD-ROM. The first one is the size of a data
track you're recording, the second is the actually physical
space in audio sectors consumed by your data. The
inconsistency occurs because "data" tracks are storing
additional (ECC) checksums for all sectors, hence reducing
the storage capacity of a single sector from 2354 (?Keep
forgetting :_)) to 2048 Bytes.
So when you're storing 650MB of data residing in a data
track you're in fact writing some 700MB of "audio data".
GnomeToaster is calculating tracksizes in audio frames
multiplied by their size in bytes. That's what makes for the
difference.
So it's not a bug, it's a feature- plus it's documented
in the GnomeToaster user's guide available from http://gnometoaster.rulez.org/
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Logged In: YES
user_id=44260
There's two "tracksizes" to be taken into account when
recording a CD-ROM. The first one is the size of a data
track you're recording, the second is the actually physical
space in audio sectors consumed by your data. The
inconsistency occurs because "data" tracks are storing
additional (ECC) checksums for all sectors, hence reducing
the storage capacity of a single sector from 2354 (?Keep
forgetting :_)) to 2048 Bytes.
So when you're storing 650MB of data residing in a data
track you're in fact writing some 700MB of "audio data".
GnomeToaster is calculating tracksizes in audio frames
multiplied by their size in bytes. That's what makes for the
difference.
So it's not a bug, it's a feature- plus it's documented
in the GnomeToaster user's guide available from
http://gnometoaster.rulez.org/