Recherche avancée

Médias (0)

Mot : - Tags -/signalement

Aucun média correspondant à vos critères n’est disponible sur le site.

Autres articles (37)

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

  • MediaSPIP version 0.1 Beta

    16 avril 2011, par

    MediaSPIP 0.1 beta est la première version de MediaSPIP décrétée comme "utilisable".
    Le fichier zip ici présent contient uniquement les sources de MediaSPIP en version standalone.
    Pour avoir une installation fonctionnelle, 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 (...)

Sur d’autres sites (6589)

  • FFMPEG taking too long in offline encryption

    30 janvier 2018, par avi

    FFMPEG taking too much time to encrypting a video file.
    I am running following command "ffmpeg -i "Sample.mp4" -hls_time 10 -hls_list_size 0 -hls_key_info_file enc.keyinfo "sample.m3u8"".
    To encrypt 708MB video file it takes around 22 minutes, Which is too much time so
    Is there any way to decress the time without changing the video quality ?

  • Long video files are shortened when exported [closed]

    28 avril, par Mathilda

    I'm working on videos with a maximal length of 23h59m59s (let's say 24h). I wanted to do several modifications on these videos, including dividing them into smaller parts and converting them into images. I'm doing it with Python in the Anaconda interface.

    


    My 24-hour videos are properly read by the Windows "Films & TV" player. They are also properly read by VLC media player. However, as soon as I try to use them :

    


      

    • in editing software (Movavi) ;
    • 


    • on an online editing site (Video-cutter) ;
    • 


    • on Python (cv2 and moviepy packages) ; or
    • 


    • on ffmpeg
    • 


    


    the indicated video duration is correct only if the video is less than 13h15m22s. If it is longer than that, the indicated duration is equal to the real duration minus 13h15m22s, regardless of the loaded video's metadata (size, weight, fps, duration).

    


    I have tried with videos of different durations, different pixel sizes and weights in GB, and different fps. I had variable fps mode on the videos, so I tried to set them to fixed mode using ffmpeg, but the exported video with fixed fps still has 13h15m22s missing. For videos taken from the web (YouTube), this problem does not appear on any of the 4 tested supports, so there is no problem coming from my machine or software. The issue must be in the videos. But I don't understand what could be in the videos for it to always be 13h15m22s that are removed, regardless of the video size. Moreover, if the video was corrupted, I wouldn't be able to display it in Films & TV or VLC media player.

    


    I used ffmpeg to see if the video was corrupted :

    


    ffmpeg.exe -v error -i "/Users/myname/Desktop/myvideo.mp4" -f null >error.log 2>&1

ffmpeg.exe -v error -i "/Users/myname/Desktop/myvideo.mp4" -f null

ffprobe -show_entries stream=r_frame_rate,nb_read_frames,duration -select_streams v -count_frames -of compact=p=1:nk=1 -threads 3 -v 0


    


    And nothing appears in the output so I guess there's no error detected. I tried to repair my video with ffmpeg anyway :

    


    ffmpeg -i "/Users/myname/Desktop/myvideo.mp4" -c copy "/Users/myname/Desktop/myvideo_fixed.mp4”


    


    And there is still 13h15m22s missing.

    


    I finally tried to repair it with Untrunc, which gave me a completely black video of 55 minutes for a video supposed to last several hours. Untrunc asks for the corrupted file and a functional video file taken by the same camera as input, so I used a 3min26 file for this, assuming that since the file is less than 13h15m22s and does not appear truncated on the software, it is not corrupted. Maybe I should have taken a larger video file (a few hours for example), but I'm not sure it's going to change anything.

    


    I don't know what to do to be able to cut these videos and use them in Python without them being truncated.

    


  • FFmpeg to push RTMP stream problem, the video completed by push stream takes a long time to display。

    5 juin 2020, par Sacher

    FFmpeg to push RTMP stream problem, the video completed by push stream takes a long time to display。
    
I feel that ffmpeg has a long start time。
My command is
    
ffmpeg -i rtmp://play ip/appName/streamName -threads 4 -tune zerolatency -vcodec copy -bf 0 -g 1 -preset ultrafast -acodec copy -f flv rtmp://push ip/appName/streamName
    
In this way, the startup user will wait for a long time to use, how to deal with it.