Recherche avancée

Médias (1)

Mot : - Tags -/Rennes

Autres articles (75)

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

  • Support de tous types de médias

    10 avril 2011

    Contrairement à beaucoup de logiciels et autres plate-formes modernes de partage de documents, MediaSPIP a l’ambition de gérer un maximum de formats de documents différents qu’ils soient de type : images (png, gif, jpg, bmp et autres...) ; audio (MP3, Ogg, Wav et autres...) ; vidéo (Avi, MP4, Ogv, mpg, mov, wmv et autres...) ; contenu textuel, code ou autres (open office, microsoft office (tableur, présentation), web (html, css), LaTeX, Google Earth) (...)

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

Sur d’autres sites (5327)

  • Revision 29188 : 2 options de plus pour personnaliser la page d’activation de la mutu : * ...

    15 juin 2009, par real3t@… — Log

    2 options de plus pour personnaliser la page d’activation de la mutu :
    * ’branding’ : texte libre en HTML
    * ’branding_logo’ => logo (sous forme de HTML)

  • Struggling getting FFMPEG to work on Lambda function (Serverless Framework)

    3 juin 2022, par Red Vic

    I've been trying to get FFMPEG to work on my serverless framework for hours and I can't get to grasp how all this should work.

    


    This is my JavaScript code in the handler (just for testing purposes) :

    


    require("dotenv").config();

const ffmpegSync = (url) => {
  const ffmpeg = require("fluent-ffmpeg");
  ffmpeg.setFfprobePath("/opt/ffmpeg-layer/ffprobe");
  ffmpeg.setFfmpegPath("/opt/ffmpeg-layer/ffmpeg")

  return new Promise((resolve, reject) => {
    ffmpeg.ffprobe(url, async (err, metadata) => {
      if (err) {
        resolve(err);
      }
      console.log(metadata);
      resolve(metadata);
    });
  });
};

const ffmpegTeller = async (e, context) => {
  const AWS = require("aws-sdk");

  const s3 = new AWS.S3();
  AWS.config.update({
    accessKeyId: process.env.AWS_ACCESS_KEY,
    secretAccessKey: process.env.AWS_SECRET_KEY,
    region: "us-east-1",
  });

  const sourceBucket = e["Records"][0]["s3"]["bucket"]["name"];
  const sourceKey = e["Records"][0]["s3"]["object"]["key"];
  const signedUrlExpireSeconds = 60 * 5;

  const url = s3.getSignedUrl("getObject", {
    Bucket: sourceBucket,
    Key: sourceKey,
    Expires: signedUrlExpireSeconds,
  });

  await ffmpegSync(url).then((data) => {
    console.log(data);
    return {
      body: JSON.stringify(data),
      statusCode: 200,
    };
  });
};

module.exports = {
  ffmpegTeller,
};


    


    serverless.yaml :

    


    service: my-ffmpeg-api
frameworkVersion: '3'

provider:
  name: aws
  runtime: nodejs14.x
  region: us-east-1

functions:
  ffmpegTeller:
    handler: handler.ffmpegTeller
    events: 
      - s3:
          bucket: sourceBucket
          event: s3:ObjectCreated:*


    


    package.json

    


    {
  "dependencies": {
    "dotenv": "^16.0.1",
    "fluent-ffmpeg": "^2.1.2"
  }
}


    


    The error I'm getting on CloudWatch when trying to use FFprobe
enter image description here

    


    This is the view on the Lambda function page on AWS :

    


    enter image description here

    


    I'd really appreciate some help. I'm really going mad. Thanks in advance.

    


  • Optimize x264 based remote desktop by dirty regions

    23 novembre 2016, par useprxf

    I was using x264 to achieve remote desktop, but had some problems on handling P_SKIP detection.

    Dirty regions indicate changed areas. I would like to encode those macroblocks which don’t intersect any dirty region as P_SKIP types.

    I inserted the following code into x264_macroblock_prob_skip_internal function :

    if (! h->isdirty[h->mb.i_mb_x][h->mb.i_mb_y] && ! M32(h->mb.cache.pskip_mv))
    
    return 1;

    but there is almost no speed-up. I think it may be the information preparation for the macroblock analysis that takes influence.

    My question is how to speed up x264 by considering dirty regions ?

Navigation