Recherche avancée

Médias (91)

Autres articles (41)

  • Les autorisations surchargées par les plugins

    27 avril 2010, par

    Mediaspip core
    autoriser_auteur_modifier() afin que les visiteurs soient capables de modifier leurs informations sur la page d’auteurs

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

  • Support audio et vidéo HTML5

    10 avril 2011

    MediaSPIP utilise les balises HTML5 video et audio pour la lecture de documents multimedia en profitant des dernières innovations du W3C supportées par les navigateurs modernes.
    Pour les navigateurs plus anciens, le lecteur flash Flowplayer est utilisé.
    Le lecteur HTML5 utilisé a été spécifiquement créé pour MediaSPIP : il est complètement modifiable graphiquement pour correspondre à un thème choisi.
    Ces technologies permettent de distribuer vidéo et son à la fois sur des ordinateurs conventionnels (...)

Sur d’autres sites (9734)

  • Error : Error : Cannot find module '@ffmpeg.wasm/core-mt' Require stack :

    30 septembre 2023, par James

    I'm getting this error "Error : Error : Cannot find module '@ffmpeg.wasm/core-mt', When my code is deployed on Vercel (Node.js + TypeScript) Does I get confused because when I try to run the same code on my local machine it works fine

    


    But as I deploy it on Vercel it gives that error. Obviously, i do have "@ffmpeg.wasm/core-mt" installed as said in the package https://github.com/FFmpeg-wasm/FFmpeg.wasm#installation So how do I fix it ?

    


    I'm currently using it like this

    


    import { FFmpeg } from "@ffmpeg.wasm/main";

async function myFunction() {
    const ffmpeg = await FFmpeg.create({
        core: "@ffmpeg.wasm/core-mt",
        log: true,
    });
}


    


    However, in the docs, i see doing like this

    


      import { FFmpeg } from "@ffmpeg.wasm/main";
    
     const ffmpeg = await FFmpeg.create({
            core: "@ffmpeg.wasm/core-mt",
            log: true,
        });

    async function myFunction() {
        // use ffmpeg here
    }


    


    But then i start getting errors like "top-level 'await' expressions are only allowed when the 'module' option is set to 'es2022', 'esnext', 'system', 'node16', or 'nodenext', and the 'target' option is set to 'es2017' or higher."

    


    I tried a couple of StackOverflow solutions but nothing works in my case. So what should I do ?

    


    tsconfig.json :

    


    {
    "compilerOptions": {
     "module": "CommonJS",
     "esModuleInterop": true,
      "allowSyntheticDefaultImports": true,
      "target": "es2017",
      "noImplicitAny": true,
      "moduleResolution": "node",
      "sourceMap": true,
      "outDir": "dist",
      "baseUrl": ".",
      "paths": {
        "*": ["node_modules/*", "src/types/*"]
      }
    },
    "include": ["./src/**/*", "src/firebase/serviceAccountKey.ts"]
  }


    


  • How to download audio and video as separate files and specify the output format and filename for each ?

    14 novembre 2023, par Taako

    I'd like to download a video as separate files for both audio and video and have them named [video_id]-audio.wav and [video_id]-video.mp4

    


    How do i get yt-dlp to download the video and audio separately, then convert each to the specified output format and rename them as such ?

    


    Right now I can get them each downloaded separately but the naming isnt working out.

    


    I could also use ffmpeg separately to convert the video and audio formats after they are downloaded, so all i really need is to have the audio and video files downloaded and named

    


    Right now my args are

    


    YT_OPTIONS = {
    'format': 'bestvideo[height<=720]+bestaudio/best[height<=720]',
    'extractaudio': True,
    'keepvideo': True,
    'outtmpl': '%(id)s-%(format)s.%(ext)s',
    'restrictfilenames': True,
    'noplaylist': True
}


    


    but the format is just coming out as 247_-_1280x720_720p_+251_-_audio_only_medium and whats worse is it is the same for both the audio only and video only files just one has 251 and the other has 247.

    


  • Converting Gstreamer pipeline to ffmpeg options for rtsp stream

    3 novembre 2020, par Himanshu Verma

    I am using gstreamer pipeline for streaming rtsp enabled IP camera video feed, now i want to use ffmpeg for streaming the same camera. I am not very much aware about the ffmpeg options. Can someone convert below gstreamer pipeline to ffmpeg options ?

    


    rtspsrc location=rtsp://root:pass@192.168.0.101:554/axis-media/media.amp short-header=TRUE ! rtph264depay ! video/x-h264,stream-format=byte-stream,alignment=au ! appsink sync=TRUE emit-signals=TRUE name=appsink-video