libretro / libretro/libretro-database

Directory Scan validates bin/cue compressed in 7zip, but rejects them after extraction

Open
#1,513 11 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
1.4k
Forks
877
Avg merge
3d 1h
Merged PRs (30d)
24

Description

I have a working Road Rash rom file, and both tracks MD5 matches with redump data base.

Image

But using Import Content -> Scan Directory I can't add this rom to the playlist.

All of the other CD's from the same source can be added normally. I also tried redownloading Road Rash from other sources and faced the same problem.

The strange thing I noticed is that it can be added normally while it is still inside of 7z archive, but can't be added right after extraction.

Using RetroArch 1.19.1 on M1 mac.
DB is updated via Main menu -> online update -> Update Databases

Log:

[INFO] [Scanner]: Scanning content: "/Users/tony/Roms/new sega cd/"..
[INFO] [Scanner]: 1/3: Road Rash (USA).cue..
[INFO] [Scanner]: Scanning of directory finished.

Contains of Road Rash (USA).cue:

FILE "Road Rash (USA) (Track 1).bin" BINARY
  TRACK 01 MODE1/2352
    INDEX 01 00:00:00
FILE "Road Rash (USA) (Track 2).bin" BINARY
  TRACK 02 AUDIO
    INDEX 00 00:00:00
    INDEX 01 00:02:00

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the failure with the extracted Road Rash (USA).cue through RetroArch's Import Content → Scan Directory, then compare it with the same cue inside the 7z archive. Use the supplied scan log and cue contents to trace why the extracted files are rejected; done means the extracted copy is added to the playlist like the archived copy.

Written by the indexing model from the issue text.

Assessment

Domain
databases
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.