# Rename timeline segments as record timecode **URL:** \ **Category:** Flame Questions\ **Tags:** timeline, timecode, segments\ **Created:** [September 18, 2024, 5:51pm UTC](https://forum.logik.tv/t/rename-timeline-segments-as-record-timecode/11427 "2024-09-18T17:51:40Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![cicero](https://avatars.discourse-cdn.com/v4/letter/c/ecae2f/32.png) [@cicero](https://forum.logik.tv/u/cicero)\ **Post date:** [September 18, 2024, 5:51pm UTC](https://forum.logik.tv/t/rename-timeline-segments-as-record-timecode/11427/1 "2024-09-18T17:51:40Z")
Hi everyone. I have dozens of shots (segments) on a timeline. I want to rename each one with its start TC (doesn’t matter why!). Ideally this name would be dynamic and update if the segment gets nudged up or down the timeline, but it doesn’t matter if not. Is it possible to crowbar existing tokens into achieving this with a single select-all + rename? I think probably not? If not then I guess a python script could do it? Thanks for any thoughts. ---
**Author:** ![john-geehreng](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.logik.tv/john-geehreng/32/7195_2.png) [@john-geehreng](https://forum.logik.tv/u/john-geehreng)\ **Post date:** [September 19, 2024, 7:30pm UTC](https://forum.logik.tv/t/rename-timeline-segments-as-record-timecode/11427/2 "2024-09-19T19:30:27Z")
I don’t think it’s possible to do with tokens, so I’d probably do it with a script like this: [rename\_with\_timecode.py](https://forum.logik.tv/uploads/short-url/qAtap5h2JMnIb2kNp6lFKL7iBXs.py) (1.2 KB) It’s not dynamic, so you’d have to re-run the script if you slip or edit a segment. ---
**Author:** ![cicero](https://avatars.discourse-cdn.com/v4/letter/c/ecae2f/32.png) [@cicero](https://forum.logik.tv/u/cicero)\ **Post date:** [September 20, 2024, 8:23am UTC](https://forum.logik.tv/t/rename-timeline-segments-as-record-timecode/11427/3 "2024-09-20T08:23:09Z")
@john-geehreng This is brilliant, thanks so much. I’m going to try to tweak the script to sanitise characters (colons) too, which will be good practice for my non-existent python skills! This could open up some great workflow improvements for us, so thanks again.