VOGONS

Common searches


Search results

Display options

Re: Installation Error: File copying error

in MT-32 General
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 …

Re: Installation Error: File copying error

in MT-32 General
I copied the mt32emu.dll to the system32 folder, and the mt32emu_x64.dll to the syswow64 folder, renaming it to mt32emu.dll like you said, and then restarted my computer for good measure. Sadly, this is not what I said. Thanks to Microsoft, System32 contains 64-bit files and syswow64 in contrast - …

Re: Installation Error: File copying error

in MT-32 General
Is there a way to download that file individually and manually copy it there? Sure, you can download a dedicated package with the driver only from here . Moreover, the driver DLLs must be installed with the package into Program Files/munt//mt32emu_win32drv where you should be able to copy it from. …

Re: Installation Error: File copying error

in MT-32 General
That's a rare problem, I'd say. This error message is shown when the 64-bit MIDI driver DLL (mt32emu.dll) cannot be copied to the Windows System32 directory for any reason. See if your user has permissions to write there (perhaps, some AV stuff blocking access?), or maybe an older version of the …

Re: Need help to disect some Sysex Messages

in MT-32 General
this case seem to be easy - there is a simple algorithm that creates PatchTemporaryArea/Bender-range set msgs - and it seems that the calculation is just buggy - sometimes the msg size is wrong and the wrong value is also calculated inside - seem to be some sort of overflow of the logic Oh, yeah. …

Re: Need help to disect some Sysex Messages

in MT-32 General
time to understand why the game sends this wrong value and the incomplete message Not sure this is possible :) But a few common reasons do exist. Typically, the composer works with a different hardware that may send some bogus data. It may happily remain unnoticed unless it disturbs the audio …

Re: MUNT Midi Recording Issue

in MT-32 General
Yes, I mean exactly having a single "init" recording with just SysExes. But that will work if the game only loads custom timbres once at startup, of course. Some games are known to send timbres per tune, and rarely, even while playing a tune.

Re: MUNT Midi Recording Issue

in MT-32 General
Great, I'm glad you figured it out. BTW, I have one more tip on MIDI recording. When a game uploads new tones at the very startup only (which is a quite common case), you may make a recording of that timbre bank just once. To make other recordings sound "correct", you may merely prepend that SysEx …

Re: MUNT Midi Recording Issue

in MT-32 General
Checked MIDI recorder on Windows and found no problems. Obviously, when I start recording after the initial bunch of SysExes has passed already, the captured MIDI sounds weird. But when I start recording before starting a game, everything is dandy. Maybe ScummVM sends the SysEx bank differently …

Re: MUNT Midi Recording Issue

in MT-32 General
Well, if rolling back does not help, it seems that the problem lays in something different. The recordings attached suggest that they are missing SysEx messages that contain custom timbres/patches. I'll double-check if the new version records them correctly, but the old version surely did that.

Re: MUNT Midi Recording Issue

in MT-32 General
Hi Mrdangerous, I assume you've missed one way to solve the problem you describe: downgrading the application. Munt version 2.4.0 incorporates a new implementation of the MIDI recording function, so regressions are well possible. To be honest, I only did no more than a smoke test of this particular …

Page 1 of 45