Ironically I wasn’t able to get EAC working on my Windows 10 installation due to the WinFSP clash, whilst CUERipper errors out on WINE (something to do with how it interacts with the ODD).
However, CUETools works fine and so I was able to compare the same CD ripped by CUETools/CUERipper on Windows with EAC under WINE. I used an ABBA CD as the test case (100+ matches in CTDB, 10+ in AccurateRip).
The CUE sheets are functionally identical (barring the differences in extra metadata stored between the two, as CUERipper included the IRSC where EAC has a Composer comment instead) – the gaps and indices are all the same. The raw rip itself is also identical - I ripped the CD to a disc image (with offset correction in both cases) and the md5 checksum of the WAV file from both applications is the same.
In both tools the rip validated against AccurateRip and CUETools DB as well. I double-checked the EAC rip afterwards using CUETools (again under WINE), as a further test.
Are the rips and logs identical to Windows on the same machine?
Ironically I wasn’t able to get EAC working on my Windows 10 installation due to the WinFSP clash, whilst CUERipper errors out on WINE (something to do with how it interacts with the ODD).
However, CUETools works fine and so I was able to compare the same CD ripped by CUETools/CUERipper on Windows with EAC under WINE. I used an ABBA CD as the test case (100+ matches in CTDB, 10+ in AccurateRip).
The CUE sheets are functionally identical (barring the differences in extra metadata stored between the two, as CUERipper included the IRSC where EAC has a Composer comment instead) – the gaps and indices are all the same. The raw rip itself is also identical - I ripped the CD to a disc image (with offset correction in both cases) and the md5 checksum of the WAV file from both applications is the same.
In both tools the rip validated against AccurateRip and CUETools DB as well. I double-checked the EAC rip afterwards using CUETools (again under WINE), as a further test.
great info
thank you