In README.md,
=> It can read in reverse, but specifications are not decided in redump.org
Is written,Is the specification under development?
Is /a valid for CDs that contain data tracks?
There is a theory that the exact offset may be minus 30 from AccurateRip, but is the log submitted with minus 30 valid?
Why isn't my .sub listed in the DB?
Re: Why isn't my .sub listed in the DB?
What .sub? What do you mean?mRNA wrote:Why isn't my .sub listed in the DB?
For the data-only CDs - nope.mRNA wrote:Is /a valid for CDs that contain data tracks?
We're fixing the combined offset (CD write offset + drive read offset), so it doesn't matter, the tracks are the same regardless of EAC/PR-style offset (except for the Audio CDs with no data tracks). We've even used to store both EAC and PerfectRip offset values before.mRNA wrote:There is a theory that the exact offset may be minus 30 from AccurateRip, but is the log submitted with minus 30 valid?
Re: Why isn't my .sub listed in the DB?
Can I use contain data track, that is, MIXCD or multiCD?F1ReB4LL wrote:For the data-only CDs - nope.
What about Audio CDs?F1ReB4LL wrote:(except for the Audio CDs with no data tracks)
Is Option (for CD SubChannel) OK with just / s 2 except for PSX and SecuROM?(Is there a disk that needs to use / np, / nq, / nr, etc?)
Does the .bin contain subchannel data?