I had a few technical questions about these two descriptor files.
I understand cue is to tag and break up a bin files into the right components/sections on a CD. MDS does the same.
However, doesn't CUE have some limitations? Aren't there certain scenarios or weird non-standard data/audio arrangements that it can't handle?
As far as I know MDS can tackle anything (all that extra protection junk as well). The only thing holding back the MDF/MDS format is that offset and audio integrity cannot be verified. Also, is MDS a closed format or not?
I'm thinking that if we could solve the offset issue, this combination would be the silver bullet. One file for all the raw data/audio one file to describe it. Though this prevents fancier storage techniques of selectively compressing the audio... but then you don't have much usability in that situation (HDD space is cheap anyways!)
So what if we petition Alcohol 120% developers to include offset correction (you'd have to determine it on your own)? Then we have ONE easy step (once configured) to dump a game. Yes, you'd have to verify it, so do it 2x, and try another reader. But then that is the point of an online database to compare to.
Maybe we can put together a fund to encourage the developers. I wouldn't mind giving a few bucks to have Alcohol take care of all my imaging needs (especially those weird mixed-data-audio-hybrid music CDs that can't be exactly reproduced using EAC).
Just an idea!