On Sat, 9 May 2015 10:19:40 +0200 Nicolas George <geo...@nsup.org> wrote:
> Le nonidi 19 floréal, an CCXXIII, wm4 a écrit : > > The problem is that this code was written with ffmpeg.c in mind, so you > > assumed that it was fine to open new files inside of libavformat, and > > you had to add an option to let ffmpeg.c "fix" the hardcoded policy if > > needed. > > Not at all. "use_absolute_path" is a demuxer options, just like any other > demuxer option. The only thing ffmpeg-specific in Carl Eugen's patch is to > write it with a dash. > Even if you say so... this design still doesn't make a lot of sense. FFmpeg supports custom IO, yet it will just open new files using its own IO behind the API user's back in some cases. FFmpeg also imposes its own security policy about which other files can be opened, and the API user can do almost nothing about it. What I'm suggesting would fix all of this. _______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
