Stéphane Lesimple

@Mo1sture can you explain with more details what your issue is, maybe opening a new ticket in the process? It seems your issue might be different than the one @PrimoAngelo...

About the burning speed with or without defect management, I can say that in my experience, the burning speed is indeed exactly twice as slow when defect management is enabled,...

> But I guess the project page is just stating it in a simple manner that the number of sectors RS03 worked with must be known, so it doesn't really...

> The only thing that I think is a bit confusing is the "Speed" metric. On media read, it says intelligent adaptive reading can be up to 90% faster (which...

Amended the comparison table, hopefully this is a bit clearer without being too complicated https://github.com/speed47/dvdisaster/tree/readmers03?tab=readme-ov-file#mag-comparison-table

Thanks for dumping the different format capacities available for your media, this is interesting and shows that for BD-R(E), the number of sectors is really not _that_ standard. In another...

7 hours is indeed quite long! It's probably not a bad idea to just give up with defect management in that case and use dvdisaster to augment the image indeed,...

Hello, thanks for your report. Is the behaviour on Windows 10 with 0.79.10p1 reproducible, i.e. if you scan it again, you still get errors? If yes, do you get exactly...

I believe this is fixed in the latest version: - fix: corrupt data under Windows for RS03 when memory-mapped i/o strategy was used (https://github.com/speed47/dvdisaster/issues/82) Can you retry with the latest...

This is indeed in the home folder of the users, and in several places the code (and other scripts handling the lifecycle of the ttyrec files, such as encryption and...