Recherche avancée

Médias (1)

Mot : - Tags -/intégration

Autres articles (69)

  • Supporting all media types

    13 avril 2011, par

    Unlike most software and media-sharing platforms, MediaSPIP aims to manage as many different media types as possible. The following are just a few examples from an ever-expanding list of supported formats : images : png, gif, jpg, bmp and more audio : MP3, Ogg, Wav and more video : AVI, MP4, OGV, mpg, mov, wmv and more text, code and other data : OpenOffice, Microsoft Office (Word, PowerPoint, Excel), web (html, CSS), LaTeX, Google Earth and (...)

  • Keeping control of your media in your hands

    13 avril 2011, par

    The vocabulary used on this site and around MediaSPIP in general, aims to avoid reference to Web 2.0 and the companies that profit from media-sharing.
    While using MediaSPIP, you are invited to avoid using words like "Brand", "Cloud" and "Market".
    MediaSPIP is designed to facilitate the sharing of creative media online, while allowing authors to retain complete control of their work.
    MediaSPIP aims to be accessible to as many people as possible and development is based on expanding the (...)

  • Dépôt de média et thèmes par FTP

    31 mai 2013, par

    L’outil MédiaSPIP traite aussi les média transférés par la voie FTP. Si vous préférez déposer par cette voie, récupérez les identifiants d’accès vers votre site MédiaSPIP et utilisez votre client FTP favori.
    Vous trouverez dès le départ les dossiers suivants dans votre espace FTP : config/ : dossier de configuration du site IMG/ : dossier des média déjà traités et en ligne sur le site local/ : répertoire cache du site web themes/ : les thèmes ou les feuilles de style personnalisées tmp/ : dossier de travail (...)

Sur d’autres sites (11461)

  • Correct load() and play() with new UR parameter, so that subsequent play() call uses new URL (and not URL assigned with original createSound() call.)

    16 septembre 2012, par Scott Schiller

    m script/soundmanager2-jsmin.js m script/soundmanager2-nodebug-jsmin.js m script/soundmanager2-nodebug.js m script/soundmanager2.js Correct load() and play() with new UR parameter, so that subsequent play() call uses new URL (and not URL assigned with original createSound() (...)

  • Android native runtime fails to load symbols even though they are actually found in the loaded .so files

    25 octobre 2017, par Gopinath

    I have compiled ffmpeg v3.4 using NDK v15.2 and I’m creating a wrapper lib called ffmpeg-jni.

    static {
       try {
           System.loadLibrary("avutil");
           System.loadLibrary("avcodec");
           System.loadLibrary("avformat");
           System.loadLibrary("swscale");
           System.loadLibrary("avfilter");
           System.loadLibrary("ffmpeg-jni"); // Exception here line#101
           loadedLibraries = true;
       } catch (Throwable e) {
           e.printStackTrace();
       }
    }

    Below is the exception thrown when loading my wrapper library.

    10-24 11:12:13.819 21499-21499/com.myeglu.android.canary.staging W/System.err: java.lang.UnsatisfiedLinkError: dlopen failed: cannot locate symbol "av_register_all" referenced by "/data/app/com.myeglu.android.canary.staging-2/lib/arm/libffmpeg-jni.so"...

    But, to my surprise, this function is defined in libavformat.so, which loaded successfully ; This is clear from the nm tool outputthat the av_register_all() function is defined (T) in libavformat.so

    Here is a link of all the pre-built libraries that are troubling to make peace at runtime. (There are a few other libraries as well apart from the ffmpeg libs)

    https://drive.google.com/drive/folders/0B20ExoMyOP_UeDhNdmwzc2tjR3M?usp=sharing

    Somebody help me understand what I could be missing in this case. Thanks for your time.

  • Load processed video instead of original video - Rails, Dragonfly

    1er février 2016, par Michael B

    In my Rails 4-Project, I am using Dragonfly to upload images and videos.
    For image-processing I use imagemagick, for videoprocessing I use ffmpeg.

    Videos are uploaded and stored in the folder uploads/videos. After processing, they are stored in public/ffmpeg_videos/

    My question is : How can I use the processed-video instead of the uploaded video ?

    e.g. I use this code in the view, to display a video :

    <video src="&lt;%=@video.video.url%>"></video>

    This successfully loads the original video from the upload-path. But what do I have to change, to load the video from the ffmpeg-path ?

    initializers/dragonfly.rb

    require 'dragonfly'

    # Configure
    Dragonfly.app(:images).configure do
     plugin :imagemagick
     protect_from_dos_attacks false
     secret 'd045734b043b4383a246c5c8daf2d3e31217dc8b030f21861e4fd16c4b72d382'
     url_format '/media/:job/:name'

     datastore :file,
               root_path: Rails.root.join('uploads/images/'),
               server_root: Rails.root.join('uploads')
    end

    Dragonfly.app(:videos).configure do
     secret 'd045734b043b4383a246c5c8daf2d3e31217dc8b030f21861e4fd16c4b72d382'
     url_format "/video/:job/:name"

     datastore :file,
               root_path: Rails.root.join('uploads/videos/'),
               server_root: Rails.root.join('uploads')
    end

    # Logger
    Dragonfly.logger = Rails.logger

    # Mount as middleware
    Rails.application.middleware.use Dragonfly::Middleware, :images
    Rails.application.middleware.use Dragonfly::Middleware, :videos

    # Add model functionality
    if defined?(ActiveRecord::Base)
     ActiveRecord::Base.extend Dragonfly::Model
     ActiveRecord::Base.extend Dragonfly::Model::Validations
    end