It's fairly simple. First you need a virtual MIDI cable application. I've not set this up on a system later than XP so far, so I used the Sonic Foundry Virtual MIDI Router to do the job. There are several others that work on later machines, like Maple Leaf, LoopMIDI, Loop30, (which you have to pay for) and probably a lot of others. 1. Install the virtual MIDI cable. 2. Activate the Proteus VX stand alone. (Not the VST) Find the stock instrument definition file and load it. Go to the settings or options( not sure which one, as it's been a very long while since I did this) and set your MIDI input device to the virtual cable. Also set your outputs to whatever you're using. 3. Locate the instrument definition file for the Proteus VX and put it in your QWS directory on your hard drive. You have to do this before you start up QWS, as it surveys all files that start out with INST in that directory on startup and doesn't update the list. I think I've sent that file on to James, but if not let me know and I'll send it. Note: Proteus VX uses high definition bank data. This means banks aren't multiplied by 128, you increment them by one. I haven't dealt with adding more instruments to the Proteus VX yet, but I'm going to try it at some point, as a friend of mine converted some of my sounds into a Proteus VX bank. But back on topic, trust me, you don't want to create the definition file unless you've got some strong chops in creating them. I've done dozens of them, and I've encountered this structure only twice. (The other one was the Kurzweil K2600, and it'll use any of the three structures -- low definition, high definition, and old Kurzweil/Oberheim) 4. Fire up QWS. The virtual MIDI cable or cables should show up in your port list. Go to the menu with Metronome, Instruments, etc. and go to the port list. Find the virtual MIDI cable you used as a MIDI input to the Proteus VX and change the port name to Proteus VX to make things easier. Go to the Instrument list in that same directory and select the Proteus VX port, then assign the definition file to the Proteus VX entry. You should be good to go at that point. Be aware that I used grouping labels on the definition file, because there are so many things that needed them, and because the first group of patches are a hodge podge of different sounds in no clear logical order. Also remember that I'm doing this from memory when I last set this up at least five years ago. If I slipped a gear somewhere I apologize.
-----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Richard Wells Sent: Monday, April 22, 2019 6:28 PM To: QWS list <[email protected]> Subject: Re: QWS List Looking for better sounds Nicole: Since you brought up Proteus VX, would you consider providing steps to get it working with QWS? I have it here, but cannot figure out where to start. I have been using Cool Soft with sound fonts, but I would love to get this going. Thank you so much for all of the answers you give us here. You are a valuable resource. On 4/22/2019 11:45 AM, Nicole Massey wrote: > Yes. There are several options of varying levels of complexity. > Your simplest option is to load a sound driver like BassMIDI or > Coolsoft and fill it with cool sounds you download from the web. Your > level of involvement can vary from loading a GS sound font bank and > leaving it alone to downloading every sound you can get your hands on > and building a multi-bank sound font layout in Viena (note that's not > a typo) to create a map of sounds. Note that this will also require > building an instrument definition file too, but Viena outputs patch > lists so it's not as difficult as it could be. This is the only option > that will let you share your .mid files as long as you keep to GS > sounds, as the GS sound list is common to all modern machines. (As > you've already found out with the laggy Microsoft > wavetable) > Your next level of engagement involves downloading a good freeware > synth, preferably a sample playback/"ROMpler" program and setting up a > virtual MIDI cable to connect things together. It'll show up in QWS as > a MIDI port, and it's helpful to rename that port in QWS so it tells > you where that particular port is going. Again, unless you're dealing > with a well-known synth, like Proteus VX, you'll need to create a definition > file. > Another option is to use a virtual MIDI cable to connect to VSTHost or > another VST manager. This is flexible, as it allows you to set > individual VST Sound sources on each channel. It takes more work, and > again it'll require you to create a definition file if you want the > program names to show up in your list. > > -----Original Message----- > From: [email protected] [mailto:[email protected]] On Behalf > Of Sam Doman > Sent: Sunday, April 21, 2019 5:36 PM > To: QWS list <[email protected]> > Subject: QWS List Looking for better sounds > > Hi all, so I've been using QWS for a while now and I have a question. > Are there any ways I can get better midi sounds besides the crappy > Microsoft GS Wavetable synth? My keyboard does not have any built-in sounds. > > Sent from my iPhoneTo unsubscribe or change list options, see > http://lists.andrelouis.com > > for archived list posts, see > http://www.mail-archive.com/[email protected] > > To unsubscribe or change list options, see http://lists.andrelouis.com > > for archived list posts, see > http://www.mail-archive.com/[email protected] To unsubscribe or change list options, see http://lists.andrelouis.com for archived list posts, see http://www.mail-archive.com/[email protected] To unsubscribe or change list options, see http://lists.andrelouis.com for archived list posts, see http://www.mail-archive.com/[email protected]
