I'm just a user, I haven't written any actual code for ffmpeg, but I have gotten used to some of it in my own program, I do agree that it would be cool to have that encoder metadata exposed as part of a function, but I have no authority over what they do (well it's open source so no one has actual control over others, but you know what I mean)
The best person to talk about this would be either Carl Eugen, or Michael Niedermayer On Wed, Jul 16, 2014 at 11:28 PM, Joakim Ziegler <[email protected]> wrote: > Ok, thank you. > > This doesn't sound very hard to do myself (I'll probably just do it > afterwards instead of changing the ffmpeg code, so I don't have to maintain > that patch). > > If I could make a suggestion, it might be something that would be good to > have in ffmpeg, though, perhaps as a part of -movflags. > > Or, if no one is interested in adding it, would you take a patch? I might > have time to do something at some point. > > > -- > Joakim Ziegler - Supervisor de postproducción - Terminal > [email protected] - 044 55 2971 8514 - 5264 0864 > > On 16/07/14, 11:26, Marcus Johnson wrote: > >> you can't, it's hardcoded, you yourself can in your program that you're >> calling the libX functions with make a function that writes "H.264" to the >> encoder field after it's finished, it wouldn't really be that hard to do. >> >> or you could create a script to replace the bytes at X to Y with string Z, >> just make sure the file works properly because it may have to have the >> header field size updated, dig into the h.264 header specs to find out how >> specifically to do this. >> _______________________________________________ >> ffmpeg-user mailing list >> [email protected] >> http://ffmpeg.org/mailman/listinfo/ffmpeg-user >> >> _______________________________________________ > ffmpeg-user mailing list > [email protected] > http://ffmpeg.org/mailman/listinfo/ffmpeg-user > _______________________________________________ ffmpeg-user mailing list [email protected] http://ffmpeg.org/mailman/listinfo/ffmpeg-user
