From: Michael Niedermayer <michael@niedermayer.cc> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Subject: Re: [FFmpeg-devel] [PATCH v0] Implement promeg decoder. Date: Wed, 22 Jan 2025 17:36:57 +0100 Message-ID: <20250122163657.GY4991@pb2> (raw) In-Reply-To: <CABGuwEm6+-uU1gQpxRUa2kGNV-USZXbJv_=QoSrCpYFVc_=u3A@mail.gmail.com> [-- Attachment #1.1: Type: text/plain, Size: 2526 bytes --] Hi On Mon, Jan 20, 2025 at 03:00:17PM +0000, Kieran Kunhya via ffmpeg-devel wrote: [...] > Error recovery protocols are complicated - everything is complicated > this project lacks > experience in them The project is made of many developers, and several of them do have experience in protocols and also error correction Just about myself, i have written a teletext decoder that used raw 8bit data over 20 years ago and it was more robust than TV sets I recently as part of the SDR work wrote a RDS decoder, which also worked better than the decoders i compared it to. Its less than 300 lines of code and certainly can be improved alot but there is nothing magic along the lines you suggest here. RDS needs both demodulation and error correction Also i have written a reed solomon decoder based on my own algorithm that had better asymptotic speed than what i could find at the time. > > I have no issue with it being marked experimental. > But the idea of > incremental improvement is false. You have experience with mpeg FEC and other protocols but you mix your practical experience with ridiculous claims > Error recovery implementations > require careful design from the outset with numerous heuristics > needed. Can you please stop this "my way or no way" You can design things first then implement them you can evolutionary write code you can do it incrementally you can write a implementation learn from it discard it and write a 2nd one based on lessons lerned and there are probably hundreads of other paradigms along which you can implement something For some people one way works better than others. For someone else another might work better Someone might enjoy writing, tuning and testing heuristics. Another might have a strong background in probability and statistics and they might design a model about all the restarts and damages and implement an optimal solution for teh model with no heuristics. At that level they can then even tune that model for the particular source of packets and everything adapts to be optimal for that then as there are no or few hardcoded heuristics. Noone ever did that before maybe, ok, but doesnt mean it cannot be done I dont like how you talk down on others, as if what you did is the only way things can be done. thx [...] -- Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB Those who are best at talking, realize last or never when they are wrong. [-- Attachment #1.2: signature.asc --] [-- Type: application/pgp-signature, Size: 195 bytes --] [-- Attachment #2: Type: text/plain, Size: 251 bytes --] _______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".
next prev parent reply other threads:[~2025-01-22 16:37 UTC|newest] Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <20250116200826.33624-1-romain.beauxis@gmail.com> [not found] ` <CABGuwEnazYSuZj5DDDg4T57Qp6jtM8puA7zE=pnq1kC3gCa04Q@mail.gmail.com> [not found] ` <CABWZ6OQLiA-g_+2YaEqrTDuT0PShLQcDtu4ihKUeiEzf9joPRg@mail.gmail.com> [not found] ` <CABGuwEkSD7hTNKVhwU_OXJ6Zku20OtdL=VqK2a4uDQATVYi90g@mail.gmail.com> [not found] ` <CABWZ6OQeQNGy2o40L=-xLm=JhZVNNsbYm=w6ynUfovrMB4co9w@mail.gmail.com> [not found] ` <CABGuwEk62V+yucDsv=yxKADwgk5d3snX2hX=Jg9SjPCb5RxXVw@mail.gmail.com> [not found] ` <CABGuwE=u91r5E+jq=6dMp=hCiM03T-V67ejpqffhBFMC3QfSzQ@mail.gmail.com> [not found] ` <CABWZ6OQOEmmVxDc8S5T6F1P9GAdUXRJ_GYNrbfjyqQjqR6viiw@mail.gmail.com> 2025-01-18 2:22 ` Kieran Kunhya via ffmpeg-devel [not found] ` <a129ff9f-6472-40a9-900f-cf58e133799b@gmail.com> [not found] ` <Z4psWx-rzcXuLu1Y@phare.normalesup.org> [not found] ` <082f12b8-2319-47d2-8854-f361d2039748@gmail.com> [not found] ` <CABGuwEmJbZwGTtn6AtttqYDPpgowuYm-3dX0OrJWs07cr-4usQ@mail.gmail.com> [not found] ` <20250117170823.GM4991@pb2> [not found] ` <CAHGibzFvmw6EjUMhym29AWhEOkgK7ReuWDiWwzC-+csQr-T1GQ@mail.gmail.com> 2025-01-19 22:22 ` Michael Niedermayer 2025-01-20 6:05 ` Kieran Kunhya via ffmpeg-devel 2025-01-20 6:46 ` Kieran Kunhya via ffmpeg-devel 2025-01-22 15:33 ` Michael Niedermayer 2025-01-22 16:29 ` Kieran Kunhya via ffmpeg-devel 2025-01-22 16:53 ` Romain Beauxis 2025-01-22 16:57 ` Kieran Kunhya via ffmpeg-devel 2025-01-20 14:48 ` Nicolas George 2025-01-20 14:30 ` Nicolas George 2025-01-20 15:07 ` James Almer 2025-01-20 16:22 ` Marth64 2025-01-21 22:16 ` Romain Beauxis 2025-01-22 20:36 ` Nicolas George [not found] ` <CABGuwE=Xza3-Jisr1U3AEtLAh2yLLWofsLC+Hbwc_4c1QjLtYA@mail.gmail.com> [not found] ` <20250117170321.GL4991@pb2> [not found] ` <CABGuwEndw2y1cLi-rTnYD1teWuTfd7YCr9_mQkgggqAa0e4jbA@mail.gmail.com> 2025-01-20 14:50 ` Nicolas George 2025-01-20 15:00 ` Kieran Kunhya via ffmpeg-devel 2025-01-22 16:36 ` Michael Niedermayer [this message] 2025-01-22 16:55 ` Kieran Kunhya via ffmpeg-devel 2025-01-22 16:59 ` Kieran Kunhya via ffmpeg-devel 2025-01-22 17:09 ` Kieran Kunhya via ffmpeg-devel 2025-01-22 17:03 ` Kieran Kunhya via ffmpeg-devel 2025-01-23 18:01 ` Romain Beauxis 2025-01-23 18:31 ` Kieran Kunhya via ffmpeg-devel 2025-01-24 18:14 ` Romain Beauxis
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20250122163657.GY4991@pb2 \ --to=michael@niedermayer.cc \ --cc=ffmpeg-devel@ffmpeg.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: link
Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel This inbox may be cloned and mirrored by anyone: git clone --mirror https://master.gitmailbox.com/ffmpegdev/0 ffmpegdev/git/0.git # If you have public-inbox 1.1+ installed, you may # initialize and index your mirror using the following commands: public-inbox-init -V2 ffmpegdev ffmpegdev/ https://master.gitmailbox.com/ffmpegdev \ ffmpegdev@gitmailbox.com public-inbox-index ffmpegdev Example config snippet for mirrors. AGPL code for this site: git clone https://public-inbox.org/public-inbox.git