Editing A Project With Last Minute Cuts Or Time Inserts Will Break All Existing Go-To-Time Hotspot Callouts

  • 2
  • Problem
  • Updated 10 months ago
If you change the time domain of a project AFTER you have already set properties on go-to-time hotspots, all "down stream" hotspots will become broken; their go-to-time properties will have to be reset or they will not work as expected in a production.

This is an unhandled editing exception, since every other aspect of a project is adjusted, time wise, whenever you cut or insert time.

If you have a lot of go-to-time hotspots in your project [like 330], a last minute minor time-adjust edit can be a real deal killer.

Recommend you enhance the editor to handle auto-adjusting of go-to-time values whenever an edit affects them after-the-fact.  The .tscproj file seems to use "frames" as the go-to-time values index parameter; maybe a simple add/subtract thing based on the number of frames involved in any given cut or time insert?
Photo of kayakman

kayakman, Champion

  • 6245 Posts
  • 1830 Reply Likes

Posted 11 months ago

  • 2
Photo of kayakman

kayakman, Champion

  • 6245 Posts
  • 1830 Reply Likes
HEADS UP

If you are likely to make insert or cut edits after go-to-time hotspots are placed, then a reliable workaround is to use go-to-marker hotspots instead, providing you follow certain protocols when building out the project.

If your project activities might be affected by the above, then perhaps this tutorial might be helpful ...

How To Prevent Timeline Edits From Breaking Go-To-Time Hotspots
http://www.screencast.com/t/sLUBRE6P6zJM

FYI, this issue has been reported to tech support.
(Edited)