
Recherche avancée
Autres articles (99)
-
Personnaliser en ajoutant son logo, sa bannière ou son image de fond
5 septembre 2013, parCertains thèmes prennent en compte trois éléments de personnalisation : l’ajout d’un logo ; l’ajout d’une bannière l’ajout d’une image de fond ;
-
Ecrire une actualité
21 juin 2013, parPrésentez les changements dans votre MédiaSPIP ou les actualités de vos projets sur votre MédiaSPIP grâce à la rubrique actualités.
Dans le thème par défaut spipeo de MédiaSPIP, les actualités sont affichées en bas de la page principale sous les éditoriaux.
Vous pouvez personnaliser le formulaire de création d’une actualité.
Formulaire de création d’une actualité Dans le cas d’un document de type actualité, les champs proposés par défaut sont : Date de publication ( personnaliser la date de publication ) (...) -
Publier sur MédiaSpip
13 juin 2013Puis-je poster des contenus à partir d’une tablette Ipad ?
Oui, si votre Médiaspip installé est à la version 0.2 ou supérieure. Contacter au besoin l’administrateur de votre MédiaSpip pour le savoir
Sur d’autres sites (9775)
-
Revision aa5b67add0 : Changes to adaptive inter rd thresholds. Values now carried over frame to frame
23 août 2013, par Paul WilkinsChanged Paths :
Modify /vp9/encoder/vp9_onyx_if.c
Modify /vp9/encoder/vp9_onyx_int.h
Modify /vp9/encoder/vp9_rdopt.c
Changes to adaptive inter rd thresholds.Values now carried over frame to frame.
Change to algorithm for decreasing threshold after
a hit and to max threshold (now based on speed)Removed some old commented out code relating to
VP8 adaptive thresholds.The impact of these changes tested on Akiyo (50 frames)
and measured in terms of unit rd hits is as follows :Speed 0 84.36 -> 84.67
Speed 1 29.48 -> 22.22
Speed 2 11.76 -> 8.21
Speed 3 12.32 -> 7.21Encode speed impact is broadly in line with these.
Change-Id : I5b886efee3077a11553fa950d796fd6d00c8cb19
-
Revision 4a101310e8 : Adapt mode based rd_threshold for similar block size The rd_thresholds are adap
23 septembre 2014, par Yaowu XuChanged Paths :
Modify /vp9/encoder/vp9_rdopt.c
Modify /vp9/encoder/vp9_speed_features.c
Adapt mode based rd_threshold for similar block sizeThe rd_thresholds are adaptively changed based on best mode tested.
It was only changed for the same block size, this commit makes the
adaptation for similar block sizes too. The commit also made minor
adjustment and code cleanups.The impact on encoding time for _ped :
118089 ms -> 111927 msThe impact on compression :
derf : -0.339%
stdhd : -0.303%Change-Id : I8817fed1102350497f2ec631849e43f753878e5d
-
FFMPEG reports different (wrong) video resolution compared to how it actually plays
30 mars 2015, par EmilianoQuick question, i have a movie, which was cut and rendered with Sony Vegas from its original format to a .wmv file. Here comes the tricky part, movie when played, either with
VLC
orWMP
, has a resolution of 656x480 ... BUT when i run a ffmpeg -i on it, it says it has a resolution of600x480
....I took the time of actually capturing a frame and croping it with photoshop and its
656
and not600
like ffmpeg its reporting, why would this could be happening ? How could i fix the headers resolution ? Would that have any impact on video re-rendering ? As i said, VLC and WMP seems not to care about the incorrect headers and are playing it right, BUT, jwplayer seems to be using the header information, which i don’t blame him, its correct to do that, but why the video headers could be wrong ?ffmpeg -i trailer.wmv
Input #0, asf, from ’trailer.wmv’ : Duration : 00:01:04.93, start : 3.000000, bitrate : 2144 kb/s Stream #0.0 : Audio : wmav2, 44100 Hz, mono, 32 kb/s Stream #0.1 : Video : wmv3, yuv420p, 600x480 [PAR 59:54 DAR 295:216], 2065 kb/ s, 25.00 tb(r)
And yeah, the
PAR/DAR
parameters are also wrong, but honestly, i don’t understand that technical shit, usually watch video and make sure it look good, any feedback would be appreciated :PIs there a way to change the container information with ffmpeg so applications that actually do use the container information don’t render video incorrectly ?