Re: [FFmpeg-devel] [PATCH 0/6] Patchset to remove ffserver
On 1/6/2018 4:55 PM, Lou Logan wrote: > On Sat, Jan 6, 2018, at 9:42 AM, Rostislav Pehlivanov wrote: >> >> Rebased and pushed, thanks for the reviews > > Would you add a news entry for this? The news was written like a year and a half ago before the removal was postponed a year ago, stating ffserver would be removed in an upcoming release. There's a line in Changelog for the next release about it, so it will be mentioned in the news entry for said release as the Changelog is quoted in those. ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
Re: [FFmpeg-devel] [PATCH 0/6] Patchset to remove ffserver
On Sat, Jan 6, 2018, at 9:42 AM, Rostislav Pehlivanov wrote: > > Rebased and pushed, thanks for the reviews Would you add a news entry for this? ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
Re: [FFmpeg-devel] [PATCH 0/6] Patchset to remove ffserver
On 6 January 2018 at 18:42, Rostislav Pehlivanovwrote: > > > On 21 October 2017 at 19:54, Rostislav Pehlivanov > wrote: > >> This patchset removes the long-deprecated ffserver program and all >> its privately exposed things from libavformat. >> >> Rostislav Pehlivanov (6): >> Remove the ffserver program >> libavformat: remove the ffmenc and ffmdec muxer and demuxers >> libavformat: unexpose the ff_inet_aton function >> libavformat: remove the ff_rtp_get_local_rtcp_port function >> libavformat: unexpose private ff_ functions needed by ffserver >> libavformat/mpjpeg: use "ffmpeg" instead of "ffserver" as boundary tag >> >> .gitignore|1 - >> Changelog |2 + >> MAINTAINERS |3 - >> README.md |2 - >> configure |4 - >> doc/ffmpeg-bitstream-filters.texi |4 +- >> doc/ffmpeg-codecs.texi|4 +- >> doc/ffmpeg-devices.texi |4 +- >> doc/ffmpeg-filters.texi |4 +- >> doc/ffmpeg-formats.texi |4 +- >> doc/ffmpeg-protocols.texi |4 +- >> doc/ffmpeg-resampler.texi |4 +- >> doc/ffmpeg-scaler.texi|4 +- >> doc/ffmpeg-utils.texi |4 +- >> doc/ffmpeg.texi | 18 +- >> doc/ffplay.texi |4 +- >> doc/ffprobe.texi |4 +- >> doc/ffserver.conf | 372 >> doc/ffserver.texi | 923 - >> doc/issue_tracker.txt |3 - >> doc/libavcodec.texi |4 +- >> doc/libavdevice.texi |4 +- >> doc/libavfilter.texi |4 +- >> doc/libavformat.texi |4 +- >> doc/libavutil.texi|4 +- >> doc/libswresample.texi|4 +- >> doc/libswscale.texi |4 +- >> doc/mailing-list-faq.texi |3 +- >> doc/protocols.texi|2 +- >> fftools/Makefile |4 +- >> fftools/ffmpeg_opt.c | 96 +- >> fftools/ffserver.c| 4026 -- >> --- >> fftools/ffserver_config.c | 1325 >> fftools/ffserver_config.h | 155 -- >> libavformat/Makefile |2 - >> libavformat/allformats.c |1 - >> libavformat/ffm.h | 62 - >> libavformat/ffmdec.c | 878 >> libavformat/ffmenc.c | 362 >> libavformat/libavformat.v | 11 - >> libavformat/mpjpeg.c |2 +- >> libavformat/network.h |2 - >> libavformat/os_support.c |6 +- >> libavformat/rtpproto.c|6 - >> libavformat/rtpproto.h|1 - >> tests/Makefile| 10 - >> tests/ffserver-regression.sh | 45 - >> tests/ffserver.conf | 311 --- >> tests/ffserver.regression.ref | 11 - >> tools/bisect-create |2 +- >> 50 files changed, 49 insertions(+), 8674 deletions(-) >> delete mode 100644 doc/ffserver.conf >> delete mode 100644 doc/ffserver.texi >> delete mode 100644 fftools/ffserver.c >> delete mode 100644 fftools/ffserver_config.c >> delete mode 100644 fftools/ffserver_config.h >> delete mode 100644 libavformat/ffm.h >> delete mode 100644 libavformat/ffmdec.c >> delete mode 100644 libavformat/ffmenc.c >> delete mode 100755 tests/ffserver-regression.sh >> delete mode 100644 tests/ffserver.conf >> delete mode 100644 tests/ffserver.regression.ref >> >> -- >> 2.15.0.rc1.287.g2b38de12cc >> >> > Rebased and pushed, thanks for the reviews > btw I suggest people to take a look at klaxa's mkvserver_mk2 https://github.com/klaxa/mkvserver_mk2 Its pretty basic and unstable but look promising. You give it a matroska input and it'll stream it out to clients. ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
Re: [FFmpeg-devel] [PATCH 0/6] Patchset to remove ffserver
On 21 October 2017 at 19:54, Rostislav Pehlivanovwrote: > This patchset removes the long-deprecated ffserver program and all > its privately exposed things from libavformat. > > Rostislav Pehlivanov (6): > Remove the ffserver program > libavformat: remove the ffmenc and ffmdec muxer and demuxers > libavformat: unexpose the ff_inet_aton function > libavformat: remove the ff_rtp_get_local_rtcp_port function > libavformat: unexpose private ff_ functions needed by ffserver > libavformat/mpjpeg: use "ffmpeg" instead of "ffserver" as boundary tag > > .gitignore|1 - > Changelog |2 + > MAINTAINERS |3 - > README.md |2 - > configure |4 - > doc/ffmpeg-bitstream-filters.texi |4 +- > doc/ffmpeg-codecs.texi|4 +- > doc/ffmpeg-devices.texi |4 +- > doc/ffmpeg-filters.texi |4 +- > doc/ffmpeg-formats.texi |4 +- > doc/ffmpeg-protocols.texi |4 +- > doc/ffmpeg-resampler.texi |4 +- > doc/ffmpeg-scaler.texi|4 +- > doc/ffmpeg-utils.texi |4 +- > doc/ffmpeg.texi | 18 +- > doc/ffplay.texi |4 +- > doc/ffprobe.texi |4 +- > doc/ffserver.conf | 372 > doc/ffserver.texi | 923 - > doc/issue_tracker.txt |3 - > doc/libavcodec.texi |4 +- > doc/libavdevice.texi |4 +- > doc/libavfilter.texi |4 +- > doc/libavformat.texi |4 +- > doc/libavutil.texi|4 +- > doc/libswresample.texi|4 +- > doc/libswscale.texi |4 +- > doc/mailing-list-faq.texi |3 +- > doc/protocols.texi|2 +- > fftools/Makefile |4 +- > fftools/ffmpeg_opt.c | 96 +- > fftools/ffserver.c| 4026 -- > --- > fftools/ffserver_config.c | 1325 > fftools/ffserver_config.h | 155 -- > libavformat/Makefile |2 - > libavformat/allformats.c |1 - > libavformat/ffm.h | 62 - > libavformat/ffmdec.c | 878 > libavformat/ffmenc.c | 362 > libavformat/libavformat.v | 11 - > libavformat/mpjpeg.c |2 +- > libavformat/network.h |2 - > libavformat/os_support.c |6 +- > libavformat/rtpproto.c|6 - > libavformat/rtpproto.h|1 - > tests/Makefile| 10 - > tests/ffserver-regression.sh | 45 - > tests/ffserver.conf | 311 --- > tests/ffserver.regression.ref | 11 - > tools/bisect-create |2 +- > 50 files changed, 49 insertions(+), 8674 deletions(-) > delete mode 100644 doc/ffserver.conf > delete mode 100644 doc/ffserver.texi > delete mode 100644 fftools/ffserver.c > delete mode 100644 fftools/ffserver_config.c > delete mode 100644 fftools/ffserver_config.h > delete mode 100644 libavformat/ffm.h > delete mode 100644 libavformat/ffmdec.c > delete mode 100644 libavformat/ffmenc.c > delete mode 100755 tests/ffserver-regression.sh > delete mode 100644 tests/ffserver.conf > delete mode 100644 tests/ffserver.regression.ref > > -- > 2.15.0.rc1.287.g2b38de12cc > > Rebased and pushed, thanks for the reviews ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
Re: [FFmpeg-devel] [PATCH 0/6] Patchset to remove ffserver
On 10/22/2017 7:15 AM, Paul B Mahol wrote: > On 10/22/17, Michael Niedermayerwrote: >> On Sun, Oct 22, 2017 at 10:37:28AM +0200, Clement Boesch wrote: >>> On Sun, Oct 22, 2017 at 02:55:38AM +0200, Michael Niedermayer wrote: On Sat, Oct 21, 2017 at 04:15:37PM -0300, James Almer wrote: > On 10/21/2017 3:54 PM, Rostislav Pehlivanov wrote: >> This patchset removes the long-deprecated ffserver program and all >> its privately exposed things from libavformat. >> >> Rostislav Pehlivanov (6): >> Remove the ffserver program >> libavformat: remove the ffmenc and ffmdec muxer and demuxers >> libavformat: unexpose the ff_inet_aton function >> libavformat: remove the ff_rtp_get_local_rtcp_port function >> libavformat: unexpose private ff_ functions needed by ffserver >> libavformat/mpjpeg: use "ffmpeg" instead of "ffserver" as boundary >> tag > > This set will be applied a month or so from now, when the unstable > ABI > period is over. > > If you can do in a month what was not done in a year plus, anyone is > welcome to fix all ffserver issues or preferably replace it > altogether > with a new tool with a more user friendly syntax/interface. Can you list the technical problems that require dropping ffserver, so that someone interrested in fixing them can do so ? >>> >>> It's probably too late, one month is not enough. We already had that >>> discussion: >>> http://ffmpeg.org/pipermail/ffmpeg-devel/2016-November/203482.html >>> >> >>> The goal was ZERO internal API usage + at least partial FATE coverage. We >>> gave it a year and nothing changed because no one cared. >> >> For reference, the votes text was: (uncut) >> https://ffmpeg.org/pipermail/ffmpeg-devel/2016-November/203561.html >> I propose, and put to the discussion, that the decision to drop >> ffserver >> is revoked, conditioned to the fixing of the technical issues that lead >> to it. >> >> In other words, if the technical problems that require dropping >> ffserver >> are resolved at the time it is about to be dropped, then it must not be >> and the patch is not applied. >> >> I support the decision. Pros: >> >> ffserver has users, if there are no reason to drop it, doing so is a >> gratuitous annoyance to them. >> >> Apparently James Almer opposes the decision. Cons, if I understand >> correctly: >> >> A decision was made, a project should stick to it stubbornly. > > You and Carl should step out as leaders, or we will FORK! Paul, please keep your "funny" remarks on IRC. Develop a sense of time and place for jokes and sarcasm already. ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
Re: [FFmpeg-devel] [PATCH 0/6] Patchset to remove ffserver
On Sun, Oct 22, 2017 at 12:15:25PM +0200, Paul B Mahol wrote: > On 10/22/17, Michael Niedermayerwrote: > > On Sun, Oct 22, 2017 at 10:37:28AM +0200, Clement Boesch wrote: > >> On Sun, Oct 22, 2017 at 02:55:38AM +0200, Michael Niedermayer wrote: > >> > On Sat, Oct 21, 2017 at 04:15:37PM -0300, James Almer wrote: > >> > > On 10/21/2017 3:54 PM, Rostislav Pehlivanov wrote: > >> > > > This patchset removes the long-deprecated ffserver program and all > >> > > > its privately exposed things from libavformat. > >> > > > > >> > > > Rostislav Pehlivanov (6): > >> > > > Remove the ffserver program > >> > > > libavformat: remove the ffmenc and ffmdec muxer and demuxers > >> > > > libavformat: unexpose the ff_inet_aton function > >> > > > libavformat: remove the ff_rtp_get_local_rtcp_port function > >> > > > libavformat: unexpose private ff_ functions needed by ffserver > >> > > > libavformat/mpjpeg: use "ffmpeg" instead of "ffserver" as boundary > >> > > > tag > >> > > > >> > > This set will be applied a month or so from now, when the unstable > >> > > ABI > >> > > period is over. > >> > > > >> > > If you can do in a month what was not done in a year plus, anyone is > >> > > welcome to fix all ffserver issues or preferably replace it > >> > > altogether > >> > > with a new tool with a more user friendly syntax/interface. > >> > > >> > Can you list the technical problems that require dropping ffserver, > >> > so that someone interrested in fixing them can do so ? > >> > >> It's probably too late, one month is not enough. We already had that > >> discussion: > >> http://ffmpeg.org/pipermail/ffmpeg-devel/2016-November/203482.html > >> > > > >> The goal was ZERO internal API usage + at least partial FATE coverage. We > >> gave it a year and nothing changed because no one cared. > > > > For reference, the votes text was: (uncut) > > https://ffmpeg.org/pipermail/ffmpeg-devel/2016-November/203561.html > > I propose, and put to the discussion, that the decision to drop > > ffserver > > is revoked, conditioned to the fixing of the technical issues that lead > > to it. > > > > In other words, if the technical problems that require dropping > > ffserver > > are resolved at the time it is about to be dropped, then it must not be > > and the patch is not applied. > > > > I support the decision. Pros: > > > > ffserver has users, if there are no reason to drop it, doing so is a > > gratuitous annoyance to them. > > > > Apparently James Almer opposes the decision. Cons, if I understand > > correctly: > > > > A decision was made, a project should stick to it stubbornly. > > You and Carl should step out as leaders, or we will FORK! calm down please, the only thing ive said in the whole thread was asking for a list of "technical problems that require dropping ffserver" and for reference posting the uncut text from the last years vote. Which used exactly that phrase. Which was not written by either me nor carl. I had not intended to offend anyone by posting this. I will also post a patch that hopefully fixes partial fate tests for ffserver as that was one of several things suggested. Beyond that i have no plans ATM about ffserver. [...] -- Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB Many things microsoft did are stupid, but not doing something just because microsoft did it is even more stupid. If everything ms did were stupid they would be bankrupt already. signature.asc Description: Digital signature ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
Re: [FFmpeg-devel] [PATCH 0/6] Patchset to remove ffserver
2017-10-22 12:40 GMT+02:00 Clément Bœsch: > Removal was announced, people were aware, we got discussions, > but no one cared enough to do something about it. Wasn't the (only) question what should be done? Carl Eugen ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
Re: [FFmpeg-devel] [PATCH 0/6] Patchset to remove ffserver
On Sun, Oct 22, 2017 at 10:51:38AM +0200, Marton Balint wrote: > > On Sun, 22 Oct 2017, Clément Bœsch wrote: > > > On Sun, Oct 22, 2017 at 02:55:38AM +0200, Michael Niedermayer wrote: > > > On Sat, Oct 21, 2017 at 04:15:37PM -0300, James Almer wrote: > > > > On 10/21/2017 3:54 PM, Rostislav Pehlivanov wrote: > > > > > This patchset removes the long-deprecated ffserver program and all > > > > > its privately exposed things from libavformat. > > > > > > > > > > Rostislav Pehlivanov (6): > > > > > Remove the ffserver program > > > > > libavformat: remove the ffmenc and ffmdec muxer and demuxers > > > > > libavformat: unexpose the ff_inet_aton function > > > > > libavformat: remove the ff_rtp_get_local_rtcp_port function > > > > > libavformat: unexpose private ff_ functions needed by ffserver > > > > > libavformat/mpjpeg: use "ffmpeg" instead of "ffserver" as boundary > > > > > tag > > > > > > > > This set will be applied a month or so from now, when the unstable ABI > > > > period is over. > > > > > > > > If you can do in a month what was not done in a year plus, anyone is > > > > welcome to fix all ffserver issues or preferably replace it altogether > > > > with a new tool with a more user friendly syntax/interface. > > > > > > Can you list the technical problems that require dropping ffserver, > > > so that someone interrested in fixing them can do so ? > > > > It's probably too late, one month is not enough. We already had that > > discussion: > > http://ffmpeg.org/pipermail/ffmpeg-devel/2016-November/203482.html > > > > The goal was ZERO internal API usage + at least partial FATE coverage. We > > gave it a year and nothing changed because no one cared. > > It is natural that people only care if it gets removed otherwise. > July 10th, 2016, ffserver program being dropped After thorough deliberation, we're announcing that we're about to drop the ffserver program from the project starting with the next release. ffserver has been a problematic program to maintain due to its use of internal APIs, which complicated the recent cleanups to the libavformat library, and block further cleanups and improvements which are desired by API users and will be easier to maintain. Furthermore the program has been hard for users to deploy and run due to reliability issues, lack of knowledgable people to help and confusing configuration file syntax. Current users and members of the community are invited to write a replacement program to fill the same niche that ffserver did using the new APIs and to contact us so we may point users to test and contribute to its development. source: ffmpeg.org Removal was announced, people were aware, we got discussions, but no one cared enough to do something about it. -- Clément B. signature.asc Description: PGP signature ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
Re: [FFmpeg-devel] [PATCH 0/6] Patchset to remove ffserver
On 10/22/17, Michael Niedermayerwrote: > On Sun, Oct 22, 2017 at 10:37:28AM +0200, Clement Boesch wrote: >> On Sun, Oct 22, 2017 at 02:55:38AM +0200, Michael Niedermayer wrote: >> > On Sat, Oct 21, 2017 at 04:15:37PM -0300, James Almer wrote: >> > > On 10/21/2017 3:54 PM, Rostislav Pehlivanov wrote: >> > > > This patchset removes the long-deprecated ffserver program and all >> > > > its privately exposed things from libavformat. >> > > > >> > > > Rostislav Pehlivanov (6): >> > > > Remove the ffserver program >> > > > libavformat: remove the ffmenc and ffmdec muxer and demuxers >> > > > libavformat: unexpose the ff_inet_aton function >> > > > libavformat: remove the ff_rtp_get_local_rtcp_port function >> > > > libavformat: unexpose private ff_ functions needed by ffserver >> > > > libavformat/mpjpeg: use "ffmpeg" instead of "ffserver" as boundary >> > > > tag >> > > >> > > This set will be applied a month or so from now, when the unstable >> > > ABI >> > > period is over. >> > > >> > > If you can do in a month what was not done in a year plus, anyone is >> > > welcome to fix all ffserver issues or preferably replace it >> > > altogether >> > > with a new tool with a more user friendly syntax/interface. >> > >> > Can you list the technical problems that require dropping ffserver, >> > so that someone interrested in fixing them can do so ? >> >> It's probably too late, one month is not enough. We already had that >> discussion: >> http://ffmpeg.org/pipermail/ffmpeg-devel/2016-November/203482.html >> > >> The goal was ZERO internal API usage + at least partial FATE coverage. We >> gave it a year and nothing changed because no one cared. > > For reference, the votes text was: (uncut) > https://ffmpeg.org/pipermail/ffmpeg-devel/2016-November/203561.html > I propose, and put to the discussion, that the decision to drop > ffserver > is revoked, conditioned to the fixing of the technical issues that lead > to it. > > In other words, if the technical problems that require dropping > ffserver > are resolved at the time it is about to be dropped, then it must not be > and the patch is not applied. > > I support the decision. Pros: > > ffserver has users, if there are no reason to drop it, doing so is a > gratuitous annoyance to them. > > Apparently James Almer opposes the decision. Cons, if I understand > correctly: > > A decision was made, a project should stick to it stubbornly. You and Carl should step out as leaders, or we will FORK! ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
Re: [FFmpeg-devel] [PATCH 0/6] Patchset to remove ffserver
On Sun, Oct 22, 2017 at 10:37:28AM +0200, Clément Bœsch wrote: > On Sun, Oct 22, 2017 at 02:55:38AM +0200, Michael Niedermayer wrote: > > On Sat, Oct 21, 2017 at 04:15:37PM -0300, James Almer wrote: > > > On 10/21/2017 3:54 PM, Rostislav Pehlivanov wrote: > > > > This patchset removes the long-deprecated ffserver program and all > > > > its privately exposed things from libavformat. > > > > > > > > Rostislav Pehlivanov (6): > > > > Remove the ffserver program > > > > libavformat: remove the ffmenc and ffmdec muxer and demuxers > > > > libavformat: unexpose the ff_inet_aton function > > > > libavformat: remove the ff_rtp_get_local_rtcp_port function > > > > libavformat: unexpose private ff_ functions needed by ffserver > > > > libavformat/mpjpeg: use "ffmpeg" instead of "ffserver" as boundary tag > > > > > > This set will be applied a month or so from now, when the unstable ABI > > > period is over. > > > > > > If you can do in a month what was not done in a year plus, anyone is > > > welcome to fix all ffserver issues or preferably replace it altogether > > > with a new tool with a more user friendly syntax/interface. > > > > Can you list the technical problems that require dropping ffserver, > > so that someone interrested in fixing them can do so ? > > It's probably too late, one month is not enough. We already had that > discussion: > http://ffmpeg.org/pipermail/ffmpeg-devel/2016-November/203482.html > > The goal was ZERO internal API usage + at least partial FATE coverage. We > gave it a year and nothing changed because no one cared. For reference, the votes text was: (uncut) https://ffmpeg.org/pipermail/ffmpeg-devel/2016-November/203561.html I propose, and put to the discussion, that the decision to drop ffserver is revoked, conditioned to the fixing of the technical issues that lead to it. In other words, if the technical problems that require dropping ffserver are resolved at the time it is about to be dropped, then it must not be and the patch is not applied. I support the decision. Pros: ffserver has users, if there are no reason to drop it, doing so is a gratuitous annoyance to them. Apparently James Almer opposes the decision. Cons, if I understand correctly: A decision was made, a project should stick to it stubbornly. [...] -- Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB I have often repented speaking, but never of holding my tongue. -- Xenocrates signature.asc Description: Digital signature ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
Re: [FFmpeg-devel] [PATCH 0/6] Patchset to remove ffserver
On Sun, 22 Oct 2017, Clément Bœsch wrote: On Sun, Oct 22, 2017 at 02:55:38AM +0200, Michael Niedermayer wrote: On Sat, Oct 21, 2017 at 04:15:37PM -0300, James Almer wrote: On 10/21/2017 3:54 PM, Rostislav Pehlivanov wrote: This patchset removes the long-deprecated ffserver program and all its privately exposed things from libavformat. Rostislav Pehlivanov (6): Remove the ffserver program libavformat: remove the ffmenc and ffmdec muxer and demuxers libavformat: unexpose the ff_inet_aton function libavformat: remove the ff_rtp_get_local_rtcp_port function libavformat: unexpose private ff_ functions needed by ffserver libavformat/mpjpeg: use "ffmpeg" instead of "ffserver" as boundary tag This set will be applied a month or so from now, when the unstable ABI period is over. If you can do in a month what was not done in a year plus, anyone is welcome to fix all ffserver issues or preferably replace it altogether with a new tool with a more user friendly syntax/interface. Can you list the technical problems that require dropping ffserver, so that someone interrested in fixing them can do so ? It's probably too late, one month is not enough. We already had that discussion: http://ffmpeg.org/pipermail/ffmpeg-devel/2016-November/203482.html The goal was ZERO internal API usage + at least partial FATE coverage. We gave it a year and nothing changed because no one cared. It is natural that people only care if it gets removed otherwise. A list is important so anybody interested can estimate the amount of work needed. What abouth the ffmenc/ffmdec? That needs to go as well? Or if internal api usage is fixed, and some fate coverate is added, ffmenc and ffmdec can stay? Thanks, Marton ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
Re: [FFmpeg-devel] [PATCH 0/6] Patchset to remove ffserver
On Sun, Oct 22, 2017 at 02:55:38AM +0200, Michael Niedermayer wrote: > On Sat, Oct 21, 2017 at 04:15:37PM -0300, James Almer wrote: > > On 10/21/2017 3:54 PM, Rostislav Pehlivanov wrote: > > > This patchset removes the long-deprecated ffserver program and all > > > its privately exposed things from libavformat. > > > > > > Rostislav Pehlivanov (6): > > > Remove the ffserver program > > > libavformat: remove the ffmenc and ffmdec muxer and demuxers > > > libavformat: unexpose the ff_inet_aton function > > > libavformat: remove the ff_rtp_get_local_rtcp_port function > > > libavformat: unexpose private ff_ functions needed by ffserver > > > libavformat/mpjpeg: use "ffmpeg" instead of "ffserver" as boundary tag > > > > This set will be applied a month or so from now, when the unstable ABI > > period is over. > > > > If you can do in a month what was not done in a year plus, anyone is > > welcome to fix all ffserver issues or preferably replace it altogether > > with a new tool with a more user friendly syntax/interface. > > Can you list the technical problems that require dropping ffserver, > so that someone interrested in fixing them can do so ? It's probably too late, one month is not enough. We already had that discussion: http://ffmpeg.org/pipermail/ffmpeg-devel/2016-November/203482.html The goal was ZERO internal API usage + at least partial FATE coverage. We gave it a year and nothing changed because no one cared. -- Clément B. signature.asc Description: PGP signature ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
Re: [FFmpeg-devel] [PATCH 0/6] Patchset to remove ffserver
On 10/21/2017 9:55 PM, Michael Niedermayer wrote: > On Sat, Oct 21, 2017 at 04:15:37PM -0300, James Almer wrote: >> On 10/21/2017 3:54 PM, Rostislav Pehlivanov wrote: >>> This patchset removes the long-deprecated ffserver program and all >>> its privately exposed things from libavformat. >>> >>> Rostislav Pehlivanov (6): >>> Remove the ffserver program >>> libavformat: remove the ffmenc and ffmdec muxer and demuxers >>> libavformat: unexpose the ff_inet_aton function >>> libavformat: remove the ff_rtp_get_local_rtcp_port function >>> libavformat: unexpose private ff_ functions needed by ffserver >>> libavformat/mpjpeg: use "ffmpeg" instead of "ffserver" as boundary tag >> >> This set will be applied a month or so from now, when the unstable ABI >> period is over. >> >> If you can do in a month what was not done in a year plus, anyone is >> welcome to fix all ffserver issues or preferably replace it altogether >> with a new tool with a more user friendly syntax/interface. > > Can you list the technical problems that require dropping ffserver, > so that someone interrested in fixing them can do so ? They have been listed in both the November 2016 discussion/vote thread and i think in the bump patch i sent last month as well. The most important one is of course the usage of internal API. Then there's https://ffmpeg.org/pipermail/ffmpeg-devel/2016-December/203926.html If anyone actually cared about ffserver, one think it would be fixed by now... ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
Re: [FFmpeg-devel] [PATCH 0/6] Patchset to remove ffserver
On Sat, Oct 21, 2017 at 04:15:37PM -0300, James Almer wrote: > On 10/21/2017 3:54 PM, Rostislav Pehlivanov wrote: > > This patchset removes the long-deprecated ffserver program and all > > its privately exposed things from libavformat. > > > > Rostislav Pehlivanov (6): > > Remove the ffserver program > > libavformat: remove the ffmenc and ffmdec muxer and demuxers > > libavformat: unexpose the ff_inet_aton function > > libavformat: remove the ff_rtp_get_local_rtcp_port function > > libavformat: unexpose private ff_ functions needed by ffserver > > libavformat/mpjpeg: use "ffmpeg" instead of "ffserver" as boundary tag > > This set will be applied a month or so from now, when the unstable ABI > period is over. > > If you can do in a month what was not done in a year plus, anyone is > welcome to fix all ffserver issues or preferably replace it altogether > with a new tool with a more user friendly syntax/interface. Can you list the technical problems that require dropping ffserver, so that someone interrested in fixing them can do so ? [...] -- Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB Let us carefully observe those good qualities wherein our enemies excel us and endeavor to excel them, by avoiding what is faulty, and imitating what is excellent in them. -- Plutarch signature.asc Description: Digital signature ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
Re: [FFmpeg-devel] [PATCH 0/6] Patchset to remove ffserver
On 10/21/2017 3:54 PM, Rostislav Pehlivanov wrote: > This patchset removes the long-deprecated ffserver program and all > its privately exposed things from libavformat. > > Rostislav Pehlivanov (6): > Remove the ffserver program > libavformat: remove the ffmenc and ffmdec muxer and demuxers > libavformat: unexpose the ff_inet_aton function > libavformat: remove the ff_rtp_get_local_rtcp_port function > libavformat: unexpose private ff_ functions needed by ffserver > libavformat/mpjpeg: use "ffmpeg" instead of "ffserver" as boundary tag This set will be applied a month or so from now, when the unstable ABI period is over. If you can do in a month what was not done in a year plus, anyone is welcome to fix all ffserver issues or preferably replace it altogether with a new tool with a more user friendly syntax/interface. ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
Re: [FFmpeg-devel] [PATCH 0/6] Patchset to remove ffserver
On 10/21/17, Rostislav Pehlivanovwrote: > This patchset removes the long-deprecated ffserver program and all > its privately exposed things from libavformat. > > Rostislav Pehlivanov (6): > Remove the ffserver program > libavformat: remove the ffmenc and ffmdec muxer and demuxers > libavformat: unexpose the ff_inet_aton function > libavformat: remove the ff_rtp_get_local_rtcp_port function > libavformat: unexpose private ff_ functions needed by ffserver > libavformat/mpjpeg: use "ffmpeg" instead of "ffserver" as boundary tag > OK ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
[FFmpeg-devel] [PATCH 0/6] Patchset to remove ffserver
This patchset removes the long-deprecated ffserver program and all its privately exposed things from libavformat. Rostislav Pehlivanov (6): Remove the ffserver program libavformat: remove the ffmenc and ffmdec muxer and demuxers libavformat: unexpose the ff_inet_aton function libavformat: remove the ff_rtp_get_local_rtcp_port function libavformat: unexpose private ff_ functions needed by ffserver libavformat/mpjpeg: use "ffmpeg" instead of "ffserver" as boundary tag .gitignore|1 - Changelog |2 + MAINTAINERS |3 - README.md |2 - configure |4 - doc/ffmpeg-bitstream-filters.texi |4 +- doc/ffmpeg-codecs.texi|4 +- doc/ffmpeg-devices.texi |4 +- doc/ffmpeg-filters.texi |4 +- doc/ffmpeg-formats.texi |4 +- doc/ffmpeg-protocols.texi |4 +- doc/ffmpeg-resampler.texi |4 +- doc/ffmpeg-scaler.texi|4 +- doc/ffmpeg-utils.texi |4 +- doc/ffmpeg.texi | 18 +- doc/ffplay.texi |4 +- doc/ffprobe.texi |4 +- doc/ffserver.conf | 372 doc/ffserver.texi | 923 - doc/issue_tracker.txt |3 - doc/libavcodec.texi |4 +- doc/libavdevice.texi |4 +- doc/libavfilter.texi |4 +- doc/libavformat.texi |4 +- doc/libavutil.texi|4 +- doc/libswresample.texi|4 +- doc/libswscale.texi |4 +- doc/mailing-list-faq.texi |3 +- doc/protocols.texi|2 +- fftools/Makefile |4 +- fftools/ffmpeg_opt.c | 96 +- fftools/ffserver.c| 4026 - fftools/ffserver_config.c | 1325 fftools/ffserver_config.h | 155 -- libavformat/Makefile |2 - libavformat/allformats.c |1 - libavformat/ffm.h | 62 - libavformat/ffmdec.c | 878 libavformat/ffmenc.c | 362 libavformat/libavformat.v | 11 - libavformat/mpjpeg.c |2 +- libavformat/network.h |2 - libavformat/os_support.c |6 +- libavformat/rtpproto.c|6 - libavformat/rtpproto.h|1 - tests/Makefile| 10 - tests/ffserver-regression.sh | 45 - tests/ffserver.conf | 311 --- tests/ffserver.regression.ref | 11 - tools/bisect-create |2 +- 50 files changed, 49 insertions(+), 8674 deletions(-) delete mode 100644 doc/ffserver.conf delete mode 100644 doc/ffserver.texi delete mode 100644 fftools/ffserver.c delete mode 100644 fftools/ffserver_config.c delete mode 100644 fftools/ffserver_config.h delete mode 100644 libavformat/ffm.h delete mode 100644 libavformat/ffmdec.c delete mode 100644 libavformat/ffmenc.c delete mode 100755 tests/ffserver-regression.sh delete mode 100644 tests/ffserver.conf delete mode 100644 tests/ffserver.regression.ref -- 2.15.0.rc1.287.g2b38de12cc ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel