Dominus wrote:

Then you really should get the latest munt driver to be as fair as possible 😉

From my testing so far, whatever version is included with Ykhwong's latest build, has nothing to worry about. I'm quite impressed. It even caters for the differences between MT-32 (Old) and CM-32L.

Actually, Ykhwong relies on the latest munt sources. BTW, he added load/save state functionality and made the number of partials configurable by the user.

P.S. Those differences between LA unit models are recognized because of loading some data from the control ROM. Sadly, those quirks of the old MT-32 are not reproduced properly by now. 🙁

First and foremost, thanks to the mt-32 emulator developers for their hard work to bring us this wonderful emulator 😀.
Bug report: it seems the last commit (https://github.com/munt/munt/commit/a1478d243 … 99391963c64f0b1) broke Gods (maybe others?). Whenever a lot of sounds are to be played (and sometimes randomly) my DosBox crashes when using code from that commit (a sure fire way to test it is in the second level: grab the skull that shoots the star (it's almost at the beginning, after the ladder, to the right) and when it shoots DosBox crashes). The problem went away when I reverted to the previous code (https://github.com/munt/munt/commit/34d7bd656 … 969acbbdbaf0cbd).

The https://github.com/munt/munt/commit/e5d7c9a63 … 6217ce9292eb0d5 commit seems to have fixed it, thanks 😀

Ah, thanks for quick reporting, bloodbat 😀 Yep, that offending commit appears a bit rushed...
Unfortunately, I haven't got the notification from VOGONS in time 🙁
Seems like I need to press "Watch this topic for replies" every time I post a message...

This problem:
Munt Reloaded - Development
has been fixed by the new build as well. Good job. However, I have discovered a new problem (that existed in the previous version as well 😀).

Attached find INIT.SYX plus a Standard MIDI File from King's Quest V. MUNT plays the custom "Armor" timbre with a loop when it should not.

Eek! This is really weird if so 😕 but I'll try to clarify...

What can I say, THANKS again, NewRisingSun 😀

No, thank you for fixing it.

For ubuntu users: this ppa has the latest git changes (auto built buildbot) to the mt32 library embedded in the dosbox svn (well, except the actual diff patch to dosbox itself, if that changed recently - which i know it hasn't ATM).

https://code.launchpad.net/~i30817/+recipe/dosbox-patched

For info:

https://github.com/blog/1302-goodbye-uploads

Nevermind... I could upload stuff to the repo anyway 😀

But KG seems finally decided to grant me freedom on making releases and the corresponding access to SF page. (though, maybe this was a joke %S)

Another (but great) news: LA32 have been decapped 😀))

--- Status update ---

- Changes in the repo:
master branch renamed to legacy
mt32emu_qt -> master

- KingGuppy added more ROMs (though, few still unavailable)
- DOSBox patch works with legacy only but I'm working on the quick update

sergm wrote:

Nevermind... I could upload stuff to the repo anyway 😀

But KG seems finally decided to grant me freedom on making releases and the corresponding access to SF page. (though, maybe this was a joke %S)

Thanks a lot for all of your work 😀
Any way we could get the binary drivers back? (GitHub has, indeed, disabled downloads)

Don't really mention, I just love this work as all guys from our team 😀
FYI, GitHUB has disabled _uploads_ only. So, the download page is still available (though, hidden in their UI):

https://github.com/sergm/munt_devel/downloads

Anyway, I'm on the final preparation for long-awaited upcoming release.

That's great 😀
I know downloads are hidden there, but I already got that one 😉

Cool!
Can you tell us what's in store for munt due to the decapping?

It's difficult to tell now since the analysis at the very beginning phase. Though, I suppose we should expect bit-perfect emulation eventually.

If anyone wants to see a decap image, here you go:

https://dl.dropbox.com/s/ellocl0ig0dfc9v/LA32 … -res_3.jpg?dl=1

This is not perfect, but I was able to image it well enough to extract the ROM tables. These are nearly identical to the Yamaha OPL2/3 tables from https://docs.google.com/document/pub?id=18IGx … oAqoIn1rIm42nwo .

They can be generated with the following equations:

the table that has a very visible curve:
f(x) = x == 0 ? 8191 : -1024*log(sin((x+0.5)*pi/1024))/log(2)

The other table has two tables within it:
g(x) = (1-2^(-(x+1)/512))*8192-1
g_delta(n) = 15-(g[n]-g[n-1])