[Problem] MPF does not pass the speed parameter to Aaru #597

New Issue

Closed

opened 2026-01-29 16:19:09 +00:00 by claunia · 2 comments

claunia commented 2026-01-29 16:19:09 +00:00

Owner

Copy Link

Originally created by @CookiePLMonster on GitHub (Aug 23, 2023).

Originally assigned to: @mnadareski on GitHub.

Version
What version are you using?

• Stable release (2.6.3) - at the time of submitting this report it's equivalent to the WIP release

Build
What runtime version are you using?

• .NET Framework 4.8 running on Windows 10

Describe the issue
When dumping CD-ROM, the --speed parameter does not get passed from MPF to Aaru, despite appearing in the Parameters field. Although tests have been performed with the --private flag, this issue happens irrespectively of it.

To Reproduce
Steps to reproduce the behavior:

1. Open MPF. In my test, the dumping drive is "E:" and the output path is "C:\Redump\Dumps\test-speed\test-mpf.aaruf".
2. Set Aaru as the dumping program, set Speed to 8.
3. Observe that the Parameters field says media dump --force True --private True --speed 8 --retry-passes 500 "E:" "C:\Redump\Dumps\test-speed\test-mpf.aaruf".
4. Start dumping, notice it starts dumping at MAX speed. Cancel dumping and inspect Aaru's log to find the following - passed command line parameters lack the --speed param:

################# Program information ################
Aaru 5.3.2+f4fef21d
Running in 64-bit
Running as superuser: No
Command line: aaru.dll media dump --force True --private True --retry-passes 500  test-mpf.aaruf

5. Repeat the above steps but using aaru.exe from the command line. Notice that it starts dumping at 8x speed. Cancel dumping and inspect the log again to find all command line parameters passed properly:

################# Program information ################
Aaru 5.3.2+f4fef21d
Running in 64-bit
Running as superuser: No
Command line: aaru.dll media dump --force True --private True --speed 8 --retry-passes 500  test-cli.aaruf

Expected behavior
The --speed parameter gets passed to Aaru correctly.

Originally created by @CookiePLMonster on GitHub (Aug 23, 2023). Originally assigned to: @mnadareski on GitHub. **Version** What version are you using? - [x] Stable release (2.6.3) - at the time of submitting this report it's equivalent to the WIP release **Build** What runtime version are you using? - [x] .NET Framework 4.8 running on **Windows 10** **Describe the issue** When dumping CD-ROM, the `--speed` parameter does not get passed from MPF to Aaru, despite appearing in the **Parameters** field. Although tests have been performed with the `--private` flag, this issue happens irrespectively of it. **To Reproduce** Steps to reproduce the behavior: 1. Open MPF. In my test, the dumping drive is `"E:"` and the output path is `"C:\Redump\Dumps\test-speed\test-mpf.aaruf"`. 2. Set Aaru as the dumping program, set Speed to 8. 3. Observe that the **Parameters** field says `media dump --force True --private True --speed 8 --retry-passes 500 "E:" "C:\Redump\Dumps\test-speed\test-mpf.aaruf"`. 4. Start dumping, notice it starts dumping at MAX speed. Cancel dumping and inspect Aaru's log to find the following - passed command line parameters lack the `--speed` param: ``` ################# Program information ################ Aaru 5.3.2+f4fef21d Running in 64-bit Running as superuser: No Command line: aaru.dll media dump --force True --private True --retry-passes 500 test-mpf.aaruf ``` 5. Repeat the above steps but using `aaru.exe` from the command line. Notice that it starts dumping at 8x speed. Cancel dumping and inspect the log again to find all command line parameters passed properly: ``` ################# Program information ################ Aaru 5.3.2+f4fef21d Running in 64-bit Running as superuser: No Command line: aaru.dll media dump --force True --private True --speed 8 --retry-passes 500 test-cli.aaruf ``` **Expected behavior** The `--speed` parameter gets passed to Aaru correctly.

claunia added the bug label 2026-01-29 16:19:09 +00:00

claunia closed this issue 2026-01-29 16:19:10 +00:00

claunia commented 2026-01-29 16:19:10 +00:00

Author

Owner

Copy Link

@mnadareski commented on GitHub (Aug 27, 2023):

Did this only occur with a single disc or with multiple? And what sort of disc(s) did you try to use?

@mnadareski commented on GitHub (Aug 27, 2023): Did this only occur with a single disc or with multiple? And what sort of disc(s) did you try to use?

claunia commented 2026-01-29 16:19:11 +00:00

Author

Owner

Copy Link

@mnadareski commented on GitHub (Aug 27, 2023):

Disregard. The issue has been identified.

@mnadareski commented on GitHub (Aug 27, 2023): Disregard. The issue has been identified.

claunia referenced this issue 2026-01-29 16:25:08 +00:00

[PR #599] [MERGED] Pull PS3 Firmware Version #1056

Sign in to join this conversation.

No Branch/Tag Specified

Branches Tags

master

rolling

3.6.0

3.5.0

3.4.2

3.4.1

3.4.0

3.3.3

3.3.2

3.3.1

3.3.0

3.2.4

3.2.3

3.2.2

3.2.1

3.2.0

3.1.9

3.1.8

3.1.7

3.1.6

3.1.5

3.1.4

3.1.3

3.1.2

check-rolling

ui-rolling

3.1.1

3.1.0

3.0.3

3.0.2

3.0.1

3.0.0

2.7.5

2.7.4

2.7.3

2.7.2

2.7.1

2.7.0

2.6.6

2.6.5

2.6.4

2.6.3

2.6.2

2.6.1

2.6

2.5

2.4

2.3

2.2

2.1

2.0

1.18

1.17.1

1.17

1.16.1

1.16

1.15

1.14

1.13

1.12.2

1.12.1

1.12

1.11

1.10

1.07

1.06

1.05.1

1.05

1.04b

1.04a

1.04

1.03

1.02b

1.02

1.01d

1.01c

1.01b

Labels

Clear labels

bug

duplicate

enhancement

good first issue

help wanted

invalid

pull-request

Mirrored from GitHub Pull Request

question

regression

wontfix

No Label bug

Milestone

No items

No Milestone

Projects

Clear projects

No project

Assignees

Clear assignees

claunia

No Assignees

1 Participants

Notifications

Subscribe

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: SabreTools/MPF#597