Hennadiy Brych

Multi-BIN: I think your understanding of REM LEAD-OUT differs to ours. You assume that REM LEAD-OUT is a total gap size between sessions. We assume that gap between sessions is...

> > Multi-BIN: I think your understanding of REM LEAD-OUT differs to ours. You assume that REM LEAD-OUT is a total gap size between sessions. We assume that gap between...

> > Multi-BIN: I think your understanding of REM LEAD-OUT differs to ours. You assume that REM LEAD-OUT is a total gap size between sessions. We assume that gap between...

The approach used by all these actions is horrible. All are built around pushing a tag to have a build. It kind of defeats a primary goal of continuous integration...

> > The approach used by all these actions is horrible. All are built around pushing a tag to have a build. It kind of defeats a primary goal of...

I could do that better, for skeleton it's a matter of utilizing lzma progress callbacks, for hash could implement own progress callbacks.

Yes I agree with everything, having DVD RAW is good and I'm all in for implementing it. I recall last time we discussed it, it was about reading it from...

Hmm, is there more information on this? Ideally --verbose log plus skeleton. Wonder if that might be related to Pepka's ticket: https://github.com/superg/redumper/issues/114

All subchannel data is already preserved in .subcode file, which contains more data comparing to .sub, ccd/img/sub output will be implemented as conversion from .scram/.subcode. Keep backing up your discs...

Primary raw redumper output is *.scram and *.subcode. That's the extended cd space raw data that includes lead-in and lead-out. .bin/.cue is just an extract from that data but if...