Recherche avancée

Médias (1)

Mot : - Tags -/vidéo

Autres articles (77)

  • Websites made ​​with MediaSPIP

    2 mai 2011, par

    This page lists some websites based on MediaSPIP.

  • Mise à jour de la version 0.1 vers 0.2

    24 juin 2013, par

    Explications des différents changements notables lors du passage de la version 0.1 de MediaSPIP à la version 0.3. Quelles sont les nouveautés
    Au niveau des dépendances logicielles Utilisation des dernières versions de FFMpeg (>= v1.2.1) ; Installation des dépendances pour Smush ; Installation de MediaInfo et FFprobe pour la récupération des métadonnées ; On n’utilise plus ffmpeg2theora ; On n’installe plus flvtool2 au profit de flvtool++ ; On n’installe plus ffmpeg-php qui n’est plus maintenu au (...)

  • Creating farms of unique websites

    13 avril 2011, par

    MediaSPIP platforms can be installed as a farm, with a single "core" hosted on a dedicated server and used by multiple websites.
    This allows (among other things) : implementation costs to be shared between several different projects / individuals rapid deployment of multiple unique sites creation of groups of like-minded sites, making it possible to browse media in a more controlled and selective environment than the major "open" (...)

Sur d’autres sites (8886)

  • Attempting to compile FFmpeg 4.2.3 statically for Windows 10 (x86_64), but binaries asks for missing DLLs

    29 mai 2020, par Expectator

    I am using Msys MinGW (x86_64) and pulled a snapshot of the latest major release of FFmpeg off of their website. Here is my ./configure options. I plan to use the binaries on both the computer that I compiled it on, and other Windows computers that I own.

    



    ./configure --enable-libaom --enable-avisynth --enable-chromaprint --enable-libdav1d --enable-libdavs2 --enable-libgme --enable-libmfx --enable-libkvazaar --enable-libmp3lame --enable-libilbc --enable-libvpx --enable-libmodplug --enable-version3 --enable-nonfree --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libvo-amrwbenc --enable-libfdk-aac --enable-libopenh264 --enable-libopenjpeg --enable-nvenc --enable-nvdec --enable-cuda --enable-cuvid --enable-libtwolame --enable-vapoursynth --enable-libwavpack --enable-libx264 --enable-libx265 --enable-libxavs --enable-libxavs2 --enable-gpl --enable-static --disable-shared


    



    Output of configure script (pastebin)

    



    Output of uname -a (in Msys)

    



    MINGW64_NT-10.0-18362 <scrubbed> 3.1.4-340.x86_64 2020-05-22 08:28 UTC x86_64 Msys&#xA;</scrubbed>

    &#xA;&#xA;

    The issue that I'm facing is that despite passing the options --enable-static and --disable-shared, the executables generated still require libchromaprint.dll, libfdk-aac-2.dll, and libgme.dll to run. What I expected was that FFmpeg would execute independently of any DLL files since I passed those options to ./configure.

    &#xA;

  • how to send the input data to FFMPEG from a C# program

    18 octobre 2020, par jstuardo

    I need to send a binary stream to FFMPEG so that it sends to an RTMP server.

    &#xA;

    I did it in a nodejs script using socket.io library and in Linux. It works perfectly.

    &#xA;

    I need to do the same, but in a Windows Forms application using C#.

    &#xA;

    This is how I run the ffmpeg.exe application :

    &#xA;

            _currentProcess = new Process();&#xA;        _currentProcess.StartInfo.FileName = _ffmpegExe;&#xA;        _currentProcess.StartInfo.Arguments = BuildOptions(framesPerSecond, audioBitRate, audioEncoding, rtmpServer);&#xA;        _currentProcess.StartInfo.UseShellExecute = false;&#xA;        _currentProcess.StartInfo.CreateNoWindow = true;&#xA;        _currentProcess.StartInfo.RedirectStandardInput = true;&#xA;        _currentProcess.StartInfo.RedirectStandardError = true;&#xA;        _currentProcess.ErrorDataReceived &#x2B;= CurrentProcess_ErrorDataReceived;&#xA;        _currentProcess.Start();&#xA;        _currentProcess.BeginErrorReadLine();&#xA;

    &#xA;

    BuildOptions method is defined this way :

    &#xA;

        private string BuildOptions(int framesPerSecond, int audioBitRate, string audioEncoding, string rtmpServer)&#xA;    {&#xA;        string options;&#xA;        if (framesPerSecond == 1)&#xA;        {&#xA;            options = $"-i - -c:v libx264 -preset ultrafast -tune zerolatency -r 1 -g 2 -keyint_min 2 -x264opts keyint=2 -crf 25 -pix_fmt yuv420p -profile:v baseline -level 3 -c:a aac -b:a {audioEncoding} -ar {audioBitRate}-f flv {rtmpServer}";&#xA;        }&#xA;        else if (framesPerSecond == 15)&#xA;        {&#xA;            options = $"-i - -c:v libx264 -preset ultrafast -tune zerolatency max_muxing_queue_size 1000 -bufsize 5000 -r 15 -g 30 -keyint_min 30 -x264opts keyint=30 -crf 25 -pix_fmt yuv420p -profile:v baseline -level 3 -c:a aac -b:a {audioEncoding} -ar {audioBitRate} -f flv {rtmpServer}";&#xA;        }&#xA;        else&#xA;        {&#xA;            options = $"-i - -c:v libx264 -preset ultrafast -tune zerolatency -c:a aac -ar {audioBitRate} -b:a {audioEncoding} -bufsize 5000 -f flv {rtmpServer}";&#xA;        }&#xA;&#xA;        return options;&#xA;    }&#xA;

    &#xA;

    I am sending the data to the standard input this way :

    &#xA;

        public void EncodeAndSend(byte[] data)&#xA;    {&#xA;        if (_currentProcess != null)&#xA;        {&#xA;            var streamWriter = _currentProcess.StandardInput;&#xA;            streamWriter.Write(Encoding.GetEncoding("ISO-8859-1").GetChars(data));&#xA;        }&#xA;    }&#xA;

    &#xA;

    And finally, this method is for receiving the standard error which receives the result from ffmpeg.exe :

    &#xA;

        private void CurrentProcess_ErrorDataReceived(object sender, DataReceivedEventArgs e)&#xA;    {&#xA;        Console.WriteLine(e.Data);&#xA;    }&#xA;

    &#xA;

    When I run the application, this is shown in the console :

    &#xA;

    ffmpeg version 4.3.1-2020-10-01-essentials_build-www.gyan.dev Copyright (c) 2000-2020 the FFmpeg developers&#xA;  built with gcc 10.2.0 (Rev3, Built by MSYS2 project)&#xA;  configuration: --enable-gpl --enable-version3 --enable-static --disable-w32threads --disable-autodetect --enable-fontconfig --enable-iconv --enable-gnutls --enable-libxml2 --enable-gmp --enable-lzma --enable-zlib --enable-libsrt --enable-libssh --enable-libzmq --enable-avisynth --enable-sdl2 --enable-libwebp --enable-libx264 --enable-libx265 --enable-libxvid --enable-libaom --enable-libopenjpeg --enable-libvpx --enable-libass --enable-libfreetype --enable-libfribidi --enable-libvidstab --enable-libvmaf --enable-libzimg --enable-amf --enable-cuda-llvm --enable-cuvid --enable-ffnvcodec --enable-nvdec --enable-nvenc --enable-d3d11va --enable-dxva2 --enable-libmfx --enable-libgme --enable-libopenmpt --enable-libopencore-amrwb --enable-libmp3lame --enable-libtheora --enable-libvo-amrwbenc --enable-libgsm --enable-libopencore-amrnb --enable-libopus --enable-libspeex --enable-libvorbis --enable-librubberband&#xA;  libavutil      56. 51.100 / 56. 51.100&#xA;  libavcodec     58. 91.100 / 58. 91.100&#xA;  libavformat    58. 45.100 / 58. 45.100&#xA;  libavdevice    58. 10.100 / 58. 10.100&#xA;  libavfilter     7. 85.100 /  7. 85.100&#xA;  libswscale      5.  7.100 /  5.  7.100&#xA;  libswresample   3.  7.100 /  3.  7.100&#xA;  libpostproc    55.  7.100 / 55.  7.100&#xA;pipe:: Invalid data found when processing input&#xA;

    &#xA;

    If I change the EncodeAndSend method to be :

    &#xA;

        public void EncodeAndSend(byte[] data)&#xA;    {&#xA;        if (_currentProcess != null)&#xA;        {&#xA;            var streamWriter = _currentProcess.StandardInput;&#xA;            streamWriter.Write(data);&#xA;        }&#xA;    }&#xA;

    &#xA;

    pipe:: Invalid data found when processing input error is not produced, but no more outputs are shown so it seems it is not working.

    &#xA;

    What is wrong with this ? how can I send the data to the FFMPEG process ?

    &#xA;

    Finally, I tell you that the binary stream comes from the camera by mean of MediaRecorder in a web page (the same used for my program in nodejs server, so that it is not the issue here)

    &#xA;

  • Matomo Further Invests in Security by Doubling Bug Bounty Rewards

    7 janvier 2022, par erin — Community, Press Releases

    Matomo is the leading open-source analytics solution free from data limitations. 

    As our mission states, we aim to create, as a community, the leading open digital analytics platform that gives every user full control of their data. 

    To do this, we operate a Security Bug Bounty Programme. This programme is designed to reward the hard work of skilled security researchers who sacrifice their time and energy to find and report security and vulnerabilities. 

    To continue our investment in security, privacy and transparency, we are increasing the security bug bounty reward to as much as $10,000 USD. This is an increase of 100% from our previous 2020 bug bounty announcement.

    How much can I earn for reporting security bugs ?

    Reward amounts vary depending on the impact :

    • Low issues receive $222
    • Medium issues receive $555
    • High issues receive $1,000
    • Critical issues receive $10,000

    How can I take part ? 

    As of January 2022, global independent security researchers have identified and suggested 138 security related improvements. If you are interested in joining this growing community, head to our Security Bug Bounty Programme to find out how you can take part. 

    We thank you for keeping Matomo safe for our users and theirs.

    About Matomo

    Matomo is the leading open-source analytics solution free from data limitations. Make more informed decisions and enhance your customer experience while ensuring data privacy and ownership. Matomo is the trusted solution for over 1.5 million websites globally. Take back control of your data ownership and challenge the status quo.