Advanced search

Medias (0)

Tag: - Tags -/formulaire

No media matches your criterion on the site.

Other articles (67)

  • List of compatible distributions

    26 April 2011, by

    The table below is the list of Linux distributions compatible with the automated installation script of MediaSPIP. Distribution nameVersion nameVersion number Debian Squeeze 6.x.x Debian Weezy 7.x.x Debian Jessie 8.x.x Ubuntu The Precise Pangolin 12.04 LTS Ubuntu The Trusty Tahr 14.04
    If you want to help us improve this list, you can provide us access to a machine whose distribution is not mentioned above or send the necessary fixes to add (...)

  • Selection of projects using MediaSPIP

    2 May 2011, by

    The examples below are representative elements of MediaSPIP specific uses for specific projects.
    MediaSPIP farm @ Infini
    The non profit organizationInfini develops hospitality activities, internet access point, training, realizing innovative projects in the field of information and communication technologies and Communication, and hosting of websites. It plays a unique and prominent role in the Brest (France) area, at the national level, among the half-dozen such association. Its members (...)

  • Automated installation script of MediaSPIP

    25 April 2011, by

    To overcome the difficulties mainly due to the installation of server side software dependencies, an "all-in-one" installation script written in bash was created to facilitate this step on a server with a compatible Linux distribution.
    You must have access to your server via SSH and a root account to use it, which will install the dependencies. Contact your provider if you do not have that.
    The documentation of the use of this installation script is available here.
    The code of this (...)

On other websites (9368)

  • ffmpeg scene detection: check only every nth frame?

    4 March 2019, by user978250

    I’m working on a tool with which I can make quick supercuts of longer films.

    I’m using ffmpeg scene detection to split the scenes like this (and then parse the output in Python):

    ffmpeg -i "video.mp4" -filter_complex "select='gt(scene,0.3)',metadata=print:file=_ffScenes.txt" -vsync vfr scn_%%03d.jpg

    Many films have fades, which is a problem with scene detection.

    I don’t need the accuracy, analyzing the file at 1 fps would be sufficient. I tried to lower the input frame rate to 1 fps but the scene detection still checks every frame. How could this be done?

    Thanks!

  • Moved Flash detection to JS

    20 March 2014, by JamesMGreene
    Moved Flash detection to JS

    There are a few distinct but related changes here but they made sense to
    
just tackle together.
    

    Moved Flash detection (including Flash version parsing) into JavaScript.
    
Fixes #138.
    

    Added new `deactivatedFlash` and `overdueFlash` events. These will be
    
changed to an `error` event type in the future along with `noFlash`,
    
`wrongFlash`, etc.
    
Fixes #255.
    

    Standardized non-elemental events to all have `window` as the context
    
(`this`). Fixes #107.
    

    Removed deprecated `ZeroClipboard.detectFlashSupport` method. Fixes #198.

  • Distributing a Python module with ffmpeg dependency

    22 January 2015, by arafasse

    Rookie software developer here. I’m working on a Python module that harnesses some functionality from the FFmpeg framework - specifically, the ebur128 filter function. Ideally the module will stand on its own as an independent, platform agnostic tool for verifying that audio clips comply with EBU loudness standards. It’s being designed so that end users need only perform one simple, (hopefully!) painless installation procedure, which will encompass the installation of both the FFmpeg libraries and my Python wrapper/GUI.

    I apologize for the rather vague question, but does anyone have general advice for creating Python module with external dependencies, or specific advice for standardizing the FFmpeg installation across platforms? Distutils seems pretty helpful – are there other guidelines or standard practices for developing a neatly packaged Python tool? I want to minimize any installation headaches for end users.

    Thanks very much.

Browsing