It also supports GM, GS, and XG reset System Exclusive messages, and the drum channel enabling features of GS and XG when switched into those modes. It also supports GS and possibly XG reverb preset control messages for adjusting reverb time, delay, low-pass cut-off, high-pass cut-off, and level. And chrorus delay, depth, rate, feedback, level, and chorus to reverb send level. It also supports the master volume level message.

kode54 should be thanked for making this possible. I wrote the installer and configuration app.

Man... I've been looking for something like this for EONS! Heh, I've been nagging Ian Luck (the author of XMPlay/XMPlay MIDI Plugin/BASS libraries) for ages now for something like this, a "global" Windows MIDI driver of sorts based upon XMPlay's MIDI plugin.

In the last bit of discussion with him on the subject (quite some time ago) he replied, "Find someone to code it in BASS" <grin>, and now it looks like someone actually did

Anyhow, I installed the BASSMIDI MIDI Synthesizer driver... and it works GREAT!!!

From what I could tell, ZERO latency, and it sounds just like XMPlay's MIDI plugin Running on a P4 2.666Ghz CPU with 768MB RAM under Windows XP Pro SP3, output was smooth with no glitches or stutters.

I guess the reason why it knocks out MIDI Yoke, is because it writes to a specific reg entry, to work around issues with some Creative drvers. I guess that reg entry is used for MIDI Yoke as well, unfortunately. I guess I can try and redo the registry code to write to any other reg key which is the default WDM synth (which there is PLENTY of free slots, since the WDM driver takes a lot....heh).

Any download links for MIDI Yoke, so I can try and make a workaround? I personally use Win7 x64, if that will be a problem...

I used in the past MIDI Yoke (or Maple MIDI), with Putzlowitschs MIDI Mapper for Vista/7 and load SF from sfx+ then route the player/app or whatever was using MIDI which now is done without all this trouble

also allow me to throw another thing I forgot to praise: SF that were impossible to load due to memory limitation now can be loaded thanks to dynamic handling (which I suspect is just the same feature as present in foo_midi)

I guess the reason why it knocks out MIDI Yoke, is because it writes to a specific reg entry, to work around issues with some Creative drvers. I guess that reg entry is used for MIDI Yoke as well, unfortunately.

Thanks for the info

QUOTE (mudlord @ Mar 31 2011, 02:24)

I guess I can try and redo the registry code to write to any other reg key which is the default WDM synth (which there is PLENTY of free slots, since the WDM driver takes a lot....heh).

That would be great!

QUOTE (mudlord @ Mar 31 2011, 02:24)

Any download links for MIDI Yoke, so I can try and make a workaround? I personally use Win7 x64, if that will be a problem...

The driver emulates some GS features that E-mu based synths don't do, as well as some XG features too.

So, its a GM2 level synth. Creative's hardware synth is not.. Also, if you use a LOT of SoundFonts OR you want to load more than 4GB of soundfonts easily, sure, the memory usage will be a major contributer.

And why is that? Last time a user did that, it hosed all sorts of MIDI related stuff.

I myself don't mind keeping the MSGS SW Synth around on my PC.

Why's that? Although I'm no fan whatsoever of the sound of the Roland SC-55 MIDI modules, the "GM.DLS" sound set that the MSGS SW Synth uses is essentially a direct dump of the SC-55's onboard sample ROM.

Configure WinDoze to use the MSGS SW Synth, add a bit of Sound Blaster Live EAX reverb (as the MSGS SW Synth is 'dry' as a bone), and whammo... instant virtual SC-55 <grin>.

Although, with the newer drivers for the SBLive/Audigy/X-Fi/etc... one could always load the GM.DLS directly into the EMU of those sound cards, as the Windows XP (and newer) drivers for them support loading DLS format sound sets (as well as SoundFonts, of course).

Thanks! Now to figure out how to remove Microsoft GS as the 0 ID device.

And why is that?Last time a user did that, it hosed all sorts of MIDI related stuff.

What I meant to say was making BASS the default MIDI device. For things like PRBoom+ and eDuke32, they auto-default to MSGS. I'm assuming it's because of its placement as the 0 ID. In their config files, there are settings to specify which device to use, but regardless of what I put, it always uses MSGS.

This is a great idea! I've been using loopbe1 and programs like SFZ+ and SyFonOne, and BASSMIDI could definitely simplify things. Unfortunately, I'm getting audio glitches with BASSMIDI that I don't get with the other method. For example, I use the "ProTrax_Classical_Guitar" for the nylon string guitar, and when I play a simple .ptb file in PowerTab that uses just that single instrument, e.g. "Jesu Joy Of Man's Desiring", within 10 seconds or so, I start to hear little "bzzzt" or staticky sounds after most every note. There are also some glitches with the configuration program's listbox handling, e.g. it can generate blank items and write them to the file, clicking "Down" on the bottom item removes it, etc. Finally, am I correct in thinking that to observe changes made via the configuration program, you have to restart the client program, e.g. PowerTab?

Thanks! Now to figure out how to remove Microsoft GS as the 0 ID device.

And why is that?Last time a user did that, it hosed all sorts of MIDI related stuff.

What I meant to say was making BASS the default MIDI device. For things like PRBoom+ and eDuke32, they auto-default to MSGS. I'm assuming it's because of its placement as the 0 ID. In their config files, there are settings to specify which device to use, but regardless of what I put, it always uses MSGS.

There are also some glitches with the configuration program's listbox handling, e.g. it can generate blank items and write them to the file, clicking "Down" on the bottom item removes it, etc. Finally, am I correct in thinking that to observe changes made via the configuration program, you have to restart the client program, e.g. PowerTab?

Thanks for reporting, they seem to be all fixed, so it should be ready for the next version.

Actually, might have a solution to the MIDI sticking issue for some issues, which will be in the next version. Worked with someone who had the exact same issues, to fix it for him, so the fix might work for others.

Thanks! Now to figure out how to remove Microsoft GS as the 0 ID device.

And why is that?Last time a user did that, it hosed all sorts of MIDI related stuff.

What I meant to say was making BASS the default MIDI device. For things like PRBoom+ and eDuke32, they auto-default to MSGS. I'm assuming it's because of its placement as the 0 ID. In their config files, there are settings to specify which device to use, but regardless of what I put, it always uses MSGS.

Wow, only those? I was expecting much, much worse false positives. But yes, the files are indeed encrypted, and not just packed with something stupid like UPX/ASPack/PECompact/etc.....

Yeah, they were simply reports of packed EXE/DLL files.

I found McAfee Command Line to be pretty reliable... with the expanse of command line options that I use when scanning files, it will report anything that is packed, and if it finds anything within those packed files.

In other words, as long as it doesn't report an _actual_ virus, the packed files messages can simply be ignored (as well as the "Objects Possibly Infected" and "Possibly Infected" summaries, as if McAfee actually found a virus, it would report what it actually found; the name of the virus/infection)

C:\Test\BASS.dll ... is packaged using New Packer.C:\Test\BASSMIDI.dll ... is packaged using New Packer.C:\Test\BASSMIDIDrv.exe ... is packaged using Nullsoft.C:\Test\BASSMIDIDrv.exe\6.nsis ... is packaged using New Packer.C:\Test\BASSMIDIDrv.exe\7.nsis ... is packaged using New Packer.C:\Test\BASSMIDIDrvUninstall.exe ... is packaged using Nullsoft.

Possibly Infected:............. 0

C:\Test\BASS.dll ... is packaged using New Packer.C:\Test\BASSMIDI.dll ... is packaged using New Packer.C:\Test\BASSMIDIDrv.exe ... is packaged using Nullsoft.C:\Test\BASSMIDIDrv.exe\6.nsis ... is packaged using New Packer.C:\Test\BASSMIDIDrv.exe\7.nsis ... is packaged using New Packer.C:\Test\BASSMIDIDrvUninstall.exe ... is packaged using Nullsoft.