Hello Yalda, On Mon, Jan 26, 2026 at 1:40 PM Yalda via ffmpeg-devel <[email protected]> wrote: > > Hi Nariman, > > Thank you for your contribution. Please note that the contribution > process is transitioning to Forgejo (https://code.ffmpeg.org) and > would pivot any future patches there. > With regards to this specific patch can you give some context as to > why you think it is needed? Is there a known fault or trigger? Also > return line needs indentation. > I do not see other subtitle decoders doing this check, and am leaning > toward trusting the API that decode() should not be called as such.
I'm all for seeing 608 support modernized, but is there a more detailed scope defined? This has been a pretty contentious topic over the years in terms of how this particular problem is approached, and I would hate to see a situation where the GSoC person spends a bunch of time creating something that won't make it upstream. For a 200 hour project, I would assume we need a better project definition than what can be found in one paragraph? Devin -- Devin Heitmueller, Senior Software Engineer LTN Global Communications o: +1 (301) 363-1001 w: https://ltnglobal.com e: [email protected] _______________________________________________ ffmpeg-devel mailing list -- [email protected] To unsubscribe send an email to [email protected]
