CUETools: 0/0 ? No match but offset Options

[Rivfader]

Hi guys, I'm new here.
Someone knows what does 0/0 No match but offset mean?

This is the CUETools report:

[CUETools log; Date: 24/09/2012 23:34:54; Version: 2.1.2a]
[CTDB TOCID: NebjMALXvAQ8XG2SLuOdv8nCKNc-] found.
[ CTDBID ] Status
[4d50e724] (2/2) Accurately ripped
[AccurateRip ID: 00193120-00ccd22e-a10fd00a] found.
Track [ CRC ] Status
01 [fb082923] (0/0) No match but offset
02 [b376454e] (0/0) No match but offset
03 [4049d929] (0/0) No match but offset
04 [94f7a4c9] (0/0) No match but offset
05 [494345d2] (0/0) No match but offset
06 [aa90d7fa] (0/0) No match but offset
07 [f6c6a311] (0/0) No match but offset
08 [f8d3560a] (0/0) No match but offset
09 [1c33f1e2] (0/0) No match but offset
10 [5dfad59b] (0/0) No match but offset

Track Peak [ CRC32 ] [W/O NULL] [ LOG ]
-- 98,0 [D447F701] [B0ADE255] W/O NULL
01 98,0 [465977C1] [CBF22894]
02 94,3 [3BAC8A6B] [962936E7]
03 98,0 [663F5B28] [FD0040C8]
04 98,0 [E94C3286] [3E64702F]
05 98,0 [9E85F747] [75A06163]
06 98,0 [55AFD568] [17EF4620]
07 98,0 [A4192E5E] [6A3406E3]
08 98,0 [23272F29] [B094F4D9]
09 96,9 [35257244] [937F1987]
10 93,2 [7F5C6604] [B9097BA0]

This post has been edited by Rivfader: Sep 26 2012, 18:17

[korth]

The AR record was found, but it doesn't contain readable data.
I don't believe a definitive explanation was given why this exists for an entire disc. It's been theorized that the data was either removed or put in limbo. (link) (link)
"No match but offset" at zero offset in v2.1.2a means "No match" but the offset is probably correct. This was replaced with "No match" in v2.1.4. More on the CUETools log here.