Originally Posted by mr.vince
We have no plans to change this... emulation authors may chose to allow warnings/notices when an IPF is not "authentic".
But I still don't get where CT raw in and CT raw out would make sense... I mean you import raw, then you find out it's ok, then you write it back to disk?
Well two parts to that. First, CT raw out may be useful if other programs such as emulators can consume that format, and/or if that format can represent certain disk data that other formats cannot. Second, passing CT in and getting another CT out can make sense -- the input data is checked/validated, and regenerated in the output (e.g. bitcells all adjusted to 2us in a regular-length data track). So can avoid degeneration seen in multi-generation analog copies f.ex.