Hi,
My name is Nuno Vitorino and I'm the R&D Director at Innuos. Just to clarify a few comments with regards the ripping engine.
Our ripping engine is based on cdparanoia and adjusted to the offset of our specific drive. It will only rip bit-perfect - if it doesn't it will place the CD on Quarantine and report a damaged track.
We don't use the AccurateRip database because, unfortunately, it may be misleading. If it says it's an accurate rip, that's indeed the case. But there are multiple cases where it can report non-accurate rip when in fact it's perfectly ok namely:
1. Cd not on the Accurate Rip database
2. A different pressing of the CD
3. A slightly different version of the CD
This would cause unnecessary user anxiety in that the system was reporting a non-accurate rip. So we prefer not to use it. A better alternative IMO would be CueDB as its algorithm would solve 2 and 3. However, it's a challenge enough to get metadata from most CDs nevermind being in the CueDB database. Our TEAC drive also features AccurateStream technology, which ensures a consistent ripping. AccurateRip was, IMO, more relevant in the past where drive offsets could actually vary during the rip, causing jitter. These do not and, as previously said, the offset has been adjusted to our drive.
As for ripping in AIFF, our WAV ripping already contains all necessary tags. We want the system to be as simple as possible and want to have only one fully uncompressed format. WAV would arguably enjoy better compatibility than AIFF. However, if user feedback would say to use AIFF instead of WAV, it's an easy change for us. We already support playing and editing AIFF anyway.
Hope this helps clarifying our options.