Skip to content

Conversation

@Malkierian
Copy link
Contributor

@Malkierian Malkierian commented May 17, 2025

This reverts commit feea299.

Also applies rupee screech fix LL provided to 2ship (HarbourMasters/2ship2harkinian#1154). LL mentioned having found this fix originally on SoH because of having the octave shift option enabled, and as pointed out in the 2ship PR, it completely fixed the screech even on 32khz.

Build Artifacts

}
std::unique_lock<std::mutex> Lock(audio.mutex);
// AudioMgr_ThreadEntry(&gAudioMgr);
// 528 and 544 relate to 60 fps at 32 kHz 32000/60 = 533.333..
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
// 528 and 544 relate to 60 fps at 32 kHz 32000/60 = 533.333..
// 528 and 560 relate to 60 fps at 32 kHz 32000/60 = 533.333..

stale comment?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No, 544 is the accurate number for the math, but the define was 560 from the beginning as far as I can tell. Doesn't seem to negatively impact it to leave it at 560, as that's what it is in 2ship as well.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think the point is that ideally it would be 544, but SoH/2ship aren't in an ideal state, which is why 560 is what's actually used.

@Malkierian Malkierian merged commit be22c02 into HarbourMasters:develop Jun 19, 2025
6 checks passed
@Malkierian Malkierian deleted the 32khz-mk-ii branch June 19, 2025 20:34
krazyjakee pushed a commit to krazyjakee/OOT that referenced this pull request Sep 6, 2025
…asters#5234) (HarbourMasters#5508)

This reverts commit feea299.

Also applies rupee screech fix LL provided to 2ship.
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

Successfully merging this pull request may close these issues.

2 participants