dvdisaster provides additional ECC protection for optical media. If a medium gets damaged, dvdisaster can recover it as long as the amount of damage is smaller than the amount of ECC data you added to protect it.
It can loosely be compared to .par2 files, but the protection works at the iso level instead of working at the file level. This way, even if metadata from the optical medium filesystem is damaged, dvdisaster can still work flawlessly.
Please refer to the PDF manual for more information.
The last upstream version dates back to 2021, and can be found on the official website.
This version is built on top of the latest upstream version, with the following notable enhancements:
- Added pre-defined sizes for BD-R Triple Layer (100GB), BD-R Quadruple Layer (128GB)
- Added an option to use more space for ECC on BD-R when using RS03 (
--no-bdr-defect-management) - Re-enabled adaptive reading for RS01 and RS02, and optionally for RS03 on user request (more on that below)
- Ability to strip an augmented image from its additional ECC-data
- A new CLI-only version, not depending on gtk (
./configure --with-gui=no && make clean && make -j4) - GUI codebase ported from gtk2 to gtk3 to ensure future-proofness
- Windows and macOS builds are supported again, those were dropped upstream a few versions back
- Non-regression tests on each code change, along with prebuilt binaries for Linux64, Windows32/64 and macOS, for both CLI and GUI versions
- Fixed a bunch of other (minor) quirks, a few (minor) bugs, added a couple other (minor) features
Please refer to the CHANGELOG for all the details.
This version will never break compatibility with upstream versions, the goal is to ensure an optical media protected by upstream dvdisaster will still be able to be repaired with this version, decades from now. Regression tests are here to ensure this is the case.
For a more detailed explanation of the algorithms, please refer to the codecs specification PDF.
- It can use multiple CPU cores and is therefore WAY faster than RS01/RS02 on modern hardware.
- RS03 augmented images and error correction files are - contrary to RS01, and to a lesser extent RS02 - robust against damage of the dvdisaster-added recovery data itself
There are, however, a few cons that must be noted for RS03:
- In image mode, the RS03 augmented image file size will be picked up from a predefined list of well-known medium sizes, while the size of augmented images can be freely chosen in RS02. This is the "price to pay" for the added robustness of the correction data.
- In image mode, intelligent adaptive reading is not available for RS03-protected images. The "divide and conquer" algorithm will still be used, but dvdisaster will not stop as soon as enough sectors have been recovered to rebuild the image: it'll attempt to read them all until you stop it, or until it tried to read all the sectors. You can still stop it manually and attempt a "verify" of the resulting image file, to see if enough data has been read for recovery, otherwise resuming the adaptive reading until this is the case.
- The changes for parallel computation and higher robustness make RS03 a tiny bit less space efficient, e.g. RS03 error correction data has slighly less (around -3%) error correction capacity than RS02 on images with equal size. This is usually considered a cheap price to pay for the added robustness against corruption.
This attempts to summarize the differences, pros and cons of each codec:
| Codecs | RS01 (separate file, obsolete) | RS02 (augmented image) | RS03 (in separate file mode) | RS03 (in augmented image mode) |
|---|---|---|---|---|
| Robustness 1️⃣ | ⭐ | ⭐⭐⭐ | ⭐⭐⭐⭐⭐ | ⭐⭐⭐⭐⭐ |
| Space efficiency | ⭐⭐ | ⭐⭐⭐⭐⭐ | ⭐⭐⭐⭐ | ⭐⭐⭐⭐ |
| Computational generation speed 2️⃣ | ⭐⭐ | ⭐⭐ | ⭐⭐⭐⭐⭐ | ⭐⭐⭐⭐⭐ |
| Computational repair speed 2️⃣ | ⭐⭐⭐ | ⭐⭐⭐ | ⭐⭐⭐ | ⭐⭐⭐ |
| Damaged media recovery speed 3️⃣ | ⭐ | ⭐⭐⭐ | ⭐ | ⭐ |
| Supports customizing redundancy size | ✔️ | ✔️ | ✔️ | ❌ 4️⃣ |
1️⃣ Here we're talking about the robustness against corruption of the dvdisaster-added ECC parts themselves. The higher the ranking, the less it is likely than a few badly located damaged sectors render the whole correction impossible because they affect dvdisaster metadata on-disc. For example, corruption of the first dozens of sectors of an image can make RS02 entirely unusable regardless of the redundancy data originally stored on it.
2️⃣ When algorithm is CPU-bound, i.e. generating or repairing an image stored on a SSD/NVMe drive where the storage i/o speed is not an issue.
3️⃣ Using adaptive reading when supported (RS02), limiting the number of damaged sectors that need to be read to what is strictly necessary for repair. Using linear reading otherwise (RS03 and separate file codecs), assuming a badly damaged media, taking into account the time the drive takes to try to read damaged sectors.
4️⃣ The robustness of RS03 comes at the cost of having to augment images strictly to well-known media sizes, as explained in the previous section above. This usually doesn't make much difference as long as you intend to burn the augmented image to a classic medium (CD-R, DVD-R, BD-R, ...).
Even if the peak of the optical media era is well behind us, optical media is still of some value for specific use cases such as off-site backups. In any case, we still have media in our hands that we want to be able to repair, should it be damaged, during the next years/decades. Repairing is actually pretty much the very reason of dvdisaster existence (as long as parity data has been added, of course). The main purpose of this unofficial version is to ensure dvdisaster doesn't get hard to find, use or compile on recent systems. To this effect, prebuilt binaries are available for the 3 main categories of operating systems, and on top of that we've also fixed a few bugs and added a few tiny features.
See the INSTALL file. The workflow file that is used to automatically build binaries for each release can also help.
Note that the disc still has some room for more sessions (capacity is 128 GB).