Re: [FFmpeg-devel] Global options to compile FFmpeg with only audio-related features
Nobody has an idea? Thanks. -Message d'origine- De : ffmpeg-devel [mailto:ffmpeg-devel-boun...@ffmpeg.org] De la part de Cyber Sinh Envoyé : samedi 30 décembre 2017 21:03 À : 'FFmpeg development discussions and patches' <ffmpeg-devel@ffmpeg.org> Objet : Re: [FFmpeg-devel] Global options to compile FFmpeg with only audio-related features Hi Ronald, Checking AVMEDIA_TYPE seems to be the best way to split audio and video codecs. But what is the best way to exclude demuxers and parsers which have no sense for audio (because they are intended to be used only with video/image without audio for example)? Thanks! -Message d'origine- De : ffmpeg-devel [mailto:ffmpeg-devel-boun...@ffmpeg.org] De la part de Ronald S. Bultje Envoyé : samedi 30 décembre 2017 18:15 À : FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Objet : Re: [FFmpeg-devel] Global options to compile FFmpeg with only audio-related features Hi, On Sat, Dec 30, 2017 at 11:28 AM, Derek Buitenhuis < derek.buitenh...@gmail.com> wrote: > On 12/30/2017 4:00 PM, Cyber Sinh wrote: > > What do you think? > > That patches are welcome :). Just to be clear: I'm not OK with a list of audio or video thingies in configure. Similar to the scraping of allcodecs.c, we should be able to classify them based on their AVMEDIA_TYPE and use that classification automatically in configure to do what you say. Just to prevent you from doing a lot of work that won't be upstreamable for maintenance reasons. Ronald ___ 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 ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
Re: [FFmpeg-devel] Global options to compile FFmpeg with only audio-related features
Hi Ronald, Checking AVMEDIA_TYPE seems to be the best way to split audio and video codecs. But what is the best way to exclude demuxers and parsers which have no sense for audio (because they are intended to be used only with video/image without audio for example)? Thanks! -Message d'origine- De : ffmpeg-devel [mailto:ffmpeg-devel-boun...@ffmpeg.org] De la part de Ronald S. Bultje Envoyé : samedi 30 décembre 2017 18:15 À : FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Objet : Re: [FFmpeg-devel] Global options to compile FFmpeg with only audio-related features Hi, On Sat, Dec 30, 2017 at 11:28 AM, Derek Buitenhuis < derek.buitenh...@gmail.com> wrote: > On 12/30/2017 4:00 PM, Cyber Sinh wrote: > > What do you think? > > That patches are welcome :). Just to be clear: I'm not OK with a list of audio or video thingies in configure. Similar to the scraping of allcodecs.c, we should be able to classify them based on their AVMEDIA_TYPE and use that classification automatically in configure to do what you say. Just to prevent you from doing a lot of work that won't be upstreamable for maintenance reasons. Ronald ___ 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
Re: [FFmpeg-devel] Global options to compile FFmpeg with only audio-related features
Hi Derek, I would have already sent one if I could... But I do not know enough bash to code one. I was hoping that a developer could either write one, or at least give directions to do so if my feature request makes sense. Cyber Sinh -Message d'origine- De : ffmpeg-devel [mailto:ffmpeg-devel-boun...@ffmpeg.org] De la part de Derek Buitenhuis Envoyé : samedi 30 décembre 2017 17:29 À : ffmpeg-devel@ffmpeg.org Objet : Re: [FFmpeg-devel] Global options to compile FFmpeg with only audio-related features On 12/30/2017 4:00 PM, Cyber Sinh wrote: > What do you think? That patches are welcome :). - 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
[FFmpeg-devel] Global options to compile FFmpeg with only audio-related features
Hi, I use FFmpeg in an audio-oriented software (for playing and acoustic fingerprinting). So, I want to compile FFmpeg with only: - audio-oriented features to reduce the size (and compilation time) of the lib (eg. bypass video codecs). A feature should be considered as audio-related if it is video-only oriented (eg. A media container which supports audio stream should be considered as an audio feature). - player-oriented features to demux/decode files (not to mux/encode them). Disabling all muxers and encoders is easy: passing “--disable-muxers” and “--disable-encoders” to “configure” is enough. But to enable only audio-oriented features, I have to pass many options (and maintain) to “configure” script: https://github.com/CyberSinh/Luminescence.Audio/blob/master/lib/make/ffmpeg/configure-ffmpeg-msvc.sh It would be great if there was more global options in the “configure” bash script to enable all audio-related (or disable all video-related) features, like (eg. for decoders): --disable-video-decoders --enable-audio-decoders What do you think? Thanks. Cyber Sinh ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
Re: [FFmpeg-devel] [MSVC toolchain] Patch to allow building FFmpeg with Linux bash on Windows (WSL)
Sorry for the diff instead of regular git patch. Here is the patch. -Message d'origine- De : ffmpeg-devel [mailto:ffmpeg-devel-boun...@ffmpeg.org] De la part de wm4 Envoyé : vendredi 29 décembre 2017 12:54 À : ffmpeg-devel@ffmpeg.org Objet : Re: [FFmpeg-devel] [MSVC toolchain] Patch to allow building FFmpeg with Linux bash on Windows (WSL) On Fri, 29 Dec 2017 10:44:21 +0100 Hendrik Leppkes <h.lepp...@gmail.com> wrote: > On Fri, Dec 29, 2017 at 3:43 AM, Cyber Sinh <cyber.s...@free.fr> wrote: > > The attached patch changes the configure script for FFmpeg (and > > associated shell scripts) to call MSVC tools including their > > extensions (cl.exe instead of cl for example). This is necessary, > > because WSL can automatically launch Windows processes from the > > Linux side but only if the process is in the path and includes the > > full name. Linux doesn't automatically append .exe and such to invoke a > > file. > > > > > > The attached file is corrupted. Please ensure its in git format-patch > format. As it is, I can't even read it at all. It's in UTF-16, and just a diff. Yeah, nobody can comfortably read it. ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel 0001-Allow-MSVC-building-under-WSL-Linux-bash-on-Windows-.patch Description: Binary data ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
Re: [FFmpeg-devel] [MSVC toolchain] Patch to allow building FFmpeg with Linux bash on Windows (WSL)
Hi Aaron, - I were not aware of the Gilles Khouzam patch when I make the patch (I read its useful blog post). But feel free to give credits to anyone you want. Adding ".exe" to the end of Windows executables is not rocket science, as you said. - My patch is sufficient to build FFmpeg on bash on Windows. At least on my machine with the current master. The Gilles patch was used for compiling the FFmpegInterop project and was post for one year. - Performance is not the sole benefit of using bash on Windows. We don't have to install/use msys2 which is a pain for Windows user. Sylvain Rougeaux -Message d'origine- De : ffmpeg-devel [mailto:ffmpeg-devel-boun...@ffmpeg.org] De la part de Aaron Levinson Envoyé : vendredi 29 décembre 2017 04:12 À : FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Objet : Re: [FFmpeg-devel] [MSVC toolchain] Patch to allow building FFmpeg with Linux bash on Windows (WSL) On 12/28/2017 6:43 PM, Cyber Sinh wrote: > The attached patch changes the configure script for FFmpeg (and > associated shell scripts) to call MSVC tools including their > extensions (cl.exe instead of cl for example). This is necessary, > because WSL can automatically launch Windows processes from the Linux > side but only if the process is in the path and includes the full > name. Linux doesn't automatically append .exe and such to invoke a file. I haven't confirmed yet that this works in the msys2 environment on Windows, although according to https://blogs.msdn.microsoft.com/gillesk/2016/12/02/building-ffmpeg-using-wsl/ , it supposedly shouldn't cause any issues with building under msys2 or WSL. It appears all of the contents of this patch have been taken from another patch, available at https://github.com/Microsoft/FFmpegInterop/blob/gillesk/wsl/0001-Updating-scripts-to-run-under-WSL.patch , although its reasonable that the author of this patch would have come up with it on their own since it is so simple. It would be reasonable to give credit to Gilles Khouzam in the patch description, if the author of this patch (Cyber Sinh) and Gilles Khouzam are not the same individual. Also, Gilles's patch does more to get FFmpeg to build properly under WSL, so just adding the file extension may not be sufficient to get FFmpeg to build under WSL. On a separate note, building under WSL, as opposed to msys2, seems promising if only from a build performance perspective. According to the blog post, it builds at least twice as fast under WSL than it does with msys2. Aaron Levinson ___ 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
[FFmpeg-devel] [MSVC toolchain] Patch to allow building FFmpeg with Linux bash on Windows (WSL)
The attached patch changes the configure script for FFmpeg (and associated shell scripts) to call MSVC tools including their extensions (cl.exe instead of cl for example). This is necessary, because WSL can automatically launch Windows processes from the Linux side but only if the process is in the path and includes the full name. Linux doesn't automatically append .exe and such to invoke a file. build_with_wsl.diff Description: Binary data ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
