For your consideration, here you are Zeliard title recording. Sampled at 32000 Hz.

You can clearly hear the difference in the attack phase of one patch. This is due to a bit inaccurate TVA/TVF ramping time. But there is no any problem with PCM patches. And most of drums/hats patches are plain PCM samples.
And yes, FFT spectrum displays how noisy LA32 is.

sergm wrote:

For your consideration, here you are Zeliard title recording. Sampled at 32000 Hz. […]
Show full quote

For your consideration, here you are Zeliard title recording. Sampled at 32000 Hz.

______________

You can clearly hear the difference in the attack phase of one patch. This is due to a bit inaccurate TVA/TVF ramping time. But there is no any problem with PCM patches. And most of drums/hats patches are plain PCM samples.
And yes, FFT spectrum displays how noisy LA32 is.

Thank you for taking your time and recording those. I notice that your MUNT recording still has muffled percussion instruments compared to the CM-64 version, so then that means this is the best I can get with emulation, but I'm happy with this too, since the emulation is still relevant. Thank you again for sitting through my questions and helping AND for the awesome development to MUNT ^^

You are right, I've already said that 😀
Munt's wave generator performs computations with much better precision. But we recently got the die scans and the hope is to greatly improve thing towards being bit-perfect. BTW, I'm currently converting the WG to use native LA32 logarithmic integer numbers. Not sure how accurate it'll become, but the die shots should hopefully help. Watch for the future updates 😀

sergm wrote:

You are right, I've already said that 😀

Ah, well you probably did, but wasn't clear enough for me, haha.

sergm wrote:

Munt's wave generator performs computations with much better precision. But we recently got the die scans and the hope is to greatly improve thing towards being bit-perfect. BTW, I'm currently converting the WG to use native LA32 logarithmic integer numbers. Not sure how accurate it'll become, but the die shots should hopefully help. Watch for the future updates 😀

Wish you luck with your future endeavors =)

Thanks 😀
I just wanted to clarify that recordings well available 'round the net can differ from munt a lot more 😒

Just a heads-up for people not up to date:

http://sourceforge.net/projects/munt

Version 1.0 is available since Christmas. Thanks Sergey and Jerome :)

Well, actually, Windows distro files only so far...

Oh nice 😀 Will give it a spin and check it out!

Q for you - playing this http://www.queststudios.com/mt32midi/sq3_1.zip using the Munt MIDI player and this http://wiw.org/~jess/download/sq3music/SQ3_01 … ntroduction.mp3 in Winamp; should these sound the same?! I ask as they do not for me 🙁

Can I verify the SYX file is being used?

BTW - great to see a V1 release 😀

sergm wrote:

Well, actually, Windows distro files only so far...

WOW 😳

Well done. I'm hugely impressed with this release. Simple installation. User friendly UI. The LCD display is fantastic. Volume control. Loading ROMs to switch between MT-32 and CM-32L is a doddle.

Had a quick listen and can't spot any flaws to be honest...

Reckless wrote:

Q for you - playing this

Same issue. But the attached one works!

That one has SySex embedded inside the mid.

Yep, you're right - looks like I was on the right track thinking the custom instruments weren't making it to the device.

Cannot Install MT32Emu MIDI driver. There is no MIDI ports available.

robertmo wrote:

Cannot Install MT32Emu MIDI driver. There is no MIDI ports available.

Windows allows only 10 MIDI drivers, BAD luck 🙁

But see if you can delete entries like midiX=wdmaud.drv in the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Drivers32. Usually this crap appears after a USB-MIDI device get reconnected to a different USB port. And I've found no kernel MIDI driver that really needs that midiX=wdmaud.drv entry.

Reckless wrote:

Can I verify the SYX file is being used?

The point is in the "Pin Synth" option. When not checked, a MIDI session exists until an external application is connected or the MIDI player is playing a file. So by default, the MIDI player resets the synth after each file is played, including .syx files, until you set the "Pin Synth".
A "pinned" synth is like a real hardware unit. It remembers its state and need to be reset manually when needed.
I like the latter mode. A reset can easily be done adding a reset.syx file into the MIDI list when needed. But it's a user's choice. 😉

I just installed this and now it's complaining it can't find the ROM's yet I had them in the folder the last time I installed.

Where is it expecting the ROM's now? The INI says C:\WINDOWS like I told it too and the ROM's are there... I don't understand what's going on.

EDIT: copied it into SysWOW64 and now it's working... I guess the ROM's have to be in the same directory as the .DLL now?

The INI isn't used anymore and can be safely deleted. Use Options->ROM Configuration.

Ah okay, thanks... And well done with making MUNT actually sound as close as possible to the MT-32. I have nightmares still of what MUNT used to sound like..

sergm wrote:

The INI isn't used anymore and can be safely deleted. Use Options->ROM Configuration.

That is good. How are the preferences stored, now? XML in the user folder?

Qt features a special facility QSettings. It stores settings in a platform-dependent way. Also usage of text files can be enforced. In the case of Windows, it's the system registry. Both user and system hives are supported. XML format is used on Mac. 😜
http://qt-project.org/doc/qt-4.8/qsettings.html