Yes, but maybe you know how it is... similar to that threshold where "I've done this three times before, if I had automated it, I'd maybe have spent the same am

Yes, but maybe you know how it is... similar to that threshold where "I've done this three times before, if I had automated it, I'd maybe have spent the same amount of time writing the automation, but the fourth time on would be free" and doing the sort of quick on-the-fly gut-math cost/benefit analysis that either results in an eventual time savings to be celebrated, or a "dammit, I should have just done this by hand again" unique type of regret. So for this particular set of words and timing, I found I really disliked eyeballing the lines and doing quick time arithmetic and sanity checks because there were no obvious errors the two or three passes I made. So I found myself making a quick script to return the differences, to try to see what odd combination might be triggering a bug, etc. plus although what you see now looks like just standard subtitles, the original burn of them used some of the ass format's unique rendering capabilities and, as with the one-off script type automation cost/benefit.. I think it's actually cool enough and potentially useful for other cases (generative TTS/ai vocals, etc) that even if I never make another "rap"-style track and video, someone else is likely to encounter the same problem and find this solution useful. But probably mostly it's a combination of sunk cost fallacy and stubbornness, with some laziness and fatigue thrown on top that has now a video for a song I wanted to share with whoever it might reach with broken subtitles and an unfinished tool to correct them.