Rips with different offsets stored in AR Database?

[Oliver]

Hello,
I checked an Album Rip with CUETools ang got this message:
---------------------------------------------------------------
[CUETools log; Date: 06.07.2014 15:51:40; Version: 2.1.4]
Offset applied: 40
[CTDB TOCID: QBelmC9E6wqFDi.Rd4QPRottX6Q-] found.
Track | CTDB Status
1 | (11/11) Accurately ripped
2 | (11/11) Accurately ripped
3 | ( 0/11) No match
4 | (11/11) Accurately ripped
5 | (11/11) Accurately ripped
6 | (11/11) Accurately ripped
7 | (11/11) Accurately ripped
8 | (11/11) Accurately ripped
9 | (11/11) Accurately ripped
10 | (11/11) Accurately ripped
11 | (11/11) Accurately ripped
12 | (11/11) Accurately ripped
13 | (11/11) Accurately ripped
14 | (11/11) Accurately ripped
15 | (11/11) Accurately ripped
16 | (11/11) Accurately ripped
17 | (11/11) Accurately ripped
18 | (11/11) Accurately ripped
19 | ( 0/11) No match
[AccurateRip ID: 003231c6-02c6e438-07113f13] found.
Track [ CRC | V2 ] Status
01 [a711594f|c891b1de] (00+00/54) No match
02 [54b38a41|c04e4b60] (00+00/55) No match
03 [2935c698|23e4ee26] (00+00/54) No match
04 [b63c73a4|f5684468] (00+00/55) No match
05 [8806f59f|91284ebc] (00+00/55) No match
06 [3ec50828|f069471b] (00+00/53) No match
07 [0cc6b118|22858ec7] (00+00/55) No match
08 [8bd4fe92|34e2eadf] (00+00/55) No match
09 [598d6297|fd370ed7] (00+00/55) No match
10 [5481488c|859cf105] (00+00/55) No match
11 [dc28c518|ce028415] (00+00/55) No match
12 [76219743|f97f2aab] (00+00/55) No match
13 [0db7195e|d147d92f] (00+00/55) No match
14 [831c9bd4|0db54ddb] (00+00/54) No match
15 [a4166156|60f929f9] (00+00/54) No match
16 [72781e05|c924c768] (00+00/53) No match
17 [103777dd|e59e9a93] (00+00/53) No match
18 [de6cfd81|0ef61590] (00+00/51) No match
19 [8e1f11cf|96d6c5af] (00+00/50) No match
Offsetted by -10:
01 [5b752337] (04/54) Accurately ripped
02 [21297ebd] (04/55) Accurately ripped
03 [e02cd2f2] (00/54) No match (V2 was not tested)
04 [87c64caa] (00/55) No match
05 [e55b806b] (04/55) Accurately ripped
06 [e536da4e] (04/53) Accurately ripped
07 [cebfe51c] (04/55) Accurately ripped
08 [661006aa] (04/55) Accurately ripped
09 [d350b99f] (04/55) Accurately ripped
10 [9e88c8a4] (04/55) Accurately ripped
11 [bcda7a26] (04/55) Accurately ripped
12 [3af9cb84] (04/55) Accurately ripped
13 [59f461b1] (04/55) Accurately ripped
14 [964b6ae6] (04/54) Accurately ripped
15 [80da1de8] (04/54) Accurately ripped
16 [8e3c31d3] (04/53) Accurately ripped
17 [40e0f9ad] (04/53) Accurately ripped
18 [b233fd0d] (04/51) Accurately ripped
19 [4dfd8f31] (00/50) No match (V2 was not tested)
Offsetted by 5:
01 [96a9a5fb] (33/54) Accurately ripped
02 [ee170edf] (33/55) Accurately ripped
03 [cdba406b] (00/54) No match (V2 was not tested)
04 [cd778721] (04/55) Accurately ripped
05 [74b15791] (34/55) Accurately ripped
06 [6a9e9e47] (33/53) Accurately ripped
07 [2bca1716] (34/55) Accurately ripped
08 [1eb77a86] (33/55) Accurately ripped
09 [fece544c] (34/55) Accurately ripped
10 [2fa6081b] (34/55) Accurately ripped
11 [ebcfea91] (34/55) Accurately ripped
12 [944a9764] (34/55) Accurately ripped
13 [e7bdf55b] (34/55) Accurately ripped
14 [7985344b] (34/54) Accurately ripped
15 [35b4830d] (33/54) Accurately ripped
16 [6496141e] (32/53) Accurately ripped
17 [77e2b6f5] (33/53) Accurately ripped
18 [74897dbb] (32/51) Accurately ripped
19 [ae2fd31e] (00/50) No match (V2 was not tested)
Offsetted by 8:
01 [8bd0a118] (09/54) Accurately ripped
02 [7d30c488] (09/55) Accurately ripped
03 [63a35650] (00/54) No match (V2 was not tested)
04 [41ce2c6c] (00/55) No match
05 [1beecfbb] (09/55) Accurately ripped
06 [84e0c4dc] (08/53) Accurately ripped
07 [d7ff5448] (09/55) Accurately ripped
08 [107291b2] (09/55) Accurately ripped
09 [747056af] (09/55) Accurately ripped
10 [b32e47b8] (09/55) Accurately ripped
11 [f5343440] (09/55) Accurately ripped
12 [a7703b93] (09/55) Accurately ripped
13 [6a9adfce] (09/55) Accurately ripped
14 [73c3f62c] (08/54) Accurately ripped
15 [26acfdae] (09/54) Accurately ripped
16 [c2a80e2d] (09/53) Accurately ripped
17 [1c7ca99d] (08/53) Accurately ripped
18 [68343111] (07/51) Accurately ripped
19 [c16d13e7] (00/50) No match (V2 was not tested)
---------------------------------------------------------------

1) What Offset does this Rip have? I just can see on top of the report that I have no matches.



2) Then I can see matches in the database with rips with ofsetts of -10, 5 and 8.
I thought when taking part in accurate rip, the ripping programme does automatically set the right offset.
Or is it possible to set it manually? And then take part?

That would explain, why there are rips with different offsets stored in the database.

If thats right so far ...
It would mean:
my report tells me, I would have matches with the offset of 5, right?
So this rip has the wrong offset. So I can correct the offset with CUETools on 5 and write new files.
Then I should have matches, right?

I did it, but got again no matches. And then the message came: matches - offsetted by 40!


I don´t catch on.

[Spoon]

Re: Rips with different offsets stored in AR Database?

Different offsets are different pressings of the same disc, they are very common.

As long as you get a match, regardless of offset, it is correct, a match is a match.

[Oliver]

Re: Rips with different offsets stored in AR Database?

Well, in the other thread (http://forum.dbpoweramp.com/showthre...ication-number) you told me, this would probably be a different pressing:

Track [ CRC | V2 ] Status
01 [acd9b3d6|0ac7e965] (007+000/528) Accurately ripped
02 [850d250b|933e9659] (007+002/525) Accurately ripped
03 [b4de8534|094e71f1] (007+002/529) Accurately ripped
04 [5a99b657|47f4559c] (007+002/528) Accurately ripped
05 [485d6950|3e13582d] (007+002/527) Accurately ripped
06 [8eb638c9|7cece9c4] (007+002/526) Accurately ripped
07 [29e8ad91|d06060b9] (007+002/527) Accurately ripped
08 [7bb71b0b|6876b98c] (007+002/525) Accurately ripped
09 [37beaf95|5112dfa5] (007+002/527) Accurately ripped
10 [9260d49c|191b3fc9] (007+002/527) Accurately ripped
11 [13ecd9d8|7ad0ecf8] (007+002/523) Accurately ripped
12 [3ed6c94f|ffe3d788] (006+002/527) Accurately ripped

This is the first part of a CUETools report. The Rips with Zero Offset (after offset correction).
So when I have less matches here, it means a different pressing.

But now you tell me, different pressings appear with another offset, in the CUETools report!

--------------------------------------------------------------------------------------------

Whean I get matches to rips with another offset, then the database just compares the audio data checksum, right?
It can tell me, when someone else has another offset but the same audio stream.
So why then is offset correction necessary, to take part in Accurate Rip?

[Oliver]

Re: Rips with different offsets stored in AR Database?

something else:
I got this CUETools report:

Track [ CRC | V2 ] Status
01 [f76f1f8e|72f6ebca] (000+000/118) No match
02 [b0c2a008|e35c832f] (000+000/119) No match
03 [656c9401|5ccabf37] (000+000/120) No match
04 [672d4e3e|909f6175] (000+000/120) No match
05 [7fc30094|97095c29] (000+000/120) No match
Offsetted by 600:
01 [5db9eb8f] (025/118) Accurately ripped
02 [f785da89] (025/119) Accurately ripped
03 [39690dfa] (026/120) Accurately ripped
04 [4c32b790] (026/120) Accurately ripped
05 [c70b7f62] (026/120) Accurately ripped


I have set the correct offset!
So why do I have no match of 120 ?
I have a match in 25 cases with another offset.

Assuming that nearly all people taking part in accurate rip have set their offsets correctly - it would mean I have a rare pressing that no one else has ripped so far! ?
Otherwise I would have matches in the first part of the report; for a very rare pressing maybe 5 or 10 of 120. Is that right?

[Spoon]

Re: Rips with different offsets stored in AR Database?

Different pressings, 120 is the total submissions for the disc, the 25 is submissions for one pressing.