touchAble 3 is out! Now connects via simple USB cable & more

[Matt_Quinn]

Random question: I have a 2 delays in parallel in an instrument rack. When I try to select the rack from the Device view in Touchable, , it drops down the 2 parallel chains, which I can then go into, but I can't seem to grab the rack itself (which is where all the useful controls are mapped). What am I doing wrong?

[Le k]

Random question: I have a 2 delays in parallel in an instrument rack. When I try to select the rack from the Device view in Touchable, , it drops down the 2 parallel chains, which I can then go into, but I can't seem to grab the rack itself (which is where all the useful controls are mapped). What am I doing wrong?

I guess you mean macro controls..to access them, just double tap

[Matt_Quinn]

Random question: I have a 2 delays in parallel in an instrument rack. When I try to select the rack from the Device view in Touchable, , it drops down the 2 parallel chains, which I can then go into, but I can't seem to grab the rack itself (which is where all the useful controls are mapped). What am I doing wrong?

I guess you mean macro controls..to access them, just double tap

Awesome, thank you!! Knew I was missing something simple.

[freepuppies]

I have an iPad1 and an iPad4. There is no difference in Touchable performance. I really have to say how much I appreciate the developer making the app work on the older gen iPad. It's really great. Thank you!

[Stromkraft]

Only thing missing in my eyes is drum rack sub channel control, but this problem seems to be on abletons side if i understand correctly.

That might be so. However, I'm surprised no-one have suggested the obvious solution while you are waiting for full drum rack support from Touchable (or Ableton with the Push), which is chain extraction. This makes the chain a full-on track outside of the drum rack, but can still be played from there.

There are effects of this move that might not suit everyone, but having full access from controllers may outweigh this. I had to rethink my whole strategy to drum racks — that I love — and I'm happy that I did embrace extraction as it has revolutionized my music making.

[login]

Only thing missing in my eyes is drum rack sub channel control, but this problem seems to be on abletons side if i understand correctly.

That might be so. However, I'm surprised no-one have suggested the obvious solution while you are waiting for full drum rack support from Touchable (or Ableton with the Push), which is chain extraction. This makes the chain a full-on track outside of the drum rack, but can still be played from there.

There are effects of this move that might not suit everyone, but having full access from controllers may outweigh this. I had to rethink my whole strategy to drum racks — that I love — and I'm happy that I did embrace extraction as it has revolutionized my music making.

In fact PXT Live has control over drum rack channels volume and sends, so there isnt a technical limitation Its just not being implemented.

[fishmonkey]

is anyone else on OS X getting their system log flooded with error messages like this:

Code: Select all

4/02/2015 3:38:13.712 pm com.apple.usbmuxd[64]: SCEDeviceSocketCallback Client 0x10200cdf0-touchAble/NULL connect to 0x36 failed, connection failed with error 61 - Connection refused
4/02/2015 3:38:15.710 pm com.apple.usbmuxd[64]: MuxTCPInputSCE received RST for 0x39-e088ce68b2b2da60fb2d6e32b772f193869b5f5e@0x80412000:2345->0x1004093e0-touchAble/NULL:29195: handleConnectResult: failure - 61
4/02/2015 3:38:15.965 pm com.apple.usbmuxd[64]: SCEDeviceSocketCallback Client 0x100405b20-touchAble/NULL connect to 0x36 failed, connection failed with error 61 - Connection refused
4/02/2015 3:38:17.783 pm com.apple.usbmuxd[64]: MuxTCPInputSCE received RST for 0x39-e088ce68b2b2da60fb2d6e32b772f193869b5f5e@0x80412000:2345->0x10200cdf0-touchAble/NULL:29451: handleConnectResult: failure - 61
4/02/2015 3:38:18.219 pm com.apple.usbmuxd[64]: SCEDeviceSocketCallback Client 0x100605c30-touchAble/NULL connect to 0x36 failed, connection failed with error 61 - Connection refused
4/02/2015 3:38:19.859 pm com.apple.usbmuxd[64]: MuxTCPInputSCE received RST for 0x39-e088ce68b2b2da60fb2d6e32b772f193869b5f5e@0x80412000:2345->0x1004093e0-touchAble/NULL:29707: handleConnectResult: failure - 61
4/02/2015 3:38:20.470 pm com.apple.usbmuxd[64]: SCEDeviceSocketCallback Client 0x10200cdf0-touchAble/NULL connect to 0x36 failed, connection failed with error 61 - Connection refused
4/02/2015 3:38:21.000 pm kernel[0]: System Events (map: 0xffffff8043bd90f0) triggered DYLD shared region unnest for map: 0xffffff8043bd90f0, region 0x7fff85c00000->0x7fff85e00000. While not abnormal for debuggers, this increases system memory footprint until the target exits.
4/02/2015 3:38:21.936 pm com.apple.usbmuxd[64]: MuxTCPInputSCE received RST for 0x39-e088ce68b2b2da60fb2d6e32b772f193869b5f5e@0x80412000:2345->0x10200cdf0-touchAble/NULL:29963: handleConnectResult: failure - 61
4/02/2015 3:38:22.698 pm com.apple.usbmuxd[64]: SCEDeviceSocketCallback Client 0x1022050e0-touchAble/NULL connect to 0x36 failed, connection failed with error 61 - Connection refused
4/02/2015 3:38:24.012 pm com.apple.usbmuxd[64]: MuxTCPInputSCE received RST for 0x39-e088ce68b2b2da60fb2d6e32b772f193869b5f5e@0x80412000:2345->0x10200cdf0-touchAble/NULL:30219: handleConnectResult: failure - 61
4/02/2015 3:38:24.636 pm com.apple.usbmuxd[64]: _SendAttachNotification Device b0:34:95:11:0f:5c@fe80::b234:95ff:fe11:f5c._apple-mobdev2._tcp.local. has already appeared on interface 4. Suppressing duplicate attach notification.
4/02/2015 3:38:24.726 pm com.apple.usbmuxd[64]: SCEDeviceSocketCallback Client 0x100405c50-touchAble/NULL connect to 0x49 failed, connection failed with error 61 - Connection refused
4/02/2015 3:38:24.775 pm com.apple.usbmuxd[64]: SCEDeviceSocketCallback Client 0x100307d30-touchAble/NULL connect to 0x36 failed, connection failed with error 61 - Connection refused
4/02/2015 3:38:26.089 pm com.apple.usbmuxd[64]: MuxTCPInputSCE received RST for 0x39-e088ce68b2b2da60fb2d6e32b772f193869b5f5e@0x80412000:2345->0x10060d9f0-touchAble/NULL:30475: handleConnectResult: failure - 61

[Stromkraft]

In fact PXT Live has control over drum rack channels volume and sends, so there isnt a technical limitation Its just not being implemented.

Yes, but that's not a comfort.

[login]

In fact PXT Live has control over drum rack channels volume and sends, so there isnt a technical limitation Its just not being implemented.

Yes, but that's not a comfort.

I know, just pointing out it is possible.

I have requested it many times to app developers as well as promote it around in the beta forum.

I really can' understand how this is such an overlooked feature.

[empathy1]

never heard of touchAble before today. looks like something I'll be purchasing soon.

[jestermgee]

On windows I can't even run the installer

I have iTunes 12.1 installed but when I try run the installer it says "Apple mobile device is missing. Please install iTunes. "

I have checked in windows programs that the mobile service is installed correct

[Chris / touchAble]

Hey jestermgee,

there is an issue with Apples latest iTunes 12.1 update and their Apple Mobile Device Service - deinstalling iTunes 12.1 and reinstalling 12.0.1 will fix this issue for the moment. We are investigating what causes it! sorry for the inconvenience :/

[Chris / touchAble]

is anyone else on OS X getting their system log flooded with error messages like this:

Code: Select all

4/02/2015 3:38:13.712 pm com.apple.usbmuxd[64]: SCEDeviceSocketCallback Client 0x10200cdf0-touchAble/NULL connect to 0x36 failed, connection failed with error 61 - Connection refused
4/02/2015 3:38:15.710 pm com.apple.usbmuxd[64]: MuxTCPInputSCE received RST for 0x39-e088ce68b2b2da60fb2d6e32b772f193869b5f5e@0x80412000:2345->0x1004093e0-touchAble/NULL:29195: handleConnectResult: failure - 61
4/02/2015 3:38:15.965 pm com.apple.usbmuxd[64]: SCEDeviceSocketCallback Client 0x100405b20-touchAble/NULL connect to 0x36 failed, connection failed with error 61 - Connection refused
4/02/2015 3:38:17.783 pm com.apple.usbmuxd[64]: MuxTCPInputSCE received RST for 0x39-e088ce68b2b2da60fb2d6e32b772f193869b5f5e@0x80412000:2345->0x10200cdf0-touchAble/NULL:29451: handleConnectResult: failure - 61
4/02/2015 3:38:18.219 pm com.apple.usbmuxd[64]: SCEDeviceSocketCallback Client 0x100605c30-touchAble/NULL connect to 0x36 failed, connection failed with error 61 - Connection refused
4/02/2015 3:38:19.859 pm com.apple.usbmuxd[64]: MuxTCPInputSCE received RST for 0x39-e088ce68b2b2da60fb2d6e32b772f193869b5f5e@0x80412000:2345->0x1004093e0-touchAble/NULL:29707: handleConnectResult: failure - 61
4/02/2015 3:38:20.470 pm com.apple.usbmuxd[64]: SCEDeviceSocketCallback Client 0x10200cdf0-touchAble/NULL connect to 0x36 failed, connection failed with error 61 - Connection refused
4/02/2015 3:38:21.000 pm kernel[0]: System Events (map: 0xffffff8043bd90f0) triggered DYLD shared region unnest for map: 0xffffff8043bd90f0, region 0x7fff85c00000->0x7fff85e00000. While not abnormal for debuggers, this increases system memory footprint until the target exits.
4/02/2015 3:38:21.936 pm com.apple.usbmuxd[64]: MuxTCPInputSCE received RST for 0x39-e088ce68b2b2da60fb2d6e32b772f193869b5f5e@0x80412000:2345->0x10200cdf0-touchAble/NULL:29963: handleConnectResult: failure - 61
4/02/2015 3:38:22.698 pm com.apple.usbmuxd[64]: SCEDeviceSocketCallback Client 0x1022050e0-touchAble/NULL connect to 0x36 failed, connection failed with error 61 - Connection refused
4/02/2015 3:38:24.012 pm com.apple.usbmuxd[64]: MuxTCPInputSCE received RST for 0x39-e088ce68b2b2da60fb2d6e32b772f193869b5f5e@0x80412000:2345->0x10200cdf0-touchAble/NULL:30219: handleConnectResult: failure - 61
4/02/2015 3:38:24.636 pm com.apple.usbmuxd[64]: _SendAttachNotification Device b0:34:95:11:0f:5c@fe80::b234:95ff:fe11:f5c._apple-mobdev2._tcp.local. has already appeared on interface 4. Suppressing duplicate attach notification.
4/02/2015 3:38:24.726 pm com.apple.usbmuxd[64]: SCEDeviceSocketCallback Client 0x100405c50-touchAble/NULL connect to 0x49 failed, connection failed with error 61 - Connection refused
4/02/2015 3:38:24.775 pm com.apple.usbmuxd[64]: SCEDeviceSocketCallback Client 0x100307d30-touchAble/NULL connect to 0x36 failed, connection failed with error 61 - Connection refused
4/02/2015 3:38:26.089 pm com.apple.usbmuxd[64]: MuxTCPInputSCE received RST for 0x39-e088ce68b2b2da60fb2d6e32b772f193869b5f5e@0x80412000:2345->0x10060d9f0-touchAble/NULL:30475: handleConnectResult: failure - 61

Hey fishmonkey,
these messages appear whenever the ipad is plugged in, but touchAble is not running / connected. It is in fact simply a message telling us that we can't reach the app via USB at this time, so we can try again. However, to ensure quick reaction times when you open the app, we put this reconnection on a 2 second timer - which is the flood of messages you see there. We can't hide this message as it's burried deep in Apples framework, but we will issue an update shortly that is silent when you quit the Server completely - even if it's just for reading the Console log!

Hope it's not too much of an issue for you right now!
Cheers,
Chris

[h3rtz]

Only thing missing in my eyes is drum rack sub channel control, but this problem seems to be on abletons side if i understand correctly.

That might be so. However, I'm surprised no-one have suggested the obvious solution while you are waiting for full drum rack support from Touchable (or Ableton with the Push), which is chain extraction. This makes the chain a full-on track outside of the drum rack, but can still be played from there.

There are effects of this move that might not suit everyone, but having full access from controllers may outweigh this. I had to rethink my whole strategy to drum racks — that I love — and I'm happy that I did embrace extraction as it has revolutionized my music making.

how do you manage track arm?

[fishmonkey]

Hey fishmonkey,
these messages appear whenever the ipad is plugged in, but touchAble is not running / connected. It is in fact simply a message telling us that we can't reach the app via USB at this time, so we can try again. However, to ensure quick reaction times when you open the app, we put this reconnection on a 2 second timer - which is the flood of messages you see there. We can't hide this message as it's burried deep in Apples framework, but we will issue an update shortly that is silent when you quit the Server completely - even if it's just for reading the Console log!

Hope it's not too much of an issue for you right now!
Cheers,
Chris

hey Chris, yep it would be much better if this constant polling stopped when the server is not running...