Recherche avancée

Médias (0)

Mot : - Tags -/formulaire

Aucun média correspondant à vos critères n’est disponible sur le site.

Autres articles (31)

  • Use, discuss, criticize

    13 avril 2011, par

    Talk to people directly involved in MediaSPIP’s development, or to people around you who could use MediaSPIP to share, enhance or develop their creative projects.
    The bigger the community, the more MediaSPIP’s potential will be explored and the faster the software will evolve.
    A discussion list is available for all exchanges between users.

  • 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 (...)

  • 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 (3615)

  • Merge commit ’728e80cd2e1d4b7c3e26489efcd77bd7a9e84a99’

    20 mars 2017, par Clément Bœsch
    Merge commit ’728e80cd2e1d4b7c3e26489efcd77bd7a9e84a99’
    

    * commit ’728e80cd2e1d4b7c3e26489efcd77bd7a9e84a99’ :
    High Definition Compatible Digital (HDCD) decoder filter, using libhdcd

    This commit is a noop, we have that code natively.

    Merged-by : Clément Bœsch <u@pkh.me>

  • stop or kill node media server

    9 juillet 2019, par user_66663333

    I am trying to implement stop feature for live video streaming using node-media-server.

    Basically I want to stop node-media-server completely, restart it later.

    const NodeMediaServer = require("node-media-server");
       let config = {
         logType: 3,
         rtmp: {
           port: rtmpPort,
           chunk_size: 60000,
           gop_cache: true,
           ping: 60,
           ping_timeout: 30,
         },
         http: {
           port: httpPort,
           allow_origin: "*",
         },
         relay: {
           ffmpeg: "/usr/bin/ffmpeg",
           tasks: [
             {
               app: "cctv",
               mode: "static",
               edge: "rtsp://" + cameraUrl + "/h264_ulaw.sdp",
               name: "uterum",
               rtsp_transport: "udp",
             },
           ],
         },
       };

       let nms = new NodeMediaServer(config);
       nms.run();
  • How to Manage User Uploaded Content and Storage

    6 novembre 2014, par Ben

    I’m building an app in PHP (Laravel 4 framework) where a teacher in their account can create a digital lesson for a student. Digital lessons can contain the following content :

    • Text (text from form, .doc, .txt, .pdf, etc.)
    • Images (.gif, .png, .jpg etc.)
    • Video (.avi, .mov, .mp4, etc.)
    • Audio (.mp3, etc.)

    Raw text entered from forms can obviously be stored in the DB against the lesson_id. All the other content formats will need to be stored somewhere, where I can manage and read the files, as well as keep track of the teachers storage total as I plan to bill for storage thresholds at 5GB, 10GB etc.

    On the create a lesson page, content files need to be uploaded as lesson attachments before the lesson is saved, so a teacher can visually see all the lessons content, and then hit save to create the lesson instantly.

    Here’s what I’ve come up with :

    1. Upload all lesson file attachments to AWS S3 to the teachers dedicated bucket, before the lesson is created. Add the teachers ID and date time to each filename.

    2. Force all uploaded video / audio files to be converted to .mp4, .mp3, etc. if they are not in an iDevice friendly format or they exceed a file size limit. Use FFmpeg to do this.

    3. When the lesson is saved and created, record the S3 file URL’s against the lesson ID in the DB.

    4. If the lesson has not been created after a specific period of time, run a cron job to check for uploaded S3 files with no lesson and delete them.

    I am unsure what is the best way to solve this problem as user uploaded content management is really new to me.

    What do you think of this approach ? Can you recommend an improved or better way to solve this problem ?