[Feature Request] NSZ support #294

New Issue

2024-11-21T21:22:07Z

fpiesche commented

2024-11-21 21:22:07 +00:00

(Migrated from github.com)

Overview

It would be extremely useful for saving storage space if Ryujinx would support running content from compressed .nsz files. The zstd algorithm used to compress these is lossless, and the nsz format as a whole allows for bit-identical decompression, so the files are of archival quality. zstd is also designed for fast decompression to minimise performance overhead and is commonly used for other emulation projects (e.g. in MAME's chd format which is widely supported in emulators for disc-based systems).

Smaller details

There is an example implementation in Python over at https://github.com/nicoboss/nsz.

Nature of request

Additional ROM file format support

Why would this feature be useful?

Uncompressed NSP files are very large in some cases so this could save significant amounts of space for larger archives.

Trimmed XCIs would be an alternative option here, but either need updates to be stored in separate, uncompressed NSP files or, when updates are merged into the XCI, require rebuilding if new updates are released. Furthermore, trimmed XCIs are not well suited to preservation as AFAIK they cannot easily be restored to match the original dump.

### Overview It would be extremely useful for saving storage space if Ryujinx would support running content from compressed .nsz files. The zstd algorithm used to compress these is lossless, and the nsz format as a whole allows for bit-identical decompression, so the files are of archival quality. zstd is also designed for fast decompression to minimise performance overhead and is commonly used for other emulation projects (e.g. in MAME's `chd` format which is widely supported in emulators for disc-based systems). ### Smaller details There is an example implementation in Python over at https://github.com/nicoboss/nsz. ### Nature of request Additional ROM file format support ### Why would this feature be useful? Uncompressed NSP files are very large in some cases so this could save significant amounts of space for larger archives. Trimmed XCIs would be an alternative option here, but either need updates to be stored in separate, uncompressed NSP files or, when updates are merged into the XCI, require rebuilding if new updates are released. Furthermore, trimmed XCIs are not well suited to preservation as AFAIK they cannot easily be restored to match the original dump.

MetrosexualGarbodor commented

2024-11-21 21:22:21 +00:00

(Migrated from github.com)

no

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: MeloNX/Ryujinx-ryubing#294