Recherche avancée

Médias (3)

Mot : - Tags -/plugin

Autres articles (90)

  • Support de tous types de médias

    10 avril 2011

    Contrairement à beaucoup de logiciels et autres plate-formes modernes de partage de documents, MediaSPIP a l’ambition de gérer un maximum de formats de documents différents qu’ils soient de type : images (png, gif, jpg, bmp et autres...) ; audio (MP3, Ogg, Wav et autres...) ; vidéo (Avi, MP4, Ogv, mpg, mov, wmv et autres...) ; contenu textuel, code ou autres (open office, microsoft office (tableur, présentation), web (html, css), LaTeX, Google Earth) (...)

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

  • Les formats acceptés

    28 janvier 2010, par

    Les commandes suivantes permettent d’avoir des informations sur les formats et codecs gérés par l’installation local de ffmpeg :
    ffmpeg -codecs ffmpeg -formats
    Les format videos acceptés en entrée
    Cette liste est non exhaustive, elle met en exergue les principaux formats utilisés : h264 : H.264 / AVC / MPEG-4 AVC / MPEG-4 part 10 m4v : raw MPEG-4 video format flv : Flash Video (FLV) / Sorenson Spark / Sorenson H.263 Theora wmv :
    Les formats vidéos de sortie possibles
    Dans un premier temps on (...)

Sur d’autres sites (11886)

  • libavutil/hwcontext_d3d11va : adding more texture information to the D3D11 hwcontext API

    20 août 2021, par Artem Galin
    libavutil/hwcontext_d3d11va : adding more texture information to the D3D11 hwcontext API

    Microsoft VideoProcessor requires texture with D3DUSAGE_RENDERTARGET flag as output.
    
There is no way to allocate array of textures with D3D11_BIND_RENDER_TARGET flag
    
and .ArraySize > 2 by ID3D11Device_CreateTexture2D due to the Microsoft limitation.
    
Adding AVD3D11FrameDescriptors array to store array of single textures
    
instead of texture with multiple slices resolves this.
    

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

  • Warning VSP2005 & Error VSP1048 when instrumenting C++ code dynamically linked to FFMPEG

    6 mai 2015, par TTJG

    I am trying to profile my project with the Instrumentation profiler of Visual Studio 2013 Ultimate. I have a 64bit C++ project which is dynamically linked to FFMPEG. However, the profiler is giving me the following error Error VSP1048: Internal instrumentation error. I don’t want to profile FFMPEG but only analyze the performance of my code. I downloaded the pre-built FFMPEG libs from this site ffmpeg.zeranoe.com/builds/. The project is also linking against Boost, live555 and x264. It is running and debugging fine. The full output of the profiler is :

    Profiling started.
    
Instrumenting ...\Player.exe in place
    
Info VSP3049: Small functions will be excluded from instrumentation.
    
Microsoft (R) VSInstr Post-Link Instrumentation 12.0.21005 x64
    
Copyright (C) Microsoft Corp. All rights reserved.
    
Warning VSP2005: Internal instrumentation warning: The object '...\ffmpeg-20150506-git-a2190de-win64-dev\lib\avutil.lib(dbyqh.o)' was built without debug information.
    
File to Process:
    
\Player.exe --> ...\Player.exe
    
Original file backed up to ...\Player.exe.orig
    
Warning VSP2005: Internal instrumentation warning: The object '...\ffmpeg-20150506-git-a2190de-win64-dev\lib\avutil.lib(dbyqh.o)' was built without debug information.
    
Error VSP1048: Internal instrumentation error.
    
PRF0002: Instrumentation failed with these options: /u "...\Player.exe"   /excludesmallfuncs.  Please check the output window for additional details.
    
Data written to ...\Player150506.vsp.
    
Profiling finished.
    
File contains no data buffers
    
File contains no data buffers
    
Analysis failed
    
Profiling complete.

    Any ideas how this could be solved ? I have found very little about this issue on the Internet.

  • Warning VSP2005 & Error VSP1048 when instrumenting C++ code dynamically linked to FFMPEG

    20 juin 2018, par TTJG

    I am trying to profile my project with the Instrumentation profiler of Visual Studio 2013 Ultimate. I have a 64bit C++ project which is dynamically linked to FFMPEG. However, the profiler is giving me the following error Error VSP1048: Internal instrumentation error. I don’t want to profile FFMPEG but only analyze the performance of my code. I downloaded the pre-built FFMPEG libs from this site ffmpeg.zeranoe.com/builds/. The project is also linking against Boost, live555 and x264. It is running and debugging fine. The full output of the profiler is :

    Profiling started.
    
Instrumenting ...\Player.exe in place
    
Info VSP3049: Small functions will be excluded from instrumentation.
    
Microsoft (R) VSInstr Post-Link Instrumentation 12.0.21005 x64
    
Copyright (C) Microsoft Corp. All rights reserved.
    
Warning VSP2005: Internal instrumentation warning: The object '...\ffmpeg-20150506-git-a2190de-win64-dev\lib\avutil.lib(dbyqh.o)' was built without debug information.
    
File to Process:
    
\Player.exe --> ...\Player.exe
    
Original file backed up to ...\Player.exe.orig
    
Warning VSP2005: Internal instrumentation warning: The object '...\ffmpeg-20150506-git-a2190de-win64-dev\lib\avutil.lib(dbyqh.o)' was built without debug information.
    
Error VSP1048: Internal instrumentation error.
    
PRF0002: Instrumentation failed with these options: /u "...\Player.exe"   /excludesmallfuncs.  Please check the output window for additional details.
    
Data written to ...\Player150506.vsp.
    
Profiling finished.
    
File contains no data buffers
    
File contains no data buffers
    
Analysis failed
    
Profiling complete.

    Any ideas how this could be solved ? I have found very little about this issue on the Internet.

Navigation