Recherche avancée

Médias (91)

Autres articles (29)

  • Mise à jour de la version 0.1 vers 0.2

    24 juin 2013, par

    Explications des différents changements notables lors du passage de la version 0.1 de MediaSPIP à la version 0.3. Quelles sont les nouveautés
    Au niveau des dépendances logicielles Utilisation des dernières versions de FFMpeg (>= v1.2.1) ; Installation des dépendances pour Smush ; Installation de MediaInfo et FFprobe pour la récupération des métadonnées ; On n’utilise plus ffmpeg2theora ; On n’installe plus flvtool2 au profit de flvtool++ ; On n’installe plus ffmpeg-php qui n’est plus maintenu au (...)

  • MediaSPIP v0.2

    21 juin 2013, par

    MediaSPIP 0.2 est la première version de MediaSPIP stable.
    Sa date de sortie officielle est le 21 juin 2013 et est annoncée ici.
    Le fichier zip ici présent contient uniquement les sources de MediaSPIP en version standalone.
    Comme pour la version précédente, il est nécessaire d’installer manuellement l’ensemble des dépendances logicielles sur le serveur.
    Si vous souhaitez utiliser cette archive pour une installation en mode ferme, il vous faudra également procéder à d’autres modifications (...)

  • Mise à disposition des fichiers

    14 avril 2011, par

    Par défaut, lors de son initialisation, MediaSPIP ne permet pas aux visiteurs de télécharger les fichiers qu’ils soient originaux ou le résultat de leur transformation ou encodage. Il permet uniquement de les visualiser.
    Cependant, il est possible et facile d’autoriser les visiteurs à avoir accès à ces documents et ce sous différentes formes.
    Tout cela se passe dans la page de configuration du squelette. Il vous faut aller dans l’espace d’administration du canal, et choisir dans la navigation (...)

Sur d’autres sites (4116)

  • Choose CUDA version for ffmpeg encoding

    8 février 2023, par A GV

    I have multiple CUDA versions installed and I need all of them, so I can’t unistall any. The problem is when I try to encode with the nvenc_h264 encoder, it doesn’t work because it says that there are multiple version of CUDA.

    


    I’m trying to choose the CUDA version, but I don’t find any parameter in ffmpeg documentation to do so.

    


    Does anyone know how to choose the CUDA version ?

    


    I’m working with Linux 22 and the latest ffmpeg version with the NVIDIA libraries.

    


  • MPlayer not playing HTTP video stream for a specific type of content from the same source

    2 août 2017, par Joel

    Implementation overview

    Before I dive into the question, I need to establish the context from the start.

    I am currently implementing a cloud gaming solution utilising the following :

    • Nvidia Capture SDK
    • Nvidia Video Codec SDK
    • FFmpeg
    • MPlayer

    The Nvidia Capture SDK is used to produce a shim layer (via DXGI.dll), intercepting and capturing DirectX frames so that they can be passed to the Nvidia Video Codec SDK to be encoded into an h264 video format. All this is done within DXGI.dll.

    I then pass the encoded video to FFmpeg. FFmpeg acts as an HTTP server that broadcasts the video stream for MPlayer to play.

    Problem

    I am running an Unreal Engine 4 game called "Epic Survival Game Series". The Nvidia Capture SDK’s shim layer kicks off when the game starts, and FFmpeg launches the HTTP server to start streaming. However, when I start MPlayer to receive the stream, MPlayer stops at the following message, and nothing happens after that.

    libavformat version 57.72.101 (internal)
    Stream not seekable!
    H264-ES file format detected

    The thing is, when I play the same video using ffplay, it works without any issue. This is not the only quirk. When I launch a different Unreal Engine 4 game called "First Person Shooter Template", MPlayer can play that video as well. Also, if I modify the Survival Game to load directly into the game level by skipping the menu, MPlayer is also able to play the video.

    Using FFmpeg to write the video to a file instead of streaming it to a video also works, no matter the game or whether I loaded into the menu or game level.

    This is very strange and I do not have any idea why this is the case. Any ideas ?

    Edit : One strange quirk I forgot to mention is that MPlayer does manage to play the video in very rare occasions - maybe once every 10-20 tries or so.

    Implementation Details

    Additional details of how certain parts are implemented.

    (1) For the Nvidia Capture SDK, I use the provided DXIFRShim example that is provided in the SDK

    (2) for the Nvidia Video Codec SDK, I use the provided NvEncoder example that is provided in the SDK

    (3) The FFmpeg command I use is this :
    ffmpeg -i - -listen 1 -threads 1 -vcodec copy -preset ultrafast -an -tune zerolatency -f h264 http://address:port
    The encoded frames from Nvidia Video Codec SDK is piped to FFmpeg.

    (4) The MPlayer command I use is this :
    mplayer -quiet -vo gl -nosound -benchmark http://address:port

    Things I’ve tried

    I am suspecting MPlayer to be the cause, so I’ve only played around with MPlayer parameters.
    mplayer http://address:port

    mplayer -fps 30 -vo gl -nosound -benchmark http://address:port

    mplayer -fps 30 -screenw 720 -screenh 1280 -vo gl -nosound -benchmark http://address:port

    mplayer -fps 30 -vo directx -nosound -benchmark http://address:port

    mplayer -fps 30 -vo null -nosound -benchmark http://address:port

    None of these worked.

  • ffmpeg transcode to youtube live bad video container

    13 juillet 2017, par popcorn9499

    I’ve been attempting to transcode a stream produced by obs studio to my nginx server and send it off to youtube. Now I’ve made it work with twitch and I know these settings are actually transcoding it mostly correctly and is viewable. The problem being that youtube live picks it up as Bad video settings and tells me to change the current video container format. The other side effect that is probly unrelated is the stream looks really poorly on youtube. Looks like it was streamed at a poor bitrate and stuff but the real problem is the bad video settings error.

    The ffmpeg command being used is as follows

    ffmpeg -i rtmp://localhost/Private/Private1 -vb 6000k -minrate 6000k -maxrate 6000k -bufsize 6000k -s 1280x720 -c:v libx264 -preset faster -r 50 -g 100 -keyint_min 50 -x264opts nal-hrd=cbr:force-cfr=1 -sws_flags lanczos -tune film -pix_fmt yuv420p -c:a copy -f flv -threads 6 -strict normal  rtmp://a.rtmp.youtube.com/live2/{key}

    I’ve tried with different framerates and been googling for awhile and found nothing or interpreted everything wrongly. Either way I would be very happy for some help here.

    System info.

    • OS : Ubuntu Server 16.04 LTS
    • Ram : 10gb
    • Processor : AMD Phenom(tm) II X6 1090T
    • GPU : Geforce GT 520

    Internet.

    • Upload 15mbit
    • Download 150mbit

    If you need any more info I will gladly send it. Thanks for reading.

    Edit 1

    After some googling about what I’m doing wrong I decided to try and change stuff slightly and came up with this command

    ffmpeg -re -i rtmp://localhost/(app)/(key) -c:v libx264 -r 50 -g 100 -keyint_min 100 -x264opts "keyint=100:min-keyint=100:no-scenecut" -sws_flags lanczos -profile:v baseline -preset veryfast -vb 6000K -minrate 6000k -maxrate 6000k -bufsize 6000k -s 1280x720 -tune film,zerolatency -pix_fmt yuv420p -f flv -c:a copy -ac 1 -strict normal rtmp://(output site)/(output app)/(output key)

    which as of my current testing seems to at least have a healthy stream for longer than 2 minutes if i only output to youtube live directly. Ive found output to my nginx server then youtube live breaks things.

    my nginx rtmp settings are on this link https://pastebin.com/siE99Tv8

    Edit 2

    If I push the stream to a site like restream to stream it to youtube then it seems to be working. tested for 25 minutes with no change of them saying bad video container or anything. So I’m going to say nginx is partly to blame in how its distributing the files ? Unsure what I’m doing wrong. I am pretty sure ffmpeg isn’t to blame here at least