Recherche avancée

Médias (3)

Mot : - Tags -/plugin

Autres articles (63)

  • Les autorisations surchargées par les plugins

    27 avril 2010, par

    Mediaspip core
    autoriser_auteur_modifier() afin que les visiteurs soient capables de modifier leurs informations sur la page d’auteurs

  • Publier sur MédiaSpip

    13 juin 2013

    Puis-je poster des contenus à partir d’une tablette Ipad ?
    Oui, si votre Médiaspip installé est à la version 0.2 ou supérieure. Contacter au besoin l’administrateur de votre MédiaSpip pour le savoir

  • HTML5 audio and video support

    13 avril 2011, par

    MediaSPIP uses HTML5 video and audio tags to play multimedia files, taking advantage of the latest W3C innovations supported by modern browsers.
    The MediaSPIP player used has been created specifically for MediaSPIP and can be easily adapted to fit in with a specific theme.
    For older browsers the Flowplayer flash fallback is used.
    MediaSPIP allows for media playback on major mobile platforms with the above (...)

Sur d’autres sites (8434)

  • Senior Software Engineer to join Piwik Product Engineering team

    10 janvier 2015, par Matthieu Aubry — Jobs

    At Piwik and Piwik PRO we develop the leading open source web analytics platform, used by more than one million websites worldwide. Our vision is to help the world liberate their analytics data by building the best open alternative to Google Analytics.

    The Piwik platform collects, stores and processes a lot of information : hundreds of millions of data points each month. We create intuitive, simple and beautiful reports that delight our users.

    Are you seeking a new challenge ? We are currently looking for a full time Software Developer to join our small and dedicated Product Engineering team.

    At Piwik PRO we practise agile methodology, test driven development and fast release cycles. The main technologies we work with are PHP5, JavaScript (AngularJS, jQuery) and MySQL and our tools include PhpStorm, Github, Travis CI and Slack.

    As a Software Developer for Piwik PRO, you will be writing open source code that will directly benefit 250,000+ Piwik users in 200+ countries and 50 languages.

    Key Responsibilities

    • Writing server-side code (PHP 5) and front-end code (JavaScript).
    • Creating robust high-volume production applications and developing prototypes quickly.
    • Tackling new problems as we continue to push technology forward.
    • Assisting other developers by writing peer code reviews.
    • Improving and updating our platform developer guides.
    • Lead by example, able to self manage and use initiative to get things done.

    Minimum qualifications

    • Experience in product development, security, the open source philosophy and usable interface design.
    • Understanding of, and practical experience with PHP5 and JavaScript application development.
    • 3+ years experience building successful production software systems.
    • Solid knowledge of testing principles and OOP.
    • Strong analytical and coding skills.
    • Strong written communication.

    Location

    • Offices based in Wellington, New Zealand or Wrocław, Poland.
    • However remote work is also possible.

    Apply online

    To apply for this position, please Apply online here. We look forward to receiving your applications !

  • Senior Software Engineer to join Piwik Product Engineering team

    10 janvier 2015, par Matthieu Aubry — Jobs

    At Piwik and Piwik PRO we develop the leading open source web analytics platform, used by more than one million websites worldwide. Our vision is to help the world liberate their analytics data by building the best open alternative to Google Analytics.

    The Piwik platform collects, stores and processes a lot of information : hundreds of millions of data points each month. We create intuitive, simple and beautiful reports that delight our users.

    Are you seeking a new challenge ? We are currently looking for a full time Software Developer to join our small and dedicated Product Engineering team.

    At Piwik PRO we practise agile methodology, test driven development and fast release cycles. The main technologies we work with are PHP5, JavaScript (AngularJS, jQuery) and MySQL and our tools include PhpStorm, Github, Travis CI and Slack.

    As a Software Developer for Piwik PRO, you will be writing open source code that will directly benefit 250,000+ Piwik users in 200+ countries and 50 languages.

    Key Responsibilities

    • Writing server-side code (PHP 5) and front-end code (JavaScript).
    • Creating robust high-volume production applications and developing prototypes quickly.
    • Tackling new problems as we continue to push technology forward.
    • Assisting other developers by writing peer code reviews.
    • Improving and updating our platform developer guides.
    • Lead by example, able to self manage and use initiative to get things done.

    Minimum qualifications

    • Experience in product development, security, the open source philosophy and usable interface design.
    • Understanding of, and practical experience with PHP5 and JavaScript application development.
    • 3+ years experience building successful production software systems.
    • Solid knowledge of testing principles and OOP.
    • Strong analytical and coding skills.
    • Strong written communication.

    Location

    • Offices based in Wellington, New Zealand or Wrocław, Poland.
    • However remote work is also possible.

    Apply online

    To apply for this position, please Apply online here. We look forward to receiving your applications !

  • How would I dynamically link FFmpeg in a C# Project for use with FFMpegCore ?

    15 octobre 2024, par liamliam

    So far, I have FFMpegCore working in my project with a ffmpeg.exe dropped into the project directory. This works, but for LGPL license compliance FFmpeg requires dynamic linking :
    
Use dynamic linking (on windows, this means linking to dlls) for linking with FFmpeg libraries..

    


    While I understand the basic concept of dynamic vs static linking, my problem is likely a misunderstanding of how .dlls work and how they apply to C# and .NET.
    
Would it be possible to compile ffmpeg into a single .dll that could be accessed by FFMpegCore cross-platform ? From what I can gather in the source, FFMpegCore looks for an ffmpeg or ffmpeg.exe file in its configuration path.

    


    Is it possible to have .NET dynamically link FFmpeg and expose it to libraries for use or is that a complete misunderstanding and would I then need a wrapper library with different capabilities ?

    


    I've attempted to find the answer in the relevant documentation, but I found none for this specific use of either library. I suspect my problem might be a fundamental misunderstanding of how these tools work and work together.
My ideal result would be using FFMpegCore with an FFmpeg.dll that works cross-platform instead of the .exe.

    


    Edit 1 : @taratect's answer and graphic sent me down a path that cleared up quite a bit about exes and dlls. .Net compiles source code down to platform agnostic Intermediate Language in the form of a .dll or .exe(completely different to C++ variants of these files), which is executed by the Common Language Runtime using a Just In Time compiler to convert that Intermediate Language to Machine Code that can be run on the specific platform .Net is installed on. C++(FFmpeg) compiles directly to platform specific Machine Code (as shown in the graphic), confusingly in the form of a .dll or .exe (on Windows). .Net can indeed load and run machine code unmanaged by Common Language Runtime, since everything is run as Machine Code by the end, however memory and other complexities must then be managed by me, which seems to be what FFMpegCore does in wrapping the executable. I might still be confused/incorrect on some of this, unmanaged code is beyond my understanding so far.
This does more or less confirm that FFMpegCore probably can't be expected to use FFmpeg in the way I hoped and a better workaround might be having the user just supply an FFmpeg source or implement a downloader as part of installation so that I don't have to redistribute it at all.