sön 2023-07-23 klockan 16:01 -0300 skrev James Almer:
> What bothers me is that even though it's added outside of lavd, it's 
> being added as a brand new lavd, with all the drawbacks this implies,
> including it being tied to lavf in an awful way. And all for a single
> "device" AVInputFormat. It's completely overkill.
> 
> Why is this libavradio not designed as a standalone library, with its
> own, carefully designed API for general radio usage, that can be then
> glued to lavd as an AVInputFormat relying on said external library? 

Such libraries already exist. Libraries that need talented developers
working on them. Something that I have already suggested, but it
appears to be falling on deaf ears. Which is a shame.

GNU Radio Companion can be used to generate Python code that does
everything that avradio tries to do, including GUI code. This code can
then be further massaged to one's individual needs, the heavy lifting
already being handled by gnuradio's DSP stuff.

/Tomas

_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel

To unsubscribe, visit link above, or email
ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".

Reply via email to