Multiple data tracks Picard CD TOC Disc ID calculation

datatrack
cd
cccd
discid
picard
Tags: #<Tag:0x00007f2a05db6c68> #<Tag:0x00007f2a05db6718> #<Tag:0x00007f2a05db60d8> #<Tag:0x00007f2a05db5930> #<Tag:0x00007f2a05db5520>

#1

Hello there.
@lucascarvalho has a CD with two trailing data tracks as part of a CD anti copy attempt.
The Disc ID computed by Picard 1.4.2 latest version includes those, as you can see in Edit #47179248 - Add disc ID.
In general, I think, the Disc ID algorithm is trying to ignore them but in this case it didn’t work, apparently.


#2

That sounds like the Cactus Data Shield copy control method. I’ve seen generated TOCs from CDs using that method before (via FreeDB imports, RIP) and usually there was only one data track listed, not two. Perhaps that’s what tripped Picard up?