Recherche avancée

Médias (0)

Mot : - Tags -/organisation

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

Autres articles (2)

  • Les tâches Cron régulières de la ferme

    1er décembre 2010, par

    La gestion de la ferme passe par l’exécution à intervalle régulier de plusieurs tâches répétitives dites Cron.
    Le super Cron (gestion_mutu_super_cron)
    Cette tâche, planifiée chaque minute, a pour simple effet d’appeler le Cron de l’ensemble des instances de la mutualisation régulièrement. Couplée avec un Cron système sur le site central de la mutualisation, cela permet de simplement générer des visites régulières sur les différents sites et éviter que les tâches des sites peu visités soient trop (...)

  • Selection of projects using MediaSPIP

    2 mai 2011, par

    The examples below are representative elements of MediaSPIP specific uses for specific projects.
    MediaSPIP farm @ Infini
    The non profit organizationInfini develops hospitality activities, internet access point, training, realizing innovative projects in the field of information and communication technologies and Communication, and hosting of websites. It plays a unique and prominent role in the Brest (France) area, at the national level, among the half-dozen such association. Its members (...)

Sur d’autres sites (1458)

  • lavf/movenc : enable dvh1 FourCC

    5 février 2023, par Damiano Galassi
    lavf/movenc : enable dvh1 FourCC

    This is required to pass through Dolby Vision metadata to x265.
    
Profiles 5 and 8 require the "dvh1" fourCC :
    
https://professional.dolby.com/siteassets/content-creation/dolby-vision-for-content-creators/dolby-vision-streams-within-the-http-live-streaming-format-v2.0-13-november-2018.pdf#unique_10
    
https://professional.dolby.com/siteassets/content-creation/dolby-vision-for-content-creators/dolbyvisioninmpegdashspecification_v2_0_public_20190107.pdf#unique_13
    
https://professional.dolby.com/siteassets/content-creation/dolby-vision-for-content-creators/dolby_vision_bitstreams_within_the_iso_base_media_file_format_dec2017.pdf
    

    See also https://github.com/HandBrake/HandBrake/pull/4838 for more
    
details.
    

    Fixes : https://trac.ffmpeg.org/ticket/10257
    • [DH] libavformat/movenc.c

  • FFmpeg trim filter fails to use sexagisimal time specification and the output stream is empty. Is it a bug and is there a fix ?

    29 novembre 2020, par Link-akro

    With ffmpeg the trim filter (or its audio variant atrim) malfunctions whenever i try to write a sexagesimal time specification for the boundaries or duration parameters of the filter : the result is always an empty stream.

    


    According to the documentation i already linked, which was generated on November 26, 2020 so far, the time duration specification should be supported.

    


    


    start, end, and duration are expressed as time duration specifications

    


    


    Quote of the spec.

    


    


    [-][HH :]MM:SS[.m...]

    


    


    


    [-]S+[.m...][s|ms|us]

    


    


    I am working in a Windows_10-64bit and scripting in its CMD.exe command-line, should it matter.

    


    Here is an instance of trimming a video stream out of a media file with hardcoded value for simplicity. The audio is retained unless i use atrim as well.
We may or may not append the setpts filter as recommended in the documentation henceforth setpts=PTS-STARTPTS if we want to shift the stream to start at the beginning of the cut range.

    


        ffmpeg -i sample-counter.mp4 -vf "trim=start=start='1:2':end='1:5'" sample-counter-trimmed.mp4


    


    If i use decimal it works as intended.

    


        ffmpeg -i sample-counter.mp4 -vf "trim=start=start='2':end='5'" sample-counter-trimmed.mp4


    


    This is the banner of my ffmpeg build. We may see it is the latest build by gyan.dev at the moment i post this.

    


        ffmpeg version 4.3.1-2020-11-19-full_build-www.gyan.dev Copyright (c) 2000-2020 the FFmpeg developers
      built with gcc 10.2.0 (Rev5, Built by MSYS2 project)
      configuration: --enable-gpl --enable-version3 --enable-static --disable-w32threads --disable-autodetect --enable-fontconfig --enable-iconv --enable-gnutls --enable-libxml2 --enable-gmp --enable-lzma --enable-libsnappy --enable-zlib --enable-libsrt --enable-libssh --enable-libzmq --enable-avisynth --enable-libbluray --enable-libcaca --enable-sdl2 --enable-libdav1d --enable-libzvbi --enable-librav1e --enable-libwebp --enable-libx264 --enable-libx265 --enable-libxvid --enable-libaom --enable-libopenjpeg --enable-libvpx --enable-libass --enable-frei0r --enable-libfreetype --enable-libfribidi --enable-libvidstab --enable-libvmaf --enable-libzimg --enable-amf --enable-cuda-llvm --enable-cuvid --enable-ffnvcodec --enable-nvdec --enable-nvenc --enable-d3d11va --enable-dxva2 --enable-libmfx --enable-libcdio --enable-libgme --enable-libmodplug --enable-libopenmpt --enable-libopencore-amrwb --enable-libmp3lame --enable-libshine --enable-libtheora --enable-libtwolame --enable-libvo-amrwbenc --enable-libilbc --enable-libgsm --enable-libopencore-amrnb --enable-libopus --enable-libspeex --enable-libvorbis --enable-ladspa --enable-libbs2b --enable-libflite --enable-libmysofa --enable-librubberband --enable-libsoxr --enable-chromaprint


    


    The incorrect stream is always reported as 0kB weight in the output of ffmpeg. I confirmed with ffprobe Movie_Countdown-trim-2-5.mov -show_streams -show_entries format=duration that the incorrect stream is duration zero.

    


    Should i report it as a bug ? Is there some correction or workaround ?

    


    I would rather a solution with the trim filter itself, but if not possible a CMD batch scripting.
We should not need a different filter like select or seeking option like there are tutorials and questions/answers everywhere already. Scripting would be straight-forward in a proper *nix shell+distrib and taught everywhere so it is not worth caring while CMD answers on the other hand are rare so a scripting workaround for CMD would have some microcosmic worth since making one is considerably less straight-forward than a shell with modern mathematics and parsing abilities built-in or packaged.

    


  • libavutil/hwcontext_qsv : add usage child_device_type argument to explicitly select...

    20 août 2021, par Artem Galin
    libavutil/hwcontext_qsv : add usage child_device_type argument to explicitly select d3d11va/DX11 device type

    UPD : Rebase of last patch set over current master and use DX9 as default device type.
    

    Makes selection of dxva2/DX9 device type by default as before with explicit d3d11va/DX11 usage to cover more HW configurations.
    
Added warning message to expect changing default device type in the future.
    

    Fixes TGL / AV1 decode as requires DX11 with explicit DX11 type
    
selection.
    

    Add headless/multi adapter support and fixes :
    
    https://trac.ffmpeg.org/ticket/7511
    
    https://trac.ffmpeg.org/ticket/6827
    
    http://ffmpeg.org/pipermail/ffmpeg-trac/2017-November/041901.html
    
    https://trac.ffmpeg.org/ticket/7933
    
    https://github.com/InitialForce/FFmpeg/commit/338fbcd5bba1de0e1b3e3bad8985eee2fdfbeca1
    
    https://github.com/jellyfin/jellyfin/issues/2626#issuecomment-602153952
    

    Any other fixes are welcome including OpenCL interop patch since I don't have proper setup to validate this use case
    

    Decoding, encoding, transcoding have been validated.
    

    child_device_type option is responsible for d3d11va/dxva2 device selection
    

    Usage examples :
    

    DirectX 11 :
    
    -init_hw_device qsv:hw,child_device_type=d3d11va
    
    -init_hw_device qsv:hw,child_device_type=d3d11va,child_device=0
    
OR
    
    -init_hw_device d3d11va=dx -init_hw_device qsv@dx
    

    DirectX 9 is still supported but requires explicit selection :
    
    -init_hw_device qsv:hw,child_device_type=dxva2
    
OR
    
    -init_hw_device dxva2=dx -init_hw_device qsv@dx
    

    Signed-off-by : Artem Galin <artem.galin@intel.com>
    • [DH] doc/ffmpeg.texi
    • [DH] libavutil/hwcontext_qsv.c

Navigation