On Sat, Oct 23, 2021 at 09:18:46PM -0400, Leo Izen wrote: > On Fri, Oct 22, 2021 at 5:38 PM Michael Niedermayer > <mich...@niedermayer.cc> wrote: > > its 2 separate libraries they are often shiped by distributions in > > separate packages. libavformat can depend on libavcodec but not the > > other way around. libavcodec could get upgraded without libavformat > > separate patches make it more natural to keep this clean and working > > if a patch chages both its a hint something might be intermingled > I see, I'll split it into a libavcodec patch that handles the codec > only, and then a libavformat patch for the muxers/demuxers. > > >Is there some public format spec of this ? > I will have to reverse-engineer the libjxl code, since the spec is > copyrighted and I can't access it. It might be available for a number > of CHF but I can't afford it. > > Speaking of the bitstream format, this is starting to get a lot of > code in the prober, mostly because of how permissive JXL codestreams > are. I'm thinking that it might make sense to write a parser for Jpeg > XL in libavcodec, and then have libavformat's jpegxl prober just call > some of that same code. Thoughts?
possible, it does add some extra complexity though thx [...] -- Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB Why not whip the teacher when the pupil misbehaves? -- Diogenes of Sinope
signature.asc
Description: PGP signature
_______________________________________________ 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".
