Hydrogenaudio Forums

Hydrogenaudio Forum => General Audio => Topic started by: mudlord on 23 March, 2011, 09:33:16 AM

Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: mudlord on 23 March, 2011, 09:33:16 AM
This is a new SoundFont-based usermode MIDI system driver for Windows XP, Vista, 7 and 8.
It uses the BASSMIDI (http://www.un4seen.com/bass.html) library by Ian Luck, as the synthesiser.

Features:
* Dynamic sample caching
* Unlimited polyphony
* Compressed SoundFont support
* SoundFont chaining/stacking
* Works on Windows Vista and Windows 7, including 64-bit versions.
* Support for the following controllers & events:

MIDI note events.
MIDI program events.
Channel pressure.
Pitch wheel.
Bank change MSB. (CC#0)
Modulation. (CC#1)
Portamento. (CC#65 / CC#84 / CC#5)
Volume. (CC#7)
Panning. (CC#10)
Expression. (CC#11)
Sustain pedal. (CC#64)
Soft pedal. (CC#67)
Low-pass filter resonance. (CC#71 or NRPN 121h)
Release time. (CC#72 or NRPN 166h)
Attack time. (CC#73 or NRPN 163h)
Low-pass filter cut-off. (CC#74 or NRPN 120h)
Reverb send level. (CC#91)
Chorus send level. (CC#93)
Stop all sounds. (CC#120)
Reset all controllers. (CC#121)
Release all keys. (CC#123)
Mono/poly mode. (CC#126 and CC#127, respectively.)
Pitch wheel range. (RPN 0)
Fine tuning. (RPN 1)
Coarse tuning. (RPN 2)

And presumably if GS/GM2 mode is activated:
Drum key low-pass filter cut-off. (NRPN 14knh)
Drum key low-pass filter resonance. (NRPN 15knh)
Drum key coarse tune. (NRPN 18knh)
Drum key fine tune. (NRPN 19knh)
Drum key volume level. (NRPN 1Aknh)
Drum key panning. (NRPN 1Cknh)
Drum key reverb send level. (NRPN 1Dknh)
Drum key chorus send level. (NRPN 1Eknh)

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.

http://mudlord.info/bassmididrv (http://mudlord.info/bassmididrv)
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: romor on 29 March, 2011, 03:50:54 AM
Thanks kode54

(https://hydrogenaud.io/imgcache.php?id=aa4acd688101c012f277645e80f0c5e8" rel="cached" data-warn="External image, click to view at original size" data-url="http://i55.tinypic.com/iz0tol.png)

How should I add Colossus?
It's one instrument per soundfont, and it seems that it can't load sflist (like foo_midi i.e.)
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: RichNagel on 31 March, 2011, 02:51:30 AM
Hi Mudlord and Kode54,

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.

One problem for me though, it seems to completely knock out/disable Jamie O'Connell's "MIDI Yoke" patch driver (MIDI devices: "Out To MIDI Yoke: #", "In From MIDI Yoke: #", etc...). I use that driver for various things when composing MIDI music.

Other than that, it works great. Any idea as to why the driver would disable MIDI Yoke?

Anyways, thanks for a GREAT soundfont compatable MIDI driver!
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: mudlord on 31 March, 2011, 03:24:30 AM
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...
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: mudlord on 31 March, 2011, 03:27:45 AM
Thanks kode54

(https://hydrogenaud.io/imgcache.php?id=aa4acd688101c012f277645e80f0c5e8" rel="cached" data-warn="External image, click to view at original size" data-url="http://i55.tinypic.com/iz0tol.png)

How should I add Colossus?
It's one instrument per soundfont, and it seems that it can't load sflist (like foo_midi i.e.)



One workaround until I fix that is you can reuse your foo_midi SoundFont lists. In your %systemroot% folder, copy your listfile, to "bassmidi.sflist".
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: romor on 31 March, 2011, 03:56:50 AM
great
thanks for the tip

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
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: romor on 31 March, 2011, 05:33:07 AM
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)
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: mudlord on 31 March, 2011, 05:59:10 AM
Same feature, because of exact same synth library used.
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: RichNagel on 31 March, 2011, 01:40:17 PM
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


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!


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...


MIDI Yoke can be downloaded from here -> http://www.midiox.com/myoke.htm (http://www.midiox.com/myoke.htm) . I'm not sure about issues with Windows 7, but here are the forums for MIDI Yoke (which mention installation under W7) -> http://www.midiox.com/cgi/yabb/YaBB.pl?board=MYInstall (http://www.midiox.com/cgi/yabb/YaBB.pl?board=MYInstall) .


Again, thanks for a great MIDI driver, and any help
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: mudlord on 02 April, 2011, 07:25:19 PM
I posted a updated driver a while back on my site, to work around these bugs.
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: Vagabond on 02 April, 2011, 09:00:34 PM
If I have a Creative sound card and use the Creative Sound Font Bank Manager, will I have any use for this? The prospect of lower memory usage is appealing.
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: mudlord on 03 April, 2011, 02:33:52 AM
If you play around with MIDI's a fair bit, sure.

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 the synth was tested with around 4.5GB of SoundFonts.
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: Vagabond on 03 April, 2011, 03:08:45 PM
Thanks! Now to figure out how to remove Microsoft GS as the 0 ID device.
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: mudlord on 04 April, 2011, 06:19:44 AM
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.
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: RichNagel on 04 April, 2011, 07:21:25 AM
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).
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: Vagabond on 04 April, 2011, 12:35:43 PM
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.

Setting the default device in the BASSMIDI config isn't working.
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: tima on 05 April, 2011, 01:14:14 AM
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?
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: mudlord on 05 April, 2011, 06:08:49 AM
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.

Setting the default device in the BASSMIDI config isn't working.


Tried other stuff like:
http://software.bootblock.co.uk/?id=vistamidipicker (http://software.bootblock.co.uk/?id=vistamidipicker)
http://www.brainmaster.com/kb/entry/334/ (http://www.brainmaster.com/kb/entry/334/)

?

If those don't work, I dunno what the issue is.
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: mudlord on 05 April, 2011, 06:10:50 AM
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.

And yes for SoundFont changes, the host app needs to be restarted.
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: mudlord on 06 April, 2011, 03:57:54 AM
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.
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: Vagabond on 06 April, 2011, 08:07:26 PM
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.

Setting the default device in the BASSMIDI config isn't working.


Tried other stuff like:
http://software.bootblock.co.uk/?id=vistamidipicker (http://software.bootblock.co.uk/?id=vistamidipicker)
http://www.brainmaster.com/kb/entry/334/ (http://www.brainmaster.com/kb/entry/334/)

?

If those don't work, I dunno what the issue is.


Doesn't work. Maybe the issue is with the programs I mentioned.

Regardless, thanks for the help!
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: mudlord on 07 April, 2011, 06:59:13 AM
Uploaded new version. Don't blame me if your AV goes utterly haywire. Blame the leeching slut for it....
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: RichNagel on 07 April, 2011, 08:35:00 AM
Uploaded new version. Don't blame me if your AV goes utterly haywire. Blame the leeching slut for it....


Mine simply reported that the file(s) were packed with something (I forget now, "EXE Append" or "EXE Pack", something like that, I forget now). Otherwise, no reports of viri

P.S. This using McAfee Command Line v6.0.3, with the latest DAT files/updates.

Anyhow, works perfectly, Mudlord, thanks!
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: mudlord on 07 April, 2011, 08:42:34 AM
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.....
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: RichNagel on 07 April, 2011, 09:08:53 AM
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)

FWIW, here's a scan log:

Code: [Select]
Copyright (C) 2010 McAfee, Inc.
(408) 988-3832 LICENSED COPY - June 16 2010

AV Engine version: 5400.1158 for Win32.
Dat set version: 6308 created Apr 6 2011
Scanning for 657207 viruses, trojans and variants.

Summary Report on Process Scanning
Process(es)
        Total processes:...............     22
        Clean:.........................     22
        Not Scanned:...................     0
        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.

        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.

Summary Report on C:\Test
File(s)
        Total files:...................     6
        Total Objects:.................     24
        Clean:.........................     2
        Not Scanned:...................     0
        Possibly Infected:.............     4
        Objects Possibly Infected:.....     6

Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: mudlord on 07 April, 2011, 10:06:52 AM
Lets see.....
Quote
C:\Test\BASS.dll ... is packaged using New Packer.

No, McAfee, its packed with Ian's packer/protector, Petite. Not "New Packer"....
Quote
C:\Test\BASSMIDIDrv.exe ... is packaged using Nullsoft.

NSIS you mean, not nullsoft.....
Quote
C:\Test\BASSMIDIDrv.exe\6.nsis ... is packaged using New Packer.

rofl....
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: RichNagel on 07 April, 2011, 10:26:00 AM
Hehe, well at least it realizes they are packed LOL!
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: mudlord on 08 April, 2011, 12:37:24 AM
Yep, thats the main thing.  I still need to fix up the final bugs though.
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: mudlord on 11 April, 2011, 03:55:16 AM
Finally managed to reproduce the issues people are having after a complete reformat....
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: RichNagel on 15 April, 2011, 12:49:51 AM
@Mudlord,

Just a status-report, the new version (that I'm unofficially calling "v1.05" <grin>) that you released on April 14 works without any problems (WXP Pro SP3)
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: mudlord on 17 April, 2011, 06:37:48 AM
yay!
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: RichNagel on 19 April, 2011, 06:39:07 PM
Hey Mudlord,

Is something up with your web site? Seems that *everything* has disappeared, including the download for the latest version of the BASSMIDI driver

P.S. I also mirrored this message over at the VGMusic message forums... didn't know if you log in to that one more frequently than this one.
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: romor on 19 April, 2011, 09:08:28 PM
it seems your IP address is blocked for some reason: http://i54.tinypic.com/nmz0ok.png (http://i54.tinypic.com/nmz0ok.png)
you could mirror on HA upload forums I guess 
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: tpijag on 19 April, 2011, 09:30:05 PM
Connection and download fine here.

Correction: That was to post link Homepage - not the other two links.
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: mudlord on 19 April, 2011, 11:12:01 PM
Hey Mudlord,

Is something up with your web site? Seems that *everything* has disappeared, including the download for the latest version of the BASSMIDI driver

P.S. I also mirrored this message over at the VGMusic message forums... didn't know if you log in to that one more frequently than this one.



Long story short, as I explained to #foobar2000 regulars:
Legal threats caught up with me in regards to tools that aid piracy in source form. I am in the process of rebuilding the site to have not such content, but because the DMCA and shit, it could apply to anything, so I don't know what I should reupload. Like the tools for kode54 and Peter I made for the MDK1 PC version's audio archives.

Quote
It seems your IP address is blocked for some reason: http://i54.tinypic.com/nmz0ok.png (http://i54.tinypic.com/nmz0ok.png)
you could mirror on HA upload forums I guess


What the hell? Who do I see to get that blacklist removed?
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: romor on 19 April, 2011, 11:48:55 PM
I don't know, try contacting them http://www.eset.com/about/contact/ (http://www.eset.com/about/contact/) or http://kb.eset.com/esetkb/index?page=content&id=SOLN141 (http://kb.eset.com/esetkb/index?page=content&id=SOLN141)

The other day (you posted yay) I downloaded fine, so something in between must have happened
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: mudlord on 20 April, 2011, 12:38:33 AM
Hmmm I wonder why its on the list.....

tima's payback?
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: romor on 20 April, 2011, 01:00:07 AM
don't think that single user can make IP blacklisted, although I'm interested out of curiosity why is blacklisted as I don't see those red boxes without real reason
hope you resolve this quickly
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: mudlord on 20 April, 2011, 01:20:18 AM
Newly updated content is now:
http://www.virustotal.com/file-scan/report...d931-1303276373 (http://www.virustotal.com/file-scan/report.html?id=28b3688f58ede1a27e6325446e2fd6a33cbfbf49887eff0bbd32242031edd931-1303276373)
http://mudlord.emuxhaven.net/crap/audio/bassmididrv.exe (http://mudlord.emuxhaven.net/crap/audio/bassmididrv.exe)
http://mudlord.emuxhaven.net/crap/audio/bassmididrv.rar (http://mudlord.emuxhaven.net/crap/audio/bassmididrv.rar)

Now the leechers can go back to raping our content. Well done ESET.
See what you morons had to do, to get full source access? Go make some phony virus reports!!!!
I hope you are fucking happy tima. We also did it under a WTFPL so you can even SELL our code, and we don't get a cent!
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: romor on 20 April, 2011, 02:17:06 AM
If someone submitted report (which includes attaching suspected file) it wasn't 'bassmididrv' as NOD never complained about. Should I guess that in past three days someone submitted shared infected file from your IP?

I excluded your IP from checking, but any ESET user will experience Access Denied block of course - pity complications for such a nice tool
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: mudlord on 20 April, 2011, 03:04:26 AM
Sent some reports to ESET.

Waiting on them.
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: RichNagel on 20 April, 2011, 06:53:34 AM
The new one downloads just fine

It was weird though... with the old link ( http://mudlord.emuxhaven.net/stuff/audio/bassmididrv.exe (http://mudlord.emuxhaven.net/stuff/audio/bassmididrv.exe) ) I was getting the Internet Explorer "Smart" Screen Filter Thing "This site may be unsafe!" (I read on other message forums people that were seeing this too); but simply chalked it up to Mickey$oft in their "infinite wisdom".

Anyhow, glad to see it's back online... as well as 'backpack girl' on your main web page
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: mudlord on 20 April, 2011, 08:05:20 AM
Yay, I am just glad every major bug is now eliminated.
Just some cosmetic updates I want to do next, like disabling the synth selection for XP, icons, etc...
Not much I can do about the DOSBox issues though.
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: RichNagel on 20 April, 2011, 09:28:00 AM
Just some cosmetic updates I want to do next, like disabling the synth selection for XP


I'd say just leave it. It's kind of handy to have it there: A simple click in one's start menu to start the config utility to change the Windows MIDI device, verses the Bill Gates way (i.e. click-click-click; "Start/Control Panel/Sounds and Audio Devices/Audio/etc..." <grin>)


Not much I can do about the DOSBox issues though.


Like I've posted previously, using it with DOSBox works great for me

BTW, for the actual driver itself, any chance of some sort of master reverb slider like I mentioned earlier over in the XMPlay forums?

Also, is there any real advantage to modifying the code for the driver itself to address the 'vanBasco's Karaoke Player' problem that the "One We Don't Speak Of" <LOL> talked about over in the XMPlay forums? I mean, that's the only thing so far that I've seen that has an issue with the driver... everything else that I've tried works GREAT
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: mudlord on 20 April, 2011, 11:13:30 AM
I use foo_midi, so I personally find that a non-issue.
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: RichNagel on 20 April, 2011, 11:01:59 PM
I use foo_midi, so I personally find that a non-issue.


Thanks for the info... yeah, I didn't think it was that important either


BTW, someone ("Csonicgo") over at the DOOM World forums was having a real bad problem uninstalling (what I'm sure was) an older version of the BASSMIDI driver. He said he had trouble registering here (I'm assuming here at the Hydrogen Audio forums); so's I replied to him that I'd let you know about it -> http://www.doomworld.com/vb/showthread.php...3072#post963072 (http://www.doomworld.com/vb/showthread.php?postid=963072#post963072) .

He posted a few screenies fof the problem, maybe you could help him out
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: mudlord on 21 April, 2011, 12:13:38 AM
Maybe we should go back to force restarting your system to uninstall drivers, for all Windows versions...
Heh. Maybe then that jerk would have sense.

Oh he wants to uninstall it! >_> And NO mention of the OS used for install!
Knowing the OS version would help.....a lot?
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: RichNagel on 21 April, 2011, 12:24:28 AM
Oh he wants to uninstall it!


I'm thinking that he was uninstalling it (an older version) to install the newer version.
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: mudlord on 21 April, 2011, 12:25:44 AM
Oh...that certainly complicates things.
I posted in the thread more details.
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: Vagabond on 22 April, 2011, 12:10:24 PM
In case anyone ventures here about changing MIDI ID device, Putzlowitsch's Vista MIDI Mapper Control Panel (http://www.sierrahelp.com/Utilities/SoundUtilities/PutzlowitschsVistaMIDI_Mapper.html) did the trick.
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: tima on 23 April, 2011, 03:40:49 PM
Long story short, as I explained to #foobar2000 regulars:
Legal threats caught up with me in regards to tools that aid piracy in source form. I am in the process of rebuilding the site to have not such content
...
What the hell? Who do I see to get that blacklist removed?


Hmmm I wonder why its on the list.....

tima's payback?


Now the leechers can go back to raping our content. Well done ESET.
See what you morons had to do, to get full source access? Go make some phony virus reports!!!! biggrin.gif
I hope you are fucking happy tima. We also did it under a WTFPL so you can even SELL our code, and we don't get a cent!


Mudlord. After your meltdown a couple of weeks ago, I wasn't going to try to talk to you further, but since you have not been able to get me out of your head and are continuing to publicly hurl false accusations at me, I guess I do have something to say about that.

1. I have not reported you to anyone. I have not discussed you with anyone. I have not mentioned your project to anyone. My last visit to these forums was almost two weeks ago. Any difficulties you have encountered are due to your real enemies, not me. I don't care about you.

2. Despite your repeated baseless accusations, my only interest in your source code was in potentially offering to help you fix it if you proved incapable, which seemed not unlikely considering what you included in your initial release. Of course, I was too polite to come out and say that, and so in my first post in this thread, which began with "This is a great idea!", I simply mentioned a couple of bugs. I was looking forward to seeing if you could fix them. My second post was just a quick statement that I wasn't interested in dealing with the new protection stuff you were doing in your second release. In my third post (deleted, I must continue to hope, only because of your vulgar, crazed reply to it), among other things, I responded to one of your questions "Why?" by explaining my interest in the source code was in seeing how the code evolved WRT buffering and multithreading, which was where it was really naively written, the latter of course being something I was again too polite to come out and say. I believe I also said I wanted to determine why soundfont changes didn't occur immediately but required restarting the client application, which became apparent after examining the source code.

3. That's all over now. I mentioned in my first message that the closed source loopbe1 and SyFonOne and/or sfz+ meet my needs (which I also described in detail, I think also in my third message), though they are a little difficult to use, but they are nothing compared to the difficulty of trying to have a rational conversation with you. It's just not worth the time or energy for me, as based on your meltdown, I could tell there would be no end to your nonsense, so why even try?. Indeed, two weeks later, you're continuing with it all on your own. That's why I didn't respond to you, and it's beyond pathetic that you believe that since then, I've been busy trying to screw you up and get even, when the truth is, I haven't thought about you at all. (And so there will be no mistake, this message is not an attempt to continue having a conversation with you. It's just another attempt to help you.)

4. Let me state unequivocally that I'm not now and never was interested in "stealing and selling your code". That's just a paranoid construction of your brain, and it was not even remotely suggested by anything I said to you in the three messages I wrote to you before this one.

5. Though I had nothing to do with your troubles, as I so patiently explained to you, it's bad policy to deliberately cause false positives in A/V software. Note that I said false positive, which is all I've ever said. I never once even remotely suggested that your software contained an actual virus. From your other messages, I see you had to deal with the false reports and change your practices, not to mentioned whatever you were doing that got your website blacklisted for "tools that aid piracy in source form". While I had nothing to do with any of that, it's no shock to find out I was completely right and gave you outstanding advice in my message that was deleted, the one that caused you to melt down for no reason.

I hope all this helps to ease your mind and allows you to forget about me, move on, and focus on your real enemies, perhaps including the "leeching slut" you first mentioned many days ago. Maybe that entity is the one causing you all your woe in this weird world you've described. In the world in which reality occurs, it is not me causing you problems, I have no idea who it is, and I have had no part in it. I don't care about you.
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: mudlord on 27 April, 2011, 12:21:44 AM
Quote
I have not reported you to anyone. I have not discussed you with anyone. I have not mentioned your project to anyone. My last visit to these forums was almost two weeks ago. Any difficulties you have encountered are due to your real enemies, not me. I don't care about you.


However, to me, it seemed quite the opposite and quite suspicious.

Quote
my only interest in your source code was in potentially offering to help you fix it if you proved incapable, which seemed not unlikely considering what you included in your initial release.


Now I want to know, how do you think I am incapable of ANYTHING I program? Do you and other people really think I am a talentless HACK?
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: mudlord on 28 April, 2011, 12:09:20 AM
unrelated:
been busy on new dialogs and options for next version: http://stashbox.org/1106004/config.JPG (http://stashbox.org/1106004/config.JPG)

Took a leaf out of Peter's book and redid the config app in WTL. Has better registry functions, better tab handling, etc....
So much easier than Win32 code to maintain.
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: mudlord on 29 April, 2011, 12:25:57 PM
uploaded 1.06
with volume control abilities as requested by members of the doom modding community.
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: RichNagel on 29 April, 2011, 08:20:54 PM
uploaded 1.06
with volume control abilities as requested by members of the doom modding community.


Volume control works like a champ, uninstall of old version and install of new version works perfectly  Thanks, Mudlord!
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: RichNagel on 06 May, 2011, 10:16:04 PM
XMPlay MIDI Plugin/BASSMIDI/BASSMIDI Driver MIDI Implementation Chart

Folks,

I threw this together the other day; a MIDI Implementation Chart and system exclusive messages list for the XMPlay MIDI Plugin, BASSMIDI, and the BASSMIDI Driver. It may not be 100% accurate, and doesn't list but the very basic XG system exclusive messages that they support... but it might prove useful to someone nonetheless

http://www.cmoo.com/snor/weeds/SoundFonts/...ation_Chart.htm (http://www.cmoo.com/snor/weeds/SoundFonts/XMPlay/BASSMIDI_Driver_MIDI_Implementation_Chart.htm)

Other links of interest (that y'all may, or may not have seen):

http://www.cmoo.com/snor/weeds/SoundFonts/XMPlay/XMPlay.htm (http://www.cmoo.com/snor/weeds/SoundFonts/XMPlay/XMPlay.htm)
http://www.cmoo.com/snor/weeds/SoundFonts/...XMPlay.htm#midi (http://www.cmoo.com/snor/weeds/SoundFonts/XMPlay/XMPlay.htm#midi)
http://www.cmoo.com/snor/weeds/SoundFonts/...nfiguration.htm (http://www.cmoo.com/snor/weeds/SoundFonts/XMPlay/BASSMIDI_Driver_Installation_and_Configuration.htm)
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: mudlord on 19 May, 2011, 01:52:28 PM
Uploaded 2.0 to github on frontpage.

The changelog is done, too.
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: Dynamic on 21 May, 2011, 02:29:52 AM
Thanks to all concerned. It's been years since I did anything with MIDI but wanted to on my new laptop and didn't realise how bad the default synthesis was in Windows 7 32-bit. I must have been spoiled by relatively decent synthesis of my ancient SB 32 AWE sound card (which used the original closed SoundFont 1 format).

This driver in conjunction with Real_Font_2_1.SF2 (the first SoundFont I tried) has improved matters immensely with embedded MIDI players and the font works with BASSMIDI or FluidSynth in fb2k. I hope I can work out how to transpose and possibly edit some backing tracks too.
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: E.J. on 21 May, 2011, 01:05:00 PM
Thanks for this. It's great stuff.

Are there plans to implement support for the 64bit bassmidi libraries?
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: RichNagel on 21 May, 2011, 11:24:24 PM
I hope I can work out how to transpose and possibly edit some backing tracks too.


Gawd knows that I plug the old Cakewalk Professional v3.01 as much as I do XMPlay and the BASSMIDI Driver <grin>, but it's the best MIDI sequencer/editor hands-down  I'm not sure about Windows 7, but even as old as it is, it runs great under Windows XP (and Vista, so I've heard).

Anyhow, surf here for the lowdown and the download -> http://www.simpilot.net/~richnagel/#cakewalk (http://www.simpilot.net/~richnagel/#cakewalk)
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: mudlord on 22 May, 2011, 08:26:51 AM
Thanks for this. It's great stuff.

Are there plans to implement support for the 64bit bassmidi libraries?


No point, will break compat. with lots of things.
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: mudlord on 22 May, 2011, 06:19:25 PM
Started uploading a few recordings from the synth....
http://www.mudlord.info/musix/bassmidi_record/ (http://www.mudlord.info/musix/bassmidi_record/)

Started uploading recordings of Rich Nagel's DOOM soundtrack, with his nice SoundFont. Might look for more good examples of the synth.
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: RichNagel on 22 May, 2011, 09:39:45 PM
Started uploading recordings of Rich Nagel's DOOM soundtrack, with his nice SoundFont.


Cool! Thanks, Mudlord
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: RichNagel on 22 May, 2011, 11:30:45 PM
Might look for more good examples of the synth.


By "synth" are you refering to synthesized/electronic/techno/etc...? If so, you might like this one, almost forgot about that old page (Warning! Put your sunglasses on before surfing to the page... i.e. retro late 90's "I CAN MAKE A WEB PAGE, TOO!!!!" LOL!) -> http://www.cmoo.com/snor/weeds/The_Smiley_...Banana_Band.htm (http://www.cmoo.com/snor/weeds/The_Smiley_Dancing_Banana_Band/The_Smiley_Dancing_Banana_Band.htm)
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: Dynamic on 28 May, 2011, 05:25:27 PM
Gawd knows that I plug the old Cakewalk Professional v3.01 as much as I do XMPlay and the BASSMIDI Driver <grin>, but it's the best MIDI sequencer/editor hands-down :) I'm not sure about Windows 7, but even as old as it is, it runs great under Windows XP (and Vista, so I've heard).

Anyhow, surf here for the lowdown and the download -> http://www.simpilot.net/~richnagel/#cakewalk (http://www.simpilot.net/~richnagel/#cakewalk) :)


Thank you so much for the link, RichNagel. Incidentally I'd seen your Sound Font praised an awful lot (but had only a broken link) when I googled for free SoundFonts, so I've now downloaded that too. For anyone else who downloads Cakewalk 3.01, you need to unzip it into C:\Install\DISK1 for Setup to locate the required files to install it.
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: kode54 on 28 May, 2011, 07:31:19 PM
Are there plans to implement support for the 64bit bassmidi libraries?

Not much point to doing this anyway, since most software which will be using the driver is already 32-bit. I'm not sure about Windows Media Player or Internet Explorer 64-bit, though.

(Not to mention that there is no 64-bit DirectMusic, and it doesn't look like there ever will be, either. Oh yeah, and I also had no idea there was a 64-bit BASS or BASSMIDI to even use for this purpose.)
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: RichNagel on 28 May, 2011, 08:55:52 PM
Thank you so much for the link, RichNagel.


Yer welcome!


Incidentally I'd seen your Sound Font praised an awful lot (but had only a broken link) when I googled for free SoundFonts, so I've now downloaded that too.


I think you'll like it... like you said, I've had rave reviews about it  BTW, as far as the download, the permanent home for it is here -> http://www.un4seen.com/download.php?extra/WeedsGM3.zip (http://www.un4seen.com/download.php?extra/WeedsGM3.zip) .


For anyone else who downloads Cakewalk 3.01, you need to unzip it into C:\Install\DISK1 for Setup to locate the required files to install it.


Yeah, I should have mentioned that. The CWP301 installer expects to find it's files in a "DISK1" directory (that's how it was on the original installation floppy).
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: RichNagel on 29 May, 2011, 12:24:46 PM
@Kode54,

It doesn't look like Mudlord has logged into the forum here in about a week or so (or over at VGMusic either). I had posted a message over at VGMusic here -> http://www.vgmusic.com/phpBB3/viewtopic.ph...7&start=120 (http://www.vgmusic.com/phpBB3/viewtopic.php?f=16&t=13967&start=120) refering to a problem with the installation of the BASSMIDI Driver.

Just figured you might wanna know.
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: mudlord on 31 May, 2011, 01:40:59 AM
A workaround is in the source now....
I do not visit forums every day now. Makes more sense waiting till I am actually needed/wanted for something than constantly watching for replies.
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: RichNagel on 31 May, 2011, 12:40:51 PM
A workaround is in the source now....
I do not visit forums every day now. Makes more sense waiting till I am actually needed/wanted for something than constantly watching for replies.


A-OK  Will give it a test ASAP, thanks!

(edit) It appears that only the source for the update is available (you still have to release the updated compiled installer?)?
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: mudlord on 06 June, 2011, 03:37:54 AM
The installer will be compiled when things in my life get to a state where they are a lot more managable.

Right now, I have way too much shit personally to deal with to even be in the mood to code. Sorry.
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: RichNagel on 06 June, 2011, 11:09:26 AM
No problem, Mudlord.

I hope everything works out for you
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: mudlord on 14 June, 2011, 11:42:40 PM
Shit settled down, so I looked at some stuff.

Not sure to be honest how to best fix the issues, as they are quite bothersome to implement (dynamic loading all BASS, etc)...
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: RichNagel on 24 June, 2011, 11:28:44 PM
Not sure to be honest how to best fix the issues, as they are quite bothersome to implement (dynamic loading all BASS, etc)...


Is the "dynamic loading" that you mention refering to what I had posted over at the VGMusic forums (as a non-coder, I wasn't sure)?

For the problem that I had mentioned over there at the VGMusic forums, wouldn't all that be required was to install the BASSMIDI Driver (and support files) within it's own subdirectory?
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: mudlord on 25 June, 2011, 05:29:57 AM
I am personally curious how that ass solved it in that coolsoft synth.

I suppose that would be one solution, methinks. (installing in own directory).

I am rewriting that installer script anyway for the XG Win7 synth (since that expects VSTis for synths instead of BASS).

though legally, thats in a minefield of its own. Maybe I should do in-memory patching of the synth in the driver itself whenever a XG VSTi is loaded, to crack it. Or risk distributing a no-longer published VSTi since Yamaha can't get off its arse and support it. So I ended up having to recrack the synth myself anyway to no longer require a registry key or even installation for it to work in foo_midi properly without a installer.
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: RichNagel on 25 June, 2011, 12:16:10 PM
I am personally curious how that ass solved it in that coolsoft synth.


LOL! I think that's what he did.. install the files to their own subdirectory.


I suppose that would be one solution, methinks. (installing in own directory).


Yeah, I'm sure that would fix it. As long as the PopCap games (or any other games that use BASS.DLL) don't find it in one of the system "path" directories, it should work just fine.

Kind of similar to the hex-edit hacks that I did to rename the files (that I mentioned over at VGMusic)... the games in question can't find a BASS.DLL in one of the system path directories, so it simply uses the one that is installed and located within it's own game directory.


I am rewriting that installer script anyway for the XG Win7 synth (since that expects VSTis for synths instead of BASS).

though legally, thats in a minefield of its own. Maybe I should do in-memory patching of the synth in the driver itself whenever a XG VSTi is loaded, to crack it. Or risk distributing a no-longer published VSTi since Yamaha can't get off its arse and support it. So I ended up having to recrack the synth myself anyway to no longer require a registry key or even installation for it to work in foo_midi properly without a installer.


Hehe, all that code talk boggles my mind <grin>. In a nutshell though, it sounds as if you're attempting to get the S-YXG50 to function under Vista/7? If so, that would be extremely cool

I've been using the S-YXG50 WDM softsynth for quite sometime now (under Windows XP), and it would be great if Vista/7 users had an easier way to install it as well . Would it act as a "global" kernel driver of sorts (like it does under Windows XP, and like the BASSMIDI Driver does), or would it still be a "VSTi" sort of thing (requring a virtual MIDI patch cable)?


P.S. BTW, dunno if any of this is of help, but a collection of XG type stuff here -> http://www.cmoo.com/snor/weeds/Yamaha_XG/ (http://www.cmoo.com/snor/weeds/Yamaha_XG/)
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: mudlord on 25 June, 2011, 03:42:30 PM
Yes, using a heavily modified XG VSTi, allow for a XG driver under Windows 7/Vista.
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: mudlord on 27 June, 2011, 06:37:56 PM
Yay:
http://blog.bits-in-motion.com/2009/05/vis...-weirdness.html (http://blog.bits-in-motion.com/2009/05/vista-registry-weirdness.html)

Found the solution to all the MIDI selection madness.
Your MS funding at work, gentlemen >_>
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: mudlord on 03 July, 2011, 06:17:52 AM
http://www.vgmusic.com/phpBB3/viewtopic.ph...=120189#p120189 (http://www.vgmusic.com/phpBB3/viewtopic.php?f=16&t=13659&p=120189#p120189)

We got a VST based MIDI driver working. XG in Win7, enough said.

Quote
Would it act as a "global" kernel driver of sorts (like it does under Windows XP, and like the BASSMIDI Driver does)


Yes, it functions as a usermode driver. Not one of those crappy MIDI loopback solutions.
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: mudlord on 10 July, 2011, 02:08:27 AM
added 2.01/2.02

changelog is at usual spot.
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: raygrote on 13 August, 2011, 05:30:00 PM
Hi,
Just came across this driver awhile ago, and I must say it is the best I've seen! There are only two things I can see that would make it perfect.
First, I have midis where instruments cut out left and right, that work fine in XM Play with the same soundfont especially when the voice limit is set all the way up to 300. Maybe a voice limit in bassmidi could be added? And, while not necessary, a master reverb in bassmidi would be nice. I turned it up a little in XM Play. For XM play, I'm using midi plug-in revision 10d, which I believe is the latest version. Maybe that will help implement new features if you decide to do so. It also has mixing, transposing, and tempo control, but to include them in a realtime driver would be pretty wasteful.
Other than that, the driver is perfect! Thank you so much for rescuing us with something that actually works well. Well i'm being a bit sarcastic, there are of course other options, but why bother with them now?
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: mudlord on 19 August, 2011, 01:31:56 AM
Are you sure there is a voice limit like that? In the driver, there is a limit of 256 voices, because of BASSMIDI itself. XMPlay should have the same limit, since xmp-midi and bassmidi is the same code basically.
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: raygrote on 19 August, 2011, 02:08:33 AM
Hi,
Thank you for replying. In the newest version of the plug-in, there is a voice limit that goes up to 300. But I just lowered XM play's voice limit, and it still works fine, so it's not just that, I'm pretty sure it's an issue with short notes not being rendered properly because of being in realtime. The midi in question has a ton of drum rolls and cymbol rolls and maybe that was just too much to handle at once even with a small soundfont.
I doubt there's anything that can be done about that, but 256 voices should be sufficient.
Do you think it's worth adding a master reverb to bassmidi which is like that in the midi plug-in? It's not totally necessary but I think it would be useful.
Thanks.
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: mudlord on 20 August, 2011, 08:59:05 PM
So newest plugin has a increased voice limit? never klnew that.
and no, I dont think its worth the effort honestly to add more controls than volume.
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: PaVliQ on 05 September, 2011, 11:47:13 AM
Great. I have installed it on several machines on XP. Works perfect.


But I don't see any advanced SF2-synth options in config settings of midi-driver like:

-Reverb & Chorus & Gain e.t.c. thats exists in XMPLAY SF2 BASSMIDI config (a competent reference sf-2 midi decoder for me)

-Reverb, Chorus, Samplerate, Bitdepth, Buffer, Polyphony e.t.c like in Tuxguitar SF2 Fluidsynth Plugin


Maybe I don't understand this in a true meaning, but I see what I see: Great SF2 replacement of standard Windows GS Soft Synth gm.dls with the same non customisable settings. Simplier than ever possible.


P.S. From all sf2 synths I have seen a more advanced settings was in twsyng.exe (TiMidity++ Windows Synthesizer) - but it's very buggy and non-stable.

It's good to develop this system BASSMIDI driver that stable as it is, but with advanced preferences of highly customised in settings like on timidity++ and fluidsynth. In spite of all, this Windows BASSMIDI driver is best from all. And think will be better having more advanced options in driver settings.


And if you don't want to make more complex and advanced settings in driver, I agree with you because of a rule "more simplier - more stable".
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: raygrote on 05 September, 2011, 12:54:33 PM
I agree with you. They would be nice to have but aren't necessary. Besides, I use XM Play for my rendering, so bassmidi is only there for the sequencing. I can deal with certain things not sounding exactly the same while I'm sequencing it.
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: mudlord on 08 September, 2011, 06:57:57 AM
I really need to get my ass in gear and fixing some bugs before adding new features...
Same goes for the VST driver.
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: bennetng on 17 September, 2011, 12:58:38 PM
I am using win7 x64 and BASSMIDI driver version 2.02 but the volume setting in the driver configuration dialog doesn't work (always maximum no matter what I set)
Is this only my problem?

Reduce volume in Windows mixer is not a good method as the output is already clipped before entering Windows mixer.
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: mudlord on 18 September, 2011, 12:56:52 AM
Known bug.
Keep pestering us about it with a bugreport on the github page and we will fix it.
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: raygrote on 18 September, 2011, 07:36:22 PM
Interesting bug there. My problem with volume is opposite at least on my computers with win xp sp3 I believe. Even when everything is maxed out, notes at velocity 127 are just at normal volume for me. I think when the volume bug is fixed, the default should be at around halfway up, and at max volume things are clipping, so that we have a wide range of volumes to choose from, from too quiet to distorted. Just my opinions.
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: mudlord on 19 September, 2011, 08:03:18 AM
When was volume changing last working?
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: raygrote on 19 September, 2011, 04:10:48 PM
Hmm, I don't know. I never had to use it since it was maxed out by default and it was almost loud enough, not quite.
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: mudlord on 19 September, 2011, 09:42:32 PM
Oh, weird, will need to look at it.
In the meantime, tried altering the registry key at HKEY_CURRENT_USER\Software\BASSMIDI Driver?
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: bennetng on 20 September, 2011, 07:29:53 AM
Oh, weird, will need to look at it.
In the meantime, tried altering the registry key at HKEY_CURRENT_USER\Software\BASSMIDI Driver?

No difference, volume unchanged.
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: Batman321 on 20 September, 2011, 01:48:53 PM
How do I uninstall it?
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: raygrote on 20 September, 2011, 08:06:09 PM
Hi,
there is an uninstall option in all programs, if you're using XP. Don't know about anything higher but it shouldn't be hard to find, just follow standard uninstallation procedure that you would with most other programs.
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: HunterZ on 21 September, 2011, 10:25:06 AM
What happened to Mudlord's account and the project page on Github? They're both giving 404 errors now.
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: mudlord on 21 September, 2011, 04:21:30 PM
I'm migrating the source code and binaries to my own server.
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: HunterZ on 21 September, 2011, 04:42:00 PM
I'm migrating the source code and binaries to my own server.

Thanks. Was causing some concern over at VOGONS.
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: mudlord on 21 September, 2011, 04:44:50 PM
Sorry bout that.
Source for bassmididrv is here: http://svn.mudlord.info/bassmididrv (http://svn.mudlord.info/bassmididrv)
Binaries are here:                    http://www.mudlord.info/crap/audio/ (http://www.mudlord.info/crap/audio/)
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: mudlord on 23 September, 2011, 12:41:41 AM
looking at volume bug now, seems for some reason the driver itself won't read the key which is set in HKEY_CURRENT_USER.
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: raygrote on 23 September, 2011, 06:49:57 AM
Now, that is pretty strange. Hopefully it can be fixed.
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: [JAZ] on 23 September, 2011, 02:02:46 PM
looking at volume bug now, seems for some reason the driver itself won't read the key which is set in HKEY_CURRENT_USER.


The first obvious question is... are you sure it is running as the current user and not system or something else?  (As i understand it, bassmidi acts as a driver)
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: mudlord on 23 September, 2011, 08:38:32 PM
you were right, fixed.
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: raygrote on 23 September, 2011, 09:33:56 PM
Here's a question. If the volume bug gets fixed, will a new version get released with just that fix? Or will you wait until you fix other things? Personally I would prefer to wait til other bugs are fixed, since you'd get all of the revisions in one update.
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: mudlord on 24 September, 2011, 05:56:14 AM
the second one
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: mudlord on 11 October, 2011, 09:22:28 AM
updated site, thanks to richnagel for letting me use his site for the new domain.
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: mambo on 26 October, 2011, 11:38:24 AM
Hello,
I just started using the BassMidi driver together with VanBasko and it happens very often that when I play some MIDIs and stop them with the stop button going to press again after few seconds the Play button VanBasko hangs and in the TasKManager I see the CPU used at around 50%. I have to kill it manually
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: mudlord on 28 October, 2011, 02:38:31 PM
known issue with delay. might work on that, cant make promises.
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: markbg on 10 November, 2011, 03:52:29 AM
Hi,
this is my first post, so first of all hello to everyone from Italy!
I am posting because I need some help: I was looking for a good SW synth with low latency and I found this bassmididrv that is considered a great one, I would like to use it to playalong with my midikeyboard and benefit of good soundfonts and low latecny.

My problem: I tried to install it (both the low lat. and the recent 2.0 version) but I am unable to generate any sound out of it. Porbably I am forgetting something really stupid but I cannot figure it out.

I have an ASUS P7P55 motherboard with VIA Vynil VT1828S embedded audio and Windows XP SP3.
midi playback works fine with:

-MS GS synthetiser (XP default)
-SynthFont synthetiser with and without ASIO drivers, routing through Maple Midi virtual cable

The installation of bassmidi goes well. I see the device listed and I set it as a default as a midi out and I force the selection to it also in the midi players programs.
I can open and see the midi mixer panel with all the 17 volume sliders, but when I start the playback there is no activity shown in it (probably Vu-Meters should show some movement) and no sound, while I can see the midi stream is sent to the driver from the app.

side notes:
- it seems that version 2 does not provide the disinstaller, while it comes with the 1.6
- after the first attempt, when I was selecting the bassmidi synth as output port in the player, I got a pop up with a sort of "general internal error" in the driver. To fix this I have to force via control panel/audio the selection of bassmidi synth as default output.
- tried to remove and add back asio drivers
- tried different soundfonts loaded
- tried to remove maple midi cable, since with bassmidi is not needed
- I am unable to disinstall entirely the bassmidi driver from the controlpanel/system/hardwaremanger/legacyaudiodrivers, I remove it, I reboot, it comes back

any idea of what could be interfering?
thank you,
best regards,
Mark
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: mudlord on 15 November, 2011, 12:29:49 AM
im sure there is more stable players than SynthFont...cannot begin to go on about how bad it is.
as for the rest, driver works here....
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: kode54 on 15 November, 2011, 11:22:28 AM
The driver currently routes through your default DirectSound device. Is this a working sound output device?
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: markbg on 15 November, 2011, 05:34:39 PM
The driver currently routes through your default DirectSound device. Is this a working sound output device?

today I made a test just using the bass libraries:
if I use bassasio, the simple sinewave player is able to work, while if I use bass, I got the error " 3 -no output device"
I have a nvidia video card, maybe the system is detecting its digitalaudio outputport as the first one directsound,how can I check this and modifybthe enumeration.?
best regards
mark
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: mudlord on 15 November, 2011, 09:05:53 PM
Okay, that suggests a more severe underlying issue.

What version is your sound card drivers? Do other applications work?
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: markbg on 20 November, 2011, 01:57:23 PM
Okay, that suggests a more severe underlying issue.

What version is your sound card drivers? Do other applications work?

Hi,
yes, bassmidi synth is the only one that does not work.Synthfont for example works well, both with asio and without.
I tested also some midi files with XMPlay today, that I think is using the same bass libraries, and it works well and I am able to change the soundfont too.

The audio driver is the latest one: VIA High Definition Audio 04.08.2010  ver. 6.0.1.8700
I cheched and this is correctly set as default playback sound device.

The message I get when I try to use bassmidi syth is exactly this one:
"Can't initialise output device (Error code 3)"

is there any log / dump that I could get to facilitate the troubleshooting?

is there a way to use bassmididrv together with bassasio.dll instead of bass.dll (this seems to work with other programs)?

thank you for the help
best regards,
Mark
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: mudlord on 23 November, 2011, 07:53:58 AM
Very odd, I have a similar chipset and all is well here O.O

As for BASSWASAPI/BASSASIO, I have to personally wonder why such a odd workaround.
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: markbg on 27 November, 2011, 04:08:35 AM
Very odd, I have a similar chipset and all is well here O.O

As for BASSWASAPI/BASSASIO, I have to personally wonder why such a odd workaround.


Hi,
today I installed a new fresh XP SP3 on another partition and it works if I boot from this one!
Clearly it is not an hardware problem.
Driver versions are the same too, but there must be something from some previous installations that is interfering. I had a SB Live in the past that was removed, maybe its driver is still listed somewhere and seen as #1.

best regards,
Marco

p.s. and thank very much for the support!
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: mudlord on 09 January, 2012, 09:01:04 PM
weird, so driver installer bugs again?

got around to uploading older installs, so people can try out older ones if they work better.

http://www.mudlord.info/crap/audio/ (http://www.mudlord.info/crap/audio/)

Thanks to Rich Nagel for archiving all the installers so I can grab them, much appreciated.
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: raygrote on 09 January, 2012, 09:17:31 PM
Hi Mudlord,
Hopefully Bassmidi development is going well.
Just a few questions.
1. I'm using Bassmidi 1.06 low latency and it works better for me than 2.02 but doesn't seem to have any new stuff that I can see anyway. When new versions of Bassmidi get released, particularly those with major changes, will low latency versions of them be released as well? Or maybe a latency setting could be added even if it's just in a config file somewhere like Timidity does, or maybe a slider like in some other synths.
2. Is the volume slider fixed? If so, IMHO it would be a good idea to release that as 2.03 or something.
Thanks for what we have so far. I can use 1.06 as is.
BTW, I wouldn't recommend trying bassmidi 1.0, as it has looping issues if the finish loop point is too close to the end of a sample. This was also a bug in the older versions of the midi plug-in of XM Play.
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: mudlord on 09 January, 2012, 09:33:20 PM
Quote
1. I'm using Bassmidi 1.06 low latency and it works better for me than 2.02 but doesn't seem to have any new stuff that I can see anyway. When new versions of


Thanks for the awesome idea, I don't personally see the harm in adding extra options to the installer to allow picking of "low latency" forks, which forgoe the DirectMusic implementation for something more basic. Sure a little more work, but nice idea!

Main reason why 2.0x versions have latency is DirectMusic: Which is something we cannot work around in that. Thanks a lot MS >_>. But its needed for the VST driver though, unless we go to the extra hassle of coding a DirectSound backend.

Quote
2. Is the volume slider fixed? If so, IMHO it would be a good idea to release that as 2.03 or something.
Thanks for what we have so far. I can use 1.06 as is.


I honestly can't remember when it first broke. I remember tinkering with the SVN at some point to but I can't remember when.


Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: mudlord on 17 January, 2012, 04:44:51 PM
updated vstdriver to 1.1
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: raygrote on 07 February, 2012, 07:26:26 PM
Hi guys,
This is a pretty complicated problem I am having with the Bassmidi driver. Hopefully you can figure it out.
About six months ago I installed Bassmidi 2.02 on here. A few months later a friend told me that bassmidi 1.06 low latency was working better for him, so I put it on, and sure enough it was working for me too. But, I have a bad habbit of forgetting to uninstall other versions of stuff, so Bassmidi 1 was installed right over Bassmidi 2. bassmidi 1 was working fine but the bassmidi 2 wasn't working at all. So, I just avoided using that version of the driver.
But, some programs don't like two drivers with the same name, which was happening in my bassmidi situation. So I tried to install one of them. Bassmidi 1 was the only one I could actually get rid of because Basssmidi 2's uninstaller may have gotten deleted or something. I don't know enough to tell exactly what might have happened but Bassmidi 1 was the only one that was showing up in C Clean'er's uninstaller.
Once Bassmidi 1 was removed, I discovered that Bassmidi 2 was working again, but the shortcuts were missing, like configure driver and uninstall. So, I reinstalled Bassmidi 2 thinking I could get them back and working properly, then I would uninstall it and start over using Bassmidi 1 since that is my preferred version now.
Unfortunately it's not working out. After reinstalling Bassmidi 2, some problems occured. Bassmidi no longer works now because everything that tries to use it says it can't open the output port because it is already in use. I can't uninstall it because the uninstaller was not installed. I extracted Bassmidi 2's setup file with uniextract, and found the uninstaller and tried to run it, but it popped up a window and then it disappeared and nothing was changed.
So, I have a severely broken Bassmidi driver 2.02 that I can not get rid of. Is there any way i can clean this up so I can start over?
Thanks very much in advance!
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: mudlord on 08 February, 2012, 01:46:46 AM
Run regsvr /u bassmididrv.dll on the driver dll

(https://hydrogenaud.io/imgcache.php?id=7d90bcc281be4424ad7ce57c85ffc4ae" rel="cached" data-warn="External image, click to view at original size" data-url="http://i.imgur.com/jjntC.jpg)

Delete any bassmididrv.dll related keys from there.
Find any bassmididrv.dll files on your drive and delete them.
Then, restart.
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: raygrote on 08 February, 2012, 06:53:14 AM
Hi guys,
I am having a pretty big problem with Bassmidi now which has probably resulted in me having two broken bassmidis trying to use each other..
It started when I got bassmidi 2.02 about six months ago. As you might have read from earlier posts, I went back to 1.06 because its low latency was working better for me. However, when I installed version 1, I forgot to uninstall version 2. So it left two bassmidi ports in my outputs, one of which didn't work.
I thought I would just let it go since bassmidi 1 was working as expected, but some programs didn't like the fact that I had two midi devices with the exact same name, so I had to uninstall one of them. So, Bassmidi 1 was the only thing that I could actually get rid of, so I did that. Then Basmidi 2 was working again but all of its shortcuts, like configure driver, and uninstall, were missing. So, I reinstalled it, thinking I could uninstall it properly and put Bassmidi 1 back on.
Problem was, when I reinstalled basmidi 2, it came up with several errors. I wasn't using it but there were quite a number of files it couldn't write.
I checked one of the .exe files with unlocker, and it came up with a host of other files it thoughht were using it, the list is huge. I have restarted when the installers told me to, so I'm not quite sure what's going on. When it instaled what it could, it stopped working altogether. Now anything that tries to use Basmidi says it can't open the output port or some variation of that. The uninstaler doesn't seem to work, it didn't even look like it had gotten installed. I even tried extracting it from the setup file with uniextract, and copying it to the folder where it needed to be, and it just came up for about two seconds and disappeared. I'm guessing it's because the thing wasn't completely installed so it doesn't know how to uninstall it?
As you guys might gather, I don't know enough to go fixing registry issues, so I haven't ventured there. i'm not that savvy.
so, does anyone know how I can fix this and start over?
Thanks very much in advance!
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: db1989 on 08 February, 2012, 12:56:38 PM
I already merged in and informed you via PM about your earlier post (now #122) where you said almost exactly the same thing, and mudlord already replied with a suggested method of fixing your problem. Was something about that insufficient?
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: raygrote on 08 February, 2012, 03:01:01 PM
Hi DB1989,
My sincere apologies!
I didn't see you murged it. I will be much more careful next time. I posted that last message in a hurry this morning.
Mudlord, I don't know exactly what you mean by Run regsvr /u bassmididrv.dll on the driver dll. Since I'm visually impaired I can't see the image you posted. what steps should I take to get to it?
The rest looks pretty easy.
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: db1989 on 08 February, 2012, 03:23:31 PM
It’s no problem! It was a lot of writing to do again; I bet you now wish that you’d spared your fingers all that extra work.

Whilst I can’t presume to speak for mudlord, I’ll try to help.

First, you can run the suggested command by clicking the Start button and selecting Run (or use the shortcut: hold the Windows key and press R) and then typing “regsvr /u bassmididrv.dll” and clicking OK/pressing Enter.

Next, his image: It’s a screenshot of Registry Editor, viewing this registry entry:
Quote
Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows\Windows NT\CurrentVersion\Drivers32
Do another Run command, but this time with the text “regedit”. Next, use the newly opened program to navigate to said registry key, and follow mudlord’s instruction of deleting any values therein that mention bassmididrv.dll. Next, use a Windows file search to find any instances of said DLL, and delete them. Finally, restart.
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: raygrote on 08 February, 2012, 06:11:01 PM
Hi,
Those instructions were exactly what I needed. However several more problems presented themselves.
First, I am using XP SP3 here. I will have to upgrade soon. Anyway, that may be helpful when I explain the following things.
when I went to the run dialog and typed that command, Windows said it couldn't find regsvr. So, I downloaded a program called regsvr32 from the microsoft support center. I ran that command through it, and it said that unregistration of bassmididrv.dll succeeded.
The only bassmididrv.dll file I have is in the system32 folder. That's probably expected. I cannot delete it because when I
do, it brings up the typical file is already in use message. I'm guessing then that the registry thing didn't work out. But, I haven't restarted yet, I just ran regsvr then tried to delete the file. Maybe a restart is in order? I got the impression that I should delete the file first before the restart though.
There are a few references to bassmididrv.dll in my registry as well. Most of them are in folders I never heard of, nothing like the directory in your post. If anyone wants a list I can try to make one, but I haven't even counted them yet. Then again a registry was meant to have folders nobody knows about.  I'm thinking it would be safe to delete those references but I haven't touched them yet.
I'm not in familiar territory here. Any further advice?
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: mudlord on 08 February, 2012, 06:23:01 PM
Maybe delete the registry keys in the Drivers32 repository ONLY and unregister the DLL, then restart? Then delete the dll?
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: kode54 on 08 February, 2012, 08:31:04 PM
The exact command is regsvr32. And you may need to supply the full path to bassmididrv.dll, which is in C:\windows\system32. And since you are using a 32-bit operating system, the registry path does not include the Wow6432Node part.
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: raygrote on 09 February, 2012, 06:03:12 AM
Hi all,
Mudlord, the suggestion was very helpful. I counted three Bassmidi references to get rid of. Then I restarted and the DLL went without a problem. I deleted the whole bassmididrv folder while I was at it.
Code54, I figured those little differences out with a tiny bit of research, and by accident. Thanks for clearing that up, as I wasn't so sure.
So Bassmidi 1.06 is working flawlessly on here now, and it is only showing up once. Things are good.
Even though I am still using an older version,I am very much looking forward to see what comes  next. Hopefully this issue won't be one of those things. AT least I know what to do if I forget to uninstall the old version.
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: mudlord on 12 February, 2012, 12:09:11 AM
I thought we already added functionality to detect versions already installed to the installer, so if you run a newer installer, it will uninstall the old.
EDIT: yes, current SVN does so o.o
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: mudlord on 13 February, 2012, 08:30:57 AM
I am very much looking forward to see what comes  next.


mainly spent time trying to fix some last standing latency/stuttering issues in the winmm code base.
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: mudlord on 26 February, 2012, 06:27:40 PM
I would like to know of any games that have issues with the current driver.
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: mudlord on 27 February, 2012, 03:42:27 AM
there, 3.0 out. major changes on the winmm driver.
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: ex-driver on 01 March, 2012, 10:17:07 PM
Still crashes on Winamp and Games like Final Fantasy 7. I installed the 2.01 again....
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: ex-driver on 01 March, 2012, 10:20:11 PM
The Problem exist  since the 2.02 Version.
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: mudlord on 01 March, 2012, 11:39:10 PM
weird, I tried winamp the other day and it worked.
what OS?
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: ex-driver on 02 March, 2012, 06:37:44 AM
Windows 7 Professional 64 bit

Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: revangel on 02 March, 2012, 11:28:07 AM
If you want a absolutely great experience listening to old Game Midis, search for the 055.1mg sound canvas v1.0 bank.sf2 soundfont. Its absolutely worth it, I never experienced Midis so close to the hardware-level with BASSMIDI and that soundfont. Link is http://www.sf2midi.com/soundfonts/file-det...nk-sf2-200.html (http://www.sf2midi.com/soundfonts/file-detail/055-1mg-sound-canvas-v1-0-bank-sf2-200.html)
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: ex-driver on 02 March, 2012, 04:59:29 PM
There must be a reason for this problem. All Versions before wokrs fine. After 2.02 it began...
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: mudlord on 02 March, 2012, 08:04:26 PM
Try downloading again, it has a fix for BASS init.
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: ex-driver on 03 March, 2012, 06:51:05 AM
It works mudlord !! XD     

No crashes in FF7 or Winamp and your latest driver fixed also the missing Midi track bugs on FF7 ( 2nd drumkit channel )

Good Job !!  Now I can testing your latest driver with no interruption

Great THX !!
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: mudlord on 03 March, 2012, 08:21:52 PM
hooray >_>
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: ex-driver on 07 March, 2012, 07:45:45 AM
One bug I noticed. It was fixed with v2.0 and occurs again in v3.0

-fixed a GS rhythm channel allocation bug.

On Winamp testet:
(XM Play works right with this MIDIS)
with GS MIDIs with 2 drumkit channels

Bank MSB 127

for example:

Device 095 / 127 (sweep pad) v2.0
Device 095 / 127 (drumkit) v3.0





Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: mudlord on 07 March, 2012, 07:48:16 AM
will refer to kode54 to fix up that.
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: kode54 on 07 March, 2012, 07:27:40 PM
That was fixed in what was originally the newer DirectMusic based driver, but never applied towards the original driver. An update has been pushed, I'll wait on mudlord to take care of uploading a new installer.
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: mudlord on 07 March, 2012, 08:11:10 PM
and done..redownload from same link.
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: ex-driver on 07 March, 2012, 08:37:37 PM
Its really fixed ! =) Good job  friends
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: ex-driver on 07 March, 2012, 09:56:19 PM
Sry for a next bug report i noticed 

I tested the game Final Fantasy VII where I noticed this bug. A sound problem during normal sound and BassMIDI driver during the game. After 3 trys starting the game one of them works a bit.

Here is a mp3 (packed in rar) file where you can hear this strange problem. Only noticed in this game. It works fine with the v2.01 BassMIDI driver with drumkit 2nd channel missing bug which is fixed in V3.0.

The mp3 file contains: game start> loading a save file > battle and ending > close the game.

http://www.file-upload.net/download-417289...er-3.0.rar.html (http://www.file-upload.net/download-4172891/Driver-3.0.rar.html)

I hope you got any idea what it could be.

Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: ex-driver on 07 March, 2012, 10:17:52 PM
P.S (It runs a bit) Sometimes it works sometimes this happen. I mean.
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: mudlord on 09 March, 2012, 05:04:46 AM
Our advice would be to somehow get your hands on a decent PS1 emulator and a copy of FF7.
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: ex-driver on 29 May, 2012, 06:12:58 PM
One thing i missed is the caching feature: "Static caching" has better performacnce on Playback. XMPlay supports this for default.
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: ex-driver on 30 May, 2012, 08:45:24 AM
missing
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: mudlord on 29 July, 2012, 07:05:53 PM
Updated to have sinc interpolation plus kode54's fixes to GS detection.
The VST driver got a complete rewrite too, now it uses the same basecode as the bassmidi driver.
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: bennetng on 31 July, 2012, 12:23:58 AM
Hi,

May I ask for even better interpolation quality? The current sinc interpolation still has audible aliasing, audio sample included:

http://www.sendspace.com/file/cmdxd7 (http://www.sendspace.com/file/cmdxd7)

midi data is from vgmusic
http://www.vgmusic.com/music/console/ninte.../DKCMine-GM.mid (http://www.vgmusic.com/music/console/nintendo/snes/DKCMine-GM.mid)

soundfont can be downloaded here (AnotherGS v2.x)
http://music.geocities.jp/bennetng01/ (http://music.geocities.jp/bennetng01/)

I used the foobar plugin to render the audio files, I need to set the plugin's sample rate to 192k to reduce aliasing, the 44k one has severe aliasing.

The driver version of BASSMIDI cannot change sample rate to reduce aliasing, the foobar version of BASSMIDI cannot change volume conveniently (need to change replaygain volume instead of output volume, otherwise clipping will occur in louder midi files) . I really hope these problem will be fixed in future versions.

My X-Fi hardware synth and sfz software synth (when set to high quality) have no audible aliasing when using the same soundfont. I also followed the instruction in MAZ's aliasing test and found that BASSMIDI's aliasing is pretty severe:
http://www.maz-sound.de/index.php?show=mpc...&page_id=60 (http://www.maz-sound.de/index.php?show=mpcs&id=&mpcg=&mpc_id=34&page_id=60)
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: kode54 on 31 July, 2012, 03:31:32 AM
You'll have to report any aliasing issues in BASSMIDI to Ian Luck at un4seen.com, as it's his project.

Also, at least with Windows Vista or newer, the MIDI files should not clip in foobar2000, as long as you use DirectSound output. Otherwise, you'll need an Advanced Limiter DSP or similar.
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: bennetng on 31 July, 2012, 01:37:25 PM
Thanks. I just compared DS, WASAPI and ASIO output and found that the volume/clipping problem is not related to BASSMIDI's foobar plugin. Also thanks for pointing me to un4seen.com.
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: mudlord on 02 August, 2012, 07:58:04 PM
3.1 uploaded.
Major changes were done, including compressed sample support in SoundFonts. This makes it in line with most recent foo_midi.
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: mudlord on 16 August, 2012, 03:27:31 AM
3.2 out, with updates to the sound output for Asus Xonar cards. Includes the updated soundfont packer too.

the vsti driver got updated too, with same output stuff as well as fixes to the config too (sorry to the people that had troubles).
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: RichNagel on 16 August, 2012, 09:14:34 AM
3.2 out, with updates to the sound output for Asus Xonar cards. Includes the updated soundfont packer too.


Did you actually upload the new installer? It appears that:

http://www.mudlord.info/bassmididrv/bassmididrv.exe (http://www.mudlord.info/bassmididrv/bassmididrv.exe) (502,324 bytes)

...is the exact same as the bassmididrv.exe v3.1 installer, byte for byte <grin>.
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: kode54 on 16 August, 2012, 09:25:41 AM
I have uploaded the latest version here, until mudlord updates his site:

http://kode54.foobar2000.org/bassmididrv.exe (http://kode54.foobar2000.org/bassmididrv.exe)
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: RichNagel on 16 August, 2012, 09:30:01 AM
I have uploaded the latest version here, until mudlord updates his site:

http://kode54.foobar2000.org/bassmididrv.exe (http://kode54.foobar2000.org/bassmididrv.exe)


A-OK, and thanks


BTW, I've been meaning to ask another question.

In one of your changelog comments at https://github.com/mudlord/BASSMIDI-Driver/...4e437198cb71bdc (https://github.com/mudlord/BASSMIDI-Driver/commit/b4def5f0fd41b23cdda8100534e437198cb71bdc) you posted:

Quote
Fixed DirectSound fallback to only occur if sound was opened in floating point mode first


...and over in the VOGONS BASSMIDI Driver message thread http://vogons.zetafleet.com/viewtopic.php?t=27975 (http://vogons.zetafleet.com/viewtopic.php?t=27975) you posted:

Quote
Bah, I misinterpreted the GX mode button. It does seem to interfere with floating point output through DirectSound. I've implemented my own sound output code based on XAudio2. That failing, it will attempt to open DirectSound with floating point, or otherwise fall back on 16 bit integer format.


I was just a-wondering... does that mean that if there was some sort of problem starting the BASSMIDI Driver in "DirectSound" mode, that the driver would fallback to "WinMM" mode? Does the "DirectSound" mode have anything to do with the way that the driver used to work ("DirectMusic" mode) several versions ago?

As a non-coder... sorry for the (probably) dumb questions, that I (probably) won't understand the answers to in the first place <grin>
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: kode54 on 16 August, 2012, 09:37:37 AM
The DirectSound has to do with how BASS worked in the earliest driver, as well as the more recent versions. I replaced BASS for output, and instead use my own output interfaces. I default to XAudio2, which is guaranteed to support floating point output. If that fails to open, likely in the event that the user does not have XAudio2 installed (which requires the DirectX runtime to be installed on Windows 7 and older systems), then it will fall back on DirectSound. On Vista and up, it will then attempt to open DirectSound using a floating point sample format. If that fails, it will try to reopen it with 16 bit integer format.

The XAudio2 driver also uses a Windows Vista sound device interface to register a callback, so that it will be notified any time the default sound output device changes, which will cause it to tear down and reopen the sound output. This is because XAudio2 does not react well to its current device being disconnected. It likes to stall the output, which would stall playback completely while the player waits for a free buffer to output more sound. Nope, no free notification of sound device error in that case. So, thus, a system notification callback, and I tear it down myself.
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: RichNagel on 16 August, 2012, 02:08:57 PM
Thanks for the detailed info, Kode54

Hehe, even as a non-coder, I understood your detailed explaination fully

BTW, one last little question:

That VST Driver that you and MudLord created... from what i understand, that allows any VSTi DLL to be used as a standard Windows MIDI device, correct?

My main question is (if so):

When used with the S-YXG50 VSTi DLL, does it have extremely low latency (like the newer versions, and the oldest versions; of the BASSMIDI Driver do)?

The standalone Yamaha S-YXG50 v4.23.14S WDM has some pretty bad latency running under Windows XP. And I, was simply wondering if using the S-YXG50 VSTi DLL with your VST Driver resulted in really low latency (like the BASSMIDI Driver has)... or if the latency is "hard-coded" into the DLL itself.
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: mudlord on 16 August, 2012, 06:35:51 PM
latency for the XG VSTi sounds fine to me O_O
bassmidi driver reuploaded.
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: RichNagel on 16 August, 2012, 07:18:28 PM
latency for the XG VSTi sounds fine to me O_O


Thanks for the info... I'll definitely have to give that a try

'Twould be awesome if my SBLive_A/B+BASSMIDI Driver would 'natively' synch to the S-YXG50 (not to mention, the ability to use some of the other VSTi's that I have as a regular WinDoZe MIDI device) 
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: kode54 on 16 August, 2012, 10:55:10 PM
The latency of both the BASSMIDI and VSTi drivers is hard coded at 80ms for XAudio2 and 100ms for DirectSound. Although actually, it may not be that bad.
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: RichNagel on 17 August, 2012, 02:38:40 AM
Guys,

I seem to be having a pretty bad problem when attempting to uninstall version 3.1 of the BASSMIDI Driver (Re: this pic -> http://jasonwilliams400com.startlogic.com/...all_Problem.png (http://jasonwilliams400com.startlogic.com/snor/weeds/Temp/BASSMIDI_Driver_v3.1_Uninstall_Problem.png) ).


I had installed version 3.1 without a hitch, and everything functioned fine. On this particular PC (my main machine) I was updating to v3.1 from one of the 2.x versions of the driver (I forget which version offhand).

After installing v3.1, although everything worked properly, I noticed the things in the above-linked image in the "Before uninstalling v3.1" pics. I didn't really give that a second thought... two entries in the registry, and two entries in the "Legacy Audio Drivers" section of the Device Manager... as everything worked OK with the driver.


The reason that I mention the above, as I'm wondering if that (two entries) could have something to do with the problem I had uninstalling v3.1:


After uninstalling v3.1 the bottom two pics in the image are what I saw in the "Legacy Audio Drivers". I then tried going ahead and installing v3.2, but after the installation all of those entries were still listed.

That sort of scared me a bit, as all of those extra entires are NOT even MIDI devices at all.

I went ahead and did a WinDoZe System Restore, which got me back to v3.1 of the driver (and the entries in the top set of pics, of course).

Any idea as to what could cause this?


P.S. Dunno if this helps any, but here is a list of my usual WinDoZe MIDI devices:

0 = SB Live! Synth A [DF20]
1 = BASSMIDI Driver
2 = Out To MIDI Yoke:  1
3 = Out To MIDI Yoke:  2
4 = Out To MIDI Yoke:  3
5 = Out To MIDI Yoke:  4
6 = MT-32 Synth Emulator
7 = SB Live! Sw Synth [DF20]
8 = SB Live! Synth B [DF20]
9 = SB Live! MIDI Port [DF20]
10 = YAMAHA XG WDM SoftSynthesizer
11 = Microsoft GS Wavetable SW Synth
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: RichNagel on 17 August, 2012, 02:50:56 AM
The latency of both the BASSMIDI and VSTi drivers is hard coded at 80ms for XAudio2 and 100ms for DirectSound. Although actually, it may not be that bad.


Yeah, the v1.x and 3.x versions seemed to be quite a bit lower than that

That being said, with the 2.x of the BASSMIDI Driver here's the latency that I measured:

http://jasonwilliams400com.startlogic.com/...2.x_Latency.gif (http://jasonwilliams400com.startlogic.com/snor/weeds/SoundFonts/XMPlay/BASSMIDI_Driver_v2.x_Latency.gif)

...about 100ms.


But, with the 1.x and 3.x versions, here's the latency I measured:

http://jasonwilliams400com.startlogic.com/...Low_Latency.gif (http://jasonwilliams400com.startlogic.com/snor/weeds/SoundFonts/XMPlay/BASSMIDI_Driver_v1.x_and_v3.x_Low_Latency.gif)

REALLY low


BTW, the way I performed that test:

I configured my sequencer's port 1 for my SBLive hardware synth, and port 2 for the BASSMIDI Driver.

I then sequenced a single percussion note for each track (I forget which patch now... maybe the woodblock?), and then hard-panned the SBLive to the left and the BASSMIDI Driver to the right.

Fired up GoldWave, recorded my "masterpiece" <grin>, and those screenies were the result
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: zizouhiba on 17 August, 2012, 07:38:13 AM
Hi Everybody,

I tried MASSMIDISynth GS/XG Scale Tuning System Exclusive Messages.
All notes are correctly pitched except the B :

Scale Tuning B : F0 43 10 4C 08 00 4C Cents F7 (Cents from 00 to 7F)

If you can test it please.

Thanks
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: kode54 on 17 August, 2012, 03:54:42 PM
http://jasonwilliams400com.startlogic.com/...all_Problem.png (http://jasonwilliams400com.startlogic.com/snor/weeds/Temp/BASSMIDI_Driver_v3.1_Uninstall_Problem.png) ).

I would advise looking at HKLM\SOFTWARE\[Wow6432Node\]Microsoft\Windows NT\CurrentVersion\Drivers32 after unintstalling. There should only be one midi* entry of wdmaud.drv for each normal MIDI device.

That failing, I would also suggest using Process Monitor to log the uninstaller and see what keys it's touching.

Oh, right. It also looks like you have a legacy version of BASSMIDI Driver installed, or at least still in the registry. That entry without the bassmididrv directory in the path should be removed, and the entries that follow it renumbered.
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: RichNagel on 17 August, 2012, 05:35:08 PM
I would advise looking at HKLM\SOFTWARE\[Wow6432Node\]Microsoft\Windows NT\CurrentVersion\Drivers32 after unintstalling. There should only be one midi* entry of wdmaud.drv for each normal MIDI device.


Oh, right. It also looks like you have a legacy version of BASSMIDI Driver installed, or at least still in the registry. That entry without the bassmididrv directory in the path should be removed, and the entries that follow it renumbered.


OK, to recap (just so's I don't make a total mess of this <grin>):

(Re: this image -> http://jasonwilliams400com.startlogic.com/...try_Entries.png (http://jasonwilliams400com.startlogic.com/snor/weeds/Temp/BASSMIDI_Driver_v3.1_Windows_Registry_Entries.png) )

Should I make the registry edits BEFORE uninstalling my current version (3.1)?


In the right-hand pic of the image above, I'm supposing that I should edit these entries:

midi = wdmaud.drv
midi1 = bassmididrv.dll
midi2 = bassmididrv\bassmididrv.dll
midi3 = myokent.dll
MIDI4 = MT32Emu.dll

..to this:

midi = wdmaud.drv
midi1 = bassmididrv\bassmididrv.dll
midi2 = myokent.dll
MIDI3 = MT32Emu.dll


And then in the left-hand pic of the image above, I should delete this entry:

bassmididrv.dll = bassmididrv.dll

...but leave this entry:

bassmididrv\bassmididrv.dll = bassmididrv.dll

...correct?

And of course, leave all of the other entries like they are, right?


P.S. Almost forgot... are there any other "midi#" entries hidden away in the Windows registry that I should look for (or be concerned with)?


(Edit) P.P.S. You know, after looking at those sections in the registry, an interesting thing:

All of the entries/devices listed in the "Legacy Audio Properties" applet shown in the first image that I linked to (in my previous post) are contained in that section of the registry (in the image in this post).
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: kode54 on 17 August, 2012, 08:20:00 PM
There shouldn't be any other entries to mess with, except for maybe the entry that handles the default entry, which is set by the configuration programs. That shouldn't cause random drivers to appear as MIDI devices, though.
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: RichNagel on 17 August, 2012, 10:51:56 PM
There shouldn't be any other entries to mess with, except for maybe the entry that handles the default entry, which is set by the configuration programs. That shouldn't cause random drivers to appear as MIDI devices, though.


Thanks for the info, Kode54  Anyhow, earlier I decided to go ahead and edit/experiment with the problem (please also see "A BIG UPDATE" below as well):


-=-=-=-=-=-=-=-=-=-

OK, I *THINK* I've got it sorted out now


First (before uninstalling v3.1), I edited this:

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Drivers32]
midi = wdmaud.drv
midi1 = bassmididrv.dll
midi2 = bassmididrv\bassmididrv.dll
midi3 = myokent.dll
MIDI4 = MT32Emu.dll

..to this:

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Drivers32]
midi = wdmaud.drv
midi1 = bassmididrv\bassmididrv.dll
midi2 = myokent.dll
MIDI3 = MT32Emu.dll


Then, I deleted this registry entry:

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\drivers.desc]
"bassmididrv"="bassmididrv.dll"

...but left this one:

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\drivers.desc]
"bassmididrv\\bassmididrv.dll"="bassmididrv.dll"


Then, I went ahead and uninstalled v3.1 using the v3.2 installer, and allowed the installer to reboot my PC.


After rebooting, I noticed that the uninstaller had completely wiped out the MIDIYOKE driver (which I had configured for 4 MIDI ports)... the ports would NORMALLY be displayed within the "Sounds and Audio Devices/MIDI Music Playback/Default Device" dropdown box (as "Out To MIDI Yoke: 1", "Out To MIDI Yoke: 2", etc...), but they were totally gone.


So... I fired up the registry editor again, and saw the following:

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Drivers32]
midi = wdmaud.drv
midi1 = bassmididrv\bassmididrv.dll
MIDI3 = MT32Emu.dll

...and this (still):

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\drivers.desc]
"bassmididrv\\bassmididrv.dll"="bassmididrv.dll"


I then edited:

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Drivers32]
midi = wdmaud.drv
midi1 = bassmididrv\bassmididrv.dll
MIDI3 = MT32Emu.dll

...to read:

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Drivers32]
midi = wdmaud.drv
midi1 = myokent.dll
midi2 = MT32Emu.dll

...and deleted this registy entry:

"bassmididrv\\bassmididrv.dll"="bassmididrv.dll"


After rebooting, everything looked fine in the device manager, the Windows registry... as well as the MIDIYOKE driver ports showing up.


I then re-ran the v3.2 installer, and it seemed to install without a hitch... and everything looks fixed now


P.S. These entries NOW read:

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Drivers32]
midi = wdmaud.drv
midi1 = myokent.dll
midi2 = MT32Emu.dll
midi3 = bassmididrv\bassmididrv.dll

-=-=-=-=-=-=-=-=-=-

*A BIG UPDATE* (sorry... I typed up all of the above in WinDoZe Notepad BEFORE I found the problem detailed below):

Seems that after I installed v3.2 of the driver, the driver would crash any time something would access it


When I ran my old antique Cakewalk Professional v3.01 I got the error message shown in the top pic of this image:

http://jasonwilliams400com.startlogic.com/....2_Crashing.png (http://jasonwilliams400com.startlogic.com/snor/weeds/Temp/BASSMIDI_Driver_v3.2_Crashing.png)

Running anything else that accessed the driver (when the driver was selected as the active Windows MIDI device) also resulted in a crash (e.g. bottom pic in the above-linked image).


Once, when attempting to actually play a MIDI file using the Creative Play Center (when the driver was selected as the active Windows MIDI device) my PC completed locked up hard as a rock... had to actually UNPLUG the power cable from the wall to turn it off.


Dunno if this helps, but here is the gobbledygook shown in the Windows Event Viewer after the crashes:

Faulting application ntvdm.exe, version 5.1.2600.5512, faulting module bassmididrv.dll, version 0.0.0.0, fault address 0x00003d86.

Faulting application ctplay2.exe, version 3.1.45.0, faulting module bassmididrv.dll, version 0.0.0.0, fault address 0x00003d84.


Maybe some more helpful info (I dunno?), as I have no idea if the crashing is related to my mess that I had to straighten out... or with version 3.2 of the BASSMIDI Driver itself (?).

Seems that the DLL itself for the BASSMIDI Driver is considerably LARGER for version 3.2 of the driver, compared to v3.1 of the driver (almost double the filesize):

BASSMIDIDrv.dll v3.1 - 59,904 bytes
BASSMIDIDrv.dll v3.2 - 104,960 bytes

Another thing that I noticed, version 3.2 of the driver installer installs a MUCH older version of the BASS.dll file:

BASS.dll v2.4.7.1 - 100,408 bytes, dated December 2010

...whereby the BASS.dll installed with version 3.1 of the driver was much newer. Dated (IIRC) somewhere around May of this year.


Needless to say, I tried manually updating the BASS.dll file (and BASSMIDI.dll file as well), rebooted after the updates, but still had the crashing problem.


Anyhow... I re-ran Windows System Restore, and restored back to the previous version 3.1 of the BASSMIDI Driver (which of course, brings me back to square-one; two "MIDI for bassmididrv.dll" entries within Windows "Legacy Audio Drivers" window (which of course is no real big deal, except for the numerious entries in the "Legacy Audio Drivers" window, if/when attempting to uninstall the BASSMIDI Driver again).

-=-=-=-=-=-=-=-=-=-
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: mudlord on 18 August, 2012, 03:55:57 AM
So I take it your system doesnt like the sound driver updates in 3.2 regarding xaudio and dsound then X_X
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: RichNagel on 18 August, 2012, 06:15:08 PM
So I take it your system doesnt like the sound driver updates in 3.2 regarding xaudio and dsound then X_X


I'm guessing that's it... those updates in v3.2.
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: mudlord on 18 August, 2012, 08:49:18 PM
looks like I have to bust out the debugger and VM for this, whats your sound card?
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: RichNagel on 19 August, 2012, 12:59:35 AM
looks like I have to bust out the debugger and VM for this, whats your sound card?


A Sound Blaster Live (CT4780).
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: RichNagel on 19 August, 2012, 09:21:58 PM
Not 100% sure (unless the guy posts here in this HA thread, which I drected him to do if he still had problems), but here may be someone with the same problem -> http://forum.zdoom.org/viewtopic.php?f=4&a...tart=30#p639312 (http://forum.zdoom.org/viewtopic.php?f=4&t=29290&start=30#p639312) .
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: mudlord on 20 August, 2012, 09:05:30 AM
Tried it on a vanilla XP SP3 implementation, crashes.

Looks to crash right in the Xaudio2 destructor, after XAudio2Create call fails for some weird reason. Which hard locks the MIDI synthesis thread.

EDIT: This might sound odd, but tried updating your DirectX? Fixed the problem here in my VM doing that.

ty, zao for C++ term semantics >_>
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: kode54 on 20 August, 2012, 01:55:29 PM
Fixed the issue, uploaded here:

http://kode54.foobar2000.org/bassmididrv.exe (http://kode54.foobar2000.org/bassmididrv.exe)
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: RichNagel on 20 August, 2012, 03:22:10 PM
Fixed the issue, uploaded here:

http://kode54.foobar2000.org/bassmididrv.exe (http://kode54.foobar2000.org/bassmididrv.exe)


A-OK, Kode64, will give it a whirl ASAP  I'm a bit busy right now, but I'll test it out later this evening
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: edahS on 20 August, 2012, 10:02:03 PM
Hi Everybody,

I tried MASSMIDISynth GS/XG Scale Tuning System Exclusive Messages.
All notes are correctly pitched except the B :

Scale Tuning B : F0 43 10 4C 08 00 4C Cents F7 (Cents from 00 to 7F)

If you can test it please.

Thanks

Ian has made an update to fix this issue, you can download it in here:
http://www.un4seen.com/stuff/bassmidi.zip (http://www.un4seen.com/stuff/bassmidi.zip)
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: RichNagel on 21 August, 2012, 12:40:51 AM
Fixed the issue, uploaded here: http://kode54.foobar2000.org/bassmididrv.exe (http://kode54.foobar2000.org/bassmididrv.exe)


That seemed to do it, guys... no more crashing

I still had to go through my "voodoo ritual" detailed previously to sort out all of the registry/device manager stuff, but after sorting it out everything seemed to be working just fine


One thing that I noticed though... this version 3.3 seems to have a little more latency compared to the older version 3.1 of the driver. My previous latency tests were:

0.052 for versions 1.x and 3.1
0.110 for versions 2.x

...and for this newer version 3.3, 0.088.

0.088 seconds of latency is almost the same as the Yamaha S-YXG50 WDM driver (0.090 seconds), and is fairly close to what you posted previously, Kode54:

Quote from: kode54 link=msg=0 date=
The latency of both the BASSMIDI and VSTi drivers is hard coded at 80ms for XAudio2 and 100ms for DirectSound.



Nevertheless, it now almost borderlines on not being too useful for real-time performance. Any idea as to what would cause the differences in latency of version 3.1 compared to version 3.3 of the driver?
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: RichNagel on 21 August, 2012, 02:00:37 AM
Guys,

You should really have a look at this message thread over at the Synthesia forums (page 7 and page 8 of the thread):

https://www.synthesiagame.com/forum/viewtop...5&start=120 (https://www.synthesiagame.com/forum/viewtopic.php?f=3&t=2955&start=120)
https://www.synthesiagame.com/forum/viewtop...5&start=140 (https://www.synthesiagame.com/forum/viewtopic.php?f=3&t=2955&start=140)

...requarding the copyrights of the BASSMIDI Driver, and that "other" guy.

My concern for y'all is that the author of Synthesia just MIGHT be thinking about some sort of commercial license for that "other" guy's BASSMIDI audio library derived softsynth (to include it with an upcoming version of his "Synthesia" program).

https://www.synthesiagame.com/forum/viewtop...=latency#p26860 (https://www.synthesiagame.com/forum/viewtopic.php?f=9&t=3947&p=26860&hilit=latency#p26860)

Note that Nicholas (the author of Synthesia) is a good guy, and quite concerned about copyrights and such, so I figured that y'all might wanna know
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: mudlord on 21 August, 2012, 05:50:28 AM
Claudio already discussed with me about open sourcing it. Which to me is also a good idea.

We already discussed differences between our software and in hindsight, it was all just a massive coincidence. And I apologised to him for blaming him the first time. I admit I was pretty mad the first time, but now we are on speaking terms.

As for a custom build and license of the driver for his software, I have no objections. We did this before for a company, and I don't think kode54 also has a objection to similar one-off payments for code. Just means we have to work out a licensing agreement with the party that we both agree with. But one thing is for certain: the driver code itself is not subject to bundling of BASS license fees, which means any author wanting to license our code, also needs to buy a seperate BASS license.
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: RichNagel on 21 August, 2012, 06:01:00 AM
Thanks for the detailed info, Mudlord, as I almost  pulled an 'insert foot in mouth' sort of moment over there LOL

As far as a license, I'm now thinking that Nicholas may have been refering to the Coolsoft driver in this message thread -> https://www.synthesiagame.com/forum/viewtop...=latency#p26860 (https://www.synthesiagame.com/forum/viewtopic.php?f=9&t=3947&p=26860&hilit=latency#p26860) , due to it (supposedly) being lower latency.

I remember reading something over there (I forget which message thread that it was) about some sort of "buffer" setting in the Coolsoft driver that allowed for almost nill latency... but (as a non-coder) I know nothing about the mechanics behind that.
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: mudlord on 21 August, 2012, 06:09:22 AM
Probably changes:
http://www.un4seen.com/doc/bass/BASS_CONFIG_BUFFER.html (http://www.un4seen.com/doc/bass/BASS_CONFIG_BUFFER.html)

?

that and also modifying the updating periods.
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: kode54 on 21 August, 2012, 01:30:22 PM
Nope, that's not it. The problem is, when I doubled the samples per frame count in driver initialization, I forgot to halve the frame counts, so I doubled the latency. Things should be fine now.

I also updated BASSMIDI.

http://kode54.foobar2000.org/bassmididrv.exe (http://kode54.foobar2000.org/bassmididrv.exe)
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: RichNagel on 21 August, 2012, 04:47:26 PM
Things should be fine now. I also updated BASSMIDI.


Superb! Will test ASAP
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: RichNagel on 21 August, 2012, 05:54:49 PM
I gave it a whirl. It installed without a hitch... short of my 'voodoo ritual' that i had to do again LOL! I'm chalking up those problems as simply 'my PC' <grin>.

Anyhow, no problems or crashes, everything seems to be woking just fine  Although, after a few tests it appears that the latency is about the same as version 3.3 of the diver (approx. 0.088 seconds).
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: Lancelot Chan on 22 August, 2012, 04:23:06 AM
Hello! I've to send you a very sincere and deep thank you for your making of bass midi driver! It has resurrected my interest in making music with my soundblaster X-FI. Since it has a very problematic hardware synth that doesn't respond well with many controls, including Chorus. Your software has restored my computer's ability to sound RIGHT with all my soundfonts. Man.... you're the long-awaited solution!

After some testing, I've found that the controller 0 doesn't change the bank. Bank selection doesn't work in the current version. Also, the midi driver configuration master volume bar doesn't work in Win 7 (but that doesn't matter as much as bank selection). Also, whenever I change the soundfont list, I need to restart my cakewalk 9 to make it take effect.

BTW, 16 channels are usually more than enough, but could you give it 1 more port to make it 32 channels, just like the soundblaster hardware synth?

Thanks a lot. I can't state it enough!
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: RichNagel on 22 August, 2012, 04:35:13 AM
BTW, 16 channels are usually more than enough, but could you give it 1 more port to make it 32 channels, just like the soundblaster hardware synth?


Ditto to that feature request/suggestion

I think it would be extremely cool and handy if the BASSMIDI Driver provided 2-4 ports... something similar to a Sound Blaster Live's two hardware synthesizer ports:

SB Live! Synth A [CF20]
SB Live! Synth B [CF20]

Something like:

BASSMIDI Driver Synth A
BASSMIDI Driver Synth B

Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: mudlord on 22 August, 2012, 05:42:23 AM
How does that work out when you sequence?

do you have to select more than 1 synthesiser instance?
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: Lancelot Chan on 22 August, 2012, 06:08:41 AM
When I sequence with SBLive! or X-Fi, it actually has 2 ports like
SB Live! Synth A [CF20]
SB Live! Synth B [CF20]

Then in cakewalk, I select both ports as output ports and both as soundfont devices. Then I can allocate tracks to each of them, which contains 16 channels each.

p.s. Please fix the bank select. This is important. 

How does that work out when you sequence?

do you have to select more than 1 synthesiser instance?

Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: mudlord on 22 August, 2012, 06:25:30 AM
Did you send a GS reset in your MIDIs?
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: Lancelot Chan on 22 August, 2012, 06:49:41 AM
Did you send a GS reset in your MIDIs?


You mean for bank select? Let me try now.....

No effect. Still can't change bank regardless of using cakewalk track control or event in the track.
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: Lancelot Chan on 22 August, 2012, 08:09:39 AM
For your information, I use Win7, SB X-Fi titanium and cakewalk pro audio 9. I can select bank with X-Fi's hardware synth but can't with bassmidi driver.
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: kode54 on 22 August, 2012, 08:58:29 AM
Does the bank select work with XMPlay MIDI plug-in?
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: Lancelot Chan on 22 August, 2012, 12:14:16 PM
I don't have XMPlay midi plug-in. :|

After Edahs taught me to send Sysex bytes to Cakewalk to do a GS reset, I can select bank now. Thanks!
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: Lancelot Chan on 22 August, 2012, 01:13:23 PM
Edahs tried XMPlayer and at XMplayer he can changes bank without any problem, even without GS or GM reset. So please check with bassmidi.

Also, he mentioned that foobar2000 midi plugin has the same limitation. So please check along as well. Thanks!



I also tested something out. When I try to use my midi keyboard connected with UX16 to the X-FI hardware synth, there was no noticeable delay. But when I try to assign output MIDI port as bassmidi driver, there is a delay. This render me unable to record with the bassmidi device and only reserve it as playback.
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: RichNagel on 22 August, 2012, 08:13:33 PM
How does that work out when you sequence? do you have to select more than 1 synthesiser instance?


As Lancelot replied, you simply assign the various ports to various channels in your MIDI sequencer (of course, after configuring the various MIDI devices within the sequencers MIDI setup and configuration section).

Here's what the MIDI device config looks like in Cakewalk Pro 3.01 (of course, you can select multiple devices, and set their order within that selection box):

http://jasonwilliams400com.startlogic.com/...nfiguration.gif (http://jasonwilliams400com.startlogic.com/snor/weeds/SoundFonts/XMPlay/BASSMIDI_Driver_Cakewalk_Professional_v3.01_MIDI_Device_Configuration.gif)

...and in this screenshot:

http://jasonwilliams400com.startlogic.com/...ional_v3.01.jpg (http://jasonwilliams400com.startlogic.com/snor/weeds/SoundFonts/Cakewalk_Professional_v3.01.jpg)

...you could change the "Port" box for the various channels to assign that specific channel to a MIDI port.

I use this all the time when MIDI sequencing with my SBLive, as I can load a specific SoundFont into one hardware synth (SB Live! Synth A), and another specific SoundFont into the second hardware synth (SB Live! Synth B).

There are also quite a few MIDI files out there (my own included) that use more than 16 MIDI channels. This (of course) allows you to use more than 16 instrement presets/patches within a single MIDI file


@Lancelot,

For the bank selection problem, you might try configuring your MIDI sequencer for another bank selection method.

I'm only familiar with the old Cakewalk Professional v3.01, but in that MIDI sequencer you can navigate to a dialog window that has:

Bank Select method

...with choices of:

Normal
Controller 0 Only
Controller 32 Only
Patch 100.127

I've noticed for certain hardware and software synthsesizer that I sometimes had to change the bank selection method in order for the synth to be able to change banks. I don't remember what the setting should be for the BASSMIDI driver (as my WeedsGM3 SoundFont only has a single bank for each patch/preset), but you might try "Normal" for the bank select method (if your MIDI sequencer supports changing that option).

Also, as Mudlord said, you it's also a good idea to send a GS reset sysex for any MIDIs that will be used with the BASSMIDI Driver (or XMPlay's "MIDI Plugin" as well).


Quote from: Lancelot Chan link=msg=806149 date=
I also tested something out. When I try to use my midi keyboard connected with UX16 to the X-FI hardware synth, there was no noticeable delay. But when I try to assign output MIDI port as bassmidi driver, there is a delay. This render me unable to record with the bassmidi device and only reserve it as playback.


There is a slight bit of latency with the BASSMIDI driver (approx. 80ms or so), which can make it difficult to sequence (or play your MIDI keyboard) in real-time.

But, if you simply want to synchronize the MIDI tracks of a hardware MIDI synthesizer (such as an SBLive, or your X-Fi) and the BASSMIDI Driver (or another software synth) within your MIDI sequencer:

Some MIDI sequencers (such as Cakewalk Pro 3.01) has a setting box to "slide" the time of a specific MIDI channel in real-time. See this pic that I linked to above ( http://jasonwilliams400com.startlogic.com/...ional_v3.01.jpg (http://jasonwilliams400com.startlogic.com/snor/weeds/SoundFonts/Cakewalk_Professional_v3.01.jpg) )... the "Time+" section allows you to enter a positive or negative number (in MIDI "ticks"), which "slides" the played events earlier (or later) in real-time.

Using that "Time+" box, you can synchronize a software synth to a hardware synth PERFECTLY when the sequencer is playing the song  I use this quite a bit when I want to synchronize my SBLive (with a SoundFont loaded) with the Yamaha S-YXG50 software synth (when I want to use one of the heavy rock distortion guitars that it provides)


Refer to this document for a litte better explaination of the above:

http://jasonwilliams400com.startlogic.com/...XG/YXG50Utl.txt (http://jasonwilliams400com.startlogic.com/snor/weeds/Yamaha_XG/YXG50Utl.txt)

in the sections "Yamaha S-YXG50 Software Synthesizer WDM Driver Latency" and "Converting Latency Delay to MIDI Sequencer Timebase Ticks".
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: Lancelot Chan on 23 August, 2012, 02:43:14 AM
I tried those bank selecting methods. None worked without having done a GS reset.

I understand the sliding synchronization..... I just want to be able to play the keyboard and have realtime feedback so I can dump my problematic X-FI hardware synth altogether. Now I've to use hardware synth for input, and than bassdriver midi for mixing because only the latter handle the chorus and reverb as it should be.
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: kode54 on 23 August, 2012, 02:59:10 AM
I asked edahS to test this, but I guess I'll ask the topic to do so instead. Please test if bank changing is any different with these:

http://kode54.foobar2000.org/moo/foo_midi.fb2k-component (http://kode54.foobar2000.org/moo/foo_midi.fb2k-component)
http://kode54.foobar2000.org/moo/bassmididrv.exe (http://kode54.foobar2000.org/moo/bassmididrv.exe)
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: Lancelot Chan on 23 August, 2012, 03:38:18 AM
I hope the latency issue can be eliminated.... I suppose software synth doesn't always equal to latency or software sampler like Gigasampler won't work.



The bank selection still doesn't work on me...
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: [JAZ] on 23 August, 2012, 01:45:31 PM
RE: latency.

XAudio:
const char * err = sound_driver->open(GetDesktopWindow(), 44100, 2, sound_out_float = TRUE, 88 * 2, 30);
DSound:
err = sound_driver->open(GetDesktopWindow(), 44100, 2, sound_out_float = FALSE, 88 * 2, 50);

Interface:
virtual const char* open( void * hwnd, unsigned sample_rate, unsigned nch, bool floating_point, unsigned max_samples_per_frame, unsigned num_frames ) = 0;

I really don't understand why you use those weird settings. I haven't looked in detail if you *really* are setting 30 (or 50) *FRAMES* of buffer size, and using just 88 samples in each frame. (You know.. this is not video)


A normal application would use, for example 6 frames of  768 samples of buffer size, which means 69 milliseconds.  This works for me with directsound on my application. Of course, smaller frames should allow for less latency on the MIDI receiving end, but if you have so much audio latency, the gain is lost.

Also, i find it even more strange that you've decided to use XAudio... Why? Why not WASAPI?  With wasapi *shared* mode, i have 25ms of latency, and I can get down to 10ms with wasapi exclusive, with an integrated soundcard.

I downloaded the source, and wanted to try this myself (i.e. modify the driver to support wasapi), but I am a bit confused still with the "driver". (Am I really supposed to reboot the machine each time i compile the dll?)


[Edit: corrected a couple of things]
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: kode54 on 23 August, 2012, 04:31:50 PM
With the versions I just posted, bank selection should work just fine as long as you don't issue a GM reset, or as long as you issue a GS or XG reset afterward.
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: mudlord on 24 August, 2012, 03:50:02 AM


I downloaded the source, and wanted to try this myself (i.e. modify the driver to support wasapi), but I am a bit confused still with the "driver". (Am I really supposed to reboot the machine each time i compile the dll?)


No, just have to make sure no other apps have loaded the driver. For some reason, things like Origin, the Flash player, and Steam will load it.
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: kode54 on 24 August, 2012, 03:40:48 PM
Okay, Ian got back to me. This is the correct behavior. GM1 is not supposed to support bank change controls. XMPlay is in error, as he hasn't updated it with that change yet. (Someone reported a file to him which uses GM1 reset, and misbehaves if the bank change messages it contains have any effect.)

I'll go ahead and push the BASSMIDI Driver and foo_midi changes.
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: RichNagel on 25 August, 2012, 10:42:11 AM
Okay, Ian got back to me. This is the correct behavior. GM1 is not supposed to support bank change controls.


Man, you learn something new every day <grin>. In all of my years of "MIDI-ing", I had NO idea that bank changes weren't part of the GM1 specs.

I 've used them as far back as my original Wave Blaster 1 (and Cakewalk Pro, circa 1994-1995), and simply assumed that was part of the GM1 specs.


I'll go ahead and push the BASSMIDI Driver and foo_midi changes.


Do you mean that you're going to add the bank change feature to the BASSMIDI Driver (in GM1 mode)? If so, that would be great  If you are, one small request... add BOTH controller "0" as well as "32" to be recognized as bank change MIDI controllers.
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: bennetng on 25 August, 2012, 11:34:50 AM
Do you mean that you're going to add the bank change feature to the BASSMIDI Driver (in GM1 mode)? If so, that would be great  If you are, one small request... add BOTH controller "0" as well as "32" to be recognized as bank change MIDI controllers.

This would be a nice idea but a real soundblaster and the sf2 format only support one bank select method at a time (either MSB or LSB, not simultaneously). I mean, in order to use all MSB and LSB simultaneously, we need to load 128 separate sf2 files.
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: kode54 on 25 August, 2012, 02:42:02 PM
No, I mean I just pushed the changes to make bank changes work on all modes except for GM1.

And the only thing I can do for bank change LSB is reroute it to bank change MSB. I can't change how BASSMIDI recognizes bank change messages. (It ignores LSB.)
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: mudlord on 25 August, 2012, 09:06:13 PM
and the VST driver is now updated with the same audio output crashfixes as the BASSMIDI one.
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: kode54 on 25 August, 2012, 10:19:55 PM
I implemented dual port support in both drivers, please test and verify that both ports are acting independently:

http://kode54.foobar2000.org/bassmididrv.exe (http://kode54.foobar2000.org/bassmididrv.exe)
http://kode54.foobar2000.org/vstmididrv.exe (http://kode54.foobar2000.org/vstmididrv.exe)
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: bennetng on 26 August, 2012, 04:00:27 AM
bassmididrv's volume control is broken again in my system, using win7 x64
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: kode54 on 26 August, 2012, 05:50:03 AM
Fixed, at the same link, and at the official site.
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: bennetng on 26 August, 2012, 07:03:07 AM
Thanks. I have Roland SC-D70 (SC-8820 compatible) and SONAR producer 5. If you and other developers want to check GS compatibility (such as record MIDI files for references, checking behavior etc) I may be able to offer some help.

SC-D70 manual (appendix section contains some MIDI spec):
http://www.roland.com/support/article/?q=m...&id=1811333 (http://www.roland.com/support/article/?q=manuals&p=SC-D70&id=1811333)

I checked that both ports in bassmididrv seem working independently.
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: RichNagel on 26 August, 2012, 10:00:50 AM
I checked that both ports in bassmididrv seem working independently.


Ditto, seems to be working just fine :thumbsup:
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: kode54 on 27 August, 2012, 03:05:53 AM
I uploaded a newer version of both drivers here, and BASSMIDI driver at the official site as well.

http://kode54.foobar2000.org/bassmididrv.exe (http://kode54.foobar2000.org/bassmididrv.exe)
http://kode54.foobar2000.org/vstmididrv.exe (http://kode54.foobar2000.org/vstmididrv.exe)

New is 64 bit support in BASSMIDI, thanks to [JAZ]. I also implemented my own 64 bit support in the VSTi driver, which includes the VST host wrapper from foo_midi, so both 32 and 64 bit drivers can support both 32 and 64 bit VST instruments.
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: mudlord on 27 August, 2012, 06:26:44 AM
And somehow the MSVC projects to compile the driver got narc'ed it seems, and the vst host source isn't there.
And there is a issue on XP systems with CancelIoEx, which is a Vista and up functions. When it could use CancelEx....

bleh, I suppose the source is a "work in progress" for the VSTi driver?
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: kode54 on 27 August, 2012, 02:18:51 PM
CancelIoEx issue is fixed and uploaded in the same place.

Missing source files have also been pushed to the repository. I also need to make a project file and solution for the driver, which would be easier than using the current batch file method.
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: RichNagel on 27 August, 2012, 03:40:32 PM
Seems that a problem has cropped up with one of the newer versions of the BASSMIDI Driver

I'm not sure which version that it was (I installed the one at http://kode54.foobar2000.org/bassmididrv.exe (http://kode54.foobar2000.org/bassmididrv.exe) ), but all I hear are a lot of little pops and clicks when playing a MIDI file (no instruments/note/music at all). This when the BASSMIDI Driver is set as the main Windows MIDI device (playing a MIDI file in the WinDoZe Media Player), as well as in my MIDI sequencer.


(edit) BTW, a feature request (of course, after the above gets sorted out): It would most excellent to be able to assign different SoundFonts to the two seperate BASSMIDI Driver synth ports
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: kode54 on 27 August, 2012, 03:50:23 PM
Assigning SoundFonts separately may not be easy, as both ports are currently implemented as the first and last 16 channels of the same instance of BASSMIDI. Implementing separate SoundFont lists would require a separate dialog tab on the configuration program, then loading both lists separately in the driver, then loading the fonts separately into instances of the synthesizer.

I updated both installers to increase the DirectSound latency. I wasn't careful when importing the settings from the updated 64 bit version source. [JAZ] was not aware of how much minimum latency the DirectSound code I use requires.
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: RichNagel on 27 August, 2012, 04:26:43 PM
Assigning SoundFonts separately may not be easy, as both ports are currently implemented as the first and last 16 channels of the same instance of BASSMIDI. Implementing separate SoundFont lists would require a separate dialog tab on the configuration program, then loading both lists separately in the driver, then loading the fonts separately into instances of the synthesizer.


Understood, thanks for the info


I updated both installers to increase the DirectSound latency. I wasn't careful when importing the settings from the updated 64 bit version source. [JAZ] was not aware of how much minimum latency the DirectSound code I use requires.


Still having a problem with the new version. I'm not hearing the rapid clicks and pops (like I was before), but only hear the first note or so of the MIDI file, and then nothing/silence.
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: kode54 on 27 August, 2012, 04:38:06 PM
Try now?
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: RichNagel on 27 August, 2012, 05:43:00 PM
Try now?


Same problem.

BTW, the past few installers haven't been fully uninstalling the older version of the driver. The files are deleted, and the system reboots (effectively uninstalling the driver), but this is left in the registry:

Code: [Select]
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\BASSMIDI System Synth]
"DisplayName"="BASSMIDI System Synth"
"NoModify"=dword:00000001
"NoRepair"=dword:00000001
"UninstallString"="\"C:\\WINDOWS\\System32\\bassmididrv\\bassmididrvuninstall.exe\""

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\BASSMIDI System Synth\Backup]
"MIDI"="midi1"
"MIDIDRV"=""


...which causes the (new) installer to still think that the driver is installed (even though it isn't).
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: kode54 on 27 August, 2012, 06:39:25 PM
I fixed that in the newest installer, sorry about that. I moved the delete operation for that key to the end of the uninstall list, but didn't notice that I moved it past reboot commands issued on Windows XP systems.
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: mudlord on 27 August, 2012, 06:52:17 PM
that might be something i need to look at.
the uninstaller *should* delete its own reg keys though...
edit: oh, already fixed by u, damn >.<
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: kode54 on 27 August, 2012, 07:13:11 PM
That key on problem you describe shouldn't be there. I just tested it in a Windows XP virtual machine, and it works just fine.
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: RichNagel on 28 August, 2012, 05:22:11 AM
I just tested the latest version 3.13. Same problem with the uninstall regkey.

I ran the new installer first to uninstall the older v3.10 driver. The ununstall deleted the driver files and rebooted. But, the regkey that I mentioned previously was still there... causing the new installer (when re-ran to actually install the newer driver) to complain that an existing version was already installed.

I then deleted that regkey, and the install went without a hitch.

BTW, the new portA/portB configuration for different SoundFonts looks super


But... I couldn't really test if it _actually_ was working, as I'm still having the problem that I mentioned earlier.


Nothing heard. Sometimes I hear a single note or two when first starting to play a MIDI file, and then nothing.
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: RichNagel on 28 August, 2012, 05:38:28 AM
Just to recap:

The regkey and no-sound problems cropped up sometime after version 3.7 of the driver and installer.

I don't have all of the "sub"-versions archived, but have the installers for versions 3.4 (and ALL of the older ones, of course), 3.7, 3.10, and 3.13.

I just used the version 3.7 installer to uninstall version 3.13, and the uninstall worked fine (deleted the regkey). I then went ahead and installed version 3,7, and the music can be heard just fine

Anyways, the problem(s) are somewhere in versions 3.8-3.10 (like I said, I didn't have the installers for versions 3.8 and 3.9).
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: [JAZ] on 28 August, 2012, 03:07:35 PM
@RichNagel:
Mmm... your problem is strange.. Here it also works fine (i've even copied manually the files from the installer to be sure i was using the official version). The fact that going back to 3.7 fixes the issue seems to indicate that it is a feature added, but there aren't many clues. Could you verify in the windows mixer, if you have the volume reduced/muted for MIDI? (This setting might have started working since 3.8. It is not clear from the docs from where this volume control is changed). Also, could you try other soundfonts?

And another test, if you have a midi editor of some sort, to try if you get midi output from them.

(btw, what you describe about the uninstaller was to be expected. The uninstaller is always from the version you are uninstalling, not the one you're installing).


@Kode54:
There are still files missing in the git repository:  files makefile and sources are needed for ddk build, and there were visual studio 2008 .sln and .vcproj files. inc subdirectory is not needed anymore and there was a COMPILE.TXT file in the root directory to explain how to build.
And sorry about the Directsound buffer size. I should have tested it.
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: RichNagel on 28 August, 2012, 04:40:08 PM
Could you verify in the windows mixer, if you have the volume reduced/muted for MIDI? (This setting might have started working since 3.8. It is not clear from the docs from where this volume control is changed).


The slider is up all of the way for MIDI, and it is not muted.

(edit) I should have mentioned... the mixer MIDI slider has never allowed volume control for the BASSMIDI Driver. The ones that control it (at least in my PC) is the master and WAV sliders (which is fine by me; as being a digital device, I can apply SBLive EAX effects to the BASSMIDI Driver's MIDI output  )


Also, could you try other soundfonts?


Although I hadn't mentioned it previously, I already tried that. It didn't help though.


And another test, if you have a midi editor of some sort, to try if you get midi output from them.


As I replied previously, I tried it in my MIDI sequencer, but still had the same problem (as when  using the Windows Media Player).
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: Kaminari on 28 August, 2012, 04:43:28 PM
Since the last few builds, I'm getting an install error for both BASS MIDI Driver and VST MIDI Driver:

Code: [Select]
Error opening file for writing:
C:\Windows\SysNative\bassmididrv\bassmididrv.dll
C:\Windows\SysNative\vstmididrv.dll


Ignoring the error doesn't prevent both drivers from working though.

I'm running Win7-64.
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: [JAZ] on 28 August, 2012, 05:07:15 PM
Since the last few builds, I'm getting an install error for both BASS MIDI Driver and VST MIDI Driver:

Code: [Select]
Error opening file for writing:
C:\Windows\SysNative\bassmididrv\bassmididrv.dll
C:\Windows\SysNative\vstmididrv.dll


Ignoring the error doesn't prevent both drivers from working though.

I'm running Win7-64.


Mmm.. with a 64bit Windows, the correct directory for 64bit dlls is C:\Windows\System32  (and the 32bit ones go into C:\Windows\SysWOW64). I saw the installer using the "SysNative" naming, but I thought it was something that the installer was interpreting. I guess kode54 will need to check that.

As for not being able to write, you might need to close the windows session (or reboot). As I was told, sometimes it's because of flash player, or other applications that don't close (and free) the MIDI driver.
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: kode54 on 28 August, 2012, 06:59:13 PM
That is because TaskHost.exe and Explorer.exe like to open all the 64 bit MIDI devices. And unfortunately, the module in use checker for NSIS can't check for 64 bit modules in use.

@RichNagel: What are you using to play with? TMIDI works fine with the driver here, even in Windows XP.

EDIT: Also, sorry about that uninstall issue. Probably not my fault, but the NSIS script was writing the uninstaller to System32 instead of System32\bassmididrv on 32 bit systems. Just download the new driver, move the uninstaller to the correct place, then run a reinstall cycle.
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: RichNagel on 29 August, 2012, 06:40:29 AM
@RichNagel: What are you using to play with? TMIDI works fine with the driver here, even in Windows XP.


Anything that I try to play a MIDI file with (Windows Media Player, my MIDI sequencer Cakewalk Pro v3.01, internal "Lister" utility of Total Commander, Creative PlayCenter, etc..).

I also just tried TMIDI, same result... the first couple of notes play, then nothing, then maybe a few notes here in there (but mostly silence).

I reverted back to version 3.7 of the driver, and it works fine (other than, of course the norm wth all versions of the driver; of the occasional stutter when samples from the SoundFont are initially loaded).


BTW, I also tried this on another PC, a DELL-E510:

Dual-core Intel 3GHz CPU
3GB RAM
(IIRC) Sigmatel HD onboard audio
Windows XP SP3

...had the same problem.


EDIT: Also, sorry about that uninstall issue. Probably not my fault, but the NSIS script was writing the uninstaller to System32 instead of System32\bassmididrv on 32 bit systems. Just download the new driver, move the uninstaller to the correct place, then run a reinstall cycle.


The (newest) installer for version 3.14 uninstalled without any problems

Although (of course), I still had the problem as detailed above, and reverted back to version 3.7 of the driver.


I'm no coder (by any sense of the term <grin>), but this has definitely got something to do with the 64-bit support (or restructuring) introduced in version 3.8 of the driver.




P.S. (don't wanna get off-topic or sidetracked here, but, re: the TIMIDI player):

Download this file: http://vogons.zetafleet.com/download.php?id=8757 (http://vogons.zetafleet.com/download.php?id=8757) (StarGame.zip, contains StarGame.mid), play it in the TIMIDI player, and watch the LED display at the bottom-left of the player's GUI
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: kode54 on 29 August, 2012, 02:42:05 PM
It probably has more to do with the volume control support introduced in 3.8, but that shouldn't affect anything unless some software is muting the volume control automatically.

Please try this version instead:

http://kode54.foobar2000.org/moo/bassmididrv.exe (http://kode54.foobar2000.org/moo/bassmididrv.exe)
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: RichNagel on 29 August, 2012, 03:34:27 PM
It probably has more to do with the volume control support introduced in 3.8, but that shouldn't affect anything unless some software is muting the volume control automatically.


Thanx for the info. Like I said, I'm a non-coder <grin>.


Please try this version instead: http://kode54.foobar2000.org/moo/bassmididrv.exe (http://kode54.foobar2000.org/moo/bassmididrv.exe)


Still the same problem... although it seemed to "cut in" a little more frequently than the previous version did (but of course, that may have simply been 'luck of the draw', so to speak).


(EDIT)

Now here's a weird thing that I discovered (that may help troubleshooting the problem). Currently I'm on that other PC (the Dell E-510 with the Sigmatel onboard audio) that I previously mentioned had the problem as well:

I started playing a MIDI file with the Windows Media Player.

Then, I went to the Windows mixer, and then "Options/Properties" to the "Recording" controls (which displays the recording section of the Windows mixer).

I noticed that when I click on the "Select" checkbox for the "Microphone" slider, and then release my mouse button, I hear a short burst of music (a split second or so). Does it EVERY time too... click checkbox, release mouse button, short burst of music, silence.
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: kode54 on 29 August, 2012, 03:47:08 PM
How about now? (Same link.)
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: RichNagel on 29 August, 2012, 03:57:04 PM
How about now? (Same link.)


Problem is still there (exhibiting the same behavior as I posted in my "Edit" above).
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: kode54 on 29 August, 2012, 04:12:06 PM
Sounds like your DirectSound volume is defective. I'll just force software mixing and see if that fixes it. Try again, same link.
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: RichNagel on 29 August, 2012, 04:26:39 PM
Sounds like your DirectSound volume is defective. I'll just force software mixing and see if that fixes it. Try again, same link.


Still the same problem.
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: kode54 on 29 August, 2012, 05:25:58 PM
Monitor it with Process Monitor, then. It must be reading something wrong from the registry. I cannot reproduce the problem.

Try now. I removed the DirectSound and XAudio2 volume control, and replaced it with simple software scaling.

And by same link, I mean the kode54.foobar2000.org / moo link, not the mudlord.info link, which still has an older version.
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: RichNagel on 29 August, 2012, 10:07:47 PM
Try now. I removed the DirectSound and XAudio2 volume control, and replaced it with simple software scaling.
Still having the same problem

And by same link, I mean the kode54.foobar2000.org / moo link, not the mudlord.info link, which still has an older version.
Yeah, that's where I've been downloading the installer from ( http://kode54.foobar2000.org/moo/bassmididrv.exe (http://kode54.foobar2000.org/moo/bassmididrv.exe) ).

Monitor it with Process Monitor, then. It must be reading something wrong from the registry. I cannot reproduce the problem.
I downloaded and ran "Process Explorer" ( http://technet.microsoft.com/en-us/sysinte...s/bb896653.aspx (http://technet.microsoft.com/en-us/sysinternals/bb896653.aspx) )... I'm guessing that's what you're refering to? I'm really not sure of what to look for in PE though, can you tell me what I should be looking for (and where to to navigate to it in PE)?

That being said, I exported the entire registry to a file (on this Dell E510), and searched for every instance of "BASSMIDI". Here's what I found:

Code: [Select]
[HKEY_LOCAL_MACHINE\SOFTWARE\BASSMIDI Driver]
"volume"=dword:00002710
"path"="C:\\WINDOWS\\System32\\bassmididrv"
"sinc"=dword:00000001

[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\AppID\BASSMIDIDRV.DLL]
"AppID"="{4C5D8C86-6FD2-4BB8-BE4B-D6814CEDDE6E}"

[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\AppID\{4C5D8C86-6FD2-4BB8-BE4B-D6814CEDDE6E}]
@="BASSMIDI"

[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\BASSMIDIDrv.BASSMIDIDirectMusicSynth]
@="BASSMIDIDirectMusicSynth Class"

[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\BASSMIDIDrv.BASSMIDIDirectMusicSynth\CLSID]
@="{688DD31A-4C09-4994-ADC1-F11F15D2C863}"

[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\BASSMIDIDrv.BASSMIDIDirectMusicSynth\CurVer]
@="BASSMIDIDrv.BASSMIDIDirectMusicSynth.1"

[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\BASSMIDIDrv.BASSMIDIDirectMusicSynth.1]
@="BASSMIDIDirectMusicSynth Class"

[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\BASSMIDIDrv.BASSMIDIDirectMusicSynth.1\CLSID]
@="{688DD31A-4C09-4994-ADC1-F11F15D2C863}"

[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CLSID\{688DD31A-4C09-4994-ADC1-F11F15D2C863}]
@="BASSMIDIDirectMusicSynth Class"
"AppID"="{4C5D8C86-6FD2-4BB8-BE4B-D6814CEDDE6E}"

[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CLSID\{688DD31A-4C09-4994-ADC1-F11F15D2C863}\InprocServer32]
@="C:\\WINDOWS\\System32\\bassmididrv\\bassmididrv.dll"
"ThreadingModel"="both"

[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CLSID\{688DD31A-4C09-4994-ADC1-F11F15D2C863}\ProgID]
@="BASSMIDIDrv.BASSMIDIDirectMusicSynth.1"

[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CLSID\{688DD31A-4C09-4994-ADC1-F11F15D2C863}\TypeLib]
@="{83E56BB2-5AB9-462E-8512-80688BF4B24F}"

[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CLSID\{688DD31A-4C09-4994-ADC1-F11F15D2C863}\VersionIndependentProgID]
@="BASSMIDIDrv.BASSMIDIDirectMusicSynth"

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\DirectMusic\SoftwareSynths\{688DD31A-4C09-4994-ADC1-F11F15D2C863}]
"Description"="BASSMIDI Driver"

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\App Management\ARPCache\BASSMIDI System Synth]
"SlowInfoCache"=hex:28,02,00,00,00,00,00,00,ff,ff,ff,ff,ff,ff,ff,ff,00,00,00,\
  00,00,00,00,00,ff,ff,ff,ff,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,\
  00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,\
  00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,\
  00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,\
  00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,\
  00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,\
  00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,\
  00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,\
  00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,\
  00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,\
  00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,\
  00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,\
  00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,\
  00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,\
  00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,\
  00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,\
  00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,\
  00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,\
  00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,\
  00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,\
  00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,\
  00,00,00,00,00,00,00,00
"Changed"=dword:00000000

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\BASSMIDI System Synth]
"DisplayName"="BASSMIDI System Synth"
"NoModify"=dword:00000001
"NoRepair"=dword:00000001
"UninstallString"="\"C:\\WINDOWS\\System32\\bassmididrv\\bassmididrvuninstall.exe\""

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\BASSMIDI System Synth\Backup]
"MIDI"="midi1"
"MIDIDRV"=""

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\drivers.desc]
"msaud32.acm"="Windows Media Audio Codec"
"sl_anet.acm"="Sipro Lab Telecom Audio Codec"
"C:\\WINDOWS\\System32\\l3codeca.acm"="Fraunhofer IIS MPEG Layer-3 Codec"
"wdmaud.drv"="SigmaTel High Definition Audio CODEC"
"serwvdrv.dll"="Modem Wave Driver"
"mpg4c32.dll"="Microsoft MPEG-4 Video Codec v1"
"mciavi32.dll"="mciavi32.dll"
"mcicda.dll"="mcicda.dll"
"mciseq.dll"="mciseq.dll"
"mciwave.dll"="mciwave.dll"
"mciqtz32.dll"="mciqtz32.dll"
"midimap.dll"="midimap.dll"
"imaadp32.acm"="imaadp32.acm"
"msadp32.acm"="msadp32.acm"
"msg711.acm"="msg711.acm"
"msgsm32.acm"="msgsm32.acm"
"tssoft32.acm"="tssoft32.acm"
"iccvid.dll"="iccvid.dll"
"msh263.drv"="msh263.drv"
"ir32_32.dll"="ir32_32.dll"
"iyuv_32.dll"="iyuv_32.dll"
"msrle32.dll"="msrle32.dll"
"msvidc32.dll"="msvidc32.dll"
"msyuv.dll"="msyuv.dll"
"tsbyuv.dll"="tsbyuv.dll"
"msacm32.drv"="msacm32.drv"
"msg723.acm"="msg723.acm"
"msh261.drv"="msh261.drv"
"zmbv.dll"="Zip Motion Block Video [ZMBV]"
"bassmididrv\\bassmididrv.dll"="bassmididrv.dll"

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Drivers32]
"midimapper"="midimap.dll"
"msacm.imaadpcm"="imaadp32.acm"
"msacm.msadpcm"="msadp32.acm"
"msacm.msg711"="msg711.acm"
"msacm.msgsm610"="msgsm32.acm"
"msacm.trspch"="tssoft32.acm"
"vidc.cvid"="iccvid.dll"
"vidc.I420"="msh263.drv"
"vidc.iv31"="ir32_32.dll"
"vidc.iv32"="ir32_32.dll"
"vidc.iyuv"="iyuv_32.dll"
"vidc.mrle"="msrle32.dll"
"vidc.msvc"="msvidc32.dll"
"vidc.uyvy"="msyuv.dll"
"vidc.yuy2"="msyuv.dll"
"vidc.yvu9"="tsbyuv.dll"
"vidc.yvyu"="msyuv.dll"
"wavemapper"="msacm32.drv"
"msacm.msg723"="msg723.acm"
"vidc.M263"="msh263.drv"
"vidc.M261"="msh261.drv"
"msacm.msaudio1"="msaud32.acm"
"msacm.sl_anet"="sl_anet.acm"
"msacm.l3acm"="C:\\WINDOWS\\System32\\l3codeca.acm"
"wave"="wdmaud.drv"
"midi"="wdmaud.drv"
"mixer"="wdmaud.drv"
"wave1"="serwvdrv.dll"
"VIDC.MP42"="mpg4c32.dll"
"VIDC.MPG4"="mpg4c32.dll"
"VIDC.ZMBV"="zmbv.dll"
"midi1"="bassmididrv\\bassmididrv.dll"

[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\MediaProperties\PrivateProperties\Midi\Ports\BASSMIDI Driver [Emulated]]

[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\MediaProperties\PrivateProperties\Midi\Ports\BASSMIDI Driver [Emulated]\Out]
"DMPortGUID"=hex:06,06,ab,8f,53,de,cc,44,8e,e7,81,e0,a5,90,b5,16

[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet002\Control\MediaProperties\PrivateProperties\Midi\Ports\BASSMIDI Driver [Emulated]]

[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet002\Control\MediaProperties\PrivateProperties\Midi\Ports\BASSMIDI Driver [Emulated]\Out]
"DMPortGUID"=hex:06,06,ab,8f,53,de,cc,44,8e,e7,81,e0,a5,90,b5,16

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\Midi\Ports\BASSMIDI Driver [Emulated]]

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\Midi\Ports\BASSMIDI Driver [Emulated]\Out]
"DMPortGUID"=hex:06,06,ab,8f,53,de,cc,44,8e,e7,81,e0,a5,90,b5,16

[HKEY_USERS\S-1-5-21-606747145-2111687655-725345543-1003\Software\Microsoft\ActiveMovie\devenum\{4EFE2452-168A-11D1-BC76-00C04FB9453B}\BASSMIDI Driver]
"FriendlyName"="BASSMIDI Driver"
"CLSID"="{07B65360-C445-11CE-AFDE-00AA006C14F4}"
"FilterData"=hex:02,00,00,00,00,00,20,00,01,00,00,00,00,00,00,00,30,70,69,33,\
  02,00,00,00,00,00,00,00,01,00,00,00,00,00,00,00,00,00,00,00,30,74,79,33,00,\
  00,00,00,38,00,00,00,48,00,00,00,6d,69,64,73,00,00,10,00,80,00,00,aa,00,38,\
  9b,71,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00
"MidiOutId"=dword:00000000

[HKEY_USERS\S-1-5-21-606747145-2111687655-725345543-1003\Software\Microsoft\Windows\CurrentVersion\Multimedia\MIDIMap]
"szPname"="BASSMIDI Driver (port A)"

[HKEY_USERS\S-1-5-21-606747145-2111687655-725345543-1003\Software\sfpacker]
"path"="C:\\WINDOWS\\system32\\bassmididrv"

[HKEY_USERS\S-1-5-21-606747145-2111687655-725345543-1004\Software\BASSMIDI Driver]

[HKEY_USERS\S-1-5-21-606747145-2111687655-725345543-1004\Software\Microsoft\Windows\CurrentVersion\Multimedia\MIDIMap]
"szPname"="BASSMIDI Driver"
"RelativeIndex"=dword:00000000
"DeviceInterface"=""
"SetupPreferredAudioDevicesCount"=dword:00000000
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: kode54 on 29 August, 2012, 10:19:35 PM
Nope, I meant Process Monitor (http://technet.microsoft.com/en-us/sysinternals/bb896645.aspx).

And it looks like your registry is still polluted with data from the 2.x series of the driver. Please extract bassmididrv.dll from that series and run regsvr32 /u on it to clean up the mess, or simply delete all those DirectMusic related BASSMIDI keys.
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: RichNagel on 30 August, 2012, 07:53:07 AM
And it looks like your registry is still polluted with data from the 2.x series of the driver. Please extract bassmididrv.dll from that series and run regsvr32 /u on it to clean up the mess, or simply delete all those DirectMusic related BASSMIDI keys.


I went ahead and manually deleted all references to DirectMusic for the BASSMIDI driver.


Nope, I meant Process Monitor (http://technet.microsoft.com/en-us/sysinternals/bb896645.aspx).


A-OK. I downloaded and ran Process Monitor, but just like Process Explorer that I mentioned previously... I have no idea what I'm supposed to be looking for.

Any hints/tips?


BTW, kode54, thanks for the help
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: kode54 on 30 August, 2012, 04:25:17 PM
From the filters dialog that pops up on startup, select a filter type of Process, then add the file name of an executable that will be a MIDI player, like TMIDI.exe, then click Add.

Then run TMIDI and try to play a MIDI file.

Now stop logging in Process Monitor (click the magifying glass so there's an X on it) and save the log. Compress and upload this somewhere and PM me a link.
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: RichNagel on 31 August, 2012, 12:13:16 AM
PM with link sent

BTW, do you know if there is an English version of TMIDI available somewhere?
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: mudlord on 31 August, 2012, 06:49:04 AM
http://www.grandgent.com/tom/projects/tmidi/ (http://www.grandgent.com/tom/projects/tmidi/)
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: RichNagel on 31 August, 2012, 11:16:16 AM
http://www.grandgent.com/tom/projects/tmidi/ (http://www.grandgent.com/tom/projects/tmidi/)


Thanks for the link, mudlord

Hehe, I thought y'all was refering to this one though (it's also called "TMIDI"):

http://hp.vector.co.jp/authors/VA010012/ (http://hp.vector.co.jp/authors/VA010012/)


After having a look at the link to the one that you posted, I now realize that this:

P.S. (don't wanna get off-topic or sidetracked here, but, re: the TMIDI player):

Download this file: http://vogons.zetafleet.com/download.php?id=8757 (http://vogons.zetafleet.com/download.php?id=8757) (StarGame.zip, contains StarGame.mid), play it in the TMIDI player, and watch the LED display at the bottom-left of the player's GUI


...doesn't make any sense LOL!


@kode54,

The file that I logged with Process Monitor; I used the TMIDI player that I linked to above... I hadn't realize that you were refering to a completely different one with the same name.

Should I re-do the Process Monitor log using the TMIDI player that you were refering to, or was the one that I used OK for the log file?
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: hernaaan on 31 August, 2012, 03:26:24 PM
http://www.grandgent.com/tom/projects/tmidi/ (http://www.grandgent.com/tom/projects/tmidi/)

I logged only to say this is awesome.

The BASSMIDI driver too btw. However I may be looking for some other soundfonts since the ones linked doesn't seem to support bending (I use Guitar Pro 6).
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: [JAZ] on 31 August, 2012, 05:56:11 PM
Hehe, I thought y'all was refering to this one though (it's also called "TMIDI"):

http://hp.vector.co.jp/authors/VA010012/ (http://hp.vector.co.jp/authors/VA010012/)


Offtopic:
I also found Tom's MIDI first, and the thing about the left box didn't make sense, so I looked for another one and finally found the japanese one.
The japanese one is incredible. TiMidity looks like a small brother of it (i.e. trying to look like the former, but failing short). It might actually be based (code-wise) on it, since it even shows the battleship in StarGame.mid
Also, Bassmidi shines against TiMidity's engine. In some songs TMidi/Bassmidi sounds quite different than TiMidity, even when using the same soundfont file. (I guess it's the implementation of chorus/reverb, and some envelope handling)
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: RichNagel on 31 August, 2012, 06:19:12 PM
However I may be looking for some other soundfonts since the ones linked doesn't seem to support bending (I use Guitar Pro 6).


Are you refering to a standard MIDI pitch wheel controller? If so, the actual SoundFont has nothing to do with the ability of pitch bending, but rather the player program itself.

I have Guitar Pro v5.2 and IIRC; the MIDI pitch wheel isn't supported when importing a MIDI file into the program (but rather filtered or stripped out).
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: RichNagel on 31 August, 2012, 06:24:44 PM
since it even shows the battleship in StarGame.mid


Yeah, that's what I thought was so cool about it


Also, Bassmidi shines against TiMidity's engine. In some songs TMidi/Bassmidi sounds quite different than TiMidity, even when using the same soundfont file. (I guess it's the implementation of chorus/reverb, and some envelope handling)


Yeah, the BASSMIDI Driver (and BASSMIDI) definitely dwarfs TiMidity's SoundFont rendering by comparison

When I first discovered the BASSMIDI Driver early last year, I posted messages all over the Internet talking about/announcing it. The feedback was basically "TiMidity will NOW be deleted from my PC!" <grin>


(Edit) Folks, I've said this before, I'll say it again:

As a MIDI enthusiast who has primarily used SoundFonts with my old AWE32s (and currently my SBLive) for all of my own music, I have to say that BASSMIDI/the BASSMIDI Driver is the closest to having a REAL AWE32/SBLive (EMU-8000/EMU-10K/EMU-20K hardware) as you can get
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: kode54 on 31 August, 2012, 06:26:13 PM
Not entirely true. SoundFonts can reroute the behavior of the pitch wheel, in addition to other controllers.
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: RichNagel on 31 August, 2012, 06:31:38 PM
Not entirely true. SoundFonts can reroute the behavior of the pitch wheel, in addition to other controllers.


I wasn't aware of that. Is this something that can be edited or changed in (something like) Vienna Studio?

I know that in VS you can add a lot of reverb and chorus (essentially overriding a MIDI file's NRPN added reverb and chorus controllers) to a SoundFont, but didn't know that something similar could be done to the pitch wheel (or maybe even the mod wheel) itself.
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: mudlord on 31 August, 2012, 10:48:50 PM
yes, same can be done for low pass filter cutoff/resonance.
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: RichNagel on 01 September, 2012, 01:12:01 AM
yes, same can be done for low pass filter cutoff/resonance.


Yeah, I knew about those. But, what parameters in VS control the pitch bending (I'm assuming that it could be totally disabled)?
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: kode54 on 01 September, 2012, 05:37:20 AM
I only assumed it could control that from Audio Compositor. I can't run VS because I don't have actual SoundFont hardware installed.
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: bennetng on 01 September, 2012, 07:00:42 AM
Soundfont 2.1 (since SB Live/ E-MU APS) has much more flexible configuration than 2.0 (AWE)
http://connect.creativelabs.com/developer/...ont/sfapp21.pdf (http://connect.creativelabs.com/developer/SoundFont/sfapp21.pdf)

AFAIK BASSMIDI only supports sf 2.0 because the soundfonts I use (AnotherGS/AnotherXG) have some sf 2.1 specific effects which BASSMIDI cannot reproduce, For example, the violin in AnotherGS/XG will sound duller in lower velocity when playing in sf2.1 compatible synthesizers. GeneralUser soundfont's creator has an article comparing some obvious differences between sf2.0 and sf2.1
http://www.schristiancollins.com/sfdiagnostic/index.htm (http://www.schristiancollins.com/sfdiagnostic/index.htm)
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: [JAZ] on 01 September, 2012, 07:23:19 AM
http://www.schristiancollins.com/sfdiagnostic/index.htm (http://www.schristiancollins.com/sfdiagnostic/index.htm)

Thanks! I wasn't aware there was a new version of GeneralUserGS. I had 1.4.
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: bennetng on 01 September, 2012, 11:44:01 AM
S. Christian Collins' article is somewhat outdated. If SB Live is using the latest official driver, or using Audigy's driver, their sf2.1 compatibility are the same. X-Fi is also compatible with sf2.1, however, because X-Fi has much higher sample interpolaton quality, it will have audible differences with SB Live and Audigy. I really hope BASSMIDI will support sf2.1 modulator properties. Some of these properties can only be set in Vienna, MIDI message (such as controller, sysex) cannot change them.

I also has an article describing Creative driver's soundfont bugs
Bug 1 and 2 is specific for SB Live (and Audigy?), bug 3 is present on SB Live/Audigy/X-Fi
http://www.geocities.jp/anothergs/driver.html (http://www.geocities.jp/anothergs/driver.html)
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: RichNagel on 01 September, 2012, 12:53:44 PM
Ahh... I understand now.

I've always used Vienna SoundFont Studio version 2.3, as I CAN'T STAND the GUI of version 2.4.

In Vienna SoundFont Studio version 2.3 (which BTW is what I used to create WeedsGM3.sf2 with) there aren't any parameters for adjusting anything related to the pitch wheel.

But, I just fired up Vienna SoundFont Studio version 2.4, and there are indeed a bunch of things that can be changed as far as the pitch wheel is concerned.

I was able to set the sensitivity WAY UP (to the point of being completely useless); as well as setting the sensitivity way down, which essentially disabled the usage of the pitch wheel.
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: RichNagel on 01 September, 2012, 03:06:42 PM
BTW, on the topic of the BASSMIDI Driver and SoundFonts in general, a little something that I uploaded a few weeks ago:

You know how so many web sites that sell (or have free) SoundFonts always seem to have a page of: "Listen to an MP3 of our product HERE" / "Listen to the original MIDI with YOUR hardware HERE"? Well, here's a nice one that does just that

The original MIDI is "SYMPHONY.MID" that shipped with damned near EVERY Creative Labs' sound card since the dawn of time LOL. Originally sequenced in 1993-1994 by "Dr. Chew" (I think?), I've always thought that MIDI was 'way ahead of it's time' hardware-wise <grin>.

Anyhow, I've optimized it a bit for the BASSMIDI Driver, and also recorded an MP3 of it in action (along with my WeedsGM3.sf2 SoundFont)... the MP3 in all of it's glory really shows them both off IMHO

Hehe, the reason for the "_BM" in the filenames? Heh, just like Yamaha XG optimized MIDIs that always seem to include an "XG" in the filename... "_BM" for BASSMIDI


http://jasonwilliams400com.startlogic.com/...Symphony_BM.mid (http://jasonwilliams400com.startlogic.com/snor/weeds/SoundFonts/Symphony_BM.mid)

http://jasonwilliams400com.startlogic.com/...Symphony_BM.mp3 (http://jasonwilliams400com.startlogic.com/snor/weeds/SoundFonts/Symphony_BM.mp3)
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: kode54 on 01 September, 2012, 03:31:39 PM
What about Viena (http://www.synthfont.com/)? It even works without Creative hardware.
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: mudlord on 01 September, 2012, 08:12:41 PM
speaking of midis.
http://mudlord.info/musix/satellite_one.mp3 (http://mudlord.info/musix/satellite_one.mp3)
http://mudlord.info/musix/satellite_one.mid (http://mudlord.info/musix/satellite_one.mid)

needs some tinkering.
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: RichNagel on 01 September, 2012, 09:21:24 PM
What sort of tinkering/tweaking does it need?
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: mudlord on 01 September, 2012, 09:39:11 PM
I need to fix some NRPNs like pitch bend sensitivity on loopStart/End so that it sounds correct when looping, proper echo, etc.
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: bennetng on 01 September, 2012, 11:54:52 PM
What about Viena (http://www.synthfont.com/)? It even works without Creative hardware.

sf 2.1 modulators seems editable but the result is not audible. Maybe I am not familiar with Viena yet.
http://www.flickr.com/photos/82931408@N02/...in/photostream/ (http://www.flickr.com/photos/82931408@N02/7910766110/sizes/l/in/photostream/)
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: RichNagel on 01 September, 2012, 11:58:48 PM
I need to fix some NRPNs like pitch bend sensitivity on loopStart/End so that it sounds correct when looping, proper echo, etc.


If you can tell me what you which controllers that you want edited (and their correct values), I can do it for ya

Here's what I see in Cakewalk Pro that is RPN/NRPN related:

Code: [Select]
Trk Hr:Mn:Sc:Fr       M:B:T     Chn Kind   Type         Value
2  00:00:04:26       3:1:010   2   Contrl 101-RPN MSB    0
2  00:00:04:26       3:1:011   2   Contrl 100-RPN LSB    0
2  00:00:04:26       3:1:012   2   Contrl 6-Data MSB    21
2  00:00:04:26       3:1:013   2   Contrl 38-Data LSB    0
1  00:00:05:09       3:1:100   1   Contrl 101-RPN MSB    0
1  00:00:05:09       3:1:101   1   Contrl 100-RPN LSB    0
1  00:00:05:09       3:1:102   1   Contrl 6-Data MSB    15
1  00:00:05:09       3:1:103   1   Contrl 38-Data LSB    0
3  00:00:06:29       3:4:070   3   Contrl 101-RPN MSB    0
3  00:00:06:29       3:4:071   3   Contrl 100-RPN LSB    0
3  00:00:06:29       3:4:072   3   Contrl 6-Data MSB     5
3  00:00:06:29       3:4:073   3   Contrl 38-Data LSB    0
8  00:00:13:08       6:3:010   8   Contrl 101-RPN MSB    0
8  00:00:13:08       6:3:011   8   Contrl 100-RPN LSB    0
8  00:00:13:08       6:3:012   8   Contrl 6-Data MSB    11
8  00:00:13:08       6:3:013   8   Contrl 38-Data LSB    0
7  00:00:13:17       6:3:070   7   Contrl 101-RPN MSB    0
7  00:00:13:17       6:3:071   7   Contrl 100-RPN LSB    0
7  00:00:13:17       6:3:072   7   Contrl 6-Data MSB    20
7  00:00:13:17       6:3:073   7   Contrl 38-Data LSB    0
11  00:00:41:23      18:2:070  11   Contrl 101-RPN MSB    0
11  00:00:41:23      18:2:071  11   Contrl 100-RPN LSB    0
11  00:00:41:23      18:2:072  11   Contrl 6-Data MSB    18
11  00:00:41:23      18:2:073  11   Contrl 38-Data LSB    0
10  00:00:42:02      18:3:010   9   Contrl 101-RPN MSB    0
10  00:00:42:02      18:3:011   9   Contrl 100-RPN LSB    0
10  00:00:42:02      18:3:012   9   Contrl 6-Data MSB    33
10  00:00:42:02      18:3:013   9   Contrl 38-Data LSB    0
13  00:01:39:11      42:2:070  13   Contrl 101-RPN MSB    0
13  00:01:39:11      42:2:071  13   Contrl 100-RPN LSB    0
13  00:01:39:11      42:2:072  13   Contrl 6-Data MSB    13
13  00:01:39:11      42:2:073  13   Contrl 38-Data LSB    0
12  00:01:41:05      43:1:070  12   Contrl 101-RPN MSB    0
12  00:01:41:05      43:1:071  12   Contrl 100-RPN LSB    0
12  00:01:41:05      43:1:072  12   Contrl 6-Data MSB    33
12  00:01:41:05      43:1:073  12   Contrl 38-Data LSB    0
5  00:01:57:02      49:4:010   5   Contrl 101-RPN MSB    0
5  00:01:57:02      49:4:011   5   Contrl 100-RPN LSB    0
5  00:01:57:02      49:4:012   5   Contrl 6-Data MSB    20
5  00:01:57:02      49:4:013   5   Contrl 38-Data LSB    0
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: bennetng on 02 September, 2012, 02:11:56 AM
Pitch bend sensitivity is RPN, the MIDI file has no NRPN
The echo is created by duplicating and delaying two separate channels, it is not a MIDI effect.
The file does not loop well because it is not perfectly quantized and the loop points are not accurate.

corrected file:
http://www.sendspace.com/file/au5wyn (http://www.sendspace.com/file/au5wyn)
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: RichNagel on 02 September, 2012, 11:00:43 AM
The echo is created by duplicating and delaying two separate channels, it is not a MIDI effect.


Hehe, the old MIDI "fake reverb" effect <grin>
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: mudlord on 02 September, 2012, 06:36:36 PM
thanks bennetg, seems then this midi aint good enough for a vst driver demo...need more practise sequencing, after a 3 year or so break.

someone should indeed upload what richard did to the server, its cool.
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: bennetng on 06 September, 2012, 08:58:47 AM
Some Roland and Yamaha official demos are very good, these files can demonstrate BASSMIDI's GS/XG compatibility as well.
http://www.sendspace.com/file/pwcw2v (http://www.sendspace.com/file/pwcw2v)

OXYCUTE.MID (XG) is very interesting, changing foo_midi's sample rate will change the filter/resonance response dramatically. Other two files are GS.
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: mudlord on 22 September, 2012, 12:18:09 AM
added configurable sound buffer lengths for xaudio2 output.
should fix some issues.
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: Kaminari on 22 September, 2012, 09:44:13 AM
With the default buffer length (100), I get an APPCRASH error in faulty module XAudio2_7.dll (version 9.29.1962.0). Setting the buffer to 64 or less apparently prevents the library from crashing.

[Win7-64]
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: bennetng on 22 September, 2012, 01:27:30 PM
Same here but I don't really care because I have no problem with low latency (10). This level of latency is comparable to running VSTi in DAW. Good job, thanks!
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: RichNagel on 22 September, 2012, 06:54:48 PM
Seems to work OK here  I had a few 'inital loading' stutters, but not that many after the samples were completely loaded.

I didn't really notice any difference though no matter where the buffer slider was set... does this Xaudio2 thing apply to me? I was really excited about the possibility of real low latency.
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: mudlord on 23 September, 2012, 09:26:41 PM
Seems then your system prefers the DirectSound driver, or it must hate xaudio2?
Did the build just before the x64 changes work for you?
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: RichNagel on 24 September, 2012, 08:25:01 AM
Seems then your system prefers the DirectSound driver, or it must hate xaudio2?
Did the build just before the x64 changes work for you?


I'm not sure if you were reply to me (or the previous posters), mudlord.

Anyhow, I had no problems with the versions before the x64 changes.
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: kode54 on 24 September, 2012, 08:15:43 PM
Please try http://www.mudlord.info/bassmididrv/bassmididrv.exe (http://www.mudlord.info/bassmididrv/bassmididrv.exe) again. I dropped out the floating point XAudio2 support, since a kind WikiPedia has informed me that it wraps to DirectSound on Windows XP, so probably won't work with floating point output there either.

Just to reiterate, the problems you are experiencing are more likely due to me bypassing BASS as an output method and using my own output interfaces instead.
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: RichNagel on 24 September, 2012, 11:14:36 PM
Seems to be working OK  It might be my ears, but I think there's a little less stuttering when first playing a MIDI file and the initial samples from the SoundFont are loaded in.

I still don't hear any difference with the buffer slider though (I'm on another PC that I've been testing the BMD driver on, so I'm comparing the BMD with the MS SoftSynth's latency).


Just to reiterate, the problems you are experiencing are more likely due to me bypassing BASS as an output method and using my own output interfaces instead.


(Edit) P.S. Just a-wondering: Does the BMD still use BASS.DLL and BASSMIDI.DLL (I'm assuming so)?
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: mudlord on 25 September, 2012, 04:58:06 AM
yes, it still uses bassmidi.dll as the synthesiser. and bass.dll as the base.
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: Flynn_Taggart95 on 02 October, 2012, 06:08:00 PM
I have recently downloaded the latest version pf BASSMIDI and I am having troubles using this with DooM's MIDI music. Specifically with the music skipping, fading out, and/or stuttering (mostly on note-heavy parts like guitar riffs or when there is lag in the game). Using the XAudio2 buffer length slider helps a little bit but theirs still slight problems. Is there any way you all can fix this? My audio card is a Realtek AC97 Audio and a computer with 1GB RAM if it helps.
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: Flynn_Taggart95 on 02 October, 2012, 08:08:27 PM
Actually, I have just found out these problems pertain to just listening to MIDI music in general.
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: mudlord on 03 October, 2012, 07:48:24 PM
OS? CPU?
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: Flynn_Taggart95 on 03 October, 2012, 08:10:33 PM
OS? CPU?

OS: Windows XP Professional (5.1, build 2600)
Processor: Intel Premium 4 CPU 300GHz (2 CPUs)

Hope this is what you wanted.
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: mudlord on 03 October, 2012, 10:01:05 PM
I uploaded a new version with DirectSound buffer changing. try that?
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: Flynn_Taggart95 on 03 October, 2012, 11:18:49 PM
It helps quite a significant bit. Although there's still bits of stutter/cutout when the synth first starts up (like at Doom/Doom II's title) but once it gets going, it's sounds flawless. Just that wee hiccup.

I have both buffer sliders at max and the sync interpolation box is ticked
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: RichNagel on 03 October, 2012, 11:51:06 PM
Same here... sliding the DS buffer up, all stutters are now gone (short of the initial load when the MIDI starts, which I've experienced in almost all of the other older drivers as well... so no biggie).

P.S. NOW I can actually hear a difference in latency with the DS slider (I noticed no difference with the XAudio2 slider in all of the versions).
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: mudlord on 04 October, 2012, 04:19:12 PM
Yay. >_>
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: ex-driver on 25 October, 2012, 03:41:07 PM
I checked the driver for Windows XP 32bit.

-Missing Tracks on Playback ( windows prof. 64bit 7 works ) example MIDI Human.MID Warcraft II 047 for example ( Timpani ) missing
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: RichNagel on 26 October, 2012, 01:30:51 AM
example MIDI Human.MID Warcraft II 047 for example ( Timpani ) missing


Which WarCraft II MIDI file are you refering to? My track listing is:

Code: [Select]
INTROGM.MID
HWRRMGM.MID
HUMAN1GM.MID
HUMAN2GM.MID
HUMAN3GM.MID
HUMAN4GM.MID
HUMVGM.MID
HUMDTHGM.MID
OWRRMGM.MID
ORC1GM.MID
ORC2GM.MID
ORC3GM.MID
ORC4GM.MID
ORCVGM.MID
ORCDTHGM.MID


...which has no MIDI named only "HUMAN.MID".
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: ex-driver on 26 October, 2012, 02:36:08 PM
Human1GM.MID for example. In windows 7 i can hear all tracks. In windows xp the timpani 047 is not present and sweep pad 095 maybe. (tested with v3.19 and v3.17)
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: RichNagel on 26 October, 2012, 03:28:25 PM
Human1GM.MID for example. In windows 7 i can hear all tracks. In windows xp the timpani 047 is not present and sweep pad 095 maybe. (tested with v3.19 and v3.17)


I just tested it under Windows XP (with an older version 3.16), the timpani and sweep pad sounds just fine.

Are you _sure_ that it's not the SoundFont that you're using/loading?
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: ex-driver on 26 October, 2012, 06:51:58 PM
LOL I found out what it is. I just forget to loading the 4th soundfont bank XD. Now seems to work. Sry for that
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: Vagabond on 27 October, 2012, 07:43:00 AM
Looks like Windows 8 loathes MIDI. I'm trying to set the default MIDI device and it always reverts back to the crappy Windows default. I've tried setting the default device through BASSMIDI, Creative Soundfont Bank Manager, and Putzlowitsch's Vista MIDI Mapper Control Panel. It just doesn't save. Any tips?
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: mudlord on 28 October, 2012, 12:03:35 AM
Ask kode54. IIRC he has Windows 8 installed, im stuck on 7.
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: Vagabond on 29 October, 2012, 05:42:58 PM
To anyone wanting to change the MIDI device in Windows 8, you can run VirtualMIDISynth (http://coolsoft.altervista.org/en/virtualmidisynth). It had no issues changing the device.
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: ex-driver on 30 October, 2012, 02:14:04 PM
@RichNagel  I got some playback errors on the file TrekMedG.MID You too ? ( Windows 7 ) Winamp 0:43 sec.
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: RichNagel on 30 October, 2012, 04:22:38 PM
@RichNagel  I got some playback errors on the file TrekMedG.MID You too ? ( Windows 7 ) Winamp 0:43 sec.


I'm not sure exactly which of the files that you might be using, but I downloaded this one here -> http://www.zaxpax.com/midis/TrekMedG.MID (http://www.zaxpax.com/midis/TrekMedG.MID) .

My Sound Blaster Live's hardware synth clips the tremelo strings at that part in the song, but the BASSMIDI Driver seems to play it OK.
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: ex-driver on 30 October, 2012, 06:56:36 PM
I got this error if i use sinc interpolation. strange thing
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: ex-driver on 31 October, 2012, 12:24:08 PM
Tested on XAudio2 and Direct Sound ( windows 7 and XP ). No Problems on Xmplay. It sounds like a crisp sound.
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: sharangad on 02 November, 2012, 02:55:56 PM
Under Windows 8 I'm getting static and breakups with all MIDI files played through all players.

Not sure whether this is due to the beta drivers for Xonar D2 or an incompatibility with Bassmidi and Win 8. I've tried increasing the XAudio and DS buffer sizes without any success.
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: mudlord on 04 November, 2012, 06:57:33 AM
Could be that magic word: Xonar. Asus crap is known to be hilariously bad support wise.
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: sharangad on 04 November, 2012, 09:35:39 AM
Could be that magic word: Xonar. Asus crap is known to be hilariously bad support wise.


Worked fine on WIn7
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: prismra on 05 November, 2012, 11:25:51 AM
I can confirm the cracking and dropouts on Windows 8.

Windows 8
i7 3770k

Using motherboard audio and whatever default driver Windows installed.
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: kode54 on 05 November, 2012, 06:06:58 PM
Maybe XAudio2 in Windows 8 doesn't like such tiny frame sizes. QuickNES handles just fine with its 1/60th of a second frame sizes. Maybe I'll tweak the buffer sizes a bit and post a fix later.
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: prismra on 05 November, 2012, 06:08:39 PM
I tested Skulltag/ZDOOM and DOSBox.  DOSBox just crashes when you try to output to it as the MIDI device.

I also tried installing the VIA audio codec drivers from their website and saw no change in behavior.
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: RichNagel on 07 November, 2012, 08:01:37 PM
Maybe XAudio2 in Windows 8 doesn't like such tiny frame sizes.


Hey Kode54,

Just a-wondering, when was XAudio2 first introduced into Windows (was it Vista)?
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: ex-driver on 08 November, 2012, 12:38:26 PM
Vista was first with Xaudio2
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: thatperson1245 on 02 February, 2013, 07:39:57 PM
Is it possible to disable the processing of chorus and reverb effects in the BASSMIDI driver? According to the BASSMIDI documentation at http://www.un4seen.com/doc/#bassmidi/BASS_...CreateFile.html (http://www.un4seen.com/doc/#bassmidi/BASS_MIDI_StreamCreateFile.html) it is possible to disable those effects using the BASS_MIDI_NOFX flag. Seeing as the driver configuration application already has a checkbox labeled "Use sinc interpolation" to enable the BASS_MIDI_SINCINTER flag for sinc interpolation, is it possible to add a checkbox like "Disable effects" or similar to enable the BASS_MIDI_NOFX flag and disable effects? This is very useful when chorus and reverb effects use up CPU cycles and slow down the computer.
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: kode54 on 04 February, 2013, 08:14:46 AM
I was considering your feature, but I wondered if it would even have any measurable impact on performance. Reducing polyphony would be more likely to do that, but even still, how slow is your machine?

I kind of want to implement this into foo_midi, if only so I can prove how pointless it is with benchmarks.
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: mudlord on 07 February, 2013, 08:17:36 PM
Yes, what sort of CPU do you have?

(BASSMIDI itself can work on Android and iOS just fine, so this request indeed sounds very odd)
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: thatperson1245 on 07 February, 2013, 09:42:24 PM
It might not even be high CPU consumption, but when I play songs with a lot of reverb or chorus on some channels it seems that other voices/channels without effects get very quiet and washed out. If I use a MIDI editor to turn down the effects, I can hear the washed out channels again. If it's not too complicated, can the developers please add a toggle to switch off reverb and chorus effects? Isn't it just a flag to set in the DLL initialization? If people want the effects then just leave them enabled by default, but at least give some of us the ability to disable it globally.
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: aapitten on 05 March, 2013, 01:42:54 AM
MudLord and Kode54,

I am a senior electrical engineering student and I am using BassMidi for a capstone project I am leading.  First off, let me just say that your software is awesome and I haven't found anything else that even comes close to rivaling it! 

One of the key requirements of my project is I need to be able to run two softsynths (this works nicely since BassMidi has port A and port B) but I need each synth to output to a different soundcard or soundcard output on my PC. Is it possible to define which output is used rather than using the system default?  I was trying to read through the c++ source to find a way to add the feature, but I was getting fairly lost in the code.

Any advice would be greatly appreciated.

Thanks,
aapitten
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: mudlord on 05 March, 2013, 09:29:57 PM
you could alter in the source code which soundcard each synth instance runs on.
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: kode54 on 06 March, 2013, 11:32:04 AM
You'll want to look into the two interfaces separately. For XAudio2, you need to research the szDeviceId parameter to IXAudio2::CreateMasteringVoice, such as how to enumerate the device names it wants. For DirectSound, you need to pass a device GUID to ds_api_i::set_device() before calling ds_api_i::ds_stream_create(), and there's probably some handy documentation on MSDN for how to enumerate DirectSound devices.
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: aapitten on 06 March, 2013, 09:17:46 PM
Okay guys, thanks.  I'll give that a shot and see where it gets me.  I'll post updates as I go.

Thanks,
aapitten
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: aapitten on 08 March, 2013, 02:10:02 AM
Okay, so I got everything to compile (haven't made any changes yet, just wanted to see if I could compile everything) and the exe does run, however when I add a soundfont it instantly crashes.  Any suggestions on where to start looking?  I have tried both 32 and 64 bit builds and am running on Windows 7 x64

Thanks,
aapitten
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: ex-driver on 03 April, 2013, 08:24:25 AM
There is still one bug i noticed. Since v3.18 - 3.21

Midi playback rythm problems ( slower and faster playback issues ) it sounds not constant. I noticed this and a friend of me too.

You can check it with the v3.17 and v3.18-v3.21 .Maybe buffering bug on big soundfonts?
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: SayHelloRosco on 27 April, 2013, 10:16:01 PM
Read the entire thread, and it doesn't seem like my problem has been fixed, yet.

I am trying to use BASSMIDI in GZDoom, and whenever a level starts, within 5-10 seconds, the music starts to distort, and then just fade. It sounds like static/white noise. I screwed around with the buffer settings in the configure window, tried ticking and unticking sinc interpolation, etc. Nothing changes.

OS: Windows 8
CPU: Intel Core 2 Quad @ 2.40 GHz
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: kode54 on 28 April, 2013, 02:14:46 AM
Sounds like a buffer isn't being cleared before samples are accumulated into it, causing the buffer to eventually hit a mess of saturated samples. I have no idea what would cause that. The driver didn't work very nicely the last time I used it in Windows 8 anyway.
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: SayHelloRosco on 25 May, 2013, 07:23:02 PM
Sorry to revive a month old thread.

My previous issue has wetn away. I don't know what caused it to stop happening, but I guess I should be happy. But now two other problems have arisen.

1. Stuttering. Changing the buffer size does alleviate the problem a little bit. But it is still there no matter what
2. Distortion. Not the kind I was facing previously, now it just sounds like what you hear on speakers when the volume is too loud, except this occurs no matter what the volume is set to, whether in the Bassmidi configure tool, or in GZDoom.
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: mudlord on 06 June, 2013, 03:38:15 PM
What OS are you running on?

As for the stuttering, whats your PC specs?
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: UrielDagda on 15 June, 2013, 02:56:43 AM
What OS are you running on?

As for the stuttering, whats your PC specs?

I'm having issues too, for some reason.. With anything that uses MIDI for me like DosBox games and Doomsday.

It's like some glitches where it pops some, and occasionally drops out for up to two seconds.


MSI GT70 0ND-202US Laptop
Intel Core i7-3610QM 2.3-3.1Ghz CPU
nVidia GeForce GTX 675M 2GB
16GB 4x4gb 1600Mhz
2x 750GB HDD RAID 0
Windows 7 Home Premium 64bit
17.3" 1080p LED Non-glare Panel
46" Toshiba 46XV645U 1080p HDTV

Code: [Select]
------------------
System Information
------------------
Time of this report: 6/15/2013, 02:53:10
       Machine name: TARDIS
   Operating System: Windows 7 Home Premium 64-bit (6.1, Build 7601) Service Pack 1 (7601.win7sp1_gdr.130318-1533)
           Language: English (Regional Setting: English)
System Manufacturer: Micro-Star International Co., Ltd.
       System Model: GT70 0NC/GT70 0NC
               BIOS: MSI GT70 0NC E1762IMS Ver:1.0C MSI-Notebook
         Processor: Intel® Core™ i7-3610QM CPU @ 2.30GHz (8 CPUs), ~2.3GHz
             Memory: 16384MB RAM
Available OS Memory: 16280MB RAM
         Page File: 3243MB used, 29316MB available
       Windows Dir: C:\Windows
   DirectX Version: DirectX 11
DX Setup Parameters: Not found
   User DPI Setting: Using System DPI
 System DPI Setting: 96 DPI (100 percent)
   DWM DPI Scaling: Disabled
     DxDiag Version: 6.01.7601.17514 64bit Unicode

------------
DxDiag Notes
------------
     Display Tab 1: No problems found.
       Sound Tab 1: No problems found.
       Sound Tab 2: No problems found.
         Input Tab: No problems found.

--------------------
DirectX Debug Levels
--------------------
Direct3D:    0/4 (retail)
DirectDraw:  0/4 (retail)
DirectInput: 0/5 (retail)
DirectMusic: 0/5 (retail)
DirectPlay:  0/9 (retail)
DirectSound: 0/5 (retail)
DirectShow:  0/6 (retail)

---------------
Display Devices
---------------
         Card name: Intel® HD Graphics 4000
       Manufacturer: Intel Corporation
         Chip type: Intel® HD Graphics Family
           DAC type: Internal
         Device Key: Enum\PCI\VEN_8086&DEV_0166&SUBSYS_10CB1462&REV_09
     Display Memory: 1696 MB
   Dedicated Memory: 64 MB
     Shared Memory: 1632 MB
       Current Mode: 1920 x 1080 (32 bit) (60Hz)
       Monitor Name: Generic PnP Monitor
     Monitor Model: unknown
         Monitor Id: CMO1720
       Native Mode: 1920 x 1080(p) (60.020Hz)
       Output Type: Internal
       Driver Name: igdumd64.dll,igd10umd64.dll,igd10umd64.dll,igdumd32,igd10umd32,igd10umd32
Driver File Version: 8.15.0010.2618 (English)
     Driver Version: 8.15.10.2618
       DDI Version: 11
       Driver Model: WDDM 1.1
  Driver Attributes: Final Retail
   Driver Date/Size: 1/5/2012 07:36:50, 8034304 bytes
       WHQL Logo'd: Yes
   WHQL Date Stamp:
  Device Identifier: {D7B78E66-4226-11CF-E87D-C130A9C2C535}
         Vendor ID: 0x8086
         Device ID: 0x0166
         SubSys ID: 0x10CB1462
       Revision ID: 0x0009
 Driver Strong Name: oem6.inf:IntelGfx.NTamd64.6.0:iIVBM0:8.15.10.2618:pci\ven_8086&dev_0166
     Rank Of Driver: 00E62001
       Video Accel: ModeMPEG2_A ModeMPEG2_C ModeWMV9_C ModeVC1_C
   Deinterlace Caps: {BF752EF6-8CC4-457A-BE1B-08BD1CAEEE9F}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_EdgeFiltering
                     {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_BOBVerticalStretch
                     {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend
                     {BF752EF6-8CC4-457A-BE1B-08BD1CAEEE9F}: Format(In/Out)=(UYVY,YUY2) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_EdgeFiltering
                     {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(UYVY,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_BOBVerticalStretch
                     {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(UYVY,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend
                     {BF752EF6-8CC4-457A-BE1B-08BD1CAEEE9F}: Format(In/Out)=(YV12,YUY2) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_EdgeFiltering
                     {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(YV12,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_BOBVerticalStretch
                     {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(YV12,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend
                     {BF752EF6-8CC4-457A-BE1B-08BD1CAEEE9F}: Format(In/Out)=(NV12,YUY2) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_EdgeFiltering
                     {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(NV12,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_BOBVerticalStretch
                     {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(NV12,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend
                     {BF752EF6-8CC4-457A-BE1B-08BD1CAEEE9F}: Format(In/Out)=(IMC1,YUY2) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_EdgeFiltering
                     {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(IMC1,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_BOBVerticalStretch
                     {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC1,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend
                     {BF752EF6-8CC4-457A-BE1B-08BD1CAEEE9F}: Format(In/Out)=(IMC2,YUY2) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_EdgeFiltering
                     {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(IMC2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_BOBVerticalStretch
                     {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend
                     {BF752EF6-8CC4-457A-BE1B-08BD1CAEEE9F}: Format(In/Out)=(IMC3,YUY2) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_EdgeFiltering
                     {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(IMC3,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_BOBVerticalStretch
                     {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC3,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend
                     {BF752EF6-8CC4-457A-BE1B-08BD1CAEEE9F}: Format(In/Out)=(IMC4,YUY2) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_EdgeFiltering
                     {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(IMC4,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_BOBVerticalStretch
                     {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC4,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend
       D3D9 Overlay: Supported
           DXVA-HD: Supported
       DDraw Status: Enabled
         D3D Status: Enabled
         AGP Status: Enabled

-------------
Sound Devices
-------------
           Description: Speakers (2- Logitech USB Headset)
 Default Sound Playback: Yes
 Default Voice Playback: Yes
           Hardware ID: USB\VID_046D&PID_0A0B&REV_1013&MI_00
       Manufacturer ID: 65535
             Product ID: 65535
                   Type: WDM
           Driver Name: USBAUDIO.sys
         Driver Version: 6.01.7601.17514 (English)
     Driver Attributes: Final Retail
           WHQL Logo'd: Yes
         Date and Size: 11/20/2010 23:23:47, 109696 bytes
           Other Files:
       Driver Provider: Microsoft
         HW Accel Level: Basic
             Cap Flags: 0xF1F
   Min/Max Sample Rate: 100, 200000
Static/Strm HW Mix Bufs: 1, 0
 Static/Strm HW 3D Bufs: 0, 0
             HW Memory: 0
       Voice Management: No
 EAX™ 2.0 Listen/Src: No, No
   I3DL2™ Listen/Src: No, No
Sensaura™ ZoomFX™: No

           Description: Speakers (Realtek High Definition Audio)
 Default Sound Playback: No
 Default Voice Playback: No
           Hardware ID: HDAUDIO\FUNC_01&VEN_10EC&DEV_0892&SUBSYS_146210BE&REV_1003
       Manufacturer ID: 1
             Product ID: 100
                   Type: WDM
           Driver Name: RTKVHD64.sys
         Driver Version: 6.00.0001.6873 (English)
     Driver Attributes: Final Retail
           WHQL Logo'd: Yes
         Date and Size: 3/29/2013 21:42:42, 3379272 bytes
           Other Files:
       Driver Provider: Realtek Semiconductor Corp.
         HW Accel Level: Basic
             Cap Flags: 0xF1F
   Min/Max Sample Rate: 100, 200000
Static/Strm HW Mix Bufs: 1, 0
 Static/Strm HW 3D Bufs: 0, 0
             HW Memory: 0
       Voice Management: No
 EAX™ 2.0 Listen/Src: No, No
   I3DL2™ Listen/Src: No, No
Sensaura™ ZoomFX™: No

---------------------
Sound Capture Devices
---------------------
           Description: Microphone (2- Logitech USB Headset)
  Default Sound Capture: Yes
  Default Voice Capture: Yes
           Driver Name: USBAUDIO.sys
         Driver Version: 6.01.7601.17514 (English)
     Driver Attributes: Final Retail
         Date and Size: 11/20/2010 23:23:47, 109696 bytes
             Cap Flags: 0x1
           Format Flags: 0xFFFFF

           Description: Microphone (Realtek High Definition Audio)
  Default Sound Capture: No
  Default Voice Capture: No
           Driver Name: RTKVHD64.sys
         Driver Version: 6.00.0001.6873 (English)
     Driver Attributes: Final Retail
         Date and Size: 3/29/2013 21:42:42, 3379272 bytes
             Cap Flags: 0x1
           Format Flags: 0xFFFFF

-------------------
DirectInput Devices
-------------------
     Device Name: Mouse
         Attached: 1
   Controller ID: n/a
Vendor/Product ID: n/a
       FF Driver: n/a

     Device Name: Keyboard
         Attached: 1
   Controller ID: n/a
Vendor/Product ID: n/a
       FF Driver: n/a

     Device Name: Logitech USB Headset
         Attached: 1
   Controller ID: 0x0
Vendor/Product ID: 0x046D, 0x0A0B
       FF Driver: n/a

     Device Name: MSI EPF USB
         Attached: 1
   Controller ID: 0x0
Vendor/Product ID: 0x1770, 0xFF00
       FF Driver: n/a

Poll w/ Interrupt: No

-----------
USB Devices
-----------
+ USB Root Hub
| Vendor/Product ID: 0x8086, 0x1E2D
| Matching Device ID: usb\root_hub20
| Service: usbhub
| Driver: usbhub.sys, 3/24/2011 23:29:26, 343040 bytes
| Driver: usbd.sys, 3/24/2011 23:28:59, 7936 bytes
|
+-+ Generic USB Hub
| | Vendor/Product ID: 0x8087, 0x0024
| | Location: Port_#0001.Hub_#0001
| | Matching Device ID: usb\class_09
| | Service: usbhub
| | Driver: usbhub.sys, 3/24/2011 23:29:26, 343040 bytes
| |
| +-+ Microsoft Hardware USB Mouse
| | | Vendor/Product ID: 0x045E, 0x00CB
| | | Location: Port_#0001.Hub_#0003
| | | Matching Device ID: usb\vid_045e&pid_00cb
| | | Service: HidUsb
| | | Driver: hidusb.sys, 11/20/2010 23:23:47, 30208 bytes
| | | Driver: hidclass.sys, 11/20/2010 23:23:47, 76800 bytes
| | | Driver: hidparse.sys, 7/13/2009 20:06:17, 32896 bytes
| | | Driver: coin91.dll, 5/28/2012 08:09:04, 2168416 bytes
| | |
| | +-+ Microsoft USB Basic Optical Mouse v2.0 (Mouse and Keyboard Center)
| | | | Vendor/Product ID: 0x045E, 0x00CB
| | | | Matching Device ID: hid\vid_045e&pid_00cb
| | | | Upper Filters: Point64
| | | | Service: mouhid
| | | | Driver: point64.sys, 6/26/2012 22:38:30, 46176 bytes
| | | | Driver: mouhid.sys, 7/13/2009 20:00:20, 31232 bytes
| | | | Driver: mouclass.sys, 7/13/2009 21:48:27, 49216 bytes
| | | | Driver: wdfcoinstaller01009.dll, 7/30/2009 22:46:12, 1436920 bytes
| | |
| +-+ USB Input Device
| | | Vendor/Product ID: 0x1770, 0xFF00
| | | Location: Port_#0004.Hub_#0003
| | | Matching Device ID: generic_hid_device
| | | Service: HidUsb
| | | Driver: hidusb.sys, 11/20/2010 23:23:47, 30208 bytes
| | | Driver: hidclass.sys, 11/20/2010 23:23:47, 76800 bytes
| | | Driver: hidparse.sys, 7/13/2009 20:06:17, 32896 bytes
| | |
| | +-+ HID-compliant device
| | | | Vendor/Product ID: 0x1770, 0xFF00
| | | | Matching Device ID: hid_device

----------------
Gameport Devices
----------------

------------
PS/2 Devices
------------
+ Standard PS/2 Keyboard
| Matching Device ID: *pnp0303
| Service: i8042prt
| Driver: i8042prt.sys, 7/13/2009 19:19:57, 105472 bytes
| Driver: kbdclass.sys, 7/13/2009 21:48:04, 50768 bytes
|
+ Terminal Server Keyboard Driver
| Matching Device ID: root\rdp_kbd
| Upper Filters: kbdclass
| Service: TermDD
| Driver: i8042prt.sys, 7/13/2009 19:19:57, 105472 bytes
| Driver: kbdclass.sys, 7/13/2009 21:48:04, 50768 bytes
|
+ Microsoft PS/2 Mouse
| Matching Device ID: *pnp0f03
| Service: i8042prt
| Driver: i8042prt.sys, 7/13/2009 19:19:57, 105472 bytes
| Driver: mouclass.sys, 7/13/2009 21:48:27, 49216 bytes
|
+ Terminal Server Mouse Driver
| Matching Device ID: root\rdp_mou
| Upper Filters: mouclass
| Service: TermDD
| Driver: termdd.sys, 11/20/2010 23:23:47, 63360 bytes
| Driver: sermouse.sys, 7/13/2009 20:00:20, 26624 bytes
| Driver: mouclass.sys, 7/13/2009 21:48:27, 49216 bytes

------------------------
Disk & DVD/CD-ROM Drives
------------------------
     Drive: C:
 Free Space: 1146.9 GB
Total Space: 1430.7 GB
File System: NTFS
     Model: Volume0

     Drive: D:
     Model: Slimtype DVD A  DS8A8SH
     Driver: c:\windows\system32\drivers\cdrom.sys, 6.01.7601.17514 (English), 11/20/2010 23:23:47, 147456 bytes

--------------
System Devices
--------------
     Name: Intel® Management Engine Interface
Device ID: PCI\VEN_8086&DEV_1E3A&SUBSYS_10BE1462&REV_04\3&11583659&0&B0
   Driver: n/a

     Name: Intel® 7 Series/C216 Chipset Family PCI Express Root Port 1 - 1E10
Device ID: PCI\VEN_8086&DEV_1E10&SUBSYS_10BE1462&REV_C4\3&11583659&0&E0
   Driver: C:\Windows\system32\DRIVERS\pci.sys, 6.01.7601.17514 (English), 11/20/2010 23:23:47, 184704 bytes

     Name: NVIDIA GeForce GTX 675M
Device ID: PCI\VEN_10DE&DEV_1212&SUBSYS_10CB1462&REV_A1\4&31A1AF22&0&0008
   Driver: C:\Program Files\NVIDIA Corporation\Drs\dbInstaller.exe, 8.17.0012.9631 (English), 3/18/2012 15:53:00, 224064 bytes
   Driver: C:\Program Files\NVIDIA Corporation\Drs\nvdrsdb.bin, 3/18/2012 15:53:00, 327864 bytes
   Driver: C:\Windows\System32\DriverStore\FileRepository\nvmi.inf_amd64_neutral_31d542a24ba9e971\NvCplSetupInt.exe, 1.00.0001.0000 (English), 3/18/2012 15:53:00, 71605168 bytes
   Driver: C:\Program Files (x86)\NVIDIA Corporation\coprocmanager\Nvd3d9wrap.dll, 8.17.0012.9631 (English), 3/18/2012 15:53:00, 236352 bytes
   Driver: C:\Program Files (x86)\NVIDIA Corporation\coprocmanager\detoured.dll, 3/18/2012 15:53:00, 4096 bytes
   Driver: C:\Program Files (x86)\NVIDIA Corporation\coprocmanager\nvdxgiwrap.dll, 8.17.0012.9631 (English), 3/18/2012 15:53:00, 182080 bytes
   Driver: C:\Program Files\NVIDIA Corporation\coprocmanager\Nvd3d9wrapx.dll, 8.17.0012.9631 (English), 3/18/2012 15:53:00, 261120 bytes
   Driver: C:\Program Files\NVIDIA Corporation\coprocmanager\detoured.dll, 3/18/2012 15:53:00, 4096 bytes
   Driver: C:\Program Files\NVIDIA Corporation\coprocmanager\nvdxgiwrapx.dll, 8.17.0012.9631 (English), 3/18/2012 15:53:00, 202752 bytes
   Driver: C:\Program Files\NVIDIA Corporation\license.txt, 3/18/2012 15:53:00, 21887 bytes
   Driver: C:\Program Files\NVIDIA Corporation\OpenCL\OpenCL.dll, 1.00.0000.0000 (English), 3/18/2012 15:53:00, 61248 bytes
   Driver: C:\Program Files\NVIDIA Corporation\OpenCL\OpenCL64.dll, 1.00.0000.0000 (English), 3/18/2012 15:53:00, 68928 bytes
   Driver: C:\Windows\system32\DRIVERS\nvlddmkm.sys, 8.17.0012.9631 (English), 3/18/2012 15:53:00, 14348608 bytes
   Driver: C:\Windows\system32\DRIVERS\nvpciflt.sys, 8.17.0012.9631 (English), 3/18/2012 15:53:00, 28992 bytes
   Driver: C:\Windows\system32\nvapi64.dll, 8.17.0012.9631 (English), 3/18/2012 15:53:00, 2676032 bytes
   Driver: C:\Windows\system32\nvcompiler.dll, 8.17.0012.9631 (English), 3/18/2012 15:53:00, 25222464 bytes
   Driver: C:\Windows\system32\nvcuda.dll, 8.17.0012.9631 (English), 3/18/2012 15:53:00, 8045888 bytes
   Driver: C:\Windows\system32\nvcuvenc.dll, 6.14.0012.9631 (English), 3/18/2012 15:53:00, 2873664 bytes
   Driver: C:\Windows\system32\nvcuvid.dll, 8.17.0012.9631 (English), 3/18/2012 15:53:00, 2673984 bytes
   Driver: C:\Windows\system32\nvd3dumx.dll, 8.17.0012.9631 (English), 3/18/2012 15:53:00, 17663296 bytes
   Driver: C:\Windows\system32\nvdecodemft.dll, 8.17.0012.9631 (English), 3/18/2012 15:53:00, 364352 bytes
   Driver: C:\Windows\system32\nvinfo.pb, 3/18/2012 15:53:00, 12780 bytes
   Driver: C:\Windows\system32\nvinitx.dll, 8.17.0012.9631 (English), 3/18/2012 15:53:00, 260928 bytes
   Driver: C:\Windows\system32\nvoglv64.dll, 8.17.0012.9631 (English), 3/18/2012 15:53:00, 25557312 bytes
   Driver: C:\Windows\system32\nvumdshimx.dll, 8.17.0012.9631 (English), 3/18/2012 15:53:00, 962880 bytes
   Driver: C:\Windows\system32\nvwgf2umx.dll, 8.17.0012.9631 (English), 3/18/2012 15:53:00, 9732928 bytes
   Driver: C:\Windows\SysWow64\nvapi.dll, 8.17.0012.9631 (English), 3/18/2012 15:53:00, 2316608 bytes
   Driver: C:\Windows\SysWow64\nvcompiler.dll, 8.17.0012.9631 (English), 3/18/2012 15:53:00, 17543488 bytes
   Driver: C:\Windows\SysWow64\nvcuda.dll, 8.17.0012.9631 (English), 3/18/2012 15:53:00, 5924160 bytes
   Driver: C:\Windows\SysWow64\nvcuvenc.dll, 6.14.0012.9631 (English), 3/18/2012 15:53:00, 2438464 bytes
   Driver: C:\Windows\SysWow64\nvcuvid.dll, 8.17.0012.9631 (English), 3/18/2012 15:53:00, 2518336 bytes
   Driver: C:\Windows\SysWow64\nvd3dum.dll, 8.17.0012.9631 (English), 3/18/2012 15:53:00, 15028544 bytes
   Driver: C:\Windows\SysWow64\nvdecodemft.dll, 8.17.0012.9631 (English), 3/18/2012 15:53:00, 301376 bytes
   Driver: C:\Windows\SysWow64\nvinit.dll, 8.17.0012.9631 (English), 3/18/2012 15:53:00, 215360 bytes
   Driver: C:\Windows\SysWow64\nvoglv32.dll, 8.17.0012.9631 (English), 3/18/2012 15:53:00, 19457344 bytes
   Driver: C:\Windows\SysWow64\nvumdshim.dll, 8.17.0012.9631 (English), 3/18/2012 15:53:00, 813376 bytes
   Driver: C:\Windows\SysWow64\nvwgf2um.dll, 8.17.0012.9631 (English), 3/18/2012 15:53:00, 7727424 bytes
   Driver: C:\Windows\system32\nvdispco64.dll, 2.00.0025.0001 (English), 3/18/2012 15:53:00, 1737536 bytes
   Driver: C:\Windows\system32\nvgenco64.dll, 2.00.0014.0000 (English), 3/18/2012 15:53:00, 1466176 bytes

     Name: Intel® USB 3.0 eXtensible Host Controller
Device ID: PCI\VEN_8086&DEV_1E31&SUBSYS_10BE1462&REV_04\3&11583659&0&A0
   Driver: C:\Windows\system32\DRIVERS\iusb3xhc.sys, 1.00.0001.0209 (English), 1/4/2012 15:58:50, 786200 bytes

     Name: Intel® Centrino® Wireless-N 2230
Device ID: PCI\VEN_8086&DEV_0887&SUBSYS_40628086&REV_C4\4&3009D5B3&0&00E2
   Driver: C:\Windows\system32\DRIVERS\NETwNs64.sys, 15.00.0000.0075 (English), 12/1/2011 23:51:00, 11417088 bytes
   Driver: C:\Windows\system32\NETwNc64.dll, 15.00.0000.0009 (English), 11/16/2011 17:18:58, 879104 bytes
   Driver: C:\Windows\system32\NETwNr64.dll, 15.00.0000.0009 (English), 11/16/2011 17:20:40, 3374592 bytes
   Driver: C:\Windows\system32\drivers\vwifibus.sys, 6.01.7600.16385 (English), 7/13/2009 20:07:21, 24576 bytes

     Name: Intel® 7 Series/C216 Chipset Family USB Enhanced Host Controller - 1E2D
Device ID: PCI\VEN_8086&DEV_1E2D&SUBSYS_10BE1462&REV_04\3&11583659&0&D0
   Driver: C:\Windows\system32\drivers\usbehci.sys, 6.01.7601.17586 (English), 3/24/2011 23:29:04, 52736 bytes
   Driver: C:\Windows\system32\drivers\usbport.sys, 6.01.7601.17586 (English), 3/24/2011 23:29:14, 325120 bytes
   Driver: C:\Windows\system32\drivers\usbhub.sys, 6.01.7601.17586 (English), 3/24/2011 23:29:26, 343040 bytes

     Name: Intel® HD Graphics 4000
Device ID: PCI\VEN_8086&DEV_0166&SUBSYS_10CB1462&REV_09\3&11583659&0&10
   Driver: n/a

     Name: Intel® 7 Series/C216 Chipset Family USB Enhanced Host Controller - 1E26
Device ID: PCI\VEN_8086&DEV_1E26&SUBSYS_10BE1462&REV_04\3&11583659&0&E8
   Driver: C:\Windows\system32\drivers\usbehci.sys, 6.01.7601.17586 (English), 3/24/2011 23:29:04, 52736 bytes
   Driver: C:\Windows\system32\drivers\usbport.sys, 6.01.7601.17586 (English), 3/24/2011 23:29:14, 325120 bytes
   Driver: C:\Windows\system32\drivers\usbhub.sys, 6.01.7601.17586 (English), 3/24/2011 23:29:26, 343040 bytes

     Name: 3rd Gen Core processor DRAM Controller - 0154
Device ID: PCI\VEN_8086&DEV_0154&SUBSYS_10BE1462&REV_09\3&11583659&0&00
   Driver: n/a

     Name: Intel® 7 Series/C216 Chipset Family SMBus Host Controller - 1E22
Device ID: PCI\VEN_8086&DEV_1E22&SUBSYS_10BE1462&REV_04\3&11583659&0&FB
   Driver: n/a

     Name: Xeon® processor E3-1200 v2/3rd Gen Core processor PCI Express Root Port - 0151
Device ID: PCI\VEN_8086&DEV_0151&SUBSYS_10BE1462&REV_09\3&11583659&0&08
   Driver: C:\Windows\system32\DRIVERS\pci.sys, 6.01.7601.17514 (English), 11/20/2010 23:23:47, 184704 bytes

     Name: High Definition Audio Controller
Device ID: PCI\VEN_8086&DEV_1E20&SUBSYS_10BE1462&REV_04\3&11583659&0&D8
   Driver: C:\Windows\system32\DRIVERS\hdaudbus.sys, 6.01.7601.17514 (English), 11/20/2010 23:23:47, 122368 bytes

     Name: Ethernet Controller
Device ID: PCI\VEN_1969&DEV_E091&SUBSYS_10BE1462&REV_13\4&2ABFB514&0&00E0
   Driver: n/a

     Name: Intel® Mobile Express Chipset SATA RAID Controller
Device ID: PCI\VEN_8086&DEV_282A&SUBSYS_10BE1462&REV_04\3&11583659&0&FA
   Driver: C:\Windows\system32\DRIVERS\iaStor.sys, 11.00.0000.1032 (English), 11/29/2011 20:40:32, 568600 bytes

     Name: Intel® 7 Series/C216 Chipset Family PCI Express Root Port 5 - 1E18
Device ID: PCI\VEN_8086&DEV_1E18&SUBSYS_10BE1462&REV_C4\3&11583659&0&E4
   Driver: C:\Windows\system32\DRIVERS\pci.sys, 6.01.7601.17514 (English), 11/20/2010 23:23:47, 184704 bytes

     Name: SDA Standard Compliant SD Host Controller
Device ID: PCI\VEN_10EC&DEV_5209&SUBSYS_10BE1462&REV_01\4&3991D57F&0&01E4
   Driver: C:\Windows\system32\DRIVERS\sdbus.sys, 6.01.7601.17514 (English), 11/20/2010 23:23:47, 109056 bytes

     Name: Intel® HM77 Express Chipset LPC Controller - 1E57
Device ID: PCI\VEN_8086&DEV_1E57&SUBSYS_10BE1462&REV_04\3&11583659&0&F8
   Driver: C:\Windows\system32\DRIVERS\msisadrv.sys, 6.01.7600.16385 (English), 7/13/2009 21:48:27, 15424 bytes

     Name: Intel® 7 Series/C216 Chipset Family PCI Express Root Port 3 - 1E14
Device ID: PCI\VEN_8086&DEV_1E14&SUBSYS_10BE1462&REV_C4\3&11583659&0&E2
   Driver: C:\Windows\system32\DRIVERS\pci.sys, 6.01.7601.17514 (English), 11/20/2010 23:23:47, 184704 bytes

     Name: Realtek PCIE CardReader
Device ID: PCI\VEN_10EC&DEV_5209&SUBSYS_10BE1462&REV_01\4&3991D57F&0&00E4
   Driver: C:\Windows\system32\DRIVERS\RtsPStor.sys, 6.01.7601.0090 (English), 12/6/2011 04:14:38, 339048 bytes
   Driver: C:\Windows\SysWOW64\RtsPStorIcon.dll, 1.00.0008.0000 (English), 12/6/2011 04:14:38, 9888872 bytes

------------------
DirectShow Filters
------------------

DirectShow Filters:
WMAudio Decoder DMO,0x00800800,1,1,WMADMOD.DLL,6.01.7601.17514
WMAPro over S/PDIF DMO,0x00600800,1,1,WMADMOD.DLL,6.01.7601.17514
WMSpeech Decoder DMO,0x00600800,1,1,WMSPDMOD.DLL,6.01.7601.17514
MP3 Decoder DMO,0x00600800,1,1,mp3dmod.dll,6.01.7600.16385
Mpeg4s Decoder DMO,0x00800001,1,1,mp4sdecd.dll,6.01.7600.16385
WMV Screen decoder DMO,0x00600800,1,1,wmvsdecd.dll,6.01.7601.17514
WMVideo Decoder DMO,0x00800001,1,1,wmvdecod.dll,6.01.7601.17514
Mpeg43 Decoder DMO,0x00800001,1,1,mp43decd.dll,6.01.7600.16385
Mpeg4 Decoder DMO,0x00800001,1,1,mpg4decd.dll,6.01.7600.16385
DV Muxer,0x00400000,0,0,qdv.dll,6.06.7601.17514
Color Space Converter,0x00400001,1,1,quartz.dll,6.06.7601.17713
WM ASF Reader,0x00400000,0,0,qasf.dll,12.00.7601.17514
Screen Capture filter,0x00200000,0,1,wmpsrcwp.dll,12.00.7601.17514
AVI Splitter,0x00600000,1,1,quartz.dll,6.06.7601.17713
VGA 16 Color Ditherer,0x00400000,1,1,quartz.dll,6.06.7601.17713
SBE2MediaTypeProfile,0x00200000,0,0,sbe.dll,6.06.7601.17528
Microsoft DTV-DVD Video Decoder,0x005fffff,2,4,msmpeg2vdec.dll,12.00.9200.16426
AC3 Parser Filter,0x00600000,1,1,mpg2splt.ax,6.06.7601.17528
StreamBufferSink,0x00200000,0,0,sbe.dll,6.06.7601.17528
Microsoft TV Captions Decoder,0x00200001,1,0,MSTVCapn.dll,6.01.7601.17715
MJPEG Decompressor,0x00600000,1,1,quartz.dll,6.06.7601.17713
CBVA DMO wrapper filter,0x00200000,1,1,cbva.dll,6.01.7601.17514
MPEG-I Stream Splitter,0x00600000,1,2,quartz.dll,6.06.7601.17713
SAMI (CC) Parser,0x00400000,1,1,quartz.dll,6.06.7601.17713
VBI Codec,0x00600000,1,4,VBICodec.ax,6.06.7601.17514
MPEG-2 Splitter,0x005fffff,1,0,mpg2splt.ax,6.06.7601.17528
Closed Captions Analysis Filter,0x00200000,2,5,cca.dll,6.06.7601.17514
SBE2FileScan,0x00200000,0,0,sbe.dll,6.06.7601.17528
Microsoft MPEG-2 Video Encoder,0x00200000,1,1,msmpeg2enc.dll,6.01.7601.17514
Internal Script Command Renderer,0x00800001,1,0,quartz.dll,6.06.7601.17713
MPEG Audio Decoder,0x03680001,1,1,quartz.dll,6.06.7601.17713
DV Splitter,0x00600000,1,2,qdv.dll,6.06.7601.17514
Video Mixing Renderer 9,0x00200000,1,0,quartz.dll,6.06.7601.17713
Microsoft MPEG-2 Encoder,0x00200000,2,1,msmpeg2enc.dll,6.01.7601.17514
ACM Wrapper,0x00600000,1,1,quartz.dll,6.06.7601.17713
Video Renderer,0x00800001,1,0,quartz.dll,6.06.7601.17713
MPEG-2 Video Stream Analyzer,0x00200000,0,0,sbe.dll,6.06.7601.17528
Line 21 Decoder,0x00600000,1,1,,
Video Port Manager,0x00600000,2,1,quartz.dll,6.06.7601.17713
Video Renderer,0x00400000,1,0,quartz.dll,6.06.7601.17713
VPS Decoder,0x00200000,0,0,WSTPager.ax,6.06.7601.17514
WM ASF Writer,0x00400000,0,0,qasf.dll,12.00.7601.17514
VBI Surface Allocator,0x00600000,1,1,vbisurf.ax,6.01.7601.17514
File writer,0x00200000,1,0,qcap.dll,6.06.7601.17514
iTV Data Sink,0x00600000,1,0,itvdata.dll,6.06.7601.17514
iTV Data Capture filter,0x00600000,1,1,itvdata.dll,6.06.7601.17514
DVD Navigator,0x00200000,0,3,qdvd.dll,6.06.7601.17835
Microsoft TV Subtitles Decoder,0x00200001,1,0,MSTVCapn.dll,6.01.7601.17715
Overlay Mixer2,0x00200000,1,1,,
RDP DShow Redirection Filter,0xffffffff,1,0,DShowRdpFilter.dll,
Microsoft MPEG-2 Audio Encoder,0x00200000,1,1,msmpeg2enc.dll,6.01.7601.17514
WST Pager,0x00200000,1,1,WSTPager.ax,6.06.7601.17514
MPEG-2 Demultiplexer,0x00600000,1,1,mpg2splt.ax,6.06.7601.17528
DV Video Decoder,0x00800000,1,1,qdv.dll,6.06.7601.17514
SampleGrabber,0x00200000,1,1,qedit.dll,6.06.7601.17514
Null Renderer,0x00200000,1,0,qedit.dll,6.06.7601.17514
MPEG-2 Sections and Tables,0x005fffff,1,0,Mpeg2Data.ax,6.06.7601.17514
Microsoft AC3 Encoder,0x00200000,1,1,msac3enc.dll,6.01.7601.17514
StreamBufferSource,0x00200000,0,0,sbe.dll,6.06.7601.17528
Smart Tee,0x00200000,1,2,qcap.dll,6.06.7601.17514
Overlay Mixer,0x00200000,0,0,,
AVI Decompressor,0x00600000,1,1,quartz.dll,6.06.7601.17713
NetBridge,0x00200000,2,0,netbridge.dll,6.01.7601.17514
AVI/WAV File Source,0x00400000,0,2,quartz.dll,6.06.7601.17713
Wave Parser,0x00400000,1,1,quartz.dll,6.06.7601.17713
MIDI Parser,0x00400000,1,1,quartz.dll,6.06.7601.17713
Multi-file Parser,0x00400000,1,1,quartz.dll,6.06.7601.17713
File stream renderer,0x00400000,1,1,quartz.dll,6.06.7601.17713
Microsoft DTV-DVD Audio Decoder,0x005fffff,1,1,msmpeg2adec.dll,6.01.7140.0000
StreamBufferSink2,0x00200000,0,0,sbe.dll,6.06.7601.17528
AVI Mux,0x00200000,1,0,qcap.dll,6.06.7601.17514
Line 21 Decoder 2,0x00600002,1,1,quartz.dll,6.06.7601.17713
File Source (Async.),0x00400000,0,1,quartz.dll,6.06.7601.17713
File Source (URL),0x00400000,0,1,quartz.dll,6.06.7601.17713
Media Center Extender Encryption Filter,0x00200000,2,2,Mcx2Filter.dll,6.01.7601.17514
AudioRecorder WAV Dest,0x00200000,0,0,WavDest.dll,
AudioRecorder Wave Form,0x00200000,0,0,WavDest.dll,
SoundRecorder Null Renderer,0x00200000,0,0,WavDest.dll,
Infinite Pin Tee Filter,0x00200000,1,1,qcap.dll,6.06.7601.17514
Enhanced Video Renderer,0x00200000,1,0,evr.dll,6.01.7601.17514
BDA MPEG2 Transport Information Filter,0x00200000,2,0,psisrndr.ax,6.06.7601.17669
MPEG Video Decoder,0x40000001,1,1,quartz.dll,6.06.7601.17713

WDM Streaming Tee/Splitter Devices:
Tee/Sink-to-Sink Converter,0x00200000,1,1,ksproxy.ax,6.01.7601.17514

Video Compressors:
WMVideo8 Encoder DMO,0x00600800,1,1,wmvxencd.dll,6.01.7600.16385
WMVideo9 Encoder DMO,0x00600800,1,1,wmvencod.dll,6.01.7600.16385
MSScreen 9 encoder DMO,0x00600800,1,1,wmvsencd.dll,6.01.7600.16385
DV Video Encoder,0x00200000,0,0,qdv.dll,6.06.7601.17514
MJPEG Compressor,0x00200000,0,0,quartz.dll,6.06.7601.17713

Audio Compressors:
WM Speech Encoder DMO,0x00600800,1,1,WMSPDMOE.DLL,6.01.7600.16385
WMAudio Encoder DMO,0x00600800,1,1,WMADMOE.DLL,6.01.7600.16385
IMA ADPCM,0x00200000,1,1,quartz.dll,6.06.7601.17713
PCM,0x00200000,1,1,quartz.dll,6.06.7601.17713
Microsoft ADPCM,0x00200000,1,1,quartz.dll,6.06.7601.17713
GSM 6.10,0x00200000,1,1,quartz.dll,6.06.7601.17713
CCITT A-Law,0x00200000,1,1,quartz.dll,6.06.7601.17713
CCITT u-Law,0x00200000,1,1,quartz.dll,6.06.7601.17713
MPEG Layer-3,0x00200000,1,1,quartz.dll,6.06.7601.17713

Audio Capture Sources:
Microphone (2- Logitech USB Hea,0x00200000,0,0,qcap.dll,6.06.7601.17514
Microphone (Realtek High Defini,0x00200000,0,0,qcap.dll,6.06.7601.17514

PBDA CP Filters:
PBDA DTFilter,0x00600000,1,1,CPFilters.dll,6.06.7601.17528
PBDA ETFilter,0x00200000,0,0,CPFilters.dll,6.06.7601.17528
PBDA PTFilter,0x00200000,0,0,CPFilters.dll,6.06.7601.17528

Midi Renderers:
BASSMIDI Driver (port A),0x00200000,1,0,quartz.dll,6.06.7601.17713
BASSMIDI Driver (port B),0x00200000,1,0,quartz.dll,6.06.7601.17713
Default MidiOut Device,0x00800000,1,0,quartz.dll,6.06.7601.17713
Microsoft GS Wavetable Synth,0x00200000,1,0,quartz.dll,6.06.7601.17713

WDM Streaming Capture Devices:
Realtek HD Audio Line input,0x00200000,1,1,ksproxy.ax,6.01.7601.17514
Realtek HD Audio Mic input,0x00200000,1,1,ksproxy.ax,6.01.7601.17514
Realtek HD Audio Stereo input,0x00200000,1,1,ksproxy.ax,6.01.7601.17514
Logitech USB Headset,0x00200000,2,2,ksproxy.ax,6.01.7601.17514

WDM Streaming Rendering Devices:
Realtek HD Audio output,0x00200000,1,1,ksproxy.ax,6.01.7601.17514
Realtek HDA SPDIF Out,0x00200000,1,1,ksproxy.ax,6.01.7601.17514
Logitech USB Headset,0x00200000,2,2,ksproxy.ax,6.01.7601.17514

BDA Network Providers:
Microsoft ATSC Network Provider,0x00200000,0,1,MSDvbNP.ax,6.06.7601.17514
Microsoft DVBC Network Provider,0x00200000,0,1,MSDvbNP.ax,6.06.7601.17514
Microsoft DVBS Network Provider,0x00200000,0,1,MSDvbNP.ax,6.06.7601.17514
Microsoft DVBT Network Provider,0x00200000,0,1,MSDvbNP.ax,6.06.7601.17514
Microsoft Network Provider,0x00200000,0,1,MSNP.ax,6.06.7601.17514

Multi-Instance Capable VBI Codecs:
VBI Codec,0x00600000,1,4,VBICodec.ax,6.06.7601.17514

BDA Transport Information Renderers:
BDA MPEG2 Transport Information Filter,0x00600000,2,0,psisrndr.ax,6.06.7601.17669
MPEG-2 Sections and Tables,0x00600000,1,0,Mpeg2Data.ax,6.06.7601.17514

BDA CP/CA Filters:
Decrypt/Tag,0x00600000,1,1,EncDec.dll,6.06.7601.17708
Encrypt/Tag,0x00200000,0,0,EncDec.dll,6.06.7601.17708
PTFilter,0x00200000,0,0,EncDec.dll,6.06.7601.17708
XDS Codec,0x00200000,0,0,EncDec.dll,6.06.7601.17708

WDM Streaming Communication Transforms:
Tee/Sink-to-Sink Converter,0x00200000,1,1,ksproxy.ax,6.01.7601.17514

Audio Renderers:
Speakers (2- Logitech USB Heads,0x00200000,1,0,quartz.dll,6.06.7601.17713
Default DirectSound Device,0x00800000,1,0,quartz.dll,6.06.7601.17713
Default WaveOut Device,0x00200000,1,0,quartz.dll,6.06.7601.17713
DirectSound: Speakers (2- Logitech USB Headset),0x00200000,1,0,quartz.dll,6.06.7601.17713
DirectSound: Speakers (Realtek High Definition Audio),0x00200000,1,0,quartz.dll,6.06.7601.17713
Speakers (Realtek High Definiti,0x00200000,1,0,quartz.dll,6.06.7601.17713

---------------
EVR Power Information
---------------
Current Setting: {5C67A112-A4C9-483F-B4A7-1D473BECAFDC} (Quality)
  Quality Flags: 2576
   Enabled:
   Force throttling
   Allow half deinterlace
   Allow scaling
   Decode Power Usage: 100
  Balanced Flags: 1424
   Enabled:
   Force throttling
   Allow batching
   Force half deinterlace
   Force scaling
   Decode Power Usage: 50
  PowerFlags: 1424
   Enabled:
   Force throttling
   Allow batching
   Force half deinterlace
   Force scaling
   Decode Power Usage: 0
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: UrielDagda on 03 July, 2013, 06:09:49 PM
If this topic hasn't died, I do have a suggestion. After testing it with huge soundfonts for hours, I've come to the conclusion that it's loading the notes from the hard drive a few at a time, generating a ton of small data transfers from the hard drive.. Maybe putting a tickable option in the Advanced section to cache soundfonts up to a half of gig in size in RAM would eliminate this problem... Especially for people who have large amounts of RAM.
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: [JAZ] on 04 July, 2013, 03:23:45 PM
As you've correctly indicated, soundfonts are not loaded completely in RAM. But you probably don't know well how soundfonts work:

First, each soundfont is different, (not just by size, but size is an indicator of what could be there). With big soundfonts, a single instrument (especially pianos and other multi-octave sound) consists of several samples of different lengths.
Next, you have the standard General MIDI instrument set (up to 127 plus drums), and can have other banks of instruments (i.e. more instruments sets) for other type of sounds.
Now, remember that BASSMIDI is a driver, and as such, it does not know the whole contents of the file you are playing, nor what keys will you press (when playing live). But especially in realtime situations, you want it to react fast, and that really implies deciding to load moments before it is going to generate sound.

Now, you say "ok, buffer more beforehand". But that puts it again on a guess, and on a longer delay after initialization.
In your example, you say "loading the notes a few at a time". That is an indication of a very layered instrument, like I suggested above.
I've seen 50MB+ just for one acoustic piano. I don't think you're going to load that completely from a hard drive (SSD excluded) in less than a second (or half a second, if the drive is fast).

Said that, back in the days, soundbanks where loaded into memory (either provided by the soundcard, or by the computer). Several sizes where offered as a tradeoff between RAM usage and quality. I wouldn't think having such an option to be crazy, but I'm not sure how configurable BASSMIDI is in this regard. (Remember that this is just a driver that uses BASSMIDI).

Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: UrielDagda on 04 July, 2013, 06:16:20 PM
I'm just using it to play games, and they only make use of pre-made General MIDI banks from what I can understand.. I'll probably never understand how these really work, it's just soundfonts larger than 4MB seem to cause a lot of hard drive accesses, and it can't seem to keep up to what the game wants, so every 10 seconds or so there will be a 2 second period where the game pauses, and even loses notes.

These issues don't happen outside of the games for me, since the games themselves are using resources (most of them running at a speed modified through DOSBox that seems to be particularly sensitive to the delays).

I figured since the Driver Configuration set which soundfonts to use, it'd be able to be used to load the lists into RAM.

I didn't know about the larger files using several samples per instrument, that could be why the games can't handle it well.  Just might be too many layers (from DOS program, to DOS layer, to DOSbox, to Windows, to the BassMIDI driver to the hard drive and back again, for each sub-sample).

With an SSD this probably wouldn't be an issue, but I won't have one until the next PC build early next year.  I might just resort to sticking with the smaller GM and GS soundfonts if it's just not technically feasible, or just too much work for an ability few people are going to use.

Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: lamedude on 07 July, 2013, 01:36:48 AM
I'd put the soundfont on a RAMdisk.
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: UrielDagda on 08 July, 2013, 07:17:59 PM
Another issue I'm having that I've exhausted all other possibilities on is one with Doomsday Engine.  It seems to only happen with the BassMIDI driver MIDI, where when music loops, it'll occasionally suddenly turn all instruments to piano until the next loop.

It seem to be an issue with how SDL_mixer and BassMIDI interact when the music loops. The DE programmer says there's nothing he can do on his end of it to fix the problem.  It's either a bug with SDL_mixer or BassMIDI.
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: UrielDagda on 09 July, 2013, 03:27:51 PM
I uploaded a video of the issue on Youtube.

http://www.youtube.com/watch?v=Y1nqRTO0zao (http://www.youtube.com/watch?v=Y1nqRTO0zao)
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: bennetng on 26 September, 2013, 11:34:27 AM
Now we can use BASSMIDI in foobar2000 or as a Windows system synth, but did someone make BASSMIDI as a VSTi? It would be nice for composer like me to use BASSMIDI as VSTi because it has even lower latency and synth output can be exported in DAWs with other virtual instruments and audio tracks rather than real time playback/recording.

Although DAW users have access to many high quality virtual instruments, BASSMIDI has the best GM/GS/XG compatibility. If someone already made a BASSMIDI VSTi please tell me, thanks!
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: andoru on 15 October, 2013, 09:55:08 AM
I've been using your driver as of today, and I would like to thank you for your hard work on it.

I'm having the same issue here with stuttering and skipping. I know this is typically a buffer problem, and I've tried fiddling with the DSound and XAudio buffer settings but nothing seems to fix this problem. I also tried to disable Sinc Interpolation thinking that maybe the CPU might be overloaded due to some weird reason, but that didn't fix it either.
It's not as bad when I play the midi files from WMP (during which the CPU is around at 10-20% usage), but when I play a game or run an application that uses midi it gets worse.

Any way this can be avoided?
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: andoru on 13 November, 2013, 12:13:14 PM
*bump*
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: mudlord on 16 November, 2013, 06:06:49 AM
I've been using your driver as of today, and I would like to thank you for your hard work on it.

I'm having the same issue here with stuttering and skipping. I know this is typically a buffer problem, and I've tried fiddling with the DSound and XAudio buffer settings but nothing seems to fix this problem. I also tried to disable Sinc Interpolation thinking that maybe the CPU might be overloaded due to some weird reason, but that didn't fix it either.
It's not as bad when I play the midi files from WMP (during which the CPU is around at 10-20% usage), but when I play a game or run an application that uses midi it gets worse.

Any way this can be avoided?


Quote
I'd put the soundfont on a RAMdisk.


http://www.softperfect.com/products/ramdisk/ (http://www.softperfect.com/products/ramdisk/)
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: RichNagel on 26 November, 2013, 06:29:15 AM
A (sort of) workaround for stuttering...

I've recently set myself up an old laptop. It's and older Dell Inspiron 6000, with an Intel Centrino Mobile 1.6GHz processor, and 1GB of RAM.

After installing the BASSMIDI Driver, I also noticed a few stutters and skips when using my "Weeds General MIDI SoundFont v3.0" (approx. 55MB). Although, I was quite surprised at how well and smoothly that MIDI playback was... given that the laptops CPU was only 1.6GHz

Anyhow, I found a sort of a $hit-rig type of workaround that stops ALL of the stuttering and skips:

1 - I copied my "WeedsGM3.sf2" SoundFont to the new filename "WeedsGM3.preload".

1b - Note that I currently have an unreleased "Version 4.0" update for the SoundFont (gotta get off of my arse and upload that sometime <GRIN>), so I copied that "WeedsGM4 Update.sf2" file to the new filename "WeedsGM4 Update.preload" as well.

2 - I then created a simple batch file with the filename of "Preload SoundFont.bat", with the following contents:

---cut here---
@ECHO OFF

FC/B "C:\SoundFonts\WeedsGM3.sf2" "C:\SoundFonts\WeedsGM3.preload"

FC/B "C:\SoundFonts\WeedsGM4 Update.sf2" "C:\SoundFonts\WeedsGM4 Update.preload"
---cut here---

3 - I then created a WinDoZe shortcut link to the batch file with the filename "Preload SoundFont.lnk", setting it's properties to "Minimized", and assigning it to a hotkey combo as well (in my case, "SHIFT+ALT+F").

4 - Lastly, I copied the "Preload SoundFont.lnk" shortcut file to the "Startup" folder of my Windows Start Menu.

OK... what does this whole schmear do?

Upon powering up the PC and Windows starts, a binary file compare will be executed between the two ".sf2" and ".preload" SoundFont files. A side effect of doing this causes Windows to read the ".sf2" SoundFont files into memory, and totally fix the problem with the stuttering and skipping when playing MIDI files

P.S. I can ALSO press "SHIFT+ALT+F" hotkey combo to do the same on-the-fly if I so desire

P.P.S. Oh, and the extra startup time for Windows before the system is idle? NO MORE time than would normally be needed for my desktop PC that has an actual SoundBlaster Live card in it (when Windows initally starts up, and my SoundFont is loaded into system RAM for the SBLive).
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: mudlord on 27 November, 2013, 08:49:10 PM
Is this workaround with Windows XP?
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: RichNagel on 28 November, 2013, 05:13:45 AM
Is this workaround with Windows XP?


Yes, that's what I'm running... Windows XP Professional with Service Pack 3.

Although, I'm assuming that this should help/work with Vista/7/8 as well, as these incarnations of Windows handle "file caching" (for lack of a better term) similarly to Windows XP

In other words: Read a largish file once within a given Windows session, hard drive access. Read the same largish file a second time within the same Windows session, almost no hard drive access.

P.S. Been twiddling around with my described $hit-rig fix... seems to work quite well. 100% success (with either NO stutters, or only minimal ones) when using my SoundFont with the BASSMIDI Driver; running DOOM in DOSBox, running Tetris Classic for DOS (or Tetris Classic for Windows, running under an installed copy of Windows 3.11 in DOSBox), playing MIDI files in Windows Media Player, as well as when running my ancient version of Cakewalk Professional v3.02
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: RichNagel on 01 December, 2013, 10:39:50 AM
OK, here's another handy one...

My previous instructions are great if you load and use the SAME SoundFont (or a set of SoundFonts) ALL of the time.

The following instructions allow you to do the same, except on-the-fly for ANY SoundFont (handy if you load various different SoundFonts within a given Windows session):

1 - Create a new batch file using WinDoZe Notepad with the filename "Preload Any SoundFont.bat" with the following contents:

---cut here---
@ECHO OFF
COPY /Y %1 %1.preload
FC/B %1 %1.preload
DEL %1.preload
---cut here---

2 - Copy this file to your "C:\Windows" directory.

3 - Create a Windows shortcut to the file (right-click the file in your "C:\Windows" directory, and click "Create Shortcut.

4 - Rename this shortcut to the filename "Preload Any SoundFont.lnk".

5 - Set the properties for the shotcut to "Run" as "Minimized", and change the icon to your preference (I like icon #18 (the eighth icon in the second row) in the "C:\Windows\System32\MMSys.cpl" Windows Control Panel file).

6 - Copy the new "Preload Any SoundFont.lnk" shortcut file to your "C:\Documents and Settings\USER NAME\SendTo" directory.

After restarting Wwindows, you can right-click on any SoundFile file, click on "Send To", and then left-click on "Preload Any SoundFont" for ANY SoundFont file

P.S. Since I couldn't attach any files here in the forum, screenshots and a ZIP with the required files can be found in this message thread -> http://www.vgmusic.com/phpBB3/viewtopic.php?f=16&t=13967 (http://www.vgmusic.com/phpBB3/viewtopic.php?f=16&t=13967)
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: RichNagel on 12 December, 2013, 05:27:34 PM
Now here's a weird one...

I was playing around with the ancient "DoReMiX 2" (by Roland, circa 1994-1995):

http://static.digischool.nl/mu/Community/d...remix/disk1.zip (http://static.digischool.nl/mu/Community/download/doremix/disk1.zip)
http://static.digischool.nl/mu/Community/d...remix/disk2.zip (http://static.digischool.nl/mu/Community/download/doremix/disk2.zip)
http://static.digischool.nl/mu/Community/d...remix/disk3.zip (http://static.digischool.nl/mu/Community/download/doremix/disk3.zip)

...LOTS of fun, but I experienced a rather weird glitch with the BASSMIDI Driver.

If I run DoReMiX under an installed copy of Windows 3.11 running under DOSBox, it works fine.

Also, if I set the Windows MIDI Mapper to "Out to MIDI Yoke 1", and then pipe it to my old MIDI sequencer Cakewalk Professional v3.01 (setting CWP's MIDI input to "In from MIDI Yoke 1", and CWP's MIDI output to either of the BASSMIDI Driver ports), it ALSO works fine (running both under Windows XP).

But, If I set the Windows MIDI Mapper to the BASSMIDI Driver (port A or B), the audio IMMEDIATELY (and permanently) cuts out after a few seconds or so (again, running under Windows XP).

Now, for the weird thing...

I discovered that if I have the BASSMIDI Driver Configuration utility idling in the background WHILE running DoReMiX (under Windows XP), it works fine... NO sound dropout at all (?). :scratches_head:

I can even start playback with DoReMix, close the BASSMIDI Driver Configuration utility, and the sound cuts out. While DoReMiX is still playing, start up the BASSMIDI Driver Configuration utility, and then the sound STARTS PLAYING AGAIN... weird.

P.S. If I have the Windows MIDI Mapper set to any of my other installed MIDI devices and drivers (MUNT, Yamaha S-YXG50 softsynth, MS GS softsynth, or either of my SBLive's MIDI ports), DoReMiX works fine as well.
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: SayHelloRosco on 31 January, 2014, 03:15:11 AM
I posted in this thread sometime last year. Now I am having another issue after finally deciding to try BASSMIDI again.

While in GZDoom, ZDoom, etc., I get a crackling noise on the music. Changing settings in either GZDoom or BASSMIDI do nothing.

Another thing is that BASSMIDI is completely silent if I try to use it anywhere else (Windows Media Player, Foobar2000).

Using Windows 8.1
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: mudlord on 31 January, 2014, 04:17:34 AM
weird, i dont work on this anymore, ask kode54.
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: eeyore650 on 21 February, 2014, 03:32:18 PM
This seemed like the appropriate spot to post this, but sorry if it's not; i'm new 'round here.

i'm using the bassmidi driver - or, trying to, anyway - and i'm getting application crashes right at or shortly after launch for every 64-bit program.  32-bit apps - even 32-bit flavors of the 64-bit crashers - all appear to run fine.  i've tried sibelius 7, motu digitial performer 8, i just downloaded and tried scorecloud... all failures.  notably, sibelius croaks when i attempt to alter the audio configuration and enable bassmidi.  DP8 doesn't ever make it a full and upright position.

i've got win7 ultimate x64.  the eventviewer shows the app crashes all have the same error code: 0xc0000374.

surely i must've screwed up installation somehow.  are there any brainbulbs going off or any "a-ha!"s out there?  your help is appreciated.
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: mudlord on 21 February, 2014, 09:19:33 PM
weird, i dont work on this anymore, ask kode54.
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: RichNagel on 27 February, 2014, 05:16:52 PM
Now, for the weird thing...

I discovered that if I have the BASSMIDI Driver Configuration utility idling in the background WHILE running DoReMiX (under Windows XP), it works fine... NO sound dropout at all (?). :scratches_head:

I can even start playback with DoReMix, close the BASSMIDI Driver Configuration utility, and the sound cuts out. While DoReMiX is still playing, start up the BASSMIDI Driver Configuration utility, and then the sound STARTS PLAYING AGAIN... weird.



Found another one that does the exact same thing... SimCity Classic for Windows. Really weird.
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: Scotophor on 17 October, 2015, 01:28:21 AM
Hi, I'm an attempted new BASSMIDI user here, but failed, having install/configuration/uninstall issues. Install seemed to go fine, but then after rebooting and trying to run the Configure app, it immediately crashed (and attempted to report to Microsoft, fat lot of good that does) every time I tried to run it. So I tried to uninstall it, and then the uninstall shortcut in the Start Menu couldn't find the uninstallation file. I navigated to C:\Windows\System32\bassmididrv and the file bassmididrvuninstall.exe wasn't there. I searched my system for it, and it's nowhere to be found. Uh oh...

So then I tried to run the installer again, and what do you know, it's also an uninstaller (or so it thinks...). I clicked "OK" to uninstall, and the window simply disappeared, no progress bar, no "uninstall successful" message, nothing. So I went back to C:\Windows\System32\bassmididrv, and sure enough, it's still there and still has all the files in it that were there before.

So now I can't configure it nor uninstall it. Can you provide instructions for a full manual uninstall, including registry entries to delete/revert, etc.? The system in question is WinXP SP3 Home. Also, do you know why I'm having these problems, and can it be fixed? What about trying an older version? I downloaded the installer for 1.06 but I have NOT yet tried to run it, and don't plan to until I can be sure the current version is properly removed.
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: [JAZ] on 17 October, 2015, 08:21:04 AM
The installer script is here:

https://github.com/kode54/BASSMIDI-Driver/b...bassmididrv.nsi (https://github.com/kode54/BASSMIDI-Driver/blob/master/bassmididrv.nsi)

From there, the uninstaller should be doing the following:

Code: [Select]

Modify this entry to restore the old default driver:
  HK_LOCAL_MACHINE "Software\Microsoft\Windows NT\CurrentVersion\Drivers32"
With the values that were kept as backup in here (MIDI contains the key to modify, and MIDIDRV the driver to replace it with)
  HK_LOCAL_MACHINE "Software\Microsoft\Windows\CurrentVersion\Uninstall\BASSMIDI System Synth\Backup" on MIDI and MIDIDRV


Delete these two registry entries:
  HK_LOCAL_MACHINE "Software\Microsoft\Windows\CurrentVersion\Uninstall\BASSMIDI System Synth"
  HK_LOCAL_MACHINE "Software\BASSMIDI Driver"


Delete the uninstaller entry:

  HK_LOCAL_MACHINE Software\Microsoft\Windows\CurrentVersion\Uninstall\BASSMIDI System Synth

Delete program file icons:

  $SMPROGRAMS\BASSMIDI System Synth

Delete these files on reboot:
 $WINDIR\System32\bassmididrv\bass.dll
 $WINDIR\System32\bassmididrv\bassmidi.dll
 $WINDIR\System32\bassmididrv\bassmididrv.dll
 $WINDIR\System32\bassmididrv\bass_mpc.dll
 $WINDIR\System32\bassmididrv\bassmididrvuninstall.exe
 $WINDIR\System32\bassmididrv\bassmididrvcfg.exe
 $WINDIR\System32\bassmididrv\bassflac.dll
 $WINDIR\System32\bassmididrv\basswv.dll
 $WINDIR\System32\bassmididrv\bassopus.dll
 $WINDIR\System32\bassmididrv\sfpacker.exe


That should be all.


The usual problems that arise is files being in use, but i don't have a clear explanation of what happened in your case.

Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: Scotophor on 19 October, 2015, 02:16:04 AM
Thank you [JAZ], that was easy enough. I don't understand what the problem is/was either. The only file missing from $WINDIR\System32\bassmididrv\ was bassmididrvuninstall.exe.
Title: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: JimBayne on 22 December, 2015, 06:56:36 PM
I am porting an app to Windows 10 that uses the old winmm midi calls. It works fine as is with the Bassmidi driver.

At some point however, I wish to incorporate or migrate to the new Windows Universal midi facilities. So I began testing
and evaluating the Windows Universal - MIDI Sample app as it appears to be a good starting point.

Unfortunately the Windows Universal - MIDI Sample app does not recognize BassMidi as being an available midi out device
on my system, in spite of the fact that it is installed and is visible and works fine when the old winmm midi calls are used.

Is there something I need to do to get Bassmidi to be recognized by the Windows Universal midi facilities?
Title: Re: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: HunterZ on 23 January, 2016, 11:43:16 PM
FYI, multiple people are reporting compatibility issues with Windows 10 on VOGONS: http://www.vogons.org/viewtopic.php?p=470689#p470689
Title: Re: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: kode54 on 24 January, 2016, 01:18:42 AM
I'm not really well equipped to fix Windows 10 issues at this time, since I don't run Windows 10 on my development VPS. It currently runs Windows Server 2012 R2.

I have two Windows 10 machines at home, my previous desktop, and the Boot Camp partition on my iMac, but neither of them has Visual Studio installed.
Title: Re: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: KDDLB on 24 January, 2016, 03:21:49 AM
I run Windows 10 (1511, 64-bit) and haven't had any issues with the BASSMIDI driver.

edit - this applies to the latest update, as well.
Title: Re: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: kode54 on 24 January, 2016, 03:55:04 AM
Try the latest update.
Title: Re: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: JimBayne on 18 February, 2016, 12:47:31 PM
I have the most recent version of the BassMidi driver installed.

Tried compiling the Windows Universal - MIDI Sample app using both the x86 (24 bit) & x64 (64 bit) options. Both had the same problem (they did not see or discover the BassMidi device).

BTW (kode54): If you are able to pursue this at some time, Visual Studio 2015 Community edition is free & includes C++ as well as the .Net languages . The Windows Universal Samples can be downloaded from GitHub.

Re the issues reported at VOGONS: http://www.vogons.org/viewtopic.php?p=470689#p470689:
I have noticed some drop outs with large Sound Fonts periodically. Smaller sound fonts may crackle once or twice a minute for half a second or so (basically not noticeable) but perform pretty well.
 
Title: Re: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: VEG on 19 April, 2016, 02:46:25 AM
I've tried to use VST MIDI Driver. I've installed it, choosed Yamaha S-YXG50 VST, set VST MIDI Synth (Port A) as a default MIDI Synth. After it I had tried to listen MIDI file using the WMP from the Windows 7 x64. It works, but when I'm closing WMP, the vsthost32.exe and wmplayer.exe don't close. The window of the WMP disappears, but the process does not terminate. So, after playing 10 different midi files I have 10 ghost vsthost32.exe and wmplayer.exe processes. When I use default Microsoft MIDI synth, the problem disappears. Anyone else have this problem?

UPD. I'm creating a new patch for the Yamaha S-YXG50 VSTi, the current version is here: http://veg.by/files/midisynth/yamaha_syxg50_vsti.7z
This version is portable and doesn't need to be installed. Just extract syxg50.dll and that is all. If this VSTi does something wrong, I can try to fix it, but I have know what is wrong :)
Title: Re: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: VEG on 19 April, 2016, 06:02:30 AM
Some suggestions about the VST MIDI Driver:
— Add an option to display the icon of the vsthost in the system tray. The driver can just add some command line argument when running vsthost (e.g. --showicon). Double click on this icon have to open vst editor of the current instance. Icon can be default vsthost icon or even the first 16×16 icon from the loaded VSTi.
— Change the description of the vsthost. Now it says that it is a component of the foo_midi :)

Also it displays two ports (Port A and Port B) for the Yamaha S-YXG50 VSTi. Why is there two ports and what is the difference between them? It means that syxg50.dll reports that it have two input ports?
Title: Re: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: kode54 on 19 April, 2016, 07:14:57 PM
I need to fix the VST driver. For now, it needs manual killing of the host.
Title: Re: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: VEG on 23 April, 2016, 07:03:44 AM
It would be very nice to have this bug fixed. I'm planning to include a recommendation to use foo_midi and VST MIDI driver for installing portable version of the S-YXG50.
Title: Re: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: VEG on 25 April, 2016, 01:40:21 PM
I have released my patch for the Yamaha S-YXG50 VSTi. Probably, someone will be interested in it.
http://veg.by/en/projects/syxg50/
It is a perfect synth for the XG MIDI. It seems that soundfonts can't emulate all features of the XG. :)
Title: Re: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: Mark7 on 26 April, 2016, 06:53:23 PM
Thanks! I've uninstalled the original version and now i'm using your portable version. It works perfectly with Foobar and the VST MIDI Driver too. Btw, I never noticed an issue with the latter, so i'm not sure why you do not recommend it on your site. What kinda bug does it have?
Title: Re: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: VEG on 27 April, 2016, 02:33:44 AM
Mark7, I had described the problem above: https://hydrogenaud.io/index.php/topic,87639.msg920717.html#msg920717
Title: Re: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: Mark7 on 29 April, 2016, 07:45:52 AM
Hi Veg, i'm not using windows media player, but vanbasco karaoke player and an old version of cakewalk. I've never noticed hanging vsthost processes, but i'll verify it next time and let you know.
Title: Re: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: kode54 on 30 April, 2016, 04:04:19 AM
Try it again with the latest version?
Title: Re: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: VEG on 02 May, 2016, 06:01:59 AM
Try it again with the latest version?
Thank. It seems that it works fine now. It works fine with the Windows Media Player, but for some reason Media Player Classic uses Microsoft's MIDI synth, and I haven't found any settings according it in the MPC. Is it ok? :)
Title: Re: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: kode54 on 02 May, 2016, 11:15:09 PM
You'll either have to use the 32 bit version of Media Player Classic, or you'll have to wait until I bother to amend the VST driver installer script to bundle the 64 bit version of the user space driver. Currently, while it does support both 32 and 64 bit VST instruments, the driver itself is only 32 bit, and only works in 32 bit applications.
Title: Re: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: VEG on 03 May, 2016, 04:57:00 AM
Oh, I understand. Thanks for the explanation.
Title: Re: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: VEG on 22 September, 2016, 03:41:16 AM
It seems that foo_midi saves settings of used VST, but for some reason these settings aren't using for playback. I mean if you open VST settings again, you will see your previous configuration, but they don't affect playback at all.

How to reproduce:
1. You can use this VSTi as an example: http://veg.by/en/projects/syxg50/
2. Open S-YXG50 VSTi configuration, press setup, change volume, disable effects.
3. Apply settings in VSTi, apply settings in foobar2000.
4. Play any MIDI file. You will hear that playback uses defaults.
5. But even when you restart foobar2000, you can open VSTi settings, and you will see your values, not defaults.

So, settings are saved, but they are not used for some reason. When I'm changing these settings in other host, for example, Savihost, they work as expected.

Also some users complained that VST MIDI Driver has similar problem.

I'm planning to add an ability to change defaults also (using ini-file), so the problem will be fixed, but maybe it is not very hard to fix this problem in foo_midi and VST MIDI Driver.
Title: Re: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: kode54 on 23 September, 2016, 02:48:00 AM
That bug was supposed to be fixed by version 1.252. The latest is version 1.255. Are you sure you're up to date?
Title: Re: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: VEG on 26 September, 2016, 01:38:22 AM
kode54, I'm sorry, my bad. 1.254 from the foobar2000.org fixes the problem with foo_midi.
Title: Re: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: arch21 on 27 December, 2016, 08:02:28 AM
Thank. It seems that it works fine now. It works fine with the Windows Media Player, but for some reason Media Player Classic uses Microsoft's MIDI synth, and I haven't found any settings according it in the MPC. Is it ok? :)
Have you tried this (http://coolsoft.altervista.org/en/forum/thread/427) and/or this (http://coolsoft.altervista.org/en/virtualmidisynth) for MPC?
Title: Re: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: VEG on 25 March, 2017, 03:24:33 AM
I'm just curious which sample rate is used by the VST MIDI Driver? Yamaha S-YXG50 VSTi supports only 44100 and 48000, for example. And it would be nice to know which sample rate is used.
Title: Re: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: lukeman3000 on 27 April, 2017, 09:19:17 PM
Does anyone know how to fix this problem? I seem to have a duplicate set of ports A and B, and the Microsoft GS Wavetable Synth is now missing. Not sure how this happened.

(https://hydrogenaud.io/imgcache.php?id=704e4fa2f670318033384e0d68de00ab" rel="cached" data-warn="External image, click to view at original size" data-url="http://i.imgur.com/UehDvcu.png?1)
Title: Re: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: Chibisteven on 27 April, 2017, 10:16:19 PM
Does anyone know how to fix this problem? I seem to have a duplicate set of ports A and B, and the Microsoft GS Wavetable Synth is now missing. Not sure how this happened.

(https://hydrogenaud.io/imgcache.php?id=704e4fa2f670318033384e0d68de00ab" rel="cached" data-warn="External image, click to view at original size" data-url="http://i.imgur.com/UehDvcu.png?1)

After setting Port A or B as the default MIDI synthesizer and restarting the computer the Microsoft GS Synthesizer tends to disappear for good.

Duplicate set of a and b ports means you reinstalled the application without uninstalling the old one first or you did a feature update for Windows 10 without uninstalling the application first and reinstalled it when it didn't work after the feature update.

In hindsight they're all bugs.
Title: Re: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: lukeman3000 on 27 April, 2017, 10:20:58 PM
Does anyone know how to fix this problem? I seem to have a duplicate set of ports A and B, and the Microsoft GS Wavetable Synth is now missing. Not sure how this happened.

(https://hydrogenaud.io/imgcache.php?id=704e4fa2f670318033384e0d68de00ab" rel="cached" data-warn="External image, click to view at original size" data-url="http://i.imgur.com/UehDvcu.png?1)

After setting Port A or B as the default MIDI device and restarting the computer the Microsoft GS Synthesizer tends to disappear for good.

Duplicate set of a and b ports means you reinstalled the application without uninstalling the old one first or you did a feature update for Windows 10 without uninstalling the application first and reinstalled it when it didn't work after the feature update.

In hindsight they're all bugs.
Thanks for the reply. I can live with not having the Microsoft GS Wavetable Synth, but the duplicate ports thing kind of bugs me. Is there not some registry value somewhere that stores the contents of that drop-down box which could be edited or deleted? Because obviously, something is hanging around.

Furthermore, out of curiosity, is there no way to correct the missing Microsoft GS Wavetable Synth bug, short of reinstalling Windows? Surely whatever was done can be reversed?
Title: Re: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: Chibisteven on 27 April, 2017, 10:28:49 PM
Does anyone know how to fix this problem? I seem to have a duplicate set of ports A and B, and the Microsoft GS Wavetable Synth is now missing. Not sure how this happened.

(https://hydrogenaud.io/imgcache.php?id=704e4fa2f670318033384e0d68de00ab" rel="cached" data-warn="External image, click to view at original size" data-url="http://i.imgur.com/UehDvcu.png?1)

After setting Port A or B as the default MIDI device and restarting the computer the Microsoft GS Synthesizer tends to disappear for good.

Duplicate set of a and b ports means you reinstalled the application without uninstalling the old one first or you did a feature update for Windows 10 without uninstalling the application first and reinstalled it when it didn't work after the feature update.

In hindsight they're all bugs.
Thanks for the reply. I can live with not having the Microsoft GS Wavetable Synth, but the duplicate ports thing kind of bugs me. Is there not some registry value somewhere that stores the contents of that drop-down box which could be edited or deleted? Because obviously, something is hanging around.

Furthermore, out of curiosity, is there no way to correct the missing Microsoft GS Wavetable Synth bug, short of reinstalling Windows? Surely whatever was done can be reversed?

Honestly I do not know.  Uninstalling the application will result in no default MIDI devices at all on the system (no sound or music in all applications that use the default MIDI synthesizer such as games).  As for the duplicate problem I have no idea how that is fixed.  I'm aware of the bugs and how to avoid them.  The Microsoft GS Wavetable Synthesizer is still there as some applications can actually still access it directly, it just can no longer be set as the default MIDI synthesizer.
Title: Re: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: kode54 on 02 June, 2017, 11:07:26 PM
Deceptive Default MIDI Device selection control should be removed from the application, especially in Windows 10 and possibly 8.1 and 8.

Please install and use CoolSoft MIDI Mapper instead. You may also find that you save system memory using the CoolSoft driver as well, as its driver is merely a router to a single instance of a user mode application, which holds the instance of BASSMIDI.
Title: Re: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: VEG on 03 June, 2017, 06:35:17 AM
A critical bug in the VST MIDI Driver. It seems that VST MIDI Drivers always renders sound with 44100 sample rate, and it ignores the sample rate which was chosen for the current wave output. It is easy to reproduce: Open Playback Devices → right click on your playback device → Properties → Advanced → Default format → Set 96000Hz and apply. Try to listen any MIDI. As the result you will hear a very high pitch sound. VST MIDI Driver has to set VSTi to the same sample rate which is used by the system mixer. It will solve the problem. For example, I always use 48000Hz (because my receiver works much better with this sample rate), this is why I had a bit higher pitch.

Also it seems that VST MIDI Driver doesn't save VSTi settings, like it was in the foo_midi a year ago. It is not critical, because most VSTi MIDI synthesizers can be used with default settings. Just for information.

And... Maybe it will be nice to merge VST MIDI Driver and BASS MIDI Driver, like foo_midi supports both soundfonts and VSTi :) Just an idea.
Title: Re: BASSMIDI MIDI synthesiser for Windows XP/Vista/7
Post by: VEG on 16 June, 2017, 05:05:57 AM
A new example of a person with this problem: http://veg.by/en/projects/syxg50/#comment-541
Actually, it is not the first time when people complain about it. Now I just know the reason.