Jul 2, 2023, 23:15 by mich...@niedermayer.cc: > On Sun, Jul 02, 2023 at 08:55:40PM +0200, Lynne wrote: > >> Jul 2, 2023, 13:01 by mich...@niedermayer.cc: >> >> > On Fri, Jun 30, 2023 at 04:38:46PM +0200, Jean-Baptiste Kempf wrote: >> > >> >> On Fri, 30 Jun 2023, at 16:08, Michael Niedermayer wrote: >> >> > Also as said previously, If there is at least a 2nd developer working >> >> > on this then we could & should move this to a seperate libraray >> >> > (libavradio) >> >> >> >> Why wait for a 2nd dev? >> >> >> > >> > as libavradio so far has been the only actionable suggestion. >> > ill move the code to that and next revission or the one after that >> > will be in libavradio. >> > >> > thx >> > >> >> Could you move it to another repository which other developers >> have access to, like nv-codec-headers? It'll still be an official library >> of the project, and patches for it should still be sent to this ML, >> but it would keep the main repo from becoming a monorepo. >> > > Yes > https://git.ffmpeg.org/libavradio > g...@git.ffmpeg.org:libavradio > > everyone should have acess, but keys a syced from videolan a while ago, so > if someones is missing, mail me > > PS: i found a DAB library that i think can take raw IQ data and return > AAC frames. With that adding DAB support should be alot more practical > than a full implementation of all layers of DAB >
Thanks. I look forward to see what becomes of it. Whilst you're at it, could you also make an empty repo for my streaming protocol/container, with the same access permissions? It should be named "avstream", without "lib", as it contains specifications and a reference library, like nut. _______________________________________________ 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".
