So I've been working with TouchOSC for some time now, and only recently started using OSCulator as a bridge (when program changes didn't play nice with TouchOSC alone and I wanted better bidirectional support).
I've converted my previously midi-only touchOSC template to OSC-only, and have successfully mapped the midi CC data. I've even read through the tutorials on setting up OSC in Logic via control surface automation learning (not how I'm doing things). I'm really working purely in MIDI CC and program changes. I've built a series of faders to control stuff like modwheel, expression, filters, etc.
What I'd really like is to have them update visually in touchOSC in sync with what's been recorded in Logic. The only bidirectional tutorial is a bit overboard for what I need. I've already figured out a rudimentary way to simply pass the MIDI CC that's been recorded to a track back to OSCulator by simply creating an instrument set to the OSCulator port and cabling the output of an environment object to it. I've configured the return midi data in OSCulator, and my faders move in sync. It's wonderful!
Logic is great at taking whatever MIDI data is coming into the sequencer and automatically mapping it to the currently selected arrange track - no matter what channel it's being transmitted on - making it dead simple for my touchOSC template faders to control *only* the track I have selected. The problem is the return MIDI - if I cable the output of a specific object to OSCulator in the logic environment, I only get midi feedback for that particular object - not to mention the problem that if it's a multi-channel midi instrument, I get all 16 channels, which includes CC data for 16 independent tracks. So if they're all reading CC data changes, they're all getting funneled to OSCulator, and all trying to move my touchOSC faders at the same time!
So I don't think this is actually a problem that can be solved within OSCulator. Really I guess I'm asking if anyone knows how to limit/filter an output stream of MIDI data to *only the track currently selected/active in the arrange window* (just like all incoming midi data is only routed to that same track). This would allow my single bank of faders to display only the data from that particular track - mimicking the behavior of typical control surfaces that both input and display only the data for a selected track. I could switch tracks on the fly, and my visual display in touchOSC would reflect the current track, as well as allow input for that track.