BASSMIDI MIDI driver for Windows Vista/7 (x64 incl.)

[Maxime]

Maxime, please

Installing this driver on Windows 7 x64 might be easier on your computer than mine.

I had two problems, but maybe you'll not have them on your side:

- after running the setup, I tried to launch the Configuration utility, which complained about two missing DLL files (MSVC*100.dll). If you're getting these errors, simply download and install the "Microsoft Visual C++ 2010 Redistributable" packages from Microsoft:

• 32-bit: http://www.microsoft.com/downloads/en/d ... bf0912db84
• 64-bit: http://www.microsoft.com/downloads/en/d ... 50143d5867

- even after setup, the BASSMIDI driver didn't appear as a MIDI output device on my MIDI player. That's why I had to do the trick in the Registry, but mainly because I have lots of MIDI devices on my computer.
If you're experiencing the same issue:

• from the Start menu, type "regedit" to run the Windows registry editor
• navigate to the HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion\Drivers32 section
• modify one of the keys named midi* and change its value to bassmididrv.dll
• after making this change, without even having to reboot or close the registry editor, BASSMIDI driver should appear in your MIDI output devices list.

Does it sound easier for you now?

[ex-driver]

Good work guys . Some improvements would be good if you can do that. The first is the buffering for bigger samples at the start of midis an during the first playback time. And some playback issues from some midis. I would be great if you can improve this driver synth is could be perfect .

[Solaphar]

Maxime, please

whuppps. Sorry, fixed it in my previous post. It was late and I have trouble reading small print when I'm tired.

Installing this driver on Windows 7 x64 might be easier on your computer than mine.

I guess I just don't want to take any chances.

Does it sound easier for you now?

Yeah, that helped. Thanks for simplifying it. I'll see what problems, if any, I run into once I try it.

[mudlord]

Thanks,
Maxime, do you have a IM method? Would like to contact you to work out a custom driver installer build to fix the issue you are having.

EDIT: Tried out your method with a new installer build. Works. Now needs someone who wants to be a guinea pig....

[MaliceX]

Installer is functional and works under XP. However, I have a Creative SB Audigy 2 Value installed, and there seems to be a few issues:

1. BASSMIDI driver is invisible to WInamp's default in_midi.dll plugin. That is, it's nonexistent, so it's practically unusable in Winamp. Works fine in WMP.
2. Consistent to BASSMIDI's current spec, it was designed to load the default soundfonts present in the %windir%\system32 folder, thus making user loadable soundfonts useless unless one deleted/replaced said files present.
3. SysEx/controller reset hanging some sequencers. (WinJammer Professional)

I haven't tried this on the laptop yet, or under Win7 x64 just yet, been busy. But big thanks mudlord and kode54 for making this possible. Now we have a much more better avenue of using the GS soundset (Roland Sound Canvas soundfont variant) retrofitted with DSP us XG users got away murdering with.

[kode54]

1. Not sure how to fix that, since the ActiveMovie key that all the other drivers register under is for WDM drivers, which I think by design must be kernel drivers.
2. Yes, and those default SoundFonts are overridden by the SoundFonts you specify in the configuration utility. They would only be kicking for unmapped instruments. Of course, disabling this altogether is a one line change, so I guess I can fix it.
3. It handles SysEx messages the same as the TiMidity++ driver, except that it also catches GM/GS/XG reset messages and reenables the default drum channel in that case after sending the reset sequence to BASSMIDI.

Anyone willing to help with the development of the driver is welcome to submit source patches, in case I don't get to all the issues fast enough.

(For instance, I haven't actually tested the driver with anything other than Windows Media Player, SSynth.com MIDI File Player, and eduke32.)

As for someone's request to preload instruments, that is not really feasible, since it would have to be for entire SF2 files, in which case the sample caching would be no better than Creative's hardware synthesizer in the memory usage department. Which would also make schemes like my 95% of Colossus.SF2 plus SGM plus AnotherXG setup, which consists of 4.5GB of SoundFonts, impossible to use.

[mudlord]

could it be that this driver is tmidity??

No.
Completely different SoundFont loading methods.
Completely different synth code.
Only thing that might be shared is a heavily modded driver to support BASSMIDI, thats it.

Everything else was made entirely from scratch. BASSMIDI itself and BASS was coded by the XMPlay developer, from scratch. So the synth internals are nothing like timidity at all. So why the comparisons?

[ex-driver]

A friend of me said that so i had to ask you

Is it possible to improve this driver and cfg panel from time to time? That would be nice =)

[mudlord]

Improve it how.
What is it about the config you hate? kode54 already explained the issues we have with the driver.

Maxime/Solaphar: Can you try the installer now? I did some tweaks to it. You will need to uninstall the old version.

[Bregalad]

This sounds like a stupid question but after we installed it how are we supposed to use it ? I had installed it twice without any errors but I cant see anything added to my MIDI devices list.

[mudlord]

Whats your soundcard drivers?
EDIT: Nvm, solved, and fix included with the installer now.

[Maxime]

But big thanks mudlord and kode54 for making this possible. Now we have a much more better avenue of using the GS soundset (Roland Sound Canvas soundfont variant) retrofitted with DSP us XG users got away murdering with.

Hey, MaliceX! Glad to see you there!
I simply love your Jazz Jackrabbit MIDIs... I nearly bought my MU1000 just to listen to your work!

Thanks,
Maxime, do you have a IM method? Would like to contact you to work out a custom driver installer build to fix the issue you are having.

It seems that you've now found a fix (I still have to try your new installer build), but if you still need some beta testing, I'll PM my MSN address to you.

Improve it how.
What is it about the config you hate? kode54 already explained the issues we have with the driver.

Maxime/Solaphar: Can you try the installer now? I did some tweaks to it. You will need to uninstall the old version.

I'll try this ASAP.
BTW, in case you'd be interested: if this is a pure softsynth (not relying on any hardware SoundFont-compatible card), I guess I'll be able to test it under a virtualized environment (Parallels Desktop 6 for Mac with virtualized XP MCE on integrated Intel ICH soundchip), as MaliceX seems to confirm that the driver also works under XP.

[Solaphar]

Maxime/Solaphar: Can you try the installer now? I did some tweaks to it. You will need to uninstall the old version.

Lucky me. I didn't actually install the old one yet. =P

I'll download the latest one and give it a shot.

[Solaphar]

Update: Alright, I installed it, but when I clicked on 'Configure Driver' in the 'BASSMIDI Sytem Synth' directory, I got 'bassmididrvcfg.exe - System Error' reading: "The program can't start because MSVCP100.dll is missing from your computer. Try reinstalling the program to fix this problem." So I guess I still need to go through the steps Maxime outlined.

[mudlord]

Fixed in the newest installer.
Had to change the compilation settings to use static MSVC runtimes.