VOGONS


First post, by Trelokk

User metadata
Rank Newbie
Rank
Newbie

I am using mudlord's VST Midi Driver (latest version from Jan 2018) with the Yamaha S-YXG50 plugin on a Win 10 x64 system. Until recently, the driver conveniently offered a midi mapper in a separate tab ("Advanced") which allowed you to change the midi output device. This tab now completely disappeared in Win 10 (probably after an OS update, possibly the Fall Creators Update) while it's still shown under Win 7.

Right now, I need to use the Coolsoft Midimapper to be able to change the output device. Is mudlord aware of this and can he do anything to restore all VST driver features for Win 10 users? Thanks in advance!

Reply 1 of 11, by Falcosoft

User metadata
Rank Oldbie
Rank
Oldbie

I don't think it's easy to fix it since in Win8/10 the default MS Midi mapper completely disappeared from the system. So while in Win7 changing the default midi out port only required setting a registry key (HKCU\Software\Microsoft\Windows\CurrentVersion\Multimedia\MIDIMap), in Win8/10 you need to implement a total replacement for the missing midi mapper. It's not a coincidence that Coolsoft had to write a separate tool (Coolsoft Midi Mapper) for Win8/10, while in Win7 you could change the default midi out from Coolsoft VirtualMidiSynth (without installing Coolsoft Midi Mapper) similarly to VST Midi driver.
So it's possible that you have seen the tab before the update in Win10, but it's unlikely it worked as intended even before the update. Just like an older VirtualMidiSynth version may show a 'pesudo-working' Midi Mapper->Default Midi Out device section even without Coolsoft Midi Mapper installed (since it can predate the recognition of missing default midi mapper on Win8/10) but actually it cannot work for the same reason PLWMidiMap cannot work on Win8/10.
Win7:
file.php?id=44963&mode=view
Win8/10:
file.php?id=44967&mode=view

Website, Facebook, Youtube
Falcosoft Midi Player + Munt VSTi + BassMidi VSTi topic

Reply 2 of 11, by Trelokk

User metadata
Rank Newbie
Rank
Newbie

I actually wouldn't care that much about the option to change system-wide midi output if all game ports I am using were offering to change it via menu. GZDoom does, EDuke32 unfortunately does not (yet) (still).

MS is going down the wrong path with removing the midi mapper completely. The VST Midi Driver was convenient to use. You just needed the driver and a plugin. Now you need more. I hate being punished for using latest OS, and I also feel sorry for you guys who write these awesome drivers and software for us retro enthusiasts. It's frustrating to keep fixing what is getting broken intentionally.

I just hope that the Coolsoft solution won't stop working after the imminent April update for Win 10. I start becoming afraid of these major OS overhauls which tend to rather cut out good features instead of adding useful ones...

Reply 3 of 11, by flame21

User metadata
Rank Newbie
Rank
Newbie
Trelokk wrote:

I am using mudlord's VST Midi Driver (latest version from Jan 2018) with the Yamaha S-YXG50 plugin on a Win 10 x64 system. Until recently, the driver conveniently offered a midi mapper in a separate tab ("Advanced") which allowed you to change the midi output device. This tab now completely disappeared in Win 10 (probably after an OS update, possibly the Fall Creators Update) while it's still shown under Win 7.

Right now, I need to use the Coolsoft Midimapper to be able to change the output device. Is mudlord aware of this and can he do anything to restore all VST driver features for Win 10 users? Thanks in advance!

Hi, it seems you are the only one I can find on the internet, that having Win10 x64 and VST Midi Driver with YXG50 plugin working!
Myself have tried so many times, on 2 different PC, one with win 10 ver 2017.09 creator update, one with ver 2018.4 creator update, both are having the same problem:
when I select the VST/Yamaha YXG Midi device in Coolsoft Midimapper, both in Dosbox and Win Media Player the midi music sound tone became a lot higher than they should be, all midi musics sound funny.

Coolsoft MidiSynth is working correctly.in both Doxbox and Media Player.

However when I use foobar 2000 with YXG50 VSTi plugin (so VSTi is going through foorbar's plugin, not via VST Midi Driver), it plays all midi files correctly. So the YXG50 VSTi files I downloaded must be ok.

I thought that maybe VST Midi driver does not work with win 10 x64, but it seems you can get it run correctly!

Last edited by flame21 on 2018-09-02, 15:12. Edited 1 time in total.

Reply 4 of 11, by flame21

User metadata
Rank Newbie
Rank
Newbie
Trelokk wrote:

I am using mudlord's VST Midi Driver (latest version from Jan 2018) with the Yamaha S-YXG50 plugin on a Win 10 x64 system. Until recently, the driver conveniently offered a midi mapper in a separate tab ("Advanced") which allowed you to change the midi output device. This tab now completely disappeared in Win 10 (probably after an OS update, possibly the Fall Creators Update) while it's still shown under Win 7.

Right now, I need to use the Coolsoft Midimapper to be able to change the output device. Is mudlord aware of this and can he do anything to restore all VST driver features for Win 10 users? Thanks in advance!

may I ask what windows 10 version are you using? maybe you are using an earlier version than 2007.09 creator update?

Is it possible that you can send me the vst midi driver and YXG50 VSTI files via email? My email flamecn@hotmail.com, thank you very much!

Reply 6 of 11, by flame21

User metadata
Rank Newbie
Rank
Newbie

Hi kode54, is there a newer version?
All I can find, is the "VST MIDI Driver with S-YXG50" 3336k from google:
https://sites.google.com/site/f90d83a8/home/v … ididrv_w_syxg50

this version I have to set sound device's sample rate to 44100 Hz, any rates higher than this will cause higher tone.

...

kode54 wrote:

You need a newer VSTi driver, I have updated it to detect and use the same sample rate as the system, rather than being hard coded to one sample rate.

I just found that there are 2 versions of this vst midi driver - and I did not fully uninstall the older version.

So, after a clean uninstall and install the latest version from kode54.net/vstmididrv.exe, I can set the rate up to 96000 and still receiving correct sound tone! (192000 will be buggy, but 96000 is more than enough.)

kode54 you are the best! Thank you, thank you, thank you!

Reply 8 of 11, by evgs

User metadata
Rank Newbie
Rank
Newbie
https://kode54.net/vstmididrv.exe 

Link is dead...

I am confused.
1.0.0.6 is bigger and more fresh than 1.0.0.8
Can you share lastest version of vstmididrv.exe, please?

Attachments

  • 1008.png
    Filename
    1008.png
    File size
    23.12 KiB
    Views
    1206 views
    File license
    Fair use/fair dealing exception
  • 1006.png
    Filename
    1006.png
    File size
    23.23 KiB
    Views
    1206 views
    File license
    Fair use/fair dealing exception

Reply 9 of 11, by kode54

User metadata
Rank Member
Rank
Member

I still have the source to the host bridge, since it's part of foo_midi, but I appear to have lost the source code to the driver itself.

You're probably better off using a loopback driver with a dedicated VST host application, as it will allow sharing a single instance of the VST plugin with multiple applications.

Reply 10 of 11, by Trelokk

User metadata
Rank Newbie
Rank
Newbie

I have made a backup of the driver dated Nov 8, 2018 which you can get here.
Optionally you can also update the bass.dll library from 2.4.13.8 to 2.4.15.0 by extracting this zipfile to your C:\ directory (provided you are using a 64-bit system, otherwise dlls will be copied into the wrong subdirs).

Reply 11 of 11, by Trelokk

User metadata
Rank Newbie
Rank
Newbie

@kode54:
Someone compiled an (outdated) VSTi MIDI Driver build with the S-YXG50 plugin and also provided source code files. May this be what you are missing to continue developing the driver? The zipfile contains a folder called "vstdriver-master". Files are from mid March 2017.