
Recherche avancée
Autres articles (95)
-
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 (...) -
Gestion générale des documents
13 mai 2011, parMédiaSPIP ne modifie jamais le document original mis en ligne.
Pour chaque document mis en ligne il effectue deux opérations successives : la création d’une version supplémentaire qui peut être facilement consultée en ligne tout en laissant l’original téléchargeable dans le cas où le document original ne peut être lu dans un navigateur Internet ; la récupération des métadonnées du document original pour illustrer textuellement le fichier ;
Les tableaux ci-dessous expliquent ce que peut faire MédiaSPIP (...) -
Multilang : améliorer l’interface pour les blocs multilingues
18 février 2011, parMultilang est un plugin supplémentaire qui n’est pas activé par défaut lors de l’initialisation de MediaSPIP.
Après son activation, une préconfiguration est mise en place automatiquement par MediaSPIP init permettant à la nouvelle fonctionnalité d’être automatiquement opérationnelle. Il n’est donc pas obligatoire de passer par une étape de configuration pour cela.
Sur d’autres sites (8658)
-
Invalid pixel aspect ratio in ffmpeg
26 septembre 2014, par dudeofeaI want to scale a video to a certain size using ffmpeg, but I get the following error :
ffmpeg -i Ad_939.avi -vf scale=1000:64 test_ad.avi
ffmpeg version 2.3.3 Copyright (c) 2000-2014 the FFmpeg developers
built on Sep 26 2014 10:31:06 with gcc 4.8 (Ubuntu 4.8.2-19ubuntu1)
configuration:
libavutil 52. 92.100 / 52. 92.100
libavcodec 55. 69.100 / 55. 69.100
libavformat 55. 48.100 / 55. 48.100
libavdevice 55. 13.102 / 55. 13.102
libavfilter 4. 11.100 / 4. 11.100
libswscale 2. 6.100 / 2. 6.100
libswresample 0. 19.100 / 0. 19.100
Input #0, avi, from 'Ad_939.avi':
Metadata:
encoder : Lavf56.4.101
Duration: 00:00:20.50, start: 0.000000, bitrate: 75 kb/s
Stream #0:0: Video: wmv2 (WMV2 / 0x32564D57), yuv420p, 160x64, 68 kb/s, SAR 32:45 DAR 16:9, 24 fps, 24 tbr, 24 tbn, 24 tbc
[mpeg4 @ 0x2305cc0] Invalid pixel aspect ratio 128/1125, limit is 255/255 reducing
[mpeg4 @ 0x2305cc0] too many threads/slices (5), reducing to 4
Output #0, avi, to 'test_ad.avi':
Metadata:
ISFT : Lavf55.48.100
Stream #0:0: Video: mpeg4 (FMP4 / 0x34504D46), yuv420p, 1000x64 [SAR 19:167 DAR 2375:1336], q=2-31, 200 kb/s, SAR 128:1125 DAR 16:9, 24 fps, 24 tbn, 24 tbc
Metadata:
encoder : Lavc55.69.100 mpeg4
Stream mapping:
Stream #0:0 -> #0:0 (wmv2 (native) -> mpeg4 (native))
Press [q] to stop, [?] for help
frame= 228 fps=0.0 q=2.0 size= 222kB time=00:00:09.50 bitrate= 191.6kbits/s
frame= 468 fps=467 q=2.0 size= 435kB time=00:00:19.50 bitrate= 182.8kbits/s
frame= 492 fps=456 q=2.0 Lsize= 458kB time=00:00:20.50 bitrate= 183.1kbits/s
video:441kB audio:0kB subtitle:0kB other streams:0kB global headers:0kB muxing overhead: 3.981523%I’ve read around and it seems this was a past bug but that was 3 years ago. I’ve tried running this command with version 2.4.1, 2.3.3, 2.4.git (compiled from source Sept 16, 2014), and N-40951-g1ea7a3e (Newest static build) and they all fail.
EDIT : When I say
fail
I mean that the video is not playing at the proper resolution. The file’s properties say that it is 1000x64 but VLC plays (as well as my website using a<video></video>
tag) it with the original aspect ratio with the new width which is not what I want. I want a crunched up video the same size no matter what.Is there something I’m missing ?
-
Prevent google cloud function timeout for video processing ?
11 janvier 2018, par Muhammad UmerFirstly I’m not sure if my approach is right one.
This is what I’m doing. I’ve some video processing work to do, for which I’m gonna use FFMPEG. And it can take from 1 minute to 20 minutes to do work.
so my questions are :
- are CFs good fit for this. I don’t want my main server to do these
tasks. - can i make CF to only time out after say 60 minutes, or before if finished.
- Is it going to be cheaper than just using server instead.
From what I know it’s perfect scenario to use cloud functions. Alternative is to use build queue, wait for available processes to finish and then when time comes finish task.
- are CFs good fit for this. I don’t want my main server to do these
-
lavfi/minterpolate : Split struct Pixel to allow higher resolutions.
3 décembre 2017, par Carl Eugen Hoyos