-
Notifications
You must be signed in to change notification settings - Fork 723
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
13 changed files
with
424 additions
and
21 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
ead9e56
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The newest preview will report an error when loading any chd file. The last rolling build is normal.
ead9e56
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
all of my games are in chd format and just tested here, they're working good here with the latest version.
Please verify your dump;
Right click > properties > verify
Red results > bad dump green results are good dump.
also, do check the log to see what is going on on your end while booting the game.
ead9e56
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Indeed, I didn't make it clear. I just tested it again and finally found the problem.
Currently, the latest preview version can only run properly if the chd is compressed with default parameters. If the compression algorithm is specified during compression, the loaded chd will report an error.
An example:
with default parameters compress a chd file:
chdman -i “Crash Bash (USA).cue” -o "Crash Bash (USA).chd"
check the obtained info of Crash Bash (USA).chd
Hunks Percent Name
this chd file works fine.
But when we specify the compression algorithm as cdzs or cdlz
chdman createcd -c cdzs -i “Crash Bash (USA).cue” -o "Crash Bash (USA)_zstd.chd"
or
chdman createcd -c cdlz -i “Crash Bash (USA).cue” -o "Crash Bash (USA)_lzma.chd"
The obtained two 100% encoded lzma or zstd chd files will cause errors when read by duckstation.
Even if we specify multiple mixed encodings,like this:
chdman createcd -c cdlz,cdzs -i “Crash Bash (USA).cue” -o "Crash Bash (USA)_mix.chd"
the resulting chd file will report an error.
The reason why the encoding format is specified in practice is that although lzma encoding has a high compression rate, it has a slow decoding speed. zstd encoding has the fastest decoding speed. However, chdman does not enable zstd encoding under default parameters for some historical compatibility reasons.
In addition, everything works fine with this commit.
ead9e56
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should be fixed now.