Recherche avancée

Médias (1)

Mot : - Tags -/book

Autres articles (86)

  • Websites made ​​with MediaSPIP

    2 mai 2011, par

    This page lists some websites based on MediaSPIP.

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

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

    


  • Unable to get nginx-vod-module plugin to work

    31 octobre 2020, par AAP

    My first time trying hands on nginx-vod-module or any video streaming for that matter.
I just want to play static mp4 videos which I place on the server but via hls instead of direct mp4 access. No actual live streaming

    


    Q1. Am I right in understanding that a mp4 video which I place locally on my server, will automatically get broken down into segments for HLS ?

    


    My nginx installation is here : /opt/kaltura/nginx
The mp4 file is placed at /opt/kaltura/nginx/test/vid.mp4

    


    In ../nginx/conf/server.conf, I have this :

    


    location /hls/ {
            alias test/;
            vod hls;
            vod_bootstrap_segment_durations 2000;
            vod_bootstrap_segment_durations 2000;
            vod_bootstrap_segment_durations 2000;
            vod_bootstrap_segment_durations 4000;

            include /opt/kaltura/nginx/conf/cors.conf;
        }
location / {
            root   html;
        }


    


    Now, I am able to access the m3u8 file :
curl http://104.167xxxxx/hls/vid.mp4/index.m3u8

    


    But when I try to open this file via VLC, I see these errors in errors.log :

    


    *2020/10/31 15:00:08 [error] 12749#0: *60 mp4_parser_validate_stsc_atom: zero entries, client: 49.207 ..., server: ubuntu, request: "GET /hls/vid.mp4/seg-1-v1.ts HTTP/1.1", host: "104.167. ..."
2020/10/31 15:00:08 [error] 12752#0: *61 mp4_parser_validate_stsc_atom: zero entries, client: 49.207 ..., server: ubuntu, request: "GET /hls/vid.mp4/seg-2-v1.ts HTTP/1.1", host: "104.167. ..."
2020/10/31 15:00:09 [error] 12749#0: *62 mp4_parser_validate_stsc_atom: zero entries, client: 49.207 ..., server: ubuntu, request: "GET /hls/vid.mp4/seg-3-v1.ts HTTP/1.1", host: "104.167. ..."
2020/10/31 15:00:10 [error] 12751#0: *63 mp4_parser_validate_stsc_atom: zero entries, client: 49.207 ..., server: ubuntu, request: "GET /hls/vid.mp4/seg-4-v1.ts HTTP/1.1", host: "104.167. ..."*


    


    Q2 : Is https must for this to work ?
Q3 : I dont see any /hls/vid.mp4 folder created anywhere on the server. Do I have to manually run ffmpeg separately to create the hls segments ?

    


    What wrong am I doing ?

    


  • ffmpeg, twitch.tv, doesnt work

    7 novembre 2015, par John Smith

    Im using this command for streaming :

    ffmpeg -f dshow -i video="screen-capture-recorder" -f dshow -i audio="Mikrofon (USB audioeszköz)" -f dshow -i audio="virtual-audio-capturer" -f dshow -i audio="Mikrofon (Conexant SmartAudio H" -vcodec libx264 -r 25 -crf 0 -acodec aac -strict -2 -filter_complex amix=inputs=3:duration=first -pix_fmt yuv420p -s 640x480 -preset fast -f flv "rtmp ://live.twitch.tv/app/live_**********"

    if I save it to disk, it works. Streaming to twitch.tv also wont give error, but it just stays blank, it cannot see it "alive"