Trying to connect over network with TDAbleton - for some reason it works fine over Wi-Fi between two PC’s, but when I try to connect a PC running Touch to a Mac with Ableton, the connection is almost impossible. Has anybody had a similar experience/know of a more seamless way of connecting via TDAbleton?
Loving some of the new features In 1.18 Thanks!
One question … I Don’t seem to get any values coming into TD for TDA_Audio_Analyzer and TDA_Level COMPs … any special tricks to getting these working ?
I Can control the marcos from TD tho and see it working on the Ableton End …
I’ll dig into this next week.
- are you connecting locally or over network?
- can you send your ableton log files (instructions in wiki if you don’t know where they are) to email@example.com?
I tested the audio analyzer and level COMPs and they’re working fine on my machine. I wonder if you have a conflict on the Max Port. Try changing that in the tdMaster component parameters and the TDA Master device on the Live master track.
- fixes some problems with Rack initialization
DO NOT USE! 1.18.2 is built incorrectly
- Fix intermittent timing issues when initializing
- Fix major build error in 1.18.2
We will no longer be releasing TDAbleton updates here in the forums. They will come out with TouchDesigner builds, so keep an eye on the build notes.
As always, post any bugs here or mention TDAbleton in the title if you create your own thread. If you have a bug emergency, I can send new versions separately so you don’t have to wait for a new build.
Hi, I started using TDA and ran some performance test. Quickly, I experienced performance issues while controlling some parameters on multiple tracks (18 tracks with 3 parameters per track being change @ 30fps). It seems that each module that I instantiate in TD (abletonChain, abletonParameter) cooks between 0.1 and 0.5 ms. Is there a strategy to have better performance for project involving numerous continuous parameter modification over multiple tracks?
The most efficient way to control parameters in Live is to use the abletonRack component, put the devices you want to control inside it, and attach the rack’s macros to the device parameters you want to control. and wire a CHOP into the abletonRack’s input.
Using ableton component parameter controls is better used for setup and testing, not realtime performance.
Thanks, I’ll look into it.
I also found that if I turn Off all of the oscin_ of each instances, performance gain is dramatic!
Perhaps we could implement a toggle to decide if a Component is Send only. Would that make sense?
I will look into that possibility and also why those OSC nodes are taking so much time!
Have you found a solution for the cooking issue.
Alternatively, I was wondering if an OSC patterns list was available so we could bypass TDAbleton on TD’s side and output directly in a oscCHOP?
@barouet A couple things coming in the new version (1.21.0). Send Only mode on each component turns off incoming osc completely. Also, turning off Timeslice mode will make osc only cook when values are coming in. Hopefully this will help you.
There is no way to bypass TDAbleton completely, because it is the mechanism by which requests are made to Live for osc data. However, if you find ways to make the components more efficient, do let me know!
Great, thanks! Send Only mode should fix most of my worries concerning performances.
If you want maximum speed from TD to Live, definitely use the rack components and the mapper component.
I’m trying to debug an error i’m having with receiving the midiclip info from
ableton … .the text port says: (below)
Basically the midi clip info isn’t making in to touch…
any thooughts / tricks / clues on sorting this ?
It looks like you’re trying to ask info about a MIDI pitch range that Live doesn’t like. What are your MIDI range parameter settings for the clip slot component? You can send your set and toe if you like. firstname.lastname@example.org
Hi there, don’t mean to fill up the thread asking about connection issues, but this one is really driving me nuts!
Short version: Connects on laptop, not on desktop.
- Used the same (latest) installation file for TouchDesigner on both
- Same installation of Live Suite 10.1.0 on both
- Latest Win10 64 on both
- Followed installation instructions correctly on both
- Laptop connection between TD and Ableton is virtually bulletproof on default settings, open one, then the other and they instantly see one another and I get the prompt to add a Master.
- Desktop connection is non-existent or just confusing. The closest I’ve got is: On the default settings it sometimes shows in Ableton as being connected (yellow light) if I manually add a TDA_Master to the Master track, but will then not be connected at the TD end. Never been prompted to add master by TD on desktop. Attempted with a myriad of random port numbers. Attempted after multiple restarts. Attempted with other USB control surfaces unplugged (Push 1, MPK Mini Mk2, two random old casio keyboards through MIDI to USB adapters) and/or disabled in Live’s preferences to leave TouchDesigner as the only control surface. Cannot ping from TD, nor use any controls. Textport output is as follows:
/project1/tdAbletonPackage/tdAbleton : Requesting connection to Ableton Live.
TDA Remote Script Error
Traceback (most recent call last):
File “C:\ProgramData\Ableton\Live 10 Suite\Resources\Python/lib\SocketServer.py”, line 290, in _handle_request_noblock
File “C:\ProgramData\Ableton\Live 10 Suite\Resources\Python/lib\SocketServer.py”, line 318, in process_request
File “C:\ProgramData\Ableton\Live 10 Suite\Resources\Python/lib\SocketServer.py”, line 331, in finish_request
self.RequestHandlerClass(request, client_address, self)
File “C:\ProgramData\Ableton\Live 10 Suite\Resources\Python/lib\SocketServer.py”, line 652, in init
File “C:\ProgramData\Ableton\Live 10 Suite\Resources\MIDI Remote Scripts\TouchDesigner\OSC.py”, line 1797, in handle
File “C:\ProgramData\Ableton\Live 10 Suite\Resources\MIDI Remote Scripts\TouchDesigner\OSC.py”, line 1779, in _unbundle
self.replies += self.server.dispatchMessage(decoded, decoded[1:], decoded[2:], self.client_address)
File “C:\ProgramData\Ableton\Live 10 Suite\Resources\MIDI Remote Scripts\TouchDesigner\OSC.py”, line 1741, in dispatchMessage
reply = self.callbacks[addr](pattern, tags, data, client_address)
File “C:\ProgramData\Ableton\Live 10 Suite\Resources\MIDI Remote Scripts\TouchDesigner\TDA.py”, line 332, in onMsgCommand
File “C:\ProgramData\Ableton\Live 10 Suite\Resources\MIDI Remote Scripts\TouchDesigner\TDA.py”, line 437, in sendConnectInfo
File “C:\ProgramData\Ableton\Live 10 Suite\Resources\MIDI Remote Scripts\TouchDesigner\TDA.py”, line 487, in sendSongInfo
‘tracks[’ + str(tIndex) +’]’)
File “C:\ProgramData\Ableton\Live 10 Suite\Resources\MIDI Remote Scripts\TouchDesigner\TDA.py”, line 571, in getTrackOrChainInfo
devices[key][‘chains’] = self.getChainsInfo(device)
File “C:\ProgramData\Ableton\Live 10 Suite\Resources\MIDI Remote Scripts\TouchDesigner\TDA.py”, line 590, in getChainsInfo
chain.name, ‘chains[’ + str(cIndex) + ‘]’)
File “C:\ProgramData\Ableton\Live 10 Suite\Resources\MIDI Remote Scripts\TouchDesigner\TDA.py”, line 557, in getTrackOrChainInfo
if device.parameters.name == ‘ID_TDA_Ignore’:
IndexError: Index out of range
End TDA Remote Script Error
python >>> [/code]
Not sure what else to try!
The laptop connection is great, and am having lots of fun playing with this tool, but wondered if you could offer any advice? My laptop’s CPU load is pretty high with an Ableton set going at the same time as, say, pretty particles, so I’d love to play with it on the desktop.
P.S. I’ve seen people using this at the same time as Push so presumably the control surface clash thing is resolvable/a non-issue?
Thanks in advance for any advice you can offer.
Have you tried changing the port? There may be something on desktop already using the default one