Another way of accomplishing the same thing; mine was external, yours is internal, by storing the stuff in tracks and pasting them in where required.
On Sun, 22 Feb 2015 20:11:18 -0600, you wrote: >1. There's value in doing some grunt work in building these kinds of >messages beforehand when you're not in a creative mood. What do I mean? Say >you have a set of NRPN values from 0 to 63 available as NRPN values. Go into >QWS, build a file with64 tracks, and don't worry about setting channel, >program, or any of that stuff. Build the file with one event on beat 1 of each >measure, so you have two measures each of 101 and 100 controller numbers with >the right values to call up the parameters. Name these tracks using the >parameter. Save it. Now when you need to send NRPN values you open up this >file, copy the information, and then go to measure 3 and input the value for >controllers 6 and 38, as needed, to get the value you're seeking, then use the >time expand feature in the tools menu to compress this down nice and tight. >You're dealing only with the particular value at hand, and if you need to >tweak the value you can use a fader (or the mod wheel) set to CC6 to play with >the values >to find one you like. You'll want to use control+Shift+V to insert paste these >values, of course. >2. With the number of synths out there, even just the virtual ones, this >would become cumbersome and involve insane amounts of programming. I doubt >James has the time for this, especially for a free program. Just doing it for >Roland or Yamaha gear would take forever. >3. The controller editor in QWS keeps mystifying me, but that may be >because I learned on a very different controller editor, the one in Sequencer >Plus. It was a lot faster, simpler to use, and gave me more information. The >other issue with it is that it's called the controller editor in some places >in the manual and the control editor in others, so sometimes I have problems >refreshing my memory on just what I need to press to get certain results. But >it's still worth it to me to work around it, because of how well QWS does >other things. > >> -----Original Message----- >> From: [email protected] [mailto:[email protected]] On Behalf Of >> arfy >> Sent: Sunday, February 22, 2015 5:51 PM >> To: QWS list >> Subject: QWS List Thoughts and qws suggestions for more advanced MIDI >> users >> >> Hi, all. I thought I'd write down here my thoughts and ideas for those >> of us who like to do some pretty advanced midi tricks, such as dealing >> with sets of controllers, particularly NRPN messages, working with >> sysex messages, and a possible alternative way of viewing and working >> with midi events. This will be semi-long, just as a heads up. >> >> 1. sets of controllers. >> >> While I love working with the qws event list editor, it can get a >> little tedious when inputting sets of often, 3, sometimes even 4 >> controllers to use NRPN (non-registered parameter number) messages. For >> example, to set the pitch of a snare drum, three controllers need to be >> sent, in a particular order, such that data entry controller number 6 >> is always sent last. It would be nice if all the controllers could just >> be inserted, all at the same time, and most midi players/sequencers >> seem to handle this fine. qws, however, resorts the controllers so that >> all the data entry messages come first, then all controller 98 >> messages, and finally controller 99. To work around this, I place the >> data entry controller a tick after the rest, which works, but can get >> annoying when dealing with a hole string of these. See number 3, below >> for a possible suggestion here. >> >> 2. working with sysex. >> >> While qws has full support for sysex messages, working with them can be >> quite brain taxing! You have to not only remember the strings to >> insert, but some manufacturers (ahem, roland?) require individual >> parameter changes have a checksum calculated for each of them! >> Even something as simple as a checksum calculator would be nice here, >> but my idea, and this may be going beyond the scope of James' vision >> for qws, would be to have some sort of patch editing/librarian as part >> of the program. You could have mini scripts, or settings in ini files >> that set up the parameter names, and the messages for each one. I offer >> this suggestion because, unfortunately, most editors/librarians I've >> seen are inaccessible. >> >> 3. An alternative view of events. >> >> Again, this may be a bit trickier, or outside the scope of James' idea >> for qws, but it would be nice to have a way to view events of a track, >> in some form of text notation. Something where a-g represent notes, a# >> for sharp, bb, bf, or something similar for flat. Perhaps it could look >> similar to the gwbasic/basic play statement, known as mml (music macro >> language) in japan. I have sources available for one such system, >> mml2mid, however the comments are all in Japanese. However, this system >> can notate just about any midi event, including control changes, sysex, >> meta events, and even some text events like markers and queue points, >> that qws doesn't support. >> This might make it much easier to do things like, connecting a series >> of notes using pitchbend messages, which can be done now, but requires >> some event list editor gymnastics. It would also just make another way >> of viewing events in the midi possible. >> >> Again, if you made it this far, take a prize! or something. Thoughts on >> these ideas welcome! >> >> Arthur >> >> 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]
