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

Compatibility with FXHammer #23

Open
basxto opened this issue Mar 9, 2022 · 2 comments
Open

Compatibility with FXHammer #23

basxto opened this issue Mar 9, 2022 · 2 comments

Comments

@basxto
Copy link

basxto commented Mar 9, 2022

https://github.com/DevEd2/FXHammer-Disasm

FXHammer has two RAM registers (Ch2Flags, Ch4Flags) that it uses to see if CH2 or CH4 is currently used by the music driver.
It would be practical to use those, FXHammer doesn’t touch those channels when the least significant bit isn’t set.

@SuperDisk
Copy link
Owner

hUGEDriver already supports muting channels for use with a sound FX driver. Basically what you do is call hUGE_mute_channel before invoking the sound effect, and unmute after. This is compatible with FX Hammer and similar engines like CBT-FX.

@basxto
Copy link
Author

basxto commented Mar 11, 2022

FXHammer looks like being designed to work the other way around.
It checks if there is currently music playing on that channel and only uses it if it’s unused.
But I haven’t checked if the music driver engine does something similar.

FXHammer has a knee point which marks at which point it’s fine to interrupt the sound, but I haven’t found any code for that in FXHammer. So it’s possible that the music driver does something similar and that they coordinate who uses the channel.

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