Quote:
The TOC data length indicates the length in bytes of the following TOC data. The TOC data length value does
not include the TOC data length field itself. This value is not modified when the allocation length is insufficient
to return all of the TOC data available.
The First Track Number field indicates the first track number in the first complete session Table of Contents.
The Last Track Number field indicates the last track number in the last complete session Table of Contents
before the Lead-out.
The ADR field gives the type of information encoded in the Q Sub-channel of the block where this TOC entry
was found. The possible ADR values are defined in Table 294.
The Control Field indicates the attributes, of the track, see Table 295.
The Track Number field indicates the track number for that the data in the TOC track descriptor is valid. A
track number of AAh indicates that the track descriptor is for the start of the Lead-out area.
The Logical Block Address contains the address of the first block with user information for that track number
as read from the Table of Contents. An MSF bit of zero indicates that the Logical Block Address field contains
a logical block address. An MSF bit of one indicates the Logical Block Address field contains an MSF address
(see sub-clause 4.1.6).
|
So, the information whether a track has pre-emphasis or not is also stored in the TOC (in the control field is the information whether the sector is pre-emphasised or not).
So I think it is an "illegal" TOC when a track needs deamphasising, but it isn't entered in the TOC (of course, for most players this really doesn't matter)...
Anyway, if you know that a track is pre-emphasis, just add in the CUE Sheet FLAGS PRE
I also don't know if "Detect TOC manually" would work out pre-emphasis... Test it!
cu, Andre