Recherche avancée

Médias (1)

Mot : - Tags -/swfupload

Autres articles (103)

  • Encoding and processing into web-friendly formats

    13 avril 2011, par

    MediaSPIP automatically converts uploaded files to internet-compatible formats.
    Video files are encoded in MP4, Ogv and WebM (supported by HTML5) and MP4 (supported by Flash).
    Audio files are encoded in MP3 and Ogg (supported by HTML5) and MP3 (supported by Flash).
    Where possible, text is analyzed in order to retrieve the data needed for search engine detection, and then exported as a series of image files.
    All uploaded files are stored online in their original format, so you can (...)

  • Les formats acceptés

    28 janvier 2010, par

    Les commandes suivantes permettent d’avoir des informations sur les formats et codecs gérés par l’installation local de ffmpeg :
    ffmpeg -codecs ffmpeg -formats
    Les format videos acceptés en entrée
    Cette liste est non exhaustive, elle met en exergue les principaux formats utilisés : h264 : H.264 / AVC / MPEG-4 AVC / MPEG-4 part 10 m4v : raw MPEG-4 video format flv : Flash Video (FLV) / Sorenson Spark / Sorenson H.263 Theora wmv :
    Les formats vidéos de sortie possibles
    Dans un premier temps on (...)

  • Gestion de la ferme

    2 mars 2010, par

    La ferme est gérée dans son ensemble par des "super admins".
    Certains réglages peuvent être fais afin de réguler les besoins des différents canaux.
    Dans un premier temps il utilise le plugin "Gestion de mutualisation"

Sur d’autres sites (6730)

  • avcodec_encode_video2 crash on MinGW32 (but not on MinGW64)

    27 février 2018, par ksb496

    I have been testing for years a software that I am developing, compiled only for 64-bit systems through Qt-MinGW64, without experiencing any kind of issue regarding video encoding (which is one of the features of such application). Recently, I have been attempting to build the corresponding x86 version of my software by compiling it with Qt-MingGW32.

    However, after bulding the same ffmpeg and x264 library versions to create the 32-bit versions and successfully linking them to my project, the application keeps crashing after few frames are encoded, due to segmentation fault error. This is very strange because, as I indicated before, it works flawlessly when compiled for 64-bit systems.

    I have also lost a considerable amount hours trying to combine a big amount of different versions of both ffmpeg and x264 libraries, but with no luck either. Neither it works when disabling threads both for x264 and ffmpeg libraries, hence it does not seem to be a win32 threading issue. Therefore, I have concluded that the error is most likely in my code, which by some chance beyond my comprehension tells ffmpeg to allocate the right amount of memory in the x64 version, but not in the x86 version.

    It must be pointed out also that before the avcodec_encode_video2 call, I do the following calls, among others, in order to allocate the memory associated to the corresponding items (AVFrame, AVCodec, etc.), such as

    avcodec_open2( my_codec_context, my_codec, &opt );
    my_av_frame=av_frame_alloc();

    More precisely, the details involving the code structure that I am using can be found here.

    Therefore, the error appears to be more subtle than just issues regarding uninitialized memory.

    Many thanks in advance.

    UPDATE :

    I have discovered the focus of the problem. For some reason, FFmpeg/x264 libraries behave abnormally in Win32 GUI applications compiled with Qt-MinGW32, while they run correctly in Win32 console applications, also compiled with Qt-WinGW32. I have proven this claim performing two dummy tests, in which the exact same piece of code is run through a console application and on a GUI application, succeeding in the first case and failing in the latter one. The code for such tests can be found below, along with the x264 and FFmpeg libraries used in my projects, together with instructions to build them in msys2 with MinGW32 :

    https://takeafile.com/?f=hisusinivi

    I have no idea whether it can be solved by simply tweaking the code or it is a serious bug involving an incompatibility issue. If it is the latter, should it be reported to the Qt/FFmpeg/x264 staff as a major bug ?

  • aacenc : use the fast coder as the default

    13 janvier 2018, par Rostislav Pehlivanov
    aacenc : use the fast coder as the default
    

    The twoloop coder sounds decent at low bitrates, however at higher bitrates
    it sounds worse than the fast coder (which used to be the old twoloop coder
    before October 2015) and needs quite a lot more CPU.
    Change the default to fast. It has been well tested and has had little changes
    over the years so its been confirmed to be quite stable.
    Also change its description (not valid for more than a year) and the
    documentation.

    Signed-off-by : Rostislav Pehlivanov <atomnuker@gmail.com>

    • [DH] doc/encoders.texi
    • [DH] libavcodec/aacenc.c
    • [DH] tests/fate/aac.mak
  • Piwik is now Matomo – Announcement

    https://matomo.org/wp-content/uploads/matomo.mp3
    9 janvier 2018, par Matomo Core Team

    You may be surprised to read this announcement, but no stress, take a deep breath, nothing big is going to happen, it is just our name that is changing and here are the reasons why.

    Why are we changing from Piwik to Matomo ?

    “After an epic 10 year journey creating and perfecting the best open digital analytics solution, we felt it was a good time to refresh our brand to reflect how far we have come and to reaffirm our vision :
    To create, as a community, the leading international open source digital analytics platform, that gives every user full control of their data.”

    Matthieu Aubry, creator of Piwik

    As projects evolve, so do names. After 10 years of Piwik and the amazing achievement of building the top open source analytics software that gives every user full control of their data, we are now looking forward to the next chapter. Thus, Piwik, the community project, will now become Matomo. The only change is our name, everything else stays the same.

    This will allow users to take a fresh look at what we’ve become today and acknowledging all of the community’s hard work over the past 10 years. In addition, we also want our name to be unique, ensuring that it is not shared with any other company to remove any possible confusion or affiliations. Piwik is already used on over 1 million websites and with Matomo, we hope to reach our maximum potential.

    With the strong focus on privacy worldwide and the upcoming privacy regulations about to be legislated in Europe, it is clear that we were on the right mission from the very beginning. With the upcoming big release Matomo 4.0 planned for this year, new privacy protections will bring users the tools to be compliant with the GDPR privacy laws. And Matomo will grow in line with these regulations, with a very clear and focused vision.

    Changing our name is an exciting opportunity for us, and we hope you love the name Matomo as much as we do.

    Matomo FAQs

    So what is going to change for me ?

    Well, basically nothing, the name will change but the values stay the same : Matomo (Piwik) will continue to be free and always will be.

    Also the same people stay behind the project. We are motivated more than ever to take this project to the next level.

    Why not keep the name Piwik ?

    For a few reasons, one of which is to ensure that Matomo does not/will not share its name with any other businesses unlike Piwik. We also want to protect the Matomo brand and for it to remain the open source community project name forever.

    Where does the name Matomo come from ?

    We loved the name Piwik and were looking for something that sounded just as good ! Initially we wanted to have an acronym based on key terms, such as Free, Open Source and Privacy, but none really fit us perfectly.

    Until we found Matomo ! Easily pronounced in all languages. Short enough to remember. Concise. And best of all… Matomo means honesty in Japanese. Which aligns with one of our key values – transparency.

    We love the name Matomo and hope you do too.

    What is the vision of Matomo ?

    We have come a long way in those 10 years ! However, our mission statement remains the same :

    “To create, as a community, the leading international open source digital analytics platform, that gives every user full control of their data.”

    Matomo provides a range of amazing and innovative features, allowing you to get a 360 view of your visitors. These insights are invaluable to help understand behavior, keep track of goals, and increase conversion rates and revenue.

    Who will deliver Matomo professional services ?

    Any company who wishes to. The only exception is that no companies will be allowed to have the name Matomo.

    Our company providing professional services is and will remain InnoCraft.

    Where can I follow the Matomo project ?

    Our new website will be matomo.org (automatically redirected from Piwik.org)

    Follow our new Twitter : twitter.com/matomo_org

    Github : github.com/matomo-org

    Facebook : facebook.com/Matomo.org

    Linkedin : linkedin.com/company/matomo/

    If you are already following us on social media, you will be kept up to date with Matomo automatically as all social media accounts will be redirected.

    How should I pronounce Matomo ?

    If you’re wondering how to say ‘Matomo’, you can find out by clicking play :

    Where can I see a demo of Matomo ?

    On demo.matomo.org

    Where can I download Matomo first release ?

    On matomo.org/download

    (Matomo 3.3.0 will be released in the next few days)

    What is the new logo ?

    Check it out below.

    Matomo trademark Policy

    Matomo is an internationally registered trademark of Matthieu Aubry, Founder of Piwik (now Matomo).

    Information about how to use the name Matomo (and logo) can be found here : matomo.org/trademark/

    What are the next big steps ?

    We will keep it simple for our valued users. As it is just a name change, the only thing you will notice is that the Piwik brand will gradually be replaced on the websites you are used to seeing the name on. The first version of Matomo will be available in just a few days for download. The software version numbers stay the same : the next release after Piwik 3.2.1 will be Matomo 3.3.0.

    All our public HTTP APIs and Tracking SDKs will continue working normally. As you can imagine, there is a lot of work and complexity behind slowly updating all the SDKs and keeping backwards compatibility, so our renaming project will take a few weeks to complete.

    The Matomo trademark will later be transferred into the Matomo foundation, a non-profit that will be dedicated to promoting and ensuring access to Matomo and our related open source projects in perpetuity.


    Thank you

    Thank you for continuing to support our project, alongside our 20+ Matomo core team members and more than 500 contributors.

    Please help to spread the word about this announcement by sharing it with friends or or colleagues who may benefit from using Matomo Analytics !

    The post Piwik is now Matomo – Announcement appeared first on Analytics Platform - Matomo.