Recherche avancée

Médias (1)

Mot : - Tags -/publicité

Autres articles (67)

  • Publier sur MédiaSpip

    13 juin 2013

    Puis-je poster des contenus à partir d’une tablette Ipad ?
    Oui, si votre Médiaspip installé est à la version 0.2 ou supérieure. Contacter au besoin l’administrateur de votre MédiaSpip pour le savoir

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

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

Sur d’autres sites (9236)

  • FFMpeg incorrect execution calling two different paths in NodeJS

    17 octobre 2015, par Eli

    I’m trying to take screenshots from a movie file and my app crashes with the following error :

    $ FFMPEG_PATH=C:\\Apps\\ffmpeg\\bin\\ node .
    =====Convert Video Failed======
    { [Error: spawn c:\Apps\ffmpeg\bin\ffprobe.exe
    c:\Program Files (x86)\ImageMagick-6.8.3-Q16\ffprobe.exe ENOENT]
     code: 'ENOENT',
     errno: 'ENOENT',
     syscall: 'spawn c:\\Apps\\ffmpeg\\bin\\ffprobe.exe\r\nc:\\Program Files (x86)\\ImageMagick-6.8.3-Q16\\ffprobe.exe',
     path: 'c:\\Apps\\ffmpeg\\bin\\ffprobe.exe\r\nc:\\Program Files (x86)\\ImageMagick-6.8.3-Q16\\ffprobe.exe',
     spawnargs:
      [ '-show_streams',
        '-show_format',
        'j:\\some.avi' ] }
    stdout: undefined
    stderr: undefined

    As you can see I’m passing a the FFMPEG_PATH env variable because otherwise I’m getting a similar error :

    $ node .
    =====Convert Video Failed======
    { [Error: spawn c:\Apps\ffmpeg\bin\ffprobe.exe
    c:\Program Files (x86)\ImageMagick-6.8.3-Q16\ffprobe.exe ENOENT]
     code: 'ENOENT',
     errno: 'ENOENT',
     syscall: 'spawn c:\\Apps\\ffmpeg\\bin\\ffprobe.exe\r\nc:\\Program Files (x86)\\ImageMagick-6.8.3-Q16\\ffprobe.exe',
     path: 'c:\\Apps\\ffmpeg\\bin\\ffprobe.exe\r\nc:\\Program Files (x86)\\ImageMagick-6.8.3-Q16\\ffprobe.exe',
     spawnargs:
      [ '-show_streams',
        '-show_format',
        'j:\\some.avi' ] }
    stdout: undefined
    stderr: undefined

    In both cases you can see that the command that node/fluent-ffmpeg is using results in a double path like this : c:\\Apps\\ffmpeg\\bin\\ffprobe.exe\r\nc:\\Program Files (x86)\\ImageMagick-6.8.3-Q16\\ffprobe.exe which obviously fails.

    What causes this and how do I fix it ?


    Win 7, Node v4.1.2, ffmpeg version N-76041-g0418541

    The code I’m using :

    var ffmpeg = require('fluent-ffmpeg');
    // ffmpeg.setFfprobePath("c:\\Apps\\ffmpeg\\bin\\ffprobe.exe");

    var filename = 'j:\\some.avi';
    var command = ffmpeg(filename);


    // Code from an example
    command
     .on('filenames', function(filenames) {
       console.log('Will generate ' + filenames.join(', '))
     })
     .on('end', function() {
       console.log('Screenshots taken');
     })
     .on('error', function(err, stdout, stderr) {
       console.log(" =====Convert Video Failed======");
       console.log(err);
       console.log("stdout: " + stdout);
       console.log("stderr: " + stderr);
     })
     .screenshots({
       // Will take screens at 20%, 40%, 60% and 80% of the video
       count: 4,
       folder: 'd:\\projects\\pics'
     })
  • How can I remove encode settings from mediainfo ?

    12 octobre 2020, par Aydın Tekin

    I want to know if I can remove encode settings from the mediainfo with mkvpropedit or ffmpeg ?

    


    Video hevc x265 also how do i remove for avc
İ want to remove this :

    


    cpuid=0 / frame-threads=3 / no-wpp / no-pmode / no-pme / no-psnr / no-ssim / log-level=2 / input-csp=1 / input-res=1920x1080 / interlace=0 / total-frames=0 / level-idc=0 / high-tier=1 / uhd-bd=0 / ref=2 / no-allow-non-conformance / no-repeat-headers / annexb / no-aud / no-hrd / info / hash=0 / no-temporal-layers / open-gop / min-keyint=23 / keyint=250 / gop-lookahead=0 / bframes=4 / b-adapt=0 / b-pyramid / bframe-bias=0 / rc-lookahead=15 / lookahead-slices=0 / scenecut=40 / radl=0 / no-splice / no-intra-refresh / ctu=64 / min-cu-size=8 / no-rect / no-amp / max-tu-size=32 / tu-inter-depth=1 / tu-intra-depth=1 / limit-tu=0 / rdoq-level=0 / dynamic-rd=0.00 / no-ssim-rd / signhide / no-tskip / nr-intra=0 / nr-inter=0 / no-constrained-intra / strong-intra-smoothing / max-merge=2 / limit-refs=3 / no-limit-modes / me=1 / subme=1 / merange=57 / temporal-mvp / no-hme / weightp / no-weightb / no-analyze-src-pics / deblock=0:0 / sao / no-sao-non-deblock / rd=2 / selective-sao=4 / early-skip / rskip / fast-intra / no-tskip-fast / no-cu-lossless / no-b-intra / no-splitrd-skip / rdpenalty=0 / psy-rd=2.00 / psy-rdoq=0.00 / no-rd-refine / no-lossless / cbqpoffs=0 / crqpoffs=0 / rc=crf / crf=18.0 / qcomp=0.60 / qpstep=4 / stats-write=0 / stats-read=0 / ipratio=1.40 / pbratio=1.30 / aq-mode=2 / aq-strength=1.00 / cutree / zone-count=0 / no-strict-cbr / qg-size=32 / no-rc-grain / qpmax=69 / qpmin=0 / no-const-vbv / sar=1 / overscan=0 / videoformat=5 / range=0 / colorprim=2 / transfer=2 / colormatrix=2 / chromaloc=0 / display-window=0 / cll=0,0 / min-luma=0 / max-luma=1023 / log2-max-poc-lsb=8 / vui-timing-info / vui-hrd-info / slices=1 / no-opt-qp-pps / no-opt-ref-list-length-pps / no-multi-pass-opt-rps / scenecut-bias=0.05 / no-opt-cu-delta-qp / no-aq-motion / no-hdr / no-hdr-opt / no-dhdr10-opt / no-idr-recovery-sei / analysis-reuse-level=5 / scale-factor=0 / refine-intra=0 / refine-inter=0 / refine-mv=1 / refine-ctu-distortion=0 / no-limit-sao / ctu-info=0 / no-lowpass-dct / refine-analysis-type=0 / copy-pic=1 / max-ausize-factor=1.0 / no-dynamic-refine / no-single-sei / no-hevc-aq / no-svt / no-field / qp-adaptation-range=1.00

    


  • Formula to get frame display number after seek in FFmpeg

    27 septembre 2021, par ZeroDefect

    For a given AV file, I need to be able to seek to a particular video frame number in the file. Because of how decoding works, I am seeking to the nearest I-Frame before the required frame (which may or may not be the requested frame) and then decoding the frames in the GOP until I get to where I need to be. As such, I need to know my current position after seeking.

    


    Having found some posts of a similar nature on SO, I've gone away and collected a few interesting samples to see if I can get a formula to work across many different files, but I'm having a hard time. What works or 1 file may not work for another :

    


    File #1 (Podbox)

    


    Requested to seek to fame #1500. First video frame reports :

    


    AVFrame::pts = 760320
AVFrame::pkt_duration = 512

AVStream::time_base = {1,12800}
AVStream::start_time = 0
AVStream::avg_frame_rate = {25,1}


    


    File #2 (HTE54959)

    


    Requested to seek to fame #1500. First video frame reports :

    


    AVFrame::pts = 1500
AVFrame::pkt_duration = 1

AVStream::time_base = {1,25}
AVStream::start_time = 0
AVStream::avg_frame_rate = {25,1}


    


    File #3 (BuckBunny)

    


    Requested to seek to fame #1800. First video frame reports :

    


    AVFrame::pts = 1563562
AVFrame::pkt_duration = 1001

AVStream::time_base = {1,30000}
AVStream::start_time = 0
AVStream::avg_frame_rate = {30000,1001}


    


    File #4 (HouseDance)

    


    Requested to seek to fame #1800. First video frame reports :

    


    AVFrame::pts = 1800
AVFrame::pkt_duration = 1

AVStream::time_base = {1001,30000}
AVStream::start_time = 0
AVStream::avg_frame_rate = {30000,1001}


    


    For the above files, the following members are always zero :

    


    AVFrame::coded_picture_number
AVFrame::display_picture_number


    


    I have thought about merely using AVFrame::pts / AVFrame::pkt_duration, but I'm not sure that is the right way of doing things. I know for some codecs, there can be a variable frame rate (VFR) which would mean that my method is erroneous ? I assume that the AVFrame::pkt_duration could change per AVFrame ?

    


    I want to emphasize that my issue is not being able to seek. I am seeking to the correct location - I have verified that visually using timecode. My issue is programmatically identifying the frame number of the seek position

    


    Using FFmpeg v4.2.4