
Recherche avancée
Autres articles (50)
-
Personnaliser les catégories
21 juin 2013, parFormulaire de création d’une catégorie
Pour ceux qui connaissent bien SPIP, une catégorie peut être assimilée à une rubrique.
Dans le cas d’un document de type catégorie, les champs proposés par défaut sont : Texte
On peut modifier ce formulaire dans la partie :
Administration > Configuration des masques de formulaire.
Dans le cas d’un document de type média, les champs non affichés par défaut sont : Descriptif rapide
Par ailleurs, c’est dans cette partie configuration qu’on peut indiquer le (...) -
Keeping control of your media in your hands
13 avril 2011, parThe vocabulary used on this site and around MediaSPIP in general, aims to avoid reference to Web 2.0 and the companies that profit from media-sharing.
While using MediaSPIP, you are invited to avoid using words like "Brand", "Cloud" and "Market".
MediaSPIP is designed to facilitate the sharing of creative media online, while allowing authors to retain complete control of their work.
MediaSPIP aims to be accessible to as many people as possible and development is based on expanding the (...) -
Prérequis à l’installation
31 janvier 2010, parPréambule
Cet article n’a pas pour but de détailler les installations de ces logiciels mais plutôt de donner des informations sur leur configuration spécifique.
Avant toute chose SPIPMotion tout comme MediaSPIP est fait pour tourner sur des distributions Linux de type Debian ou dérivées (Ubuntu...). Les documentations de ce site se réfèrent donc à ces distributions. Il est également possible de l’utiliser sur d’autres distributions Linux mais aucune garantie de bon fonctionnement n’est possible.
Il (...)
Sur d’autres sites (10675)
-
avformat/matroskaenc : Remove limit on the number of tracks
15 avril 2020, par Andreas Rheinhardtavformat/matroskaenc : Remove limit on the number of tracks
The Matroska file format has practically no limit on the number of
tracks (the current limit is 2^56 - 1) ; yet because they are encoded in
a variable length format in (Simple)Blocks this muxer has simply imposed
a limit on the number of tracks in order to ensure that they can always
be written on one byte in order to simplify the muxing process.This commit removes said limit.
Also, zero is an invalid TrackNumber, so disallow this value in the
dash_track_number option.Signed-off-by : Andreas Rheinhardt <andreas.rheinhardt@gmail.com>
-
avformat/matroskaenc : Ignore AttachedFiles for track limit
27 novembre 2019, par Andreas Rheinhardtavformat/matroskaenc : Ignore AttachedFiles for track limit
Attachments are streams in FFmpeg, but they are not tracks in Matroska.
Yet they were counted when checking a limit for the number of tracks that
the Matroska muxer imposes. This is unnecessary and has been changed.Also use unsigned variables for the variables denoting TrackNumbers as
negative TrackNumbers are impossible.(The Matroska file format actually has practically no limit on the
number of tracks and this is purely what our muxer supports. But even if
this limit were removed/relaxed in the future, it still makes sense to
use small TrackNumbers as this patch does, because greater numbers need
more bytes to encode.)Signed-off-by : Andreas Rheinhardt <andreas.rheinhardt@gmail.com>
-
Pipe input GIF to FFmpeg error, does it have size limit ?
3 février 2020, par SerKoI am trying to pipe input a GIF file to FFmpeg and get output from it. And I get an error when I input a GIF file size bigger than 1MB (maybe even smaller, didn’t try).
I am running on
Debian GNU/Linux 10 (buster)
and install FFmpeg byapt-get install ffmpeg
.What’s problem ?
After reading the FFmpeg pipe document and I have try execute command below :
cat big_size.gif | ffmpeg -i pipe:0 -f gif output.gif
And it shows error :
pipe:: Input/output error
What have I tried to fix ?
If I input the GIF file directly the FFmpeg instead of using pipe input, I can output the GIF successfully.
ffmpeg -i big_size.gif -f gif output.gif
I was think of system pipe size limit, but I can pipe the GIF by using
cat
tocat
and save successfully.
cat big_size.gif | cat > output.gif
So I don’t think the system pipe size limit cause the problem.
Sample GIF
Or you may try other GIF file size bigger then 1MB.