2 ms·
> apologies I answered the three of you all in this one reply. Hope it's of enough interest and easy enough to discern if something is not what you asked. As a
by zahlman 3mo ago
> apologies I answered the three of you all in this one reply. Hope it's of enough interest and easy enough to discern if something is not what you asked.
As a heads-up, you're lucky this time — it seems to be pretty rare on HN that people keep track of threads past their initial encounter, unless they get a direct reply (and even then it's far from guaranteed). It's not a great place to have a conversation (but then, where is?).
> Yeah I'm stil working on the subtitles. Subtitles are a solved problem, right? Well, not when you want to display something like /etc/passwd (and many such things) it becomes a pain.. The funny thing is that the main purpose in making a video was to maks e Lyric videom but that ended up the last thing I did insofar as editing the video, and it doesn't work right. I was tired from being up for two days trying to finish it.
> I'm finishing up the lyric aligner I made for this video (which is why it's missing a section and starts to lag. But I was soo tired of editing and I wanted people to hear it so I took a break and upploaded it anyway I digress.) It let's you have a spoken lyric sheet for the aligner (whisper and stable_ts) to listen for, where you can put words in their phonetic spellings like you would for TTS, but the another lyrid sheet for presentation spellings that will be used in the subtitles. This was necessary due to all of the technical terms and acronyms that may not be pronounced in an expected way by the aligner tools. It zips (interleaves) the two together and creates a yaml file for hand editing tweaks suchas subtitle effects, then it generates the proper .ass file for that. I'll push the lyric aligner up to the repo when it's working 100%.
I probably would have just fixed everything manually instead of trying to improve the system...
- ycombiredd 3mo agoYes, 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.