Closed dquenne closed 10 months ago
Hi, I'm sorry for my late response.
I think the feature you suggested is great.
You're right; it would probably be better to include the contents of opm.ts in ym-voice. Could you possibly send a pull request to ym-voice as well?
Thank you very much.
Yup no problem! I’m out of town right now but should be able to PR that in a couple weeks. Thanks!
@okaxaki Got around to adding file generation methods to ym-voice
here: https://github.com/digital-sound-antiques/ym-voice/pull/1. I've tested changes to this branch using the new ym-voice
method and everything is working as expected, with much simpler code in this branch.
Thank you very much! I have combined this with the new patched ym-voice and verified that it works as expected. I will merge this pull request. After that, I will change the reference of ym-voice in package.json to 0.2.0.
I have modified
OPNToYM2413Converter
to optionally log a.opm
voice file for VOPM for a given VGM file.OPNToYM2413Converter
already does most of the work to compile and normalize voices, so this is a pretty trivial change.If this change seems reasonable, I can move the new contents of the
opm.ts
file intoym-voice
instead, since that seems like a more appropriate separation of concerns. This code works for my needs as-is, though, so I want to get some confirmation that this feature is acceptable before going through those upstream changes.Another note: some OPM values are hard-coded, because they are not represented in
OPNVoice
.An example
.opm
file I generated from running