Re: MUNT's Crash Cymbal sounding-out behavior when using MT-32 v1.07 control ROM
Posted on 2022-01-08, 19:29
Anyway, I suppose it is emulated properly now. See Issue #82 on Github.
Re: Munt issue with Windows 10
Posted on 2022-01-06, 05:30
Well, yes, there is definitely a problem with the device registry on this system, otherwise the installer would work. I suppose, dosbox is not the only MIDI app of interest, right? If yes, a build with the integrated mt32emu would be a better solution.
Re: MUNT's Crash Cymbal sounding-out behavior when using MT-32 v1.07 control ROM
Posted on 2022-01-05, 16:18
That's what I could call "subtle" 😀
Re: MUNT's Crash Cymbal sounding-out behavior when using MT-32 v1.07 control ROM
Posted on 2022-01-04, 18:27
Gah, it really is broken 🙁 Thanks for noticing, it's kind of a subtle thing.
Re: Test program for package manager
Posted on 2021-12-11, 17:55
Still, adding a bit of autotests is a good idea, and I hope I'll be able to find time for that next year 😀
Re: Test program for package manager
Posted on 2021-12-11, 17:54
Yes, this is how it always works in our world, sadly.
Re: Munt issue with Windows 10
Posted on 2021-12-11, 10:20
So much for the "proper" way of installing drivers. Perhaps, we could study the installer log and probably fix the system registry (I blame it due to lack of knowledge about the real cause), but suppose this is not fun.
Re: Munt issue with Windows 10
Posted on 2021-12-11, 08:08
Well, my research is stuck. The error seems to be this one: ERROR_NO_MORE_ITEMS 259 (0x103) No more data is available. But I'm not sure what data is meant. Yet I cannot reproduce it on a clean system after upgrade to 21H2.
Re: Munt issue with Windows 10
Posted on 2021-12-11, 07:57
Hmm, no idea what's wrong. Also, the error code looks strange, unlike all the other codes I've got from PnP manager before, so will have to research a bit. In the meantime, clarification: this issue is about infinstall tool; it relies on the system PnP manager, hence God knows how it works; the …
Re: Munt issue with Windows 10
Posted on 2021-12-11, 07:11
Thanks for pointing this out, I'll look into it.
Re: F-117 2.0 Munt problem
Posted on 2021-10-14, 04:46
It's quite possible some of those "computer music" sound effects are used there too. Well, I did it right when avoided quoting that "Internet" who said that this game required old-gen device 😒
Re: F-117 2.0 Munt problem
Posted on 2021-10-12, 09:07
Presumably, this is old MT-32 vs. new MT-32 issue (as some say on the Internet, I don't want to quote as googling is easy). What I don't completely understand is why the game worked fine in early days of munt when it was unable to emulate old-gen MT-32 properly. @JozMk.II Could you try it with …
Re: Some Channel mode and Control change msgs - any idea what the Controller-Nrs are?
Posted on 2021-07-12, 08:20
llm wrote on 2021-07-12, 08:02: thank your for the source link - as usual - the best documentation Kind of. If I was cloned, I'd write up smth in the wiki... *sigh*
Re: Some Channel mode and Control change msgs - any idea what the Controller-Nrs are?
Posted on 2021-07-12, 07:53
these are hardcoded calls in the game that im reversing - im trying to figure out what the controller-nrs are and what the values or value-ranges are allowed If you are interested in details of the MT-32 MIDI implementation, then the standard MIDI specs aren't particularly useful. I'd recommend to …
Re: Strange Bender range address offset calculation
Posted on 2021-07-11, 17:16
Yes, the pattern PlayMsg cmd_buf: B6 07 7F <-- func0 with 0xB0 Base PlaySysex: F0 41 10 16 12 03 00 54 70 39 F7 <-- func1 (with the != 10) looks very much like --value is nothing more than an adjustment for the standard MIDI channel mapping in MT-32 MIDI channel 2-9 -> part 1-8 Since we use 0-based …
Re: Strange Bender range address offset calculation
Posted on 2021-07-11, 12:03
I don't know for sure, as I didn't bother looking at the full disasm code. But again, the magic number "10" here would suggest that the code attempts to deal with the rhythm channel specially. As we both noted, part 9 does not exist, but there is a rhythm part that is specially addressed. And in …
Re: Strange Bender range address offset calculation
Posted on 2021-07-11, 09:22
but address byte1 is always 0 so its 0x03 - base address 0x00 - address byte1 0x?4 - address byte2, only the high nibble of this address byte is changed, low nibble is always 4 I still see no problems with that, assuming the parts are mapped to MIDI channels 2-9, and the game does not send bogus …
Re: Strange Bender range address offset calculation
Posted on 2021-07-11, 07:55
Not sure, do you have the MT-32 MIDI implementation handy? If not, see http://www.synthzone.com/midi/roland/mt32/mt32-2.txt
Re: Strange Bender range address offset calculation
Posted on 2021-07-11, 07:43
I don't think this is wrong. Let us look at the address mapping of the patch temp area: Whole Part (accessible on unit#) Start Address Description ------------- ---------------------------- 03 00 00 Patch Temp Area (part 1) 03 00 10 Patch Temp Area (part 2) : 03 00 60 Patch Temp Area (part 7) 03 00 …
Re: Installation Error: File copying error
Posted on 2021-07-03, 06:46
Infinstall_x64.exe install didn't work, it gave me this error: Cannot install MT32Emu MIDI Driver; Error: e0000247. Argh, right... It needs a signed driver first time you install it, so the correct spell was "infinstall_x64.exe install -sign" actually. Sorry about that (although that's all written …
Page 1 of 45