Recherche avancée

Médias (1)

Mot : - Tags -/blender

Autres articles (65)

  • Gestion générale des documents

    13 mai 2011, par

    MédiaSPIP ne modifie jamais le document original mis en ligne.
    Pour chaque document mis en ligne il effectue deux opérations successives : la création d’une version supplémentaire qui peut être facilement consultée en ligne tout en laissant l’original téléchargeable dans le cas où le document original ne peut être lu dans un navigateur Internet ; la récupération des métadonnées du document original pour illustrer textuellement le fichier ;
    Les tableaux ci-dessous expliquent ce que peut faire MédiaSPIP (...)

  • Des sites réalisés avec MediaSPIP

    2 mai 2011, par

    Cette page présente quelques-uns des sites fonctionnant sous MediaSPIP.
    Vous pouvez bien entendu ajouter le votre grâce au formulaire en bas de page.

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

Sur d’autres sites (5729)

  • Why does Apple support H.265 playback, but not when using HLS ? [closed]

    13 mars, par clark wu

    Apple devices (iPhone, iPad, macOS Safari) can natively play H.265 (HEVC) videos in .mp4 or .mov format. However, when I try to convert the same video to HLS, it fails to play. Here’s what I tested :

    


    Test Cases

    


    ✅ Directly playing H.265 .mp4 → Works fine

    


    ❌ H.265 + Opus → HLS (fMP4) → Fails

    


    ❌ H.265 + AAC → HLS (TS) → Fails

    


    ✅ H.264 + Opus → HLS fMP4 → Works fine (video + audio)

    


    ✅ H.264 + Opus → HLS TS → Video plays, but no audio

    


    ❌ H.265 + AAC → HLS fMP4 → Doesn’t play at all

    


    FFmpeg Commands Used

    


    1️⃣ H.265 + Opus (fMP4 segments)

    


    ffmpeg -i input.mp4 -c:v copy -c:a copy -hls_segment_type fmp4 -hls_time 10 -hls_list_size 0 -hls_flags independent_segments output.m3u8


    


    2️⃣ H.265 + AAC (TS segments)

    


    ffmpeg -i input.mp4 -c:v copy -c:a copy -hls_time 10 -hls_list_size 0 -hls_flags independent_segments output.m3u8


    


    Playback Attempts

    


    Vidstack.js player (Fails)

    


    Several online M3U8 players (All fail)

    


    Key Questions

    


    Why does Apple support H.265 in MP4 but not in HLS ?

    


    Is this an HLS specification limitation ?

    


    Does the audio codec (Opus / AAC) affect playback ?

    


    Does HLS require a specific HEVC profile/level ?

    


    Is HLS only compatible with AVC, not HEVC ?

    


    Looking for Answers

    


    Has anyone successfully played H.265 + HLS on Apple devices ?

    


    Are there any official Apple HLS specifications regarding HEVC support ?

    


    Possible workarounds or alternative solutions ?

    


    Would appreciate any insights or help from the community ! Thanks !

    


  • ffmpeg - Unrecognized option lavfi_complex

    4 février 2019, par Milan

    I’m working with headphone filter command from official documentation - https://ffmpeg.org/ffmpeg-filters.html#Examples-20

    ffmpeg -i input.wav -lavfi-complex "amovie=azi_270_ele_0_DFC.wav[sr],amovie=azi_90_ele_0_DFC.wav[sl],amovie=azi_225_ele_0_DFC.wav[br],amovie=azi_135_ele_0_DFC.wav[bl],amovie=azi_0_ele_0_DFC.wav,asplit[fc][lfe],amovie=azi_35_ele_0_DFC.wav[fl],amovie=azi_325_ele_0_DFC.wav[fr],[a:0][fl][fr][fc][lfe][bl][br][sl][sr]headphone=FL|FR|FC|LFE|BL|BR|SL|SR"
    
output.wav

    but I’m getting error

     Unrecognized option 'lavfi-complex'.

    Here is my ffmpeg version info -

    ffmpeg -version
    
ffmpeg version N-92377-g0c6d4e7ba4 Copyright (c) 2000-2018 the FFmpeg developers
    
built with gcc 8.2.1 (GCC) 20181017
    
configuration: --enable-gpl --enable-version3 --enable-sdl2 --enable-fontconfig --enable-gnutls --enable-iconv --enable-libass --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
    
libavutil      56. 23.101 / 56. 23.101
    
libavcodec     58. 39.100 / 58. 39.100
    
libavformat    58. 22.100 / 58. 22.100
    
libavdevice    58.  6.100 / 58.  6.100
    
libavfilter     7. 43.100 /  7. 43.100
    
libswscale      5.  4.100 /  5.  4.100
    
libswresample   3.  4.100 /  3.  4.100
    
libpostproc    55.  4.100 / 55.  4.100

  • NVidia driver libraries in nvidia/cuda image

    16 février 2018, par Islam Sabyrgaliyev

    I want to run ffmpeg with cuvid hw-accelerated decoding in the container based on official nvidia/cuda image. Ffmpeg is not able to find libnvcuvid.so, although there are all required cuda libs.
    The output of ldconfig -p | grep libnv from the container :

    libnvrtc.so (libc6,x86-64) => /usr/local/cuda-9.0/targets/x86_64-linux/lib/libnvrtc.so
    
libnvrtc-builtins.so (libc6,x86-64) => /usr/local/cuda-9.0/targets/x86_64-linux/lib/libnvrtc-builtins.so
    
libnvidia-ptxjitcompiler.so.1 (libc6,x86-64) => /usr/lib/x86_64-linux-gnu/libnvidia-ptxjitcompiler.so.1
    
libnvidia-opencl.so.1 (libc6,x86-64) => /usr/lib/x86_64-linux-gnu/libnvidia-opencl.so.1
    
libnvidia-ml.so.1 (libc6,x86-64) => /usr/lib/x86_64-linux-gnu/libnvidia-ml.so.1
    
libnvidia-fatbinaryloader.so.390.12 (libc6,x86-64) => /usr/lib/x86_64-linux-gnu/libnvidia-fatbinaryloader.so.390.12
    
libnvidia-compiler.so.390.12 (libc6,x86-64) => /usr/lib/x86_64-linux-gnu/libnvidia-compiler.so.390.12
    
libnvidia-cfg.so.1 (libc6,x86-64) => /usr/lib/x86_64-linux-gnu/libnvidia-cfg.so.1
    
libnvgraph.so (libc6,x86-64) => /usr/local/cuda-9.0/targets/x86_64-linux/lib/libnvgraph.so
    
libnvblas.so (libc6,x86-64) => /usr/local/cuda-9.0/targets/x86_64-linux/lib/libnvblas.so
    
libnvToolsExt.so (libc6,x86-64) => /usr/local/cuda-9.0/targets/x86_64-linux/lib/libnvToolsExt.so

    Should I just copy libnvcuvid.so from the host ? Wouldn’t it break if underlying driver version changes ?

Navigation