Snikes, I like it!!! So does this replace all the existing structural protection code? Or will it co-exist with the existing functionality?
And will it address this issue with Clonecd backups as well?
"- Fix: Discs created with CloneDVD did not play on some DVD player models"
No, this has nothing to do with structural / bad sector protections.And will it address this issue with Clonecd backups as well?
"- Fix: Discs created with CloneDVD did not play on some DVD player models"
No, this has nothing to do with structural / bad sector protections.
This will be fixed independently...
No, you have to to tick a check box to use it, for two reasons:Snikes, I like it!!! So does this replace all the existing structural protection code? Or will it co-exist with the existing functionality?
No, you have to to tick a check box to use it, for two reasons:
1.) This new scanner is very complex, so it might need some revisions to be 100% stable, although I am confident that it will work quite well on the first try.
2.) It will be slower. How much slower depends on the disc it is looking at. But a scan can take up to 1 minute (worst case, I hope). Average time should be below 20 seconds.
CloneCD will be affected in the same way as it is now when you enable removal of "protections based on unreadable sectors".I didn't read what he quoted there carefully enough. Yea, that's another issue entirely, but, CloneCD shouldn't be affected by it though assuming the original is mastered correctly, no?
CloneCD will be affected in the same way as it is now when you enable removal of "protections based on unreadable sectors".
So it will be a beta version?No, you have to to tick a check box to use it, for two reasons:
1.) This new scanner is very complex, so it might need some revisions to be 100% stable, although I am confident that it will work quite well on the first try.
2.) It will be slower. How much slower depends on the disc it is looking at. But a scan can take up to 1 minute (worst case, I hope). Average time should be below 20 seconds.
Probably not.So it will be a beta version?
Any timetable on the next release?Probably not.
Any timetable on the next release?
Heh, I don't wanna rush it though./me raises hand..OH OH OH OH! I KNOW I KNOW!! PICK ME PICK ME!!! Ummm, "when it's done?"
Heh, I don't wanna rush it though.
They already have it coded in?That seems unlikely with a feature this revolutionary. While it's like to have some bugs here and there, you can bet internal testing is being done. Hence, we wait.
They already have it coded in?
I didn't read what he quoted there carefully enough. Yea, that's another issue entirely, but, CloneCD shouldn't be affected by it though assuming the original is mastered correctly, no?
I'm referring to this issue: http://club.cdfreaks.com/showthread.php?t=224544&page=11
And yes, Clonecd backups are affected.
I hope they keep updating ImgBurn, it is a nice app.Yes, I know what issue it is and I didn't think it through very carefully that AnyDVD modifies the image on the fly, so, it will indeed be affected. But, James said they'll fix it, so, that's good. ImgBurn still hasn't been updated publicly to fix it, either.