![]() ![]() If (argc > 1 & strcmp(argv, "segmenter") = 0) For instance, the segmenter seems to be a completely stand-alone program. I keep thinking that it would be possible to solve these problems without modifying ffmpeg. If you want to run a standard ffmpeg for the Air Video server, this is the very first thing it will fail on, complaining that –conversion-id is an unknown argument. ![]() They actually assume that these are the two firstmost command line options (if they are present), and just remove them from the command line argument array before sending it further on to the normal ffmpeg command line processing. The two new command line options are -conversion-id and -port-number. Various other small fixes that might represent actual bugs in ffmpeg, or just be a behaviour that was not suitable for Air Video.Making fixes for building on Mac OS X or Windows.Adding a "segmenter" that chunks the file in parts and send them part by part to the client.Adding a system for merging subtitles on the output stream, complete with two new command line options.My quick analysis is that the changes divide into four parts: This is probably good for having a patch outside the main line, but not good for having a patch that eventually could be merged upstream. I created a patch file, it can be downloaded here: ffmpeg_airvideo.patchįirst of all, the patch is quite "clean" in that all new code are put in separate files, and the smallest possible changes are made in the existing files. On top of this, they had made some patches to the ffmpeg source code (but none to the libswscale source). (The snapshot of the git repository at this commit can be downloaded here.)Īlso, the custom source code bundle included libswscale including this commit. This left me to conclude that the custom ffmpeg was based on the source including this commit. Then I did a quick manual bisecting of git commits, coupled with a manual check if the corresponding changes was or was not present in the Air Video custom ffmpeg source. First I made an intelligent guess on the approximate whereabout of what the custom build was based on, based on the state of the Changelog. I did some digging into ffmpeg's git repository. When I compiled the custom ffmpeg as describe in the previous post, I got curious to the custom build of ffmpeg that was used.
0 Comments
Leave a Reply. |