Recherche avancée

Médias (0)

Mot : - Tags -/xmlrpc

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

Autres articles (98)

  • Gestion des droits de création et d’édition des objets

    8 février 2011, par

    Par défaut, beaucoup de fonctionnalités sont limitées aux administrateurs mais restent configurables indépendamment pour modifier leur statut minimal d’utilisation notamment : la rédaction de contenus sur le site modifiables dans la gestion des templates de formulaires ; l’ajout de notes aux articles ; l’ajout de légendes et d’annotations sur les images ;

  • Supporting all media types

    13 avril 2011, par

    Unlike most software and media-sharing platforms, MediaSPIP aims to manage as many different media types as possible. The following are just a few examples from an ever-expanding list of supported formats : images : png, gif, jpg, bmp and more audio : MP3, Ogg, Wav and more video : AVI, MP4, OGV, mpg, mov, wmv and more text, code and other data : OpenOffice, Microsoft Office (Word, PowerPoint, Excel), web (html, CSS), LaTeX, Google Earth and (...)

  • Dépôt de média et thèmes par FTP

    31 mai 2013, par

    L’outil MédiaSPIP traite aussi les média transférés par la voie FTP. Si vous préférez déposer par cette voie, récupérez les identifiants d’accès vers votre site MédiaSPIP et utilisez votre client FTP favori.
    Vous trouverez dès le départ les dossiers suivants dans votre espace FTP : config/ : dossier de configuration du site IMG/ : dossier des média déjà traités et en ligne sur le site local/ : répertoire cache du site web themes/ : les thèmes ou les feuilles de style personnalisées tmp/ : dossier de travail (...)

Sur d’autres sites (12655)

  • How to change output file name based on the parametars inside the command

    2 mai 2019, par Filip Glavica

    In this command, i am changing the resolution of a .yuv file to new resolution. I want to save the output file regarding the resolution i have changed it to.
    For example my video is called "skateboard.yuv", i want it to be called "skateboard_1280x720.yuv".

    Right now It is called the same as the input file"

    for %f in (*.yuv) do ffmpeg -s:v 1920x1080 -r 25 -i "%f" -vf scale=1280:720 -c:v rawvideo -pix_fmt yuv420p "%~nf.yuv"

    Thank you

  • Concatenating *.mkv files using ffmpeg

    25 mars 2020, par Daniel F

    I’ve just about lost my mind on this, I’m sure I’m missing something simple.

    I have two *.mkv files generated by OBS. Even better, I’ve just copied one file twice, so I am sure I have the same bitrate, fps, tbn, whatever.

    then I do :

    ffmepg -i "concat:file1.mkv|file1_copy.mkv" -c copy test.mkv

    It runs and my screen fills with yellow messages :

       ffmpeg -i "concat:file1.mkv|file1_copy.mkv" -c copy test.mkv
    ffmpeg version 4.2 Copyright (c) 2000-2019 the FFmpeg developers
     built with gcc 9.1.1 (GCC) 20190807
     configuration: --disable-static --enable-shared --enable-gpl --enable-version3 --enable-sdl2 --enable-fontconfig --enable-gnutls --enable-iconv --enable-libass --enable-libdav1d --enable-libbluray --enable-libfreetype --enable-libmp3lame --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libopenjpeg --enable-libopus --enable-libshine --enable-libsnappy --enable-libsoxr --enable-libtheora --enable-libtwolame --enable-libvpx --enable-libwavpack --enable-libwebp --enable-libx264 --enable-libx265 --enable-libxml2 --enable-libzimg --enable-lzma --enable-zlib --enable-gmp --enable-libvidstab --enable-libvorbis --enable-libvo-amrwbenc --enable-libmysofa --enable-libspeex --enable-libxvid --enable-libaom --enable-libmfx --enable-amf --enable-ffnvcodec --enable-cuvid --enable-d3d11va --enable-nvenc --enable-nvdec --enable-dxva2 --enable-avisynth --enable-libopenmpt
     libavutil      56. 31.100 / 56. 31.100
     libavcodec     58. 54.100 / 58. 54.100
     libavformat    58. 29.100 / 58. 29.100
     libavdevice    58.  8.100 / 58.  8.100
     libavfilter     7. 57.100 /  7. 57.100
     libswscale      5.  5.100 /  5.  5.100
     libswresample   3.  5.100 /  3.  5.100
     libpostproc    55.  5.100 / 55.  5.100
    Input #0, matroska,webm, from 'concat:file1.mkv|file1_copy.mkv':
     Metadata:
       ENCODER         : Lavf58.20.100
     Duration: 00:00:09.15, start: 0.000000, bitrate: 2006 kb/s
       Stream #0:0: Video: h264 (High), yuv420p(progressive), 1920x1080 [SAR 1:1 DAR 16:9], 60 fps, 60 tbr, 1k tbn, 120 tbc (default)
       Metadata:
         DURATION        : 00:00:09.150000000
       Stream #0:1: Audio: aac (LC), 44100 Hz, stereo, fltp (default)
       Metadata:
         title           : simple_aac_recording
         DURATION        : 00:00:09.102000000
    Output #0, matroska, to 'test.mkv':
     Metadata:
       encoder         : Lavf58.29.100
       Stream #0:0: Video: h264 (High) (H264 / 0x34363248), yuv420p(progressive), 1920x1080 [SAR 1:1 DAR 16:9], q=2-31, 60 fps, 60 tbr, 1k tbn, 1k tbc (default)
       Metadata:
         DURATION        : 00:00:09.150000000
       Stream #0:1: Audio: aac (LC) ([255][0][0][0] / 0x00FF), 44100 Hz, stereo, fltp (default)
       Metadata:
         title           : simple_aac_recording
         DURATION        : 00:00:09.102000000
    Stream mapping:
     Stream #0:0 -> #0:0 (copy)
     Stream #0:1 -> #0:1 (copy)
    Press [q] to stop, [?] for help
    [matroska,webm @ 00000156ce7f14c0] File extends beyond end of segment.
    [matroska @ 00000156cef62040] Non-monotonous DTS in output stream 0:0; previous: 9100, current: 0; changing to 9100. This may result in incorrect timestamps in the output file.
    [matroska @ 00000156cef62040] Non-monotonous DTS in output stream 0:0; previous: 9100, current: 67; changing to 9100. This may result in incorrect timestamps in the output file.
    [matroska @ 00000156cef62040] Non-monotonous DTS in output stream 0:0; previous: 9100, current: 33; changing to 9100. This may result in incorrect timestamps in the output file.
    [matroska @ 00000156cef62040] Non-monotonous DTS in output stream 0:1; previous: 9102, current: 0; changing to 9102. This may result in incorrect timestamps in the output file.
    [matroska @ 00000156cef62040] Non-monotonous DTS in output stream 0:0; previous: 9100, current: 17; changing to 9100. This may result in incorrect timestamps in the output file.

    ############## thousands of the above lines here #####################

    frame= 1098 fps=0.0 q=-1.0 Lsize=    2241kB time=00:00:09.11 bitrate=2013.0kbits/s speed=24.9x
    video:2068kB audio:159kB subtitle:0kB other streams:0kB global headers:0kB muxing overhead: 0.607770%

    When opened, the timestamps only go to the end of the first segment, even though the video continues afterwards. Normally this would be fine, but I’m recording instructional videos and it would be nice for users to be able to skip around them. This occurs even if I re-encode the videos (which I shouldn’t need, since they are identical) or re-encode the output.

    Everything I have read online says :

    • re-encode*into .mkv to fix this, since .mkv has a fixed tbn - it’s already .mkv

    • the problem is different bitrates/tbs/fps/whatever - for now, they’re the same video twice

    • use -fflags +genpts, -use_wallclock_as_timestamps 1, vsync 0 -enc_time_base -1 - none of these do anything as far as I can tell, either before -i or after -c copy

    I’ve run out of ideas. What am I doing wrong.

  • Carrierwave video not being processsed before uploading to S3

    12 décembre 2013, par Cramps

    I'm using Carrierwave, Carrierwave-video and Carrierwave-video-thumbnailer to process videos and make a thumbnail when they're uploaded. This was all working nicely while I was saving the files on my file system. However, now that I've added uploading to Amazon S3 using the carrierwave-aws gem, the videos are being uploaded to S3 without being processed first. It's as if the process encode_video and version :thumb are being skipped by the uploader.

    Here's what was working for me at first (before adding S3) :

    class VideoUploader < CarrierWave::Uploader::Base

    include CarrierWave::Video
    include CarrierWave::Video::Thumbnailer

    storage :file

    def store_dir
       "upload/path/"
    end

    process encode_video: [{ bunch of video options}]

    version :thumb do
       process thumbnail: [{ bunch of thumbnailer options }]
       def full_filename for_file
           png_name for_file, version_name
       end  
    end

    def png_name for_file, version_name
       %Q{#{version_name}_#{for_file.chomp(File.extname(for_file))}.png}
    end

    Now it's really just the same, except it's using storage :aws instead.