Several projects which had no issues in the previous version I was working on, now have playback errors.
The main issue I have is that I get a pop up error and then my timeline goes invisable. There's probably a corrupt or unrecognised effect / mediafile in there somewhere, but I can no longer bring my timeline back into vision.
Any ideas?
"Exception: CORE_SEGMENT_NOT_FOUND, className:TLtrak, methodName:DrawSegDupZones"
@jaketheeditor
Can you not either a) select Window > Timeline and get it to re-appear or b) reload whatever workspace (presumably source/record) you were using?
-- Kevin
Hi
I have that issue. Did 2018.7.1 solve this? Just curius
I\m currently editin a movie and I dont wanna keep udating if this happens. I very much like the idea of the live timeline though.
did a succecfull downgrade to 2018.5 and all works again
Best Ulrich
Ulrich Thomsen: Hi I have that issue. Did 2018.7.1 solve this? Just curius I\m currently editin a movie and I dont wanna keep udating if this happens. I very much like the idea of the live timeline though. did a succecfull downgrade to 2018.5 and all works again Best Ulrich
Ulrich
2018.7.1 resolved one issue - lagging of playback on mac 10.13.4 and higher systems.
marianna.montague@avid.com
Like you, I ended up going back.
I think it may have something to do with some of the plug-ins I had on my timeline. No way around it.
thanks for the reply, both you and Marianna
I\ll hang back for a while more... but *** it, that live timeline... why that took so long to implement is mindbogling to me.
Where you ever able to resolve this issue? What steps did you take? I am testing 2018.12.1 for my crew of 5 other systems who are all still on 8.9.4. We are on a NEXIS shared storage and I are fed footge from our live studo via an EVS. I only get the "exception: CORE_SEGMENT_NOT_FOUND, className:TLtrak, methodName:DrawSegDupZones" on footage brought in from the EVS. My timeline does not disappear, but I get this error twice, OK both times and can then continue. We also got this error on 2018.9 and then I downgraded back to 2018.5 which does not get the error. Any solutions?
© Copyright 2011 Avid Technology, Inc. Terms of Use | Privacy Policy | Site Map | Find a Reseller