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

Firmware 1.11.0 Jurassic Park 2 sound corrupted #252

Open
kscorpionx opened this issue Apr 13, 2024 · 3 comments
Open

Firmware 1.11.0 Jurassic Park 2 sound corrupted #252

kscorpionx opened this issue Apr 13, 2024 · 3 comments

Comments

@kscorpionx
Copy link

kscorpionx commented Apr 13, 2024

After playing 30 minutes or more with the sd2snes and then playing Jurassic Park 2 The sound of the plane in the intro sounds corrupt, this does not happen if you play Jurassic Park for the first few minutes, it was tested with Snes 2chip and a Snes 1chip jr.

@Ramsis-SNES
Copy link

After playing 30 minutes or more with the sd2snes

You mean, 30+ minutes of any game? Or 30+ minutes of Jurassic Park 2, and then resetting the game so it starts from the beginning?

What sd2snes hardware revision do you have? Do you play in 50 or 60 Hz (or PAL/NTSC)? Does the ROM region match your video mode? Also, could you make a video of the scene with the glitched sound effect for reference?

@kscorpionx
Copy link
Author

After playing 10 minutes with any game this problem occurs but I found that if you don't press start and let the intro repeat a few times this problem doesn't happen, I am playing on 60mz ntsc and yes this rom matches my region , I am using an sd2snes. made by ky technologies rev x, i know this is chinese but i want to buy a krikzz so i want to know if this doesn't happen with that one. Here is the video with the failure, the plane sounds distorted.

JP2.Sound.glitch.mp4

@Ramsis-SNES
Copy link

Sorry, I can't seem to reproduce it.

Then again, I don't know what games you were playing other than the one in question, and how you even got back to the menu (soft reset? Console reset? Power off/power on?). For me, there's too much guesswork involved and too much time to be invested trying again and again, so I'm afraid I'll call it quits on this one.

To be perfectly honest with you, I don't even know I'm actually hearing what you call a "failure" in your video. The sound effect sounds a bit boomy, but I wouldn't really call it a glitch in comparison to my own tests before I would have heard what it sounds like on your setup when it's not glitching out. (You might want to make another video of that but I don't really think it's worth the effort, unfortunately.)

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

No branches or pull requests

2 participants