
Recherche avancée
Autres articles (52)
-
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 (...) -
Des sites réalisés avec MediaSPIP
2 mai 2011, parCette page présente quelques-uns des sites fonctionnant sous MediaSPIP.
Vous pouvez bien entendu ajouter le votre grâce au formulaire en bas de page. -
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 (...)
Sur d’autres sites (4180)
-
avformat/matroskadec : Improve handling of circular SeekHeads
30 avril 2020, par Andreas Rheinhardtavformat/matroskadec : Improve handling of circular SeekHeads
There can be more than one SeekHead in a Matroska file, but most of the
other level 1 elements can only occur once.* Therefore the Matroska
demuxer only allows one entry per ID in its internal list of level 1
elements known to it ; the only exception to this are SeekHeads.The only exception to this are SeekHeads : When one is encountered
(either directly or in the list of entries read from SeekHeads),
a new entry in the list of known level-1 elements is always added,
even when this entry is actually already known.This leads to lots of seeks in case of circular SeekHeads : Each time a
SeekHead is parsed, a new entry for a SeekHead will be added to the list
of entries read from SeekHeads. The exception for SeekHeads mentioned
above now implies that this SeekHead will always appear new and unparsed
and parsing will be attempted. This continued until the list of known
level-1 elements is full.Fixing this is pretty simple : Don't add a new entry for a SeekHead if
its position matches the position of an already known SeekHead.* : Actually, there can be multiple Tags and several other level 1
elements are "identically recurring" which means they may be resent
multiple times, but each instance must be absolutely identical to the
previous.Signed-off-by : Andreas Rheinhardt <andreas.rheinhardt@gmail.com>
-
lavc/flacdsp : do not assume maximum R-V VL
24 mai 2024, par Rémi Denis-Courmontlavc/flacdsp : do not assume maximum R-V VL
This loop correctly assumes that VLMAX=16 (4x128-bit vectors
with 32-bit elements) and 32 >= pred_order > 16. We need to alternate
between VL=16 and VL=t2=pred_order-16 elements to add up to pred_order.The current code requests AVL=a2=pred_order elements. In QEMU and on
thte K230 hardware, this sets VL=16 as we need. But the specification
merely guarantees that we get : ceil(AVL / 2) <= VL <= VLMAX. For
instance, if pred_order equals 27, we could end up with VL=14 or VL=15
instead of VL=16. So instead, request literally VLMAX=16. -
how to implement siti filter using ffmpeg
18 septembre 2023, par hseI've asked this before, but I've tried and failed to implement siti filter with opencv, so I wanted to try implementing it with ffmpeg.


Here's the reference : https://ffmpeg.org/ffmpeg-filters.html#Examples-122


I followed that link and made sure the
calculateSITI
function was working.

export async function calculateSITI(filePath) {
 const filterGraph = `siti=print_summary=1`;

 const args = [filePath, "-v", filterGraph, "-f", "null", "- "];
 const t = await runFfmpeg(args);
 console.log(t);
}



filePath
: C :\xxxx\xxx\xxxx\ffmpeg-6.0-essentials_build\ffmpeg-6.0-essentials_build\bin

-v siti=level=1 -f null -
Invalidoglevel "siti=level=1". Possible levels are numbers or :
"quiet"
"panic"
"fatal"
"error"
"warning"
"info"
"verbose"
"debug"
"trace"


error, and I've been trying to troubleshoot it, but there seems to be very little documentation out there.
Anyone familiar with ffmpeg ?