Hennadiy Brych
Hennadiy Brych
I think you misunderstand that if() statement. The current code logic is "if drive is plextor, we spent 5 seconds or more and we're reading the sector inside gap -...
That's because all other drives return scsi error when accessing multisession gaps. It's just plextors who have it unlocked (but have trouble reading it fast because no positional Q in...
I'll repeat, other drives return SCSI error when accessing the gap. Those errors are fast so it just flies over the gap. The jump is needed only for drives that...
> I'll repeat, this does not happen on my ASUS. This is what I'm saying, each sector in the gap is read on ASUS and as error is returned instantly,...
No need for an option, I mean if(drive type is plextor or vendor is plextor and model is 4824), just how it's checked there based on vendor/model string.
> No; double-checking to be more specifc, it seems that the last 1500-ish sectors are not returned instantly, and take 1-2 seconds each to read, so a session gap can...
So, while Rib's firmware unlocks leadout ranges for all sessions, there is another issue where ASUS firmware is doing more processing if encountered sector is leadout. It's not even TOC...
I don't consider it a problem as you just have to wait a little bit longer for the gap - you still get legit sectors. The percentage of multisession disc...
Yes, 20 minutes is longer, but it's not 2+ hours. Think about it this way - I don't like making firmware workarounds in redumper unless absolutely neccessary. In this case...
I'll try to check on a weekend.