I'll take it one step farther. All keyboard problems are either instrument definition issues, connection issues, or user issues like not knowing the instrument or not hooking things up or not reading the instrument's MIDI Implementation Chart and understanding what it means. The third category also includes expecting the keyboard to do something it can't do. MIDI can be complex, but it isn't convoluted -- it's a very straightforward protocol, and if you have a keyboard that responds to MIDI, a MIDI interface QWS can recognize, (which means a MIDI interface Windows can recognize) and good functional MIDI cables hooked up the right way it'll work. But beyond that you've got to know what the instrument can and can't do, and that's outlined in the instrument's MIDI Implementation Chart. Though they're sometimes not available for some software synths, and this is a violation of the MIDI specification because they are required even more than 5 pin DIN cables or a virtual equivalent and 16 channels, It's extremely rare not to have one in the back of a hardware instrument's manual. And everything you need to know to make the instrument respond (if it can) is there on the page. It's one of the two most important things you need to make QWS do what you want it to. (The other is either an instrument definition file or a patch list you can use to create the instrument definition file, or even a Cakewalk instrument definition file that you can convert using Gavin's wonderful program)
-----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Richard Wells Sent: Monday, May 06, 2019 7:12 PM To: QWS list <[email protected]> Subject: Re: QWS List QWS Development? Lots of keyboard issues turn out to be instrument definitions. With Nicole's help, my wife was able to use Excel to create one for my particular keyboard: the Casio Privia 350. It works perfectly. On 5/6/2019 2:49 PM, Nicole Massey wrote: > Refresh my memory -- was it a QWS problem or a keyboard problem? We can only > do what we have information to try to resolve, and many keyboards bring their > own issues to the situation and that isn't QWS's fault. > > -----Original Message----- > From: [email protected] [mailto:[email protected]] On Behalf > Of Marco Oros > Sent: Monday, May 06, 2019 2:36 PM > To: QWS list <[email protected]> > Subject: Re: QWS List QWS Development? > > I don't think, that QWS is in active development. > > For example My keyboard not very well work with QWS. I have tried to solve > this problem, but people here, sorry for this expression, burried their heads > in the sand. > > 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] To unsubscribe or change list options, see http://lists.andrelouis.com for archived list posts, see http://www.mail-archive.com/[email protected]
