>At this point I'm inclined to keep the code separate/private to decklink. >It's limited to AC-3 and only produces packets which are >s16 little endian. At some point I think it would be worthwhile to have some >common code that supports 20/24 bit, both endians, and other codecs like >Dolby-E, but my concern was at this point that would require a bunch of extra >testing (much of which I don't have the >streams or hardware to do), and I >didn't want to lock us permanently into an ABI that I didn't know would meet >our needs long term. > >Moving it from a static function to something that can be shared is a >relatively simple operation, but I want to wait until we have a second use >case prior to refactoring the code.
Fully understand, yes you're right, thank you for the answer. Nicolas _______________________________________________ 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".
