You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi @juligreen, thank you for checking in and no worries at all about wording. I'm afraid I just haven't been able to dedicate as much time to this issue as I would have liked, or to the other issues where various non-speech related subtitles (hearing-impaired tags, songs, etc) can sometimes mess up the detection.
It's definitely something that I still want to do, but realistically I'm afraid I don't have any estimates on timeframe. I kind of think that I may be getting some more free time around the start of the new year, but I don't want to say anything for sure as somehow my free time always ends up getting filled with other obligations. It's a very generous offer to sponsor at the 100$ tier and if I did have such a sponsorship it would definitely be extra motivation, but money isn't the bottleneck so I'm unfortunately not able promise anything definite.
Definitely keep checking in though! I am optimistic that I'll be able to address this issue and refine the syncing to be more accurate in other ways eventually...
Have you had any success with breaks or splits (or rather all the issues in #10)?
Could you dedicate more time to this issue if I would sponsor you at the 100$ tier?
What kind of timeframe do you think it would take to solve this?
Thank you and sorry if this is worded in a rude way :)
The text was updated successfully, but these errors were encountered: