The midi jacks are Type A TRS jacks, but they are 2.5mm jacks. IRig Pro I/O, this unit does both audio and midi. (I use an iPad Pro but it was the first model with USB C instead of lightning so I use a USB C to USB C cable). It has a USB C input, but you could use a USB A to USB C cable to connect the adapter to your iPad and two 3.5mm TRS cablers to the midi breakout connected to the Disting. I guess I need the larger square lightning to USB adapter (I have one) and then a USB to dual five pin adapter, and then two 5 pin to TRS?Ī couple of options that I use if you don't want to deal with 5 pin DIN to TRS adapters:Ĭantrip USB C to TRS A Midi Adapter. Quick question for the group, for my iPhone 12 or iPad Pro what is the best adapter choice I can consider? I have the Midi XO TRS module connected to the EX. I have gone and bought a fourth EX module now, yes, I have bought and sold it three times previously. I just stumbled across the fact that you were doing this amazing work for touch OSC and the Disting EX. The only thing I can say is that with the next 1.18 version that I'm working on, received/transmitted messages can be processed in midi beyond CC64, so there shouldn't be conflicts with sysex (in theory!) I don't get it, you're getting messages like you have "soft thru" turned on, but I can't simulate your problem.Īt this point I would like to understand if other users have the same problem as you, using both the computer and smartphone I have no continuous return of these midi messages!Īt the moment I don't know how to help you, in version 1.15 and 1.17 the cursors and faders are set in the same way in midi reception/transmission. I was trying to catch the beginning when I first click on an algorithm in the Editor, in case the first messages are important, but it just goes by too fast since there's so much chatter.Įditor_1.17_Mk3_log-OSC.txt (26.36 KiB) Downloaded 16 times Editor_1.17_Mk3_log-MIDI.txt (25.65 KiB) Downloaded 13 times Thanks for trying! Hopefully the logs attached here will be helpful. When I roll back to Editor 1.15_Mk4, it's rock solid and doesn't exhibit any of these behaviors. But this was quickly overshadowed by the problem I just described here. I tried this a few different times, and at one point I saw the jumpy behavior in the Editor that I described before. It doesn't matter whether I change algorithms on the Disting EX itself, or in the Editor - the same behavior ensues. After killing off those processes, the Disting EX still shows ongoing send/receive status (until it catches up and things go quiet). But very soon after that, the CPU utilization from both TouchOSC and TouchOSC Bridge goes through the roof, and my system grinds to a halt. What happens next is I see the MIDI send/receive indicator light up (and it stay lit) on the Disting EX, and I see tons of send/receive messages in the TouchOSC log. This time I just loaded up the Editor and changed algorithms (that's usually the first thing I do to confirm everything's talking to each other). I'm sorry to report that it's actually worse now! Just to be clear, since there are new versions of things happening at the same time: I tested with Disting EX firmware 1.17.1 (same as before) and Editor 1.17_Mk3. I found conflicts on some controls sending sysex messages, I think I fixed the problem! ( tytytytyty see now if it's better! )
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |