Hooked it back up and for some reason Logic isn't recognising any keypresses/keybord shortcuts from Osculator (all the buttons on page 2 are mapped to simple keyboard shortcuts, no MIDI). However I'm having a bit of an issue with the second page - it was previously working fine and then I took a little bit of a break. It does require a bit of a build in the Logic MIDI Environment but I'm happy to share with anyone who's interested. My finest achievement to date is probably the "velocity fix" slider and button on the first page - when you click that button, all MIDI input fixes to the velocity value that you dial in with the slider, which also updates the value of the label from 0-127 so you can dial in precise velocities super useful for percussion multis to get just the right sample triggered. Here's where I'm at so far, running TouchOSC on an old iPad (1st gen Air!) via the amazing (but woefully under-supported) OSCulator: I've been recently getting into TouchOSC and OSCulator for some hands-on Logic control.
![update touchosc from osculator update touchosc from osculator](https://i3.apkfun.com/TouchOSC+n7gttfz_ox.png)
It may not be accurate, but that's what it looked like. So, due to the midi road rage developing, I decided to make it a one-way street and put the officer on desk duty. Probably the best analogy I could give based on my observation is that Bridge is acting like a traffic cop on a one lane road where the 2-way traffic has to stop and go periodically as the officer lets it. I set the faders and knobs as "pick-up" in Cubase so I do not get the jump in movement in Cubase when I touch it. The issue is that Bridge is 2-way communication BUT can only communicate one way at a time. But, as I said, it was too problematic to be functional. I had to route information through a dummy midi channel and out a virtual midi port and.quite frankly it was such a convoluted mess I cannot even remember how I did it. I could get button state information back from Cubase to the tablet to show button status but then couldn't use faders or knobs with any precision at all.īut, just using TouchOSC Bridge as the input and output device on the Generic Midi controller in Cubase did not give 2-way communication. With fader or knob control the feedback from Cubase would fight with the input from the tablet. I use Cubase but always found 2-way communication problematic so just left it as an input only midi controller. It will be interesting to see if anyone else has input. I feel like I'm missing something super obvious! Those of you who have two way communication (especially if you have Reaper)-any insight? Did your's just work right away? Incidentally I also set it up as an output, but sending info to the tablet doesn't seem to be the problem (and was working even before I set touchosc up as an output.)
![update touchosc from osculator update touchosc from osculator](https://eenews.cdnartwhere.eu/sites/default/files/styles/facebook/public/images/01-picture-libraryde/ChristophHammerschmidt/2017/11-november/crd393a_voltcraft_dso-6102_wifi_hres.jpg)
I do have touchosc bridge running and touchosc set up in Reaper as an input. Still the same result-Reaper sends to the tablet, but Reaper is not getting info from the tablet. I have opened up ports, at one point I totally disabled Firewall, Antivirus, and Malware programs so my computer was totally open. Or, perhaps the info is being transferred and the computer is not receiving it or it is blocking it. I cannot get any response from the "Listen" button in Reaper, so it seems that no information is being transferred from the Tablet. But nothing that I do on the Fire is transferred to the computer and Reaper. Got TouchOSC and Reaper happily sends messages to the Fire (just using the Logicpad setting now).
#Update touchosc from osculator windows#
I've got an Amazon Fire, Windows 10, and Reaper. I'm not sure whether this question is better suited as a new thread or whether it's appropriate to put here.