
Recherche avancée
Autres articles (26)
-
Ajouter notes et légendes aux images
7 février 2011, parPour pouvoir ajouter notes et légendes aux images, la première étape est d’installer le plugin "Légendes".
Une fois le plugin activé, vous pouvez le configurer dans l’espace de configuration afin de modifier les droits de création / modification et de suppression des notes. Par défaut seuls les administrateurs du site peuvent ajouter des notes aux images.
Modification lors de l’ajout d’un média
Lors de l’ajout d’un média de type "image" un nouveau bouton apparait au dessus de la prévisualisation (...) -
Les autorisations surchargées par les plugins
27 avril 2010, parMediaspip core
autoriser_auteur_modifier() afin que les visiteurs soient capables de modifier leurs informations sur la page d’auteurs -
Taille des images et des logos définissables
9 février 2011, parDans beaucoup d’endroits du site, logos et images sont redimensionnées pour correspondre aux emplacements définis par les thèmes. L’ensemble des ces tailles pouvant changer d’un thème à un autre peuvent être définies directement dans le thème et éviter ainsi à l’utilisateur de devoir les configurer manuellement après avoir changé l’apparence de son site.
Ces tailles d’images sont également disponibles dans la configuration spécifique de MediaSPIP Core. La taille maximale du logo du site en pixels, on permet (...)
Sur d’autres sites (7475)
-
error while compiling x264 in linux
14 avril 2011, par kartulHey all
I'm trying to compile x264 under linux (x64). But it keeps throwing me an error. I've googled around but found nothing. Here's the commandline history :spin@around : /x264$ git clone git ://git.videolan.org/x264.git Cloning into x264... remote : Counting objects : 13539, done. remote : Compressing objects : 100% (4416/4416), done. remote : Total 13539 (delta 11005), reused 11225 (delta 9082) Receiving objects : 100% (13539/13539), 3.29 MiB | 2.79 MiB/s, done. Resolving deltas : 100% (11005/11005), done. spin@around : /x264/x264$ ./configure Found no assembler Minimum version is yasm-0.7.0 If you really want to compile without asm, configure with —disable-asm. spin@around : /x264/x264$ ./configure —disable-asm Platform : X86_64 System : LINUX asm : no avs : no lavf : no ffms : no gpac : no gpl : yes thread : posix filters : crop select_every debug : no gprof : no PIC : no shared : no visualize : no bit depth : 8
You can run 'make' or 'make fprofiled' now.
spin@around : /x264/x264$ make
gcc -Wshadow -O3 -ffast-math -Wall -I. -std=gnu99 -s -fomit-frame-pointer -fno-tree-vectorize -c -o x264.o x264.c
In file included from common/common.h:864,
from x264.c:33 :
common/rectangle.h : In function āx264_macroblock_cache_rectā :
common/rectangle.h:84 : error : āv4siā undeclared (first use in this function)
common/rectangle.h:84 : error : (Each undeclared identifier is reported only once
common/rectangle.h:84 : error : for each function it appears in.)
common/rectangle.h:84 : error : expected ā ;ā before āv16ā
common/rectangle.h:86 : error : ā__m128ā undeclared (first use in this function)
common/rectangle.h:86 : error : expected ā ;ā before āv16ā
common/rectangle.h:87 : error : expected ā ;ā before āv16ā
common/rectangle.h:89 : error : expected ā ;ā before āv16ā
common/rectangle.h:90 : error : expected ā ;ā before āv16ā
make : *** [x264.o] Error 1
spin@around : /x264/x264$and here is the file, from line 83 to 91 :
#if HAVE_VECTOREXT && defined(__SSE__) v4si v16 = v,v,v,v ;
M128( d+s*0+0 ) = (__m128)v16 ;
M128( d+s*1+0 ) = (__m128)v16 ;
if( h == 2 ) return ;
M128( d+s*2+0 ) = (__m128)v16 ;
M128( d+s*3+0 ) = (__m128)v16 ;
#else -
Does Apple AS assembler replace certain NEON instructions with equivalent ones on iOS ?
5 avril 2012, par Yi WangI was trying to use ffmpeg on iOS and was debugging a crash in the optimized arm code. I have discovered that some unsigned (.u16, .u32) instruction have been replaced by signed ones (.i16, .i32). It's easy to see because disassembled instruction on GDB doesn't quite match the source code.
For example,
vrshrn.u32 -> vrshrn.i32
vrshrn.u16 -> vrshrn.i16
vadd.u16 -> vadd.i16My questions :
- Is this behavior correct and expected ? If not, how do we correct it ?
- If they are equivalent, why do we nee need the unsigned ones at all ? Is it because that way the code is more explicit ?
- Is this behavior expected with other platform's toolkit ? For example, Android's toolkit ? (I have heard Apple's AS is an ancient one)
-
How to config FFmpeg for xrgb and Aver Media capture card [closed]
12 mai 2023, par Plotter DesalorI'm trying to use FFmpeg through ffplay to display a capture card output as lossless as possible.


My capture card is named "Live Gamer Ultra-Video"


In OBS, the NV12, YV12, P010 and YUY2 lead to blurriness around text and fine pixels edges, but the XRGB one offer clear output. So I've tried to focus on this mode with FFmpeg as the default one lead to same blurriness seen in OBS.


Running "ffmpeg -f dshow -list_options true -i video="Live Gamer Ultra-Video" show me this result
(i've only kept line with wanted resolution)


ffmpeg version 6.0-essentials_build-www.gyan.dev Copyright (c) 2000-2023 the FFmpeg developers
 built with gcc 12.2.0 (Rev10, 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-bzlib --enable-lzma --enable-zlib --enable-libsrt --enable-libssh --enable-libzmq --enable-avisynth --enable-sdl2 --enable-libwebp --enable-libx264 --enable-libx265 --enable-libxvid --enable-libaom --enable-libopenjpeg --enable-libvpx --enable-mediafoundation --enable-libass --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-libvpl --enable-libgme --enable-libopenmpt --enable-libopencore-amrwb --enable-libmp3lame --enable-libtheora --enable-libvo-amrwbenc --enable-libgsm --enable-libopencore-amrnb --enable-libopus --enable-libspeex --enable-libvorbis --enable-librubberband
 libavutil 58. 2.100 / 58. 2.100
 libavcodec 60. 3.100 / 60. 3.100
 libavformat 60. 3.100 / 60. 3.100
 libavdevice 60. 1.100 / 60. 1.100
 libavfilter 9. 3.100 / 9. 3.100
 libswscale 7. 1.100 / 7. 1.100
 libswresample 4. 10.100 / 4. 10.100
 libpostproc 57. 1.100 / 57. 1.100
[dshow @ 00000240bf0eac40] DirectShow video device options (from video devices)
[dshow @ 00000240bf0eac40] Pin "Capturer" (alternative pin name "0")
[dshow @ 00000240bf0eac40] pixel_format=yuyv422 min s=2560x1440 fps=30 max s=2560x1440 fps=50
[dshow @ 00000240bf0eac40] pixel_format=yuyv422 min s=2560x1440 fps=30 max s=2560x1440 fps=50 (tv, bt709/bt709/unknown, topleft)
[dshow @ 00000240bf0eac40] pixel_format=yuv420p min s=2560x1440 fps=30 max s=2560x1440 fps=60.0002
[dshow @ 00000240bf0eac40] pixel_format=yuv420p min s=2560x1440 fps=30 max s=2560x1440 fps=60.0002 (tv, bt709/bt709/unknown, topleft)
[dshow @ 00000240bf0eac40] pixel_format=nv12 min s=2560x1440 fps=30 max s=2560x1440 fps=60.0002
[dshow @ 00000240bf0eac40] pixel_format=nv12 min s=2560x1440 fps=30 max s=2560x1440 fps=60.0002 (tv, bt709/bt709/unknown, topleft)
[dshow @ 00000240bf0eac40] unknown compression type 0xE436EB7D min s=2560x1440 fps=30 max s=2560x1440 fps=30
[dshow @ 00000240bf0eac40] unknown compression type 0xE436EB7D min s=2560x1440 fps=30 max s=2560x1440 fps=30 (tv, bt709/bt709/unknown, topleft)
[dshow @ 00000240bf0eac40] unknown compression type 0x30313050 min s=2560x1440 fps=30 max s=2560x1440 fps=30
[dshow @ 00000240bf0eac40] unknown compression type 0x30313050 min s=2560x1440 fps=30 max s=2560x1440 fps=30 (tv, bt709/bt709/unknown, topleft)

video=Live Gamer Ultra-Video: Immediate exit requested



"unknown compression type 0xE436EB7D" is a pretty bad start but from https://trac.ffmpeg.org/ticket/6279 I could figured out it was just unproperly parsed RGB24 format


But if I run a very simple "ffplay -f dshow -i video="Live Gamer Ultra-Video" -pixel_format rgb24"
I got this output


ffplay version 6.0-essentials_build-www.gyan.dev Copyright (c) 2003-2023 the FFmpeg developers
 built with gcc 12.2.0 (Rev10, 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-bzlib --enable-lzma --enable-zlib --enable-libsrt --enable-libssh --enable-libzmq --enable-avisynth --enable-sdl2 --enable-libwebp --enable-libx264 --enable-libx265 --enable-libxvid --enable-libaom --enable-libopenjpeg --enable-libvpx --enable-mediafoundation --enable-libass --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-libvpl --enable-libgme --enable-libopenmpt --enable-libopencore-amrwb --enable-libmp3lame --enable-libtheora --enable-libvo-amrwbenc --enable-libgsm --enable-libopencore-amrnb --enable-libopus --enable-libspeex --enable-libvorbis --enable-librubberband
 libavutil 58. 2.100 / 58. 2.100
 libavcodec 60. 3.100 / 60. 3.100
 libavformat 60. 3.100 / 60. 3.100
 libavdevice 60. 1.100 / 60. 1.100
 libavfilter 9. 3.100 / 9. 3.100
 libswscale 7. 1.100 / 7. 1.100
 libswresample 4. 10.100 / 4. 10.100
 libpostproc 57. 1.100 / 57. 1.100
[dshow @ 000001ec3fa39300] Could not set video options 0B f=0/0
video=Live Gamer Ultra-Video: I/O error



How could I use rgb format with this capture card ?


If not possible, any other format leading to proper output would be ok too.
I've tried parameters from this topic Capture full-range/lossless rgb frame from capture card that supports NV12 and YUYV output without any good result sadly.