romvault_comparison
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| romvault_comparison [2023/03/09 02:43] – [Table] johnsanc | romvault_comparison [2023/07/04 15:26] (current) – johnsanc | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ====== RomVault vs. clrmamepro ====== | ====== RomVault vs. clrmamepro ====== | ||
| - | RomVault is constantly changing. New features, enhancements, | + | RomVault is constantly changing. New features, enhancements, |
| | ^ RomVault | | ^ RomVault | ||
| Line 10: | Line 10: | ||
| | In-app contextual help | ✅ Yes - but somewhat limited, wiki content is more comprehensive | | In-app contextual help | ✅ Yes - but somewhat limited, wiki content is more comprehensive | ||
| | User-defined favorites for processing scope | ✅ Yes | ❌ No | | | User-defined favorites for processing scope | ✅ Yes | ❌ No | | ||
| - | | Multi-DAT processing | + | | Multi-DAT processing |
| | Speed of batch operations | | Speed of batch operations | ||
| | RAM usage | ❌ Heavy - Approximately 1GB per million files managed | | RAM usage | ❌ Heavy - Approximately 1GB per million files managed | ||
| Line 41: | Line 41: | ||
| | 7z archives | | 7z archives | ||
| | RAR archives | | RAR archives | ||
| - | | CHD files | ✅ Yes - CHD v1-4 native, v5 with chdman exe | ✅ Yes - with external chdman exe | | + | | CHD files | ✅ Yes - without needing |
| + | | Multi-threaded CHD verification | ||
| | ROM headers | | ROM headers | ||
| | Archive header scan (CRC) | ✅ Yes - optional for quick intial scanning | | Archive header scan (CRC) | ✅ Yes - optional for quick intial scanning | ||
| Line 49: | Line 50: | ||
| | Scan archives as files | ❌ No - unless you use an RV instance in Files Only mode | ✅ Yes - if the DAT specifies forcepacking unzip | | | Scan archives as files | ❌ No - unless you use an RV instance in Files Only mode | ✅ Yes - if the DAT specifies forcepacking unzip | | ||
| ^ Fixing and Rebuilding | ^ Fixing and Rebuilding | ||
| - | | Approach | + | | Fixing and rebuilding approach |
| | Collection-wide sources for fixes | ✅ Yes - core of design, tree selections determine scope | ❌ No - sources for must be managed by " | | Collection-wide sources for fixes | ✅ Yes - core of design, tree selections determine scope | ❌ No - sources for must be managed by " | ||
| | Configurable fixing scope between jobs | ✅ Yes - core of design, tree selections determine scope | ❌ No - must change settings each time | | | Configurable fixing scope between jobs | ✅ Yes - core of design, tree selections determine scope | ❌ No - must change settings each time | | ||
| + | | Fix based on size + CRC | ✅ Yes - but not recommended | ||
| + | | Fix based on size + CRC + MD5 + SHA1 | ✅ Yes - standard operation | ||
| | Uncompressed files | ✅ Yes | ✅ Yes | | | Uncompressed files | ✅ Yes | ✅ Yes | | ||
| | TorrentZip archives | | TorrentZip archives | ||
| Line 61: | Line 64: | ||
| | Rename / Move complete archivies without recompress | | Rename / Move complete archivies without recompress | ||
| | Backup removed files | ✅ Yes - files are moved to ToSort | | Backup removed files | ✅ Yes - files are moved to ToSort | ||
| + | | Delete uncollected files not needed by DATs | ❌ No - but this is to prevent user error resulting in data loss | ✅ Yes - optional setting | ||
| + | | Delete files already collected by DATs | ✅ Yes - duplicate collected files are deleted from ToSort directories | ||
| | Double check deletion | | Double check deletion | ||
| - | | Fix based on size + CRC | ✅ Yes - but not recommended | ||
| - | | Fix based on size + CRC + MD5 + SHA1 | ✅ Yes - standard operation | ||
| ^ Reporting | ^ Reporting | ||
| | Fix DATs | ✅ Yes | ✅ Yes | | | Fix DATs | ✅ Yes | ✅ Yes | | ||
| + | | Auto-create Fix DATs after task | ❌ No - at least not yet… | ||
| | Have / Miss Lists | ❌ No - at least not yet… | | Have / Miss Lists | ❌ No - at least not yet… | ||
| | Set level metrics | | Set level metrics | ||
| Line 78: | Line 82: | ||
| | Store entire DAT contents as a single set | ✅ Yes - with Single Archive settings | | Store entire DAT contents as a single set | ✅ Yes - with Single Archive settings | ||
| | Store single-file sets without subdirectories | | Store single-file sets without subdirectories | ||
| - | | Storage directory name from DAT info | ✅ Yes - can use DAT name or description | + | | Storage directory name from DAT info | ✅ Yes - can use DAT name or description |
| - | | Storage directory name from DAT location | + | | Storage directory name from DAT location |
| | Override forced packing setting from DAT header | | Override forced packing setting from DAT header | ||
| | Override forced merging setting from DAT header | | Override forced merging setting from DAT header | ||
| + | | Multiple DATs for a single ROM path | ✅ Yes - DATs are merged if no naming conflicts | ||
| | Multiple ROM paths for a single DAT | ❌ No - but you can use an [[merging_drives|rclone union mount]] | | Multiple ROM paths for a single DAT | ❌ No - but you can use an [[merging_drives|rclone union mount]] | ||
| | 1G1R Mode | ❌ No - at least not yet… | | 1G1R Mode | ❌ No - at least not yet… | ||
romvault_comparison.1678329780.txt.gz · Last modified: 2023/03/09 02:43 by johnsanc