Fixed bug with duplicate scene names only showing one scene
Added Cancel button to TDA Master warning dialog
Backwards compatibility warning: SongInfo[‘scenes’] is now a list instead of a dictionary indexed by name.
@benflock: the issue you reported is larger and will probably have to wait until TD 40k is released. I haven’t been able to duplicate the problem, but I plan on building in a Track filtering mechanism like the one you hacked into TDA.py…
Not sure if this is a legit error or just ableton stupidity,
but if there’s a scene without a name, you get the error:
line 18, in onTableChange
SystemError: error return without exception set
also, are you able to connect to another computer on the network running ableton? I thought i tested it before and was able to, but using 1.15.0 gives the error that i can’t connect.
Important - TD build 26450 has an issue that breaks TDAbleton. Will be fixed soon!
Bunch of bug fixes released in 1.15.1 (at top of thread). Thanks to everyone that has reported issues.
Max issue - Macro numbers are no longer mixed up
Max issue - deleting or adding tracks no longer breaks connection with TDA devices
Max issue - TDA Rack devices have accurate help on “OUT” buttons
Adding cue points no longer causes textport error spam
Empty scene names no longer cause errors
I’ve heard people are having some trouble connecting, possibly due to new default of OSC port 8001 instead of 8000. Make sure your tdAbleton component and TDA_Master Live device have matching settings. If at first you don’t connect, try a couple different ports. If you still have problems, do post here!
Hello! The information that arrives from Ableton to TD without problems. But not from TD to Ableton. For example, when trying to change the volume of a track. Any ideas?
It’s on “chopexec_scrubWhenStopped” (Chop Execute) in the AbletonSong COMP. It’s points to an absolute reference, when it could just be a relative one (since the CHOP is references is right next to it). I noticed this because my top-level/parent container wasn’t named project1 and i got an error.
Anyone know of a good way to render non-realtime TDAbleton controlled content?
Say for example if I wanted to render a video from Touchdesigner with realtime turned off, which slows touchdesigner so it can render every frame, as opposed to skipping frames, and have that slow down the TDAbleton connection as well so the content syncs up properly.
In an ideal setup, I would like to send OSC messages to Ableton to advance to the next frame. OR have some kind of midi clock sync going on. Any ideas?
Are you controlling Ableton with TouchDesigner or do you have controls from Ableton sending into TD?
I recently completed a music video where I had written a bunch of automation in Ableton that was controlling parts of my TD patch. The way I made the offline render was to do a play-through of the song with Realtime turned on in TD to capture all the automation into a Record CHOP. Then, when I was doing the non-realtime rendering, I looked up the channel values based on the current frame of the timeline.
Ableton doesn’t have a concept of frames, so I’m not sure how “advancing the frame in Ableton” would work. You could advance the playhead position by the amount of time that would elapse in a frame if you were in realtime mode.
Thank you so much for building this tool - it has been so fun to play with.
I am having an issue in consistently looping through ableton arrangement scenes
I am syncing a series of looks with TDAbleton. I reference a channel that counts up every time a TouchDesigner cycle completes, looping from 0-3. This count updates the ‘scene to fire’ string parameter, as well as the ‘fire clip’ boolean parameter, of the TDAbletonSong COMP.
Sometimes everything transitions perfectly. Other times, the same scene fires repeatedly. I find that if I have the network editor opened at the level of the TDAbleton COMP, the scene switching works as expected, but if i exit that view, the switching stops working.
Attaching my project below. Please refer to the ‘TDAbleton Song’ Comp and the ‘Show Control’ Comp inside of the project _Spring_Fest_Beta.13.toe (219 KB)
^^Figured out my above issue - just wanted to post the fix here in case anyone else encounters a similar issue.
Touch is pull-based, so since the Null CHOP channel being referenced in the TDAbleton Song COMP was not being called for in perform mode, the Null CHOP was not cooking.
Going to the Common page of the referenced Null CHOP and switching cooking to ‘Always’ resolves the issue.
Thanks to everyone for their help and support solving this!
[]All components now have selective cooking optional with par toggle (default is False)
[]abletonSong now has current_cuepoint and tda_connected channels
[]abletonSong now has callbacks onTDAConnectionChange and onSongInfoChanged
[]tdAbletonmaster comp now has output with connected channel
[*]fixed channel prefix stripping in MIDI, level, and rack components
Note: I am now only testing as far back as TD version 2018 26590. Should work as far back as 2017 10k versions, but that’s no longer guaranteed.
I see the notes on the Wiki - Cue Points (a.k.a Timeline Locators): abletonSong Component property LastLocatorPassed. Also available via callbacks.
What I am wanting to do is cue a visual and send a message to Live to start playing from a particular Cue Point - locator. At the moment I can only see a way to do this from Live to send ‘last locator passed’ and trigger the visual from Live.
The notes on the Wiki give me the feeling I will need a few Python commands - any way to achive TD controlling triggering of Cue points with a simple linking/triggering such as you can with Clip slots?
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?