Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Graphic Research SFC Support] Derby Jockey 2 doesn't export correctly #457

Open
N-SPC700 opened this issue Apr 20, 2024 · 1 comment
Open
Labels

Comments

@N-SPC700
Copy link

Environment details

  • Operating System+version: Windows 10 20H2
  • VGMTrans version: (The program does not specify a version, but the files of this version date to 2021)
  • Game ROM/music dump name and sha256: Derby Jockey 2 - Staff Roll (21 Staff Roll.spc), SHA-256: 9590B687DDEAC2D4B42523D6D582E9A37830EFC09BB935C3EDB22D923DDC209A (File comes from Zophar's SPC rip of the game)

Describe the bug

Loading the ending SPC rip of Derby Jockey 2 causes the lead channel to be missing in the export. The echo channel is there, and so are all the others, but the lead is missing for some odd reason. Log mentions a "Unknown Event - 0xCF".

Steps to reproduce

  1. Load SPC
  2. Export MIDI (optional: save sf2 samples)
  3. load it in a program of choice
  4. Lead channel should be missing and log should report a Unknown Event of value 0xCF.

Expected behaviour

Loading the export should include all channels, and the event error should probably not happen.

Additional context

Attempting to search for "Graphic Research" related issues or commits returns nothing but the readme. Some code related stuff from a manual search seems to be handled as "GraphicRes", but using this term in the automatic search turns up nothing

Logs

Click to expand log

image
(I can't give an actual copy-pastable or uploadable log from the program's GUI aside from screenshotting.)

@N-SPC700 N-SPC700 added the bug label Apr 20, 2024
@N-SPC700
Copy link
Author

N-SPC700 commented Apr 20, 2024

I realized I'm using an absolutely ancient version of VGMTrans. It doesn't seem to matter, though, since the error persists in the latest build (commit b6a6568). I'm not sure what caused this issue, though.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant