Recherche avancée

Médias (0)

Mot : - Tags -/configuration

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

Autres articles (39)

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

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

  • De l’upload à la vidéo finale [version standalone]

    31 janvier 2010, par

    Le chemin d’un document audio ou vidéo dans SPIPMotion est divisé en trois étapes distinctes.
    Upload et récupération d’informations de la vidéo source
    Dans un premier temps, il est nécessaire de créer un article SPIP et de lui joindre le document vidéo "source".
    Au moment où ce document est joint à l’article, deux actions supplémentaires au comportement normal sont exécutées : La récupération des informations techniques des flux audio et video du fichier ; La génération d’une vignette : extraction d’une (...)

Sur d’autres sites (5715)

  • Installing gifify on Windows

    12 octobre 2017, par Robert Wojciechowski

    So gifify is a pretty awesome script that converts videos to gifs via command line : https://github.com/vvo/gifify

    I’m keen to get this working on my Windows 10 machine. I’m pretty new to windows and relatively new to coding, but I was able to get a few things working, but ran into a problem.

    Here is what I did :

    1. Installed node.js + npm
    2. Installed FFmpeg using npm
    3. Installed ImageMagick using npm (i think i did this wrong, might have only installed the wrapper).
    4. Downloaded giflossy. It needed to be built (?)
    5. Installed Visual Studio 2015, tried to build it using nmake and got this error :
    NMAKE : fatal error U1073: don't know how to make 'win32cfg.h'

    The command I used was :

    PS C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\bin> .\nmake -f "C:\Users\Robert's Workstation\.npm-global\node_modules\giflossy-lossy-1.82.1\src\Makefile.w32"

    Would really appreciate some help with this :D

  • Using ffmpeg to split videos into frames doesn't work

    28 décembre 2018, par אבנר יעקב

    In my code i’m trying to split video to frames using ffmpeg.

    for this I’m using this code

    experiments = ['iguazu.mp4', 'boat.mp4']

    for experiment in experiments:
       exp_no_ext = experiment.split('.')[0]
       os.system('mkdir dump')
       os.system('mkdir dump\%s' % exp_no_ext)
       os.system("ffmpeg -i videos\%s dump\%s\%s%%03d.jpg" % (experiment,
    exp_no_ext, exp_no_ext))

    So in visual studio code it’s working perfect but in visual studio community the line "os.system("ffmpeg -i videos\%s dump\%s\%s%%03d.jpg" % (experiment,
    exp_no_ext, exp_no_ext))" showing error "ffmpeg is not recognized as an internal or external command".

  • How to save ffmpeg segmets to disk immediately with sub-second intervals ?

    20 octobre 2023, par amfast

    I'm trying to record video on a raspberry and have it save as much as possible (sub-second resolution) in case of a power cutoff.

    


    I use -f segment to save the encoded stream in 100ms segments with the hope that all but the interrupted (by power cutoff) segment will be saved in memory. Unfortunately, when cutting off power, all the destination files (output_0001.mp4, output_0002.mp4, ...) are created, but empty.

    


    To save the files to disk immediately, I added the -strftime 1 option that allows formatting the output filename as time. It seems weird that this is the (only ?) way to trigger immediate saving of files, but it works - untill I try to have segments smaller than 1 second. The problem seems to be that the format string %d, that previously added a sequence number in my output filenames, now represents "day" (i.e. date) and the smallest resolution time format string is %S for second. I saw %f suggested somewhere for smaller resolutions, but it only prints "%f".

    


    The result is that the segmentation part of ffmpeg does create 100ms segments and save them to disk immediately, but the strftime feature gives the output files names that only change every second, so all the interim files are overwritten.

    


    Example of the failing command below. Without the -strftime option this creates nice segments, but does not save them to disk immediately.

    


    libcamera-vid --flush \
    --framerate ${FRAMERATE} \
    --width ${WIDTH} \
    --height ${HEIGHT} \
    -n \
    -t ${TIMEOUT} \
    --codec yuv420 \
    -o - | 
ffmpeg \
    -fflags nobuffer \
    -strict experimental \
    -loglevel debug \
    -flags low_delay \
    -f rawvideo \
    -pix_fmt yuv420p \
    -s:v ${WIDTH}x${HEIGHT} \
    -r ${FRAMERATE} \
    -i - \
    -c:v h264_v4l2m2m \
    -f segment \
    -segment_time 0.1 \
    -segment_format mp4 \
    -reset_timestamps 1 \
    -strftime 1 \
    -b:v ${ENCODING_BITRATE} \
    -g 1 \
    "output_%04d.mp4"


    


    Question :
    
Is there another way besides -strftime to trigger immediate saving ? Or is there a mechanism to feed finer resolution format strings to the output filename ?