
Recherche avancée
Médias (1)
-
Rennes Emotion Map 2010-11
19 octobre 2011, par
Mis à jour : Juillet 2013
Langue : français
Type : Texte
Autres articles (92)
-
MediaSPIP version 0.1 Beta
16 avril 2011, parMediaSPIP 0.1 beta est la première version de MediaSPIP décrétée comme "utilisable".
Le fichier zip ici présent contient uniquement les sources de MediaSPIP en version standalone.
Pour avoir une installation fonctionnelle, il est nécessaire d’installer manuellement l’ensemble des dépendances logicielles sur le serveur.
Si vous souhaitez utiliser cette archive pour une installation en mode ferme, il vous faudra également procéder à d’autres modifications (...) -
MediaSPIP 0.1 Beta version
25 avril 2011, parMediaSPIP 0.1 beta is the first version of MediaSPIP proclaimed as "usable".
The zip file provided here only contains the sources of MediaSPIP in its standalone version.
To get a working installation, you must manually install all-software dependencies on the server.
If you want to use this archive for an installation in "farm mode", you will also need to proceed to other manual (...) -
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 (...)
Sur d’autres sites (10484)
-
ffmpeg_videotoolbox : skip memory copy if hwaccel_output_format match
27 avril 2021, par zhilizhaoffmpeg_videotoolbox : skip memory copy if hwaccel_output_format match
Simple test results :
Command :
./ffmpeg -y -hwaccel videotoolbox -hwaccel_output_format videotoolbox_vld \
-i test.mp4 -an -c:v h264_videotoolbox -benchmark out.mp4Before :
frame= 1221 fps= 66 q=-0.0 Lsize= 3144kB time=00:00:20.33 bitrate=1266.6kbits/s dup=4 drop=0 speed= 1.1x
bench : utime=2.714s stime=1.218s rtime=18.574sAfter :
frame= 1221 fps=137 q=-0.0 Lsize= 3144kB time=00:00:20.33 bitrate=1266.4kbits/s dup=4 drop=0 speed=2.28x
bench : utime=1.450s stime=1.440s rtime=8.924sIt has limited usecase since there is no video filter support, so
a log message is added to notify the user.Reviewed-by : Steven Liu <liuqi05@kuaishou.com>
-
iOS GPUImage : which AVAssetWriter settings to match 'Constrained Baseline' h.264
15 août 2014, par sunilrI have an iOS app which records video using GPUImage. These videos are stored remotely for viewing by other devices. I’d like the resulting video compression to match the settings which are commonly used in Instagram’s videos. I’ve inspected a number of instagram videos and running ffmpeg -i on them results in :
Stream #0:0(und) : Video : h264 (Constrained Baseline) (avc1 / 0x31637661), yuv420p, 640x640 [SAR 1:1 DAR 1:1], 1104 kb/s, 29.97 fps, 29.97 tbr, 11988 tbn, 59.94 tbc (default)
How should i match these ? The current settings i’m using are very close to the GPUImage defaults :
NSDictionary *videoCleanApertureSettings = [NSDictionary dictionaryWithObjectsAndKeys:
[NSNumber numberWithInt:videoSize.width], AVVideoCleanApertureWidthKey,
[NSNumber numberWithInt:videoSize.height], AVVideoCleanApertureHeightKey,
[NSNumber numberWithInt:0], AVVideoCleanApertureHorizontalOffsetKey,
[NSNumber numberWithInt:0], AVVideoCleanApertureVerticalOffsetKey,
nil];
NSDictionary *videoAspectRatioSettings = [NSDictionary dictionaryWithObjectsAndKeys:
[NSNumber numberWithInt:1], AVVideoPixelAspectRatioHorizontalSpacingKey,
[NSNumber numberWithInt:1], AVVideoPixelAspectRatioVerticalSpacingKey,
nil];
NSMutableDictionary * compressionProperties = [[NSMutableDictionary alloc] init];
[compressionProperties setObject:videoCleanApertureSettings forKey:AVVideoCleanApertureKey];
[compressionProperties setObject:videoAspectRatioSettings forKey:AVVideoPixelAspectRatioKey];
[compressionProperties setObject:[NSNumber numberWithInt: 1100000] forKey:AVVideoAverageBitRateKey];
[compressionProperties setObject:[NSNumber numberWithInt: 16] forKey:AVVideoMaxKeyFrameIntervalKey];
[compressionProperties setObject:AVVideoProfileLevelH264BaselineAutoLevel forKey:AVVideoProfileLevelKey];
NSMutableDictionary *settings = [[NSMutableDictionary alloc] init];
[settings setObject:AVVideoCodecH264 forKey:AVVideoCodecKey];
[settings setObject:[NSNumber numberWithInt:videoSize.width] forKey:AVVideoWidthKey];
[settings setObject:[NSNumber numberWithInt:videoSize.height] forKey:AVVideoHeightKey];
[settings setObject:compressionProperties forKey:AVVideoCompressionPropertiesKey];But when i run ffmpeg -i on the videos created, i get :
Stream #0:0(und) : Video : h264 (Baseline) (avc1 / 0x31637661), yuv420p, 480x480, 1128 kb/s, SAR 1:1 DAR 1:1, 23.86 fps, 24 tbr, 600 tbn, 1200 tbc (default)
I’m not sure what the difference is between ’Baseline’ and ’Constrained Baseline’ is, so it may be that the settings i have are adequate (for playback of the video from a remote URL on a mobile device).
Running an ffmpeg conversion on the file with : ffmpeg -i -profile:v baseline DOES recreate the instagram settings, but i’d like to have this happen on the device if possible.
-
ituh263dec : Have function signature match across declaration and definition
31 octobre 2016, par Diego Biurrun