

It was certainly no threat to P5 or Sonar in terms of track count, softsynth support, robustness, etc. Rereading your note - what shape was QSketcher in when we stopped? We had the basic environment running, some music and collaboration tools. I don't know if QSketcher, as such, will ever get revived, but a lot of the ideas for improving authoring environments have made it into various other projects where I work (Architects Workbench, a tool for 'sketching' overall project architecture from notes made during informal discussions my own work on extending Eclipse in various ways).

#USED MIDI PATCHBAY SOFTWARE#
(And yes, building software can be highly creative, and not necessarily all that different from building music composition.) The common thread is 'authoring systems' - using computers to extend peoples' creative reach. By some strange coincidence, that's also when I switched from doing C++/Windows/music software to doing Java/Linux/software development tooling. QSketcher development stopped when the Computer Music Center (my research group) shut down in mid-2001. If you hear problems (glitchy timing, playback not sounding like the original performance.) - you should look into alternatives. īottom line: if it works well enough for you, it's fine. I haven't tested current-gen devices, but my comments above are based on work described here. Strangely enough, SoundBlaster MIDI ports gave excellent performance as of 2000 (far better than USB MIDI products available at that time). (Firewire MIDI is also a good choice when 'locked in the pocket' timing accuracy is important.) In my past life as a computer music researcher, I did a lot of testing of MIDI timing performance (and worked on the Firewire MIDI spec, among other things). I'm now using the MIDI ports on my 1820M for my main keyboard controller - generally, PCI-based MIDI ports give better MIDI timing performance than USB MIDI, although the gap isn't as large as it used to be.
#USED MIDI PATCHBAY DRIVERS#
The MOTU USB products for Windows could also be good - MOTU has a proprietary time-stamping protocol that potentially gives a lot better timing accuracy (depends on how it's hooked into Windows XP drivers MOTU hasn't said what they do I haven't tested it - so no hard data here). AFAIK, the M-Audio (MIDIMan) products are still basically first-gen devices (and will probably not perform as well as the UM devices) - but I have not tested that, so could be wrong.
#USED MIDI PATCHBAY SERIES#
The 'UM' series are (at least) 2nd-generation USB MIDI products, with a number of performance improvements over the first generation. something like $160 ?) - I didn't need more than 5 MIDI ports, so the 550 was fine. The UM-880 is its bigger brother ($300 street vs. I use an Edirol UM-550 5x5 patchbay/interface.
