Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[CUERipper] Add setting for C2ErrorMode #203

Merged

Conversation

c72578
Copy link
Collaborator

@c72578 c72578 commented Jul 4, 2022

There are some drives, where automatic detection of the C2ErrorMode
does not work. CUETools already contains a fix for specific drives,
where Mode294 does not work properly. However, there are still drives,
where setting the C2ErrorMode to a specific value helps.

  • Add a setting for the C2ErrorMode
  • Values for the drive specific setting "DriveC2ErrorModes" are:
    0 (None), 1 (Mode294), 2 (Mode296), 3 (Auto)
  • CUETools.Ripper.Console.exe, add option:
    -C, --c2mode <int> use specific C2ErrorMode, 0 (None), 1 (Mode294), 2 (Mode296), 3 (Auto);

@c72578 c72578 mentioned this pull request Jul 5, 2022
@c72578 c72578 force-pushed the 2022-01-03_Add_setting_for_C2ErrorMode branch 4 times, most recently from c127aaa to 0352518 Compare July 7, 2022 21:06
@c72578
Copy link
Collaborator Author

c72578 commented Jul 8, 2022

A build for testing the current status of the PR has been prepared using GitHub Action release-windows:

CUETools_2.2.2_2022-07-08_git_0352518_Add_setting_for_C2ErrorMode.zip
SHA256: 44cd07b69125bb8710a8d80d4a7cb02498dd09e680d5c01ba554e362e13c7486

Instructions

CUETools.Ripper.Console.exe

Usage    : CUERipper.exe <options>

-S, --secure             secure mode, read each block twice (default);
-B, --burst              burst (1 pass) mode;
-P, --paranoid           maximum level of error correction;
-D, --drive <letter>     use a specific CD drive, e.g. D: ;
-O, --offset <samples>   use specific drive read offset;
-C, --c2mode <int>       use specific C2ErrorMode, 0 (None), 1 (Mode294), 2 (Mode296), 3 (Auto);
-T, --test               detect read command;
--d8                     force D8h read command;
--be                     force BEh read command;

Different C2 error modes can be specified the following way:

  • 0 (None):
    CUETools.Ripper.Console.exe -C 0
  • 1 (Mode294):
    CUETools.Ripper.Console.exe -C 1
  • 2 (Mode296):
    CUETools.Ripper.Console.exe -C 2
  • 3 (Auto), default setting:
    CUETools.Ripper.Console.exe -C 3

CUERipper

After starting CUERipper.exe once and closing it, the CUERipper\settings.txt file can be edited for each drive and the C2 error mode specified.

  • Example with default setting C2ErrorMode 3 (Auto):
=  <DriveC2ErrorModes>
=    <item>
=      <key>
=        <string>ATAPI iHAS324 F</string>
=      </key>
=      <value>
=        <int>3</int>
=      </value>
=    </item>
=  </DriveC2ErrorModes>
  • Edited settings file, C2ErrorMode 0 (None)
=  <DriveC2ErrorModes>
=    <item>
=      <key>
=        <string>ATAPI iHAS324 F</string>
=      </key>
=      <value>
=        <int>0</int>
=      </value>
=    </item>
=  </DriveC2ErrorModes>

Remark: A possibility to modify the C2ErrorMode from the GUI will be added later on (#208).

There are some drives, where automatic detection of the C2ErrorMode
does not work. CUETools already contains a fix for specific drives,
where Mode294 does not work properly. However, there are still drives,
where setting the C2ErrorMode to a specific value helps.

- Add a setting for the C2ErrorMode
- Values for the drive specific setting "DriveC2ErrorModes" are:
  0 (None), 1 (Mode294), 2 (Mode296), 3 (Auto)
- CUETools.Ripper.Console.exe, add option:
    -C, --c2mode <int>  use specific C2ErrorMode,
                  0 (None), 1 (Mode294), 2 (Mode296), 3 (Auto);
@c72578 c72578 force-pushed the 2022-01-03_Add_setting_for_C2ErrorMode branch from 2e6b00b to 85a0bb9 Compare July 15, 2022 20:33
@c72578 c72578 merged commit 20a24f5 into gchudov:master Jul 20, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant