Setting up Logic Environment for EWI-EVI / beginner

Question

Greetings - I have a Yamaha EWI-EVI (wind controller, usb midi only - no sound module) that I would like to use as input to my Logic Studio.
The data stream it generates includes standard note on and off messages, to which Logic responds appropriately. The "volume" control is sent as two-byte (cc?) messages, with the second byte encoding the desired volume, 1-127. (Looks like they actually come in pairs of messages - the first message uses '2' as the first byte, and 2nd message has null as the first byte. Both have volume info in the second data byte) If I use a "Transform Op2" fader on the C-press input, I can extract the air pressure data and the fader moves accordingly, but I can't figure out how to mix the fader's 'out' back into the rest of the data stream so that these data control the volume of the sound that the mapped software instrument generates. The pitch and pitchbend (biting pressure) information are handled appropriately without any transformations.
Bonus questions: How can I limit this pitch processing only to the EWI, and not other MIDI instruments? (It's just me, so it's sorta moot, but I'm curious.) Also, how do I map the output of the EWI to a specific software instrument in the Arrange window, rather than whichever one happens to be highlighted?
Quick Product Review: For those interested in a cheap wind controller, I like this device. I played briefly decades ago, and have picked it up pretty quickly again. The Aria software that comes with has samples of many instruments that are very good, but I wouldn't say outstanding. On the whole, it is a very good value to add a tool to your MIDI arsenal, especially if you have experience with any of several wind instruments (e.g., sax, flute, bassoon) - there's no exact match for clarinet mapping. On the downside, modifying the hardware/firmware settings can be extremely unreliable and fussy, as of v.1.0.5 or 6, depending on where you look. Have wasted hours trying to get the device fully responsive again. Once, it's working, it plays well (if you can live without tactile feedback from the keys). Best just to control it with your sequencer software ... which is why I write.
Thanks for the help. Copies of replies directly to logicuser at discountethics (period) com appreciated.

Answer 1

The "volume" control is sent as two-byte (cc?) messages, with the second byte encoding the desired volume, 1-127. (Looks like they actually come in pairs of messages - the first message uses '2' as the first byte, and 2nd message has null as the first byte.
Can you give example message strings? If' it's just standard CC volume messages, it should have a CC status (I forget what that is offhand), a MIDI channel (0-15), a controller number (6), and a data value (0-127)
but I can't figure out how to mix the fader's 'out' back into the rest of the data stream so that these data control the volume of the sound that the mapped software instrument generates.
Cable all the outputs back to a new instrument object - untick it's icon, make sure it's not channeliseing or changing anything - this dummy object will just merge all the streams back into one before sending it elsewhere. Or am I misunderstanding you?
How can I limit this pitch processing only to the EWI, and not other MIDI instruments?
On the Click & Ports environment layer, instead of taking a feed from the "SUM" output of the physical input object (ie, the sum of all MIDI ports arriving to Logic), just take a feed from the MIDI port the EWI is on. You can use transformers to further choose only a particular channel for procesing on that port, if necessary.
Cabling from one of the other ports removes that stream from the SUM output.
Also, how do I map the output of the EWI to a specific software instrument in the Arrange window, rather than whichever one happens to be highlighted?
This is how Logic is supposed to work - you can choose which instrument to play be selecting it's track. If you always want to play one instrument, in the environment you can cable it there directly - however, as this MIDI stream is bypassing the sequencer, you won't be able to record it.
Quick Product Review: For those interested in a cheap wind controller, I like this device. I played briefly decades ago, and have picked it up pretty quickly again.
Hehe - me too. I played flute for a few years back when I was about 12, and can still roughly play and remember the fingerings (which are fairly adaptable to many wind instruments).