Welcome to TVPaint Community forums !

UPDATE: this seems to have been a random occurrence with a single .tvpp file . I have not been able to reproduce the issue . So I think this was a false alarm. TVPaint Admins , please delete the topic .

This bug is present in both 11.7.5 and 12.0.3 .

I recently had to go in to an animatic and add a frame counter for each scene. Using the Time Code Generator FX to apply the frame count.
When I apply Time Code Generator to the first scene and then go to the next scene in the Project View to apply Time Code then TVPaint immediately crashes.a
Restart TVPaint open the project , apply Time Code Generator again to the first scene (because previous time code was lost due to the abrupt crash) , then I SAVE the scene ...
then go to the next scene to apply Time Code Generator it worked as expected, BUT then when I went to the next scene to apply Time Code it CRASHED again.

This seems like a rather serious bug. Is it a bug that TVPaint developers can reproduce ?

I am now having doubts that this issue is actually a bug in TVPaint . I suspect that the file I was trying to add timecode on is a corrupted file. (although it functions normally in every other way, except for crashing when I add a frame count to it). I recall in the past using Time Code Generator FX to add timecode or frame count to animatics without having this crashing issue, so that is why I am now thinking perhaps it was something corrupt about this file? (unless this is a new bug that only started with 12.0.3 and 11.7.5 ?) That's why I'm trying to confirm whether the issue happens for other people or was it just a freak random problem with this particular .tvpp file .

I've run a few tests with other animatic files this morning (using both 12.0.3 and 11.7.5) and I can't reproduce the issue.

Hi David,

I've tried to reproduce the crash several times, but I couldn't do it.
I am on Windows though, I'll see with my colleagues that are on macOS.

Nothing on macOS either, so I guess there was an issue on you original file.

Thierry wrote: ↑15 Apr 2025, 13:31 Nothing on macOS either, so I guess there was an issue on you original file.

Thank you for checking .

I have also tried several more tests with other files and have not been able to reproduce the issue, so it does seem it was just this one file that had a problem.

Feel free to delete this topic , because it was a false alarm.

If that file works normally otherwise, this is NOT a false alarm.
Something is still happening that shouldn't happen...