
Recherche avancée
Médias (91)
-
Les Miserables
9 décembre 2019, par
Mis à jour : Décembre 2019
Langue : français
Type : Textuel
-
VideoHandle
8 novembre 2019, par
Mis à jour : Novembre 2019
Langue : français
Type : Video
-
Somos millones 1
21 juillet 2014, par
Mis à jour : Juin 2015
Langue : français
Type : Video
-
Un test - mauritanie
3 avril 2014, par
Mis à jour : Avril 2014
Langue : français
Type : Textuel
-
Pourquoi Obama lit il mes mails ?
4 février 2014, par
Mis à jour : Février 2014
Langue : français
-
IMG 0222
6 octobre 2013, par
Mis à jour : Octobre 2013
Langue : français
Type : Image
Autres articles (79)
-
Websites made with MediaSPIP
2 mai 2011, parThis page lists some websites based on MediaSPIP.
-
Amélioration de la version de base
13 septembre 2013Jolie 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, parCe 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 (10234)
-
How to detect anamorphic video with FFProbe ?
29 mai 2015, par FlavorScapeThis is the output I get using FFProbe for a video I’m certain is anamorphic. I’ve converted it as a test with ffmpeg and the results are consistent with the video having a different PAR and DAR (video is squished). I ran some command line params to fix anamorphic video and it worked. Possibly my diagnosis is incorrect, the PAR and DAR are just plain wrong ?
The code I used to "correct" the anamamorphic is
--custom-anamorphic --display-width 1280 --keep-display-aspect --modulus 8 --crop 0:0:0:0
Is there an additional command with FFProbe to detect for anamorphic ? So far I’m just seeing if the sample_aspect_ratio and display_aspect_ratio are the same or not.
Additionally, a ratio of 0:1 seems incorrect. My video is not infinitely wide. Is there a bug with FFProbe output ?
This is the command
-print_format json -show_format -show_streams {originalFilePath}
FFProbe version N-54233-g86190af built on Jun 27 2013 outputs the following :
"Output{
\"streams\": [
{
\"index\": 0,
\"codec_name\": \"h264\",
\"codec_long_name\": \"H.264/AVC/MPEG-4AVC/MPEG-4part10\",
\"profile\": \"Main\",
\"codec_type\": \"video\",
\"codec_time_base\": \"1/5994\",
\"codec_tag_string\": \"avc1\",
\"codec_tag\": \"0x31637661\",
\"width\": 1280,
\"height\": 720,
\"has_b_frames\": 0,
\"sample_aspect_ratio\": \"0: 1\",
\"display_aspect_ratio\": \"0: 1\",
\"pix_fmt\": \"yuv420p\",
\"level\": 31,
\"r_frame_rate\": \"2997/100\",
\"avg_frame_rate\": \"2997/100\",
\"time_base\": \"1/2997\",
\"start_pts\": 0,
\"start_time\": \"0.000000\",
\"duration_ts\": 204100,
\"duration\": \"68.101435\",
\"bit_rate\": \"3894381\",
\"nb_frames\": \"2041\",
\"disposition\": {
\"default\": 0,
\"dub\": 0,
\"original\": 0,
\"comment\": 0,
\"lyrics\": 0,
\"karaoke\": 0,
\"forced\": 0,
\"hearing_impaired\": 0,
\"visual_impaired\": 0,
\"clean_effects\": 0,
\"attached_pic\": 0
},
\"tags\": {
\"creation_time\": \"2013-05-0318: 33: 37\",
\"language\": \"eng\",
\"handler_name\": \"AppleAliasDataHandler\"
}
},
{
\"index\": 1,
\"codec_name\": \"aac\",
\"codec_long_name\": \"AAC(AdvancedAudioCoding)\",
\"codec_type\": \"audio\",
\"codec_time_base\": \"1/44100\",
\"codec_tag_string\": \"mp4a\",
\"codec_tag\": \"0x6134706d\",
\"sample_fmt\": \"fltp\",
\"sample_rate\": \"44100\",
\"channels\": 2,
\"bits_per_sample\": 0,
\"r_frame_rate\": \"0/0\",
\"avg_frame_rate\": \"0/0\",
\"time_base\": \"1/44100\",
\"start_pts\": 0,
\"start_time\": \"0.000000\",
\"duration_ts\": 3003392,
\"duration\": \"68.104127\",
\"bit_rate\": \"125304\",
\"nb_frames\": \"2933\",
\"disposition\": {
\"default\": 0,
\"dub\": 0,
\"original\": 0,
\"comment\": 0,
\"lyrics\": 0,
\"karaoke\": 0,
\"forced\": 0,
\"hearing_impaired\": 0,
\"visual_impaired\": 0,
\"clean_effects\": 0,
\"attached_pic\": 0
},
\"tags\": {
\"creation_time\": \"2013-05-0318: 33: 37\",
\"language\": \"eng\",
\"handler_name\": \"AppleAliasDataHandler\"
}
}
],
\"format\": {
\"filename\": \"\\\\\\\\dell690\\\\vsf\\\\_asset_intake\\\\v2\\\\ed69c939-4fe1-40dd-a045-db72ed2e0009\\\\original\\\\USTC_Overview2.mov\",
\"nb_streams\": 2,
\"format_name\": \"mov,
mp4,
m4a,
3gp,
3g2,
mj2\",
\"format_long_name\": \"QuickTime/MOV\",
\"start_time\": \"0.000000\",
\"duration\": \"68.100000\",
\"size\": \"34267583\",
\"bit_rate\": \"4025560\",
\"tags\": {
\"major_brand\": \"qt\",
\"minor_version\": \"537199360\",
\"compatible_brands\": \"qt\",
\"creation_time\": \"2013-05-0318: 33: 37\"
}
}
}" -
aarch64 : Add NEON optimizations for 10 and 12 bit vp9 MC
14 décembre 2016, par Martin Storsjöaarch64 : Add NEON optimizations for 10 and 12 bit vp9 MC
This work is sponsored by, and copyright, Google.
This has mostly got the same differences to the 8 bit version as
in the arm version. For the horizontal filters, we do 16 pixels
in parallel as well. For the 8 pixel wide vertical filters, we can
accumulate 4 rows before storing, just as in the 8 bit version.Examples of runtimes vs the 32 bit version, on a Cortex A53 :
ARM AArch64
vp9_avg4_10bpp_neon : 35.7 30.7
vp9_avg8_10bpp_neon : 93.5 84.7
vp9_avg16_10bpp_neon : 324.4 296.6
vp9_avg32_10bpp_neon : 1236.5 1148.2
vp9_avg64_10bpp_neon : 4639.6 4571.1
vp9_avg_8tap_smooth_4h_10bpp_neon : 130.0 128.0
vp9_avg_8tap_smooth_4hv_10bpp_neon : 440.0 440.5
vp9_avg_8tap_smooth_4v_10bpp_neon : 114.0 105.5
vp9_avg_8tap_smooth_8h_10bpp_neon : 327.0 314.0
vp9_avg_8tap_smooth_8hv_10bpp_neon : 918.7 865.4
vp9_avg_8tap_smooth_8v_10bpp_neon : 330.0 300.2
vp9_avg_8tap_smooth_16h_10bpp_neon : 1187.5 1155.5
vp9_avg_8tap_smooth_16hv_10bpp_neon : 2663.1 2591.0
vp9_avg_8tap_smooth_16v_10bpp_neon : 1107.4 1078.3
vp9_avg_8tap_smooth_64h_10bpp_neon : 17754.6 17454.7
vp9_avg_8tap_smooth_64hv_10bpp_neon : 33285.2 33001.5
vp9_avg_8tap_smooth_64v_10bpp_neon : 16066.9 16048.6
vp9_put4_10bpp_neon : 25.5 21.7
vp9_put8_10bpp_neon : 56.0 52.0
vp9_put16_10bpp_neon/armv8 : 183.0 163.1
vp9_put32_10bpp_neon/armv8 : 678.6 563.1
vp9_put64_10bpp_neon/armv8 : 2679.9 2195.8
vp9_put_8tap_smooth_4h_10bpp_neon : 120.0 118.0
vp9_put_8tap_smooth_4hv_10bpp_neon : 435.2 435.0
vp9_put_8tap_smooth_4v_10bpp_neon : 107.0 98.2
vp9_put_8tap_smooth_8h_10bpp_neon : 303.0 290.0
vp9_put_8tap_smooth_8hv_10bpp_neon : 893.7 828.7
vp9_put_8tap_smooth_8v_10bpp_neon : 305.5 263.5
vp9_put_8tap_smooth_16h_10bpp_neon : 1089.1 1059.2
vp9_put_8tap_smooth_16hv_10bpp_neon : 2578.8 2452.4
vp9_put_8tap_smooth_16v_10bpp_neon : 1009.5 933.5
vp9_put_8tap_smooth_64h_10bpp_neon : 16223.4 15918.6
vp9_put_8tap_smooth_64hv_10bpp_neon : 32153.0 31016.2
vp9_put_8tap_smooth_64v_10bpp_neon : 14516.5 13748.1These are generally about as fast as the corresponding ARM
routines on the same CPU (at least on the A53), in most cases
marginally faster.The speedup vs C code is around 4-9x.
Signed-off-by : Martin Storsjö <martin@martin.st>
- [DH] libavcodec/aarch64/Makefile
- [DH] libavcodec/aarch64/vp9dsp_init.h
- [DH] libavcodec/aarch64/vp9dsp_init_10bpp_aarch64.c
- [DH] libavcodec/aarch64/vp9dsp_init_12bpp_aarch64.c
- [DH] libavcodec/aarch64/vp9dsp_init_16bpp_aarch64_template.c
- [DH] libavcodec/aarch64/vp9dsp_init_aarch64.c
- [DH] libavcodec/aarch64/vp9mc_16bpp_neon.S
-
lavu/pixfmt : Add P012, Y212, XV30, and XV36 formats
13 août 2022, par Philip Langdalelavu/pixfmt : Add P012, Y212, XV30, and XV36 formats
These are the formats we want/need to use when dealing with the Intel
VAAPI decoder for 12bit 4:2:0, 12bit 4:2:2, 10bit 4:4:4 and 12bit 4:4:4
respectively.As with the already supported Y210 and YUVX (XVUY) formats, they are
based on formats Microsoft picked as their preferred 4:2:2 and 4:4:4
video formats, and Intel ran with it.P12 and Y212 are simply an extension of 10 bit formats to say 12 bits
will be used, with 4 unused bits instead of 6.XV30, and XV36, as exotic as they sound, are variants of Y410 and Y412
where the alpha channel is left formally undefined. We prefer these
over the alpha versions because the hardware cannot actually do
anything with the alpha channel and respecting it is just overhead.Y412/XV46 is a normal looking packed 4 channel format where each
channel is 16bits wide but only the 12msb are used (like P012).Y410/XV30 packs three 10bit channels in 32bits with 2bits of alpha,
like A/X2RGB10 style formats. This annoying layout forced me to define
the BE version as a bitstream format. It seems like our pixdesc
infrastructure can handle the LE version being byte-defined, but not
when it's reversed. If there's a better way to handle this, please
let me know. Our existing X2 formats all have the 2 bits at the MSB
end, but this format places them at the LSB end and that seems to be
the root of the problem.