Recherche avancée

Médias (91)

Autres articles (67)

  • Les vidéos

    21 avril 2011, par

    Comme les documents de type "audio", Mediaspip affiche dans la mesure du possible les vidéos grâce à la balise html5 .
    Un des inconvénients de cette balise est qu’elle n’est pas reconnue correctement par certains navigateurs (Internet Explorer pour ne pas le nommer) et que chaque navigateur ne gère en natif que certains formats de vidéos.
    Son avantage principal quant à lui est de bénéficier de la prise en charge native de vidéos dans les navigateur et donc de se passer de l’utilisation de Flash et (...)

  • Amélioration de la version de base

    13 septembre 2013

    Jolie sélection multiple
    Le plugin Chosen permet d’améliorer l’ergonomie des champs de sélection multiple. Voir les deux images suivantes pour comparer.
    Il suffit pour cela d’activer le plugin Chosen (Configuration générale du site > Gestion des plugins), puis de configurer le plugin (Les squelettes > Chosen) en activant l’utilisation de Chosen dans le site public et en spécifiant les éléments de formulaires à améliorer, par exemple select[multiple] pour les listes à sélection multiple (...)

  • Emballe médias : à quoi cela sert ?

    4 février 2011, par

    Ce plugin vise à gérer des sites de mise en ligne de documents de tous types.
    Il crée des "médias", à savoir : un "média" est un article au sens SPIP créé automatiquement lors du téléversement d’un document qu’il soit audio, vidéo, image ou textuel ; un seul document ne peut être lié à un article dit "média" ;

Sur d’autres sites (6101)

  • Affectiva/Affdex SDK video file analysis error in Android

    5 juin 2017, par Abhishek Asole

    I have an app which records the video in the background and after a button click, the Affdex API analyzes the recorded video files stored. The application is behaving weirdly where it works the first time, but gives the following error later :

    Note : I am not recording any audio while the video is being recorded

    06-01 17:41:16.010 6829-8352/com.sample.camerarecorder E/Affectiva : Invalid index 0, size is 0
    06-01 17:41:16.052 6829-8352/com.sample.camerarecorder W/VideoCapabilities : Unrecognized profile 2130706433 for video/avc
    06-01 17:41:16.062 6829-8352/com.sample.camerarecorder W/VideoCapabilities : Unrecognized profile/level 0/3 for video/mpeg2
    06-01 17:41:16.064 6829-8352/com.sample.camerarecorder W/VideoCapabilities : Unrecognized profile/level 0/3 for video/mpeg2
    06-01 17:41:16.068 6829-8352/com.sample.camerarecorder W/VideoCapabilities : Unsupported mime video/x-ms-wmv
    06-01 17:41:16.069 6829-8352/com.sample.camerarecorder W/VideoCapabilities : Unsupported mime video/divx
    06-01 17:41:16.071 6829-8352/com.sample.camerarecorder W/VideoCapabilities : Unsupported mime video/divx311
    06-01 17:41:16.072 6829-8352/com.sample.camerarecorder W/VideoCapabilities : Unsupported mime video/divx4
    06-01 17:41:16.075 6829-8352/com.sample.camerarecorder W/VideoCapabilities : Unsupported mime video/mp4v-esdp
    06-01 17:41:16.086 6829-8352/com.sample.camerarecorder I/VideoCapabilities : Unsupported profile 4 for video/mp4v-es
    06-01 17:41:16.089 6829-8352/com.sample.camerarecorder W/AudioCapabilities : Unsupported mime audio/x-ape
    06-01 17:41:16.090 6829-8352/com.sample.camerarecorder W/AudioCapabilities : Unsupported mime audio/ffmpeg
    06-01 17:41:16.090 6829-8352/com.sample.camerarecorder W/AudioCapabilities : Unsupported mime audio/dts
    06-01 17:41:16.092 6829-8352/com.sample.camerarecorder W/AudioCapabilities : Unsupported mime audio/mpeg-L2
    06-01 17:41:16.092 6829-8352/com.sample.camerarecorder W/AudioCapabilities : Unsupported mime audio/vnd.rn-realaudio
    06-01 17:41:16.093 6829-8352/com.sample.camerarecorder W/AudioCapabilities : Unsupported mime audio/x-ms-wma
    06-01 17:41:16.094 6829-8352/com.sample.camerarecorder W/VideoCapabilities : Unsupported mime video/divx
    06-01 17:41:16.095 6829-8352/com.sample.camerarecorder W/VideoCapabilities : Unsupported mime video/x-flv
    06-01 17:41:16.099 6829-8352/com.sample.camerarecorder W/VideoCapabilities : Unsupported mime video/vnd.rn-realvideo
    06-01 17:41:16.100 6829-8352/com.sample.camerarecorder W/VideoCapabilities : Unsupported mime video/vc1
    06-01 17:41:16.101 6829-8352/com.sample.camerarecorder W/VideoCapabilities : Unsupported mime video/ffmpeg
    06-01 17:41:16.102 6829-8352/com.sample.camerarecorder W/VideoCapabilities : Unsupported mime video/x-ms-wmv
    06-01 17:41:16.104 6829-8481/com.sample.camerarecorder I/OMXClient : Using client-side OMX mux.
    06-01 17:41:16.161 6829-8480/com.sample.camerarecorder I/MediaCodec : [OMX.google.h264.decoder] setting surface generation to 6992898
    06-01 17:41:16.161 6829-8481/com.sample.camerarecorder W/OMXNodeInstance : [1:google.h264.decoder] component does not support metadata mode ; using fallback
    06-01 17:41:16.161 6829-8481/com.sample.camerarecorder E/ACodec : [OMX.google.h264.decoder] storeMetaDataInBuffers failed w/ err -1010

  • avformat/hls : Check local file extensions

    3 juin 2017, par Michael Niedermayer
    avformat/hls : Check local file extensions

    This reduces the attack surface of local file-system
    
information leaking.
    

    It prevents the existing exploit leading to an information leak. As
    
well as similar hypothetical attacks.
    

    Leaks of information from files and symlinks ending in common multimedia extensions
    
are still possible. But files with sensitive information like private keys and passwords
    
generally do not use common multimedia filename extensions.
    
It does not stop leaks via remote addresses in the LAN.
    

    The existing exploit depends on a specific decoder as well.
    
It does appear though that the exploit should be possible with any decoder.
    
The problem is that as long as sensitive information gets into the decoder,
    
the output of the decoder becomes sensitive as well.
    
The only obvious solution is to prevent access to sensitive information. Or to
    
disable hls or possibly some of its feature. More complex solutions like
    
checking the path to limit access to only subdirectories of the hls path may
    
work as an alternative. But such solutions are fragile and tricky to implement
    
portably and would not stop every possible attack nor would they work with all
    
valid hls files.
    

    Developers have expressed their dislike / objected to disabling hls by default as well
    
as disabling hls with local files. There also where objections against restricting
    
remote url file extensions. This here is a less robust but also lower
    
inconvenience solution.
    
It can be applied stand alone or together with other solutions.
    
limiting the check to local files was suggested by nevcairiel
    

    This recommits the security fix without the author name joke which was
    
originally requested by Nicolas.
    

    Found-by : Emil Lerner and Pavel Cheremushkin
    
Reported-by : Thierry Foucu <tfoucu@google.com>
    

    Signed-off-by : Michael Niedermayer <michael@niedermayer.cc>
    • [DH] libavformat/hls.c

  • dxva : add declarative profile checks

    22 juin 2017, par wm4
    dxva : add declarative profile checks

    Make supported codec profiles part of each dxva_modes entry. Every DXVA2
    
mode is representative for a codec with a subset of supported profiles,
    
so reflecting that in dxva_modes seems appropriate.
    

    In practice, this will more strictly check MPEG2 profiles, will stop
    
relying on the surface format checks for selecting the correct HEVC
    
profile, and remove the verbose messages for mismatching H264/HEVC
    
profiles. Instead of the latter, it will now print the more nebulous "No
    
decoder device for codec found" verbose message.
    

    This also respects AV_HWACCEL_FLAG_ALLOW_PROFILE_MISMATCH. Move the
    
Main10 HEVC entry before the normal one to make this work better.
    

    Originally inspired by VLC’s code.
    

    Signed-off-by : Luca Barbato <lu_zero@gentoo.org>
    • [DBH] libavcodec/dxva2.c

Navigation