My rig thus far:
Hardware:
TouchOSC 1.7.4 on iPhone 4S w/iOS 5
Evolution UC-33e
Protocols/Transports:
ASIO4All v2.10
PureData 0.45.2-extended
PureData Patch Generator 1.2 (from hexler.net)
MidiYoke or LoopBe Internal MIDI
Software Environment:
Ableton Live v8.2.x
Windows 7 x64
The problem:
One or more of the faders will always be completely schizophrenic, as if the MIDI data range were inverted and super-sensitive to adjustment, jumping from 0 to 1/3 to halfway to full on before I even finish moving the slider all the way. I forked a [print] block off the [dumposc] object in PureData and monitored changing fader values on the console to verify OSC messages are being sent smoothly and properly, and they are. I’m unable to isolate where the problem lies.
Things I’ve tried:
Different phones with different iOS versions (3G running iOS 4.x)
Different MIDI routing drivers (MidiYoke vs. LoopBe)
Different versions of Ableton Live 8.2.x
Different versions of ASIO4All (2.9 and 2.10)
Recreating the malfunctioning widgets in TouchOSC Editor
Recreating many individual faders as a multifader in TouchOSC Editor
Reassigning the MIDI mapping to another control and then back again
Other details:
Occasionally recreating the widgets in the Editor will fix the issue, but it will hop to another widget. Occasionally toggling the MIDI mapping to something else and back in Live will fix the issue, but that’s not really a viable long-term solution. When the issue is affecting a multifader it affects every fader on the widget.
I’m losing my freakin’ mind trying to figure out what the problem is and have spent about 9 days troubleshooting this problem and searching for a resolution path. If anyone could help me out here I’d really appreciate it, this is a blocker for being able to use TouchOSC.
inb4 get a mac
Spazzing Controls.
-
Warrior Bob
- Posts: 841
- Joined: Mon Apr 06, 2009 5:10 pm
- Location: Central Coast, California
- Contact:
Re: Spazzing Controls.
get a mac
Kidding aside, this kind of sounds like a problem I had where I was moving an absolute control on my hardware device, but Live was interpreting the signal as some kind of relative control. The assigned parameter wasn't useful in any meaningful way, and I was never quite sure why it moved where it did.
I forget where you can set this (MIDI mapping browser I think?) but assigning the proper control type relieved the issue.
Kidding aside, this kind of sounds like a problem I had where I was moving an absolute control on my hardware device, but Live was interpreting the signal as some kind of relative control. The assigned parameter wasn't useful in any meaningful way, and I was never quite sure why it moved where it did.
I forget where you can set this (MIDI mapping browser I think?) but assigning the proper control type relieved the issue.