RESOLVED: bug/problems with timeline

General TouchDesigner Discussion
1

when loading files created before the latest release of the timeline:

/ui/dialogs/timeline/launch (line 6 - set HASCLOCK = tabfind("/local/attributes","clock",0,"row","forward")): Expression error: Bad path argument
/ui/dialogs/timeline/launch (line 12 - set HASCLOCK = tabfind("/local/attributes","clock",0,"row","forward")): Expression error: Bad path argument
/ui/dialogs/timeline/launch (line 13 - set CLOCKIS = tab("/local/attributes",$HASCLOCK,1)): Expression error: Bad path argument
clock is
arg0 is /ui/dialogs/timeline/local/macros/init
TIMELINE INIT arg1 is
/ui/dialogs/timeline/local/macros/init (line 6 - set CLOCKTYPE = tabr("$arg1/attributes","clock",1)): Expression error: Bad path argument
INIT - KEYPATH is /local
init played
init

That may be why I don’t see any frame number change at the bottom of my touch instances - I noticed that if I open a new touch there’s a frame number changing - which tells me it’s playing.

Any suggestions on how to fix this?

2

Bump - maybe I should have posted it under bugs - feel free to reclassify - this is giving me a headache now because I can’t play the animation.

(derivative - please feel free to test on latest commit)

3

Maybe your file is missing …

/local/attributes

OR?

/local/time

This is possible if you have been working on a file for along time maybe it didnt get updated automatically.?

J

4

I guess local attributes is not there.

How to fix?

touch → cc /local
touch → lc
maps
midi
time
macros
bookmarks
shortcuts
variables
set_variables
touch →
touch → cc time
touch → lc
rate
time
clock
local
state
cframe
getscrub
override
scrubber
pausemath
attributes
properties
touch →

5

Delete the entire time component.
Next time you load the toe, it will be recreated with the current defaults.

6

had the same issue. fixed by deleting the time COMP

But I also get this error now (on a fresh session, directly after loading)

7

I actually copied/pasted to new files (and dealt with the problems that came from that route:)).

I do often notice errors that seem to have nothing to do with my networks, and I often wonder whether or not to report them.

d