Recherche avancée

Médias (3)

Mot : - Tags -/Valkaama

Autres articles (96)

  • MediaSPIP 0.1 Beta version

    25 avril 2011, par

    MediaSPIP 0.1 beta is the first version of MediaSPIP proclaimed as "usable".
    The zip file provided here only contains the sources of MediaSPIP in its standalone version.
    To get a working installation, you must manually install all-software dependencies on the server.
    If you want to use this archive for an installation in "farm mode", you will also need to proceed to other manual (...)

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

  • ANNEXE : Les plugins utilisés spécifiquement pour la ferme

    5 mars 2010, par

    Le site central/maître de la ferme a besoin d’utiliser plusieurs plugins supplémentaires vis à vis des canaux pour son bon fonctionnement. le plugin Gestion de la mutualisation ; le plugin inscription3 pour gérer les inscriptions et les demandes de création d’instance de mutualisation dès l’inscription des utilisateurs ; le plugin verifier qui fournit une API de vérification des champs (utilisé par inscription3) ; le plugin champs extras v2 nécessité par inscription3 (...)

Sur d’autres sites (9646)

  • NodeMediaServer MP4 change default video resolution 540p

    11 août 2021, par Farooq Zaman

    I have setup a nginx RTMP server and the purpose is to store videos streamed from mobile devices in MP4 format for later analysis. Although mobile devices are streaming videos in 720p resolution NodeMediaServer always store video in 540p resolution. How can I change this behaviour ? Following is NodeMediaServer configuration :

    


    const nodeMediaServerConfig = {
  rtmp: {
    port: 1936,
    chunk_size: 60000,
    gop_cache: true,
    ping: 60,
    ping_timeout: 10,
  },
  http: {
    port: 8000,
    mediaroot: './media',
    allow_origin: '*',
  },
  trans: {
    ffmpeg: '/usr/bin/ffmpeg',
    tasks: [
      {
        app: 'live',
        vcParam: [
          "-c:v",
          "libx264",
          "-vf",
          "scale=720:-1",
          "-b:v",
          "2800k",
          "-bufsize",
          "4200k",
          "-preset",
          "fast",
        ],
        ac: 'aac',
        acParam:["-b:a", "128k", "-ar", 48000],
        mp4: true,
        mp4Flags: '[movflags=faststart]',
      },
    ],
  },
};


    


    Any help in this matter is highly appreciated.

    


  • FFMPEG gdigrab not stopping when title changes

    13 avril 2021, par Vishwesh

    I am trying to capture a video playlist using ffmpeg gdigrab. The player takes in input a batch of videos. I want to create a separate video for each loaded file in the player. I was able to use ffmpeg gdigrab to capture the video for one video. The problem is, it does not stop when the window title changes (that is when the next file is loaded), and instead it creates just one file for the entire duration. The only way to stop it was if I close the entire window. The reason I can't go ahead with it is because the user will be given an option to change any settings in the beginning of the recording and then the entire playlist will use the same settings.

    


    I also tried other options like using subprocess.Popen to start the ffmpeg and then using .terminate() or .kill() to stop it, but the recording still keeps on going. Similarly, sending 'q' key from a file did not work either.

    


    Ideally, I would expect that gdigrab should be able to detect when the grabbed window title differs from the expected one and stop, however, here it looks like it's anchoring itself to the window instead of the title.

    


    I am using a Windows 10 PC and programming language for this tool is Python. I am using ffmpeg version 4.4-full_build.

    


    If you have any ideas regarding this, it would be of great help.

    


  • ExoPlayer FFMPEG can't find native libraries

    28 janvier 2021, par Cilenco

    I'm currently developing an application using the ExoPlayer library which needs ffmpeg support. I was able to build the ffmpeg extension from the ExoPlayer repo fine by following the readme. I then build an aar with :

    


    ./gradlew :extension-ffmpeg:assembleRelease


    


    I included the aar into my project and enabled the the extension through the DefaultRenderersFactory but when I load my app I get following lines in the log :

    


    W/LibraryLoader: Failed to load [avutil, swresample, avcodec, ffmpeg jni)
I/DefaultRenderersFactory: Loaded Ffmpeg AudioRenderer.


    


    According to the troubleshooting post, this is because the native parts of the library could not be loaded. Unfortunately I have no experience with Android native development so I'm not sure where to find the native parts of the library and how to add them to my application ?

    


    With the demo app it works fine !