Izlude, on 20 October 2012 - 16:16, said:
Using Windows 7 64bit here.
My current soundcard is my video card Asus 5870v2 through the HDMI to my TV/Speakers.
I'm trying to make it so that any program I use that plays midis, will be routed to use my soundfont instead of the default windows gm.dls (MS General Synth). Normally a Creative sound card is required with the soundbank manager, but I discovered that this is not necessary at all.
I found two engines, but have no idea how to make them work. The first was fluidsynth, popular on Linux, but also available on Windows. There are no instructions... anywhere! If anyone is knowledgably about it, please help
The second one is called Timidity. I believe this might be my best bet, but it's not working correctly. I installed it to the default directory, changed the cfg files (in windows folder and the program folder both) setting the location of my soundfont. When I use the midi mapper (chooser), I select timidity instead of Microsoft GS Wavetable Synth. When I play midis, no sound...
I noticed the midi chooser goes back to Microsoft GS Wavetable Synth as If it didn't let me choose Timidity, although when I "DO" click apply to go "back" to Microsoft GS, midis that played before will not and I get some error about a corrupt plugin or something.
I had to do a system restore to get back to square one... so... any suggestions?
I would recommend Virtual MIDI Synth, as it doesn't require a sound card at all (right now, I'm using it to play MIDI over HDMI, which is supposed to be a technical no-no).
Works in any version of Windows from XP forward (including Windows 8 - I'm running it in 8 Pro x64 as I type this), and is fully compatible with the compressed SoundFont (*.sfArk) and uncompressed SoundFont V2 (*.sf2) supported by all Creative audio cards with SoundFont capability (which is every sound card that doesn't rely entirely on CPU cycles back to the ISA-bus AWE series). The particular SoundFont I am running is, in fact, an update of one from my days taking the ISA bus for MIDI - back then I had replaced my then long-in-the-tooth Sound Blaster 16 with the AWE32's "poor cousin" Sound Blaster 32 PnP - while looking over SoundFont alternatives to the ones the SB32 included, I was introduced to HammerSound and their then-large and growing collection of SoundFonts - some were commercial and intended for such use; however, they also had a large number of free SoundFonts that were of commercial quality. One of my personal favorites was the Fluid GM R2 SoundFont - I called it nothing less than THE preferred GM SoundFont for everyday usage. (Not many GM SoundFonts qualified as "everyday usage" as too many had their quirks that roadblocked such use - Fluid had few in R2 form, which is why it became my preferred SoundFont. In R3 form, if anything, the quirkage got reduced again; even better, with VirtualMusic Synthesizer, MIDI is now available for audio output that normally doesn't support it, such as HDMI.
Okay - why is MIDI over HDMI even wanted?
That's easy enough to explain - consider a desktop or even portable PC; unless you're a purist, more likely than not, you're going to have as few wires connecting your display to your case as possible (desktops). The issue for portable PCs is even worse - they are basically trapped with the computer as-is, as third-party speaker options aren't all that great for laptops and notebooks, let alone tablets or slates. The easiest solution (in all cases) is HDMI - which is, after all, designed to carry both audio AND video, and at the same time, in an entirely digital manner.
The fly in the HDMI potion is HDCP - the stream-protection scheme for audio (and video) over HDMI
Thanks to HDCP, HDMI doesn't play nice with other audio options - not even when those other options include features that HDMI lacks, such as MIDI support. Therefore, HDMI's biggest hole - MIDI support - needs to be addressed.