VST MIDI Driver supports Windows XP/Vista/7+, but on the Windows XP it is better to use the official Yamaha S-YXG50 WDM driver, which you can download from the Microsoft Windows Update servers: 4MB version (better quality, consumes more RAM), 2MB version (worse quality, consumes less RAM). This WDM driver can be installed manually using Add Hardware master in the Control Panel. Don't forget to set Yamaha S-YXG50 as the default system MIDI synth in the Sound settings. VSTi version of this synth is not needed when Yamaha S-YXG50 WDM is used.
This sounds promising Veg and thanks. I have 2 problems which are probably easy to fix.1. i tried to add the xp driver in add hardware as suggested above but that sends me down a cul de sac asking if i installed hardware. How do i add the xp driver?2. using sonar 3, i am getting the xg synth rack but only the piano sound. same as Marcus above. I followed the link and got xg midi contro; and un zipped it but still no joy. How can i get access to all the sounds?Cheers
Wdm A404 Driver For Mac
To install this driver, just extract contents of the archive, open context menu of the only *.inf file, and then choose "install". After installation of the driver, you need to select the new MIDI synth as the default one for your system in the sound settings (if it wasn't done automatically).
@nicK:I'm glad it works for you. Maybe you have already noticed but I mention it anyway you can start Midi Player with '/tray' command line option. If you use loopmidi and set loopmidi port as Midi input port in Device settings and start Midi Player e.g. from startup folder at system start you can get a seamless driver like behavior. Clicking the system tray icon opens up the player. This way you can get a much more versatile 'driver' than VST Midi driver since you can see the interfaces of the player and S-YXG50 during playback if you want.
Wait, I just found that there are 2 versions of the vst midi driver, and I did not fully uninstall the older version. After a clean install of the latest version from kode54.net/vstmididrv.exe, I can set the rate up to 96000 and still receiving correct sound tone! (but 192000 will be buggy.)
I'm using windows 10 and I have a problem:The link to VST MIDI driver has a 404 error now, so I downloaded it from _w_syxg50But when I run it, on VirtualMIDISynth, it says the device is only available in x86, which is acceptable, because this happened to me on earlier installations of Windows 10, with the link on your page. But then I would open VSTHost64.exe from the VST MIDI driver folder and restart VirtualMIDISynth, and it would work fine. But now it's still on x86 only and I can't seem to fix it with restarting or anything. I even tried to run VSThost64.exe as administrator and compatibility mode, but nope.Is it because I've downloaded the file from somewhere else other than your link, like the files are different or something?
Setting up a new computer with CbB. The PC has Realtek built-in sound, and that worked fine for a couple of days when I was just playing stuff back. But When I plugged in the audio interface to record, Cakewalk stopped playing sound. In Preferences Driver Settings, my only choice is "Realtek ASIO HD Audio. The Behringer does not show up at all, and no other ASIO, WDM or WASAPI drivers show up either. In Device Manager I have disabled the Nvidiia audio drivers. In the Windows sound control panel, the Behringer is listed as the default input and output. I have uninstalled the driver, rebooted and reinstalled the latest one. I have uninstalled Cakewalk and reinstalled.
Did you install the ASIO driver from the Behringer's support page under downloads? Sometimes it helps if you read the instructions or watch the video supplied with the products. Even the Sweetwater page has a ton of information about this interface.
Yes that's pretty important. Why on earth would they update to a broken driver? And how would any body know that as like @Larry Jones I can't find that info. And is this for your device only or for all in the series? But it might explain the OP's issue if they are using a bad version of the driver. Behringers drivers have always been a bit of a quandary. Like they even are recommending ASIo4all which is totally not needed any more because Windows uses WASAPI. Are they that out of touch with Windows?
Same here. Would note that after one of the recent recent minor Win10 upgrades, when I opened Cakewalk it had ASIO4ALL drivers showing in Options. I switched it back to the UMC404 ASIO drivers and all continues to work fine. Just pointing out that there may have been some "glitch" in recent minor upgrades from Microsoft that impacted Cakewalk, but for me not worth the time to figure it out and easy to remedy.
Thank you. Yes, I saw that readme. It just says "If you're using already one of the named interfaces without any trouble, there is no need to install this driver." Since the OP was setting up a new computer, I assume he did not have any driver installed, so the logical one to use would be the newest one, right?
Why on earth would they update to a broken driver? And how would any body know that as like @Larry Jones I can't find that info. And is this for your device only or for all in the series? But it might explain the OP's issue if they are using a bad version of the driver. Behringers drivers have always been a bit of a quandary...
Up to some point Behringer had an excellent high quality ASIO driver developed by Ploytec for most of their interfaces. Later on they replaced it quietly with something undefined, maybe their own driver, idk. So perhaps the license for the previous came to end at some point or maybe they parted ways for whatever reason. Anyway that's all I know, hope it can help understanding some of their decisions.
Uninstall and/or disable every audio device on your computer (including the old Behringer drivers). So for me that means I turn off the Realtek in the BIOS and I disable the nVidia HDMI audio device (and always use the custom option when upgrading so I can deselect the audio driver). After uninstalling all of this (and especially any ASIO4ALL instalations) be sure to clean reboot (without the audio interface connected). Then install the Behringer driver. Reconnect the device.
I tried all the available drivers from the Behringer website and none of them worked. When I was uninstalling I noticed that in the list of programs in Windows Control Panel, the Behringer driver was taking up no drive space at all - the size was listed as zero. I downloaded the latest driver one last time and as a last resort I excluded the setup file from my antivirus (McAfee). I've never had to do this before and I can't say if that's what did the trick but this time the driver installed and worked. One note: I have to use WASAPI. When I try to switch to ASIO CbB freezes and I have to close it to get back into Preferences.
Sad update: Not working again. When I went back to this today and plugged my bass into the Behringer interface, Cakewalk crashed. This is with the latest driver from Behringer's website. The previous driver didn't work for me, and the newest driver only allowed WASAPI, which I was happy to use (as long as it worked). Now I'm back to ground zero. Only thing I can think is that the old bad drivers are not getting completely removed in the "uninstall" process, but I don't knwo what I can do to fix that -- or even if that's the real problem. Thanks to all who tried to help me with this. (By the way, Behringer's online support is next to useless.) It's a great box, as long as you don't need any assistance from the manufacturer ?)
It might be necessary to completely remove all drivers and adapters in the Device Manager first then reboot with the correct version of files ready to install on CD or diskette. Of course, always back up your registry files and data before making any significant changes such as deleting devices arbitrarily.
I had a Via AC97 at the time on an AK72 motherboard and did not have problem with w98 drivers. I think I used those from the mobo's site then maybe even updated later to the Via's site. You can check these here:
I have the 4.0 software (downloaded from some website, I don't have the CD), it seems to be from 1999 it's for win9x but it works (most of it) on windows XP, as far as I know there is no native XP driver for it.
I can't remember specifically but 4.0 when installing on XP SP3 will give me a warning that it was not made for "windows 2000" or something like it, but the driver works and the control panel works mostly without problems, the page for setting macros would crash, but if you disable DEP on your windows XP it actually works
for Vista+ these drivers didn't work but Vista came with drivers for it, it just lacks the control panel, even on windows 10 x64 I can use the Sidewinder ffb wheel, force feedback and all buttons work, the problem is the lack of control panel and the wheel having the "auto center spring" setting as default (which ruins it for newer FFB racing games), some games will disable it automatically as expected (like Live For Speed) but most don't , for "Project Cars" when I tested it deleting a registry value worked to disable it, but it's not always the case. 2ff7e9595c
Comments