Ableton Forum

They got it right this time. I haven't even begun to realize the likeliness of it and push. Not that I even need it, but there are features that prevent you from fiddling around with Push that may be somewhat buried. So I just keep it near by. It's like having an extra monitor and twice the controls at reach.. Yes, it's pretty cool!

lyovino wrote:They got it right this time. I haven't even begun to realize the likeliness of it and push. Not that I even need it, but there are features that prevent you from fiddling around with Push that may be somewhat buried. So I just keep it near by. It's like having an extra monitor and twice the controls at reach.. Yes, it's pretty cool!

Do you have any specific examples of the buried features that would prevent you using the Push?

I think I'm going to buy Touchable 2 even though I am still on iOS 6 (jailbroken), and iOS 6 has some problems connecting to ad-hoc networks sometimes. They said they would be rolling out support for cabled connections, and I can deal with it until they do since there isn't really any latency like you guys mentioned.

Has anyone tried using Touchable 2 with hardware like shown in the example video with a BCF 2000 (seems to be a lesser known/utilized feature from what I can gather). Having motorized faders with good remote script support, and visual feedback from touchable's faders seems really sweet. (i.e. letting touchables remote script do all the work, and just map the bcf faders to the volume faders). I really hate using Ableton's midi mapping feature when Remote scripts just open up so much more functionality.

AtomikA wrote: Do you have any specific examples of the buried features that would prevent you using the Push?

It's not that the features of Push are buried, I guess what I mean is that it can be very convenient having touchAble running along with it. Let's say you are in Arrange playing back some tracks, touchable is in clip mode, you can record a new clip without switching back to Session. Or have you ever been adjusting Volumes and then switch to Track to adjust pans. If touchable is running you can leave the pans on iPad and have both conveniently readily available. These are very small examples and may not be necessary of course, but it can surely add to one's workflow. The list goes on and on. Don't get me wrong, I'm perfectly satisfied with Push alone but the pleasure of the additional screen/functionality is a plus. Sometimes I use it, sometimes I don't..

I think I'm going to buy Touchable 2 even though I am still on iOS 6 (jailbroken), and iOS 6 has some problems connecting to ad-hoc networks sometimes. They said they would be rolling out support for cabled connections, and I can deal with it until they do since there isn't really any latency like you guys mentioned.

Touchable works beautifully on a wired computer. No ad hoc necessary. iPad automatically uses my ethernet IP. No latency problems at all.

Lyovino, that was a great example of how touchable "augments" the Push experience. They really work well together.

Push and touchAble2 here as well... I only have both of them for a few weeks now, but it changed my workflow completely! touchAble does things Push can't, like sliding your finger over the notes grid to get crazy glissando stuff, controlling EQ8 like you never have before,...

I'm also starting to make controllers for my external gear in touchable in the 'user window'. works great so far (but only just started).
like Lyovino, I also use it to control stuff like volume while Push is in another mode. browsing for scales, instruments,... seems easier on touchable than on Push,...

if you already have an iPad, I wouldn't hesitate. Haven't even used the physical part of touchable yet, which looks like fun as well.

Anyway, I used Shove on Lemur a few months ago, and after a week, I felt I needed Push. It is the best purchase I made in years, and with touchAble, I feel the iPad has finally become the controller I had bought it for.

All on OSX though, as my XP machine won't recognize the server, and this very server also brought the machine to it's knees as it kept on growing massively in size . This was after applying a patch by the touchable crew to see why I couldn't connect. The log file grew to a file of about 17 Gb. strange... no problems on the MBP.