That is fair. If that is a requirement / everyone else thinks the same, then I will push on the team making the spec to have it public before I submit a patch to FFmpeg.
On Thu, Jul 6, 2017 at 6:25 PM, Derek Buitenhuis <derek.buitenh...@gmail.com > wrote: > On 7/7/2017 1:36 AM, Louis O'Bryan wrote: > > I am adding a new encoder for camera sensor metadata. This is an > > implementation of a not-yet-published open standard for adding camera > > sensor data to mp4 containers, including the GPS, acceleration, gyro, > > and camera orientation. > > After this change is submitted, I will be sending patches for a decoder > > and usage samples under doc/examples for (de)muxing video/audio/camera > sensor > > data. > > I think it's probably unlikely this will be pushed with no public > standard/draft, > demuxer, or examples. I, for one, am not a fan of this approach. It feels > like > pushing a proprietary format with no known public samples into a FOSS > codebase. > > If this is more of an RFC, though, then that works, IMO. > > - Derek > _______________________________________________ > ffmpeg-devel mailing list > ffmpeg-devel@ffmpeg.org > http://ffmpeg.org/mailman/listinfo/ffmpeg-devel > _______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
