
Recherche avancée
Autres articles (53)
-
La file d’attente de SPIPmotion
28 novembre 2010, parUne file d’attente stockée dans la base de donnée
Lors de son installation, SPIPmotion crée une nouvelle table dans la base de donnée intitulée spip_spipmotion_attentes.
Cette nouvelle table est constituée des champs suivants : id_spipmotion_attente, l’identifiant numérique unique de la tâche à traiter ; id_document, l’identifiant numérique du document original à encoder ; id_objet l’identifiant unique de l’objet auquel le document encodé devra être attaché automatiquement ; objet, le type d’objet auquel (...) -
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 (...) -
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 (12409)
-
tests : Renamed pix_fmts wording in ffv1 test target name to match pix_fmt parameter.
31 août 2015, par Peter Btests : Renamed pix_fmts wording in ffv1 test target name to match pix_fmt parameter.
Signed-off-by : Michael Niedermayer <michael@niedermayer.cc>
- [DH] tests/fate/vcodec.mak
- [DH] tests/ref/vsynth/vsynth1-ffv1-v0
- [DH] tests/ref/vsynth/vsynth1-ffv1-v3-bgr0
- [DH] tests/ref/vsynth/vsynth1-ffv1-v3-yuv420p
- [DH] tests/ref/vsynth/vsynth1-ffv1-v3-yuv422p10
- [DH] tests/ref/vsynth/vsynth1-ffv1-v3-yuv444p16
- [DH] tests/ref/vsynth/vsynth1-ffv1.0
- [DH] tests/ref/vsynth/vsynth1-ffv1.3-420
- [DH] tests/ref/vsynth/vsynth1-ffv1.3-422p10
- [DH] tests/ref/vsynth/vsynth1-ffv1.3-444p16
- [DH] tests/ref/vsynth/vsynth1-ffv1.3-bgr
- [DH] tests/ref/vsynth/vsynth2-ffv1-v0
- [DH] tests/ref/vsynth/vsynth2-ffv1-v3-bgr0
- [DH] tests/ref/vsynth/vsynth2-ffv1-v3-yuv420p
- [DH] tests/ref/vsynth/vsynth2-ffv1-v3-yuv422p10
- [DH] tests/ref/vsynth/vsynth2-ffv1-v3-yuv444p16
- [DH] tests/ref/vsynth/vsynth2-ffv1.0
- [DH] tests/ref/vsynth/vsynth2-ffv1.3-420
- [DH] tests/ref/vsynth/vsynth2-ffv1.3-422p10
- [DH] tests/ref/vsynth/vsynth2-ffv1.3-444p16
- [DH] tests/ref/vsynth/vsynth2-ffv1.3-bgr
- [DH] tests/ref/vsynth/vsynth3-ffv1-v0
- [DH] tests/ref/vsynth/vsynth3-ffv1-v3-bgr0
- [DH] tests/ref/vsynth/vsynth3-ffv1-v3-yuv420p
- [DH] tests/ref/vsynth/vsynth3-ffv1-v3-yuv422p10
- [DH] tests/ref/vsynth/vsynth3-ffv1-v3-yuv444p16
- [DH] tests/ref/vsynth/vsynth3-ffv1.0
- [DH] tests/ref/vsynth/vsynth3-ffv1.3-420
- [DH] tests/ref/vsynth/vsynth3-ffv1.3-422p10
- [DH] tests/ref/vsynth/vsynth3-ffv1.3-444p16
- [DH] tests/ref/vsynth/vsynth3-ffv1.3-bgr
- [DH] tests/ref/vsynth/vsynth_lena-ffv1-v0
- [DH] tests/ref/vsynth/vsynth_lena-ffv1-v3-bgr0
- [DH] tests/ref/vsynth/vsynth_lena-ffv1-v3-yuv420
- [DH] tests/ref/vsynth/vsynth_lena-ffv1-v3-yuv420p
- [DH] tests/ref/vsynth/vsynth_lena-ffv1-v3-yuv422p10
- [DH] tests/ref/vsynth/vsynth_lena-ffv1-v3-yuv444p16
-
Input link in1:v0 parameters (size XXX, SAR XXX) do not match the corresponding output link in0:v0 parameters (XXX, SAR 1:1) [duplicate]
1er mars 2020, par theapache64I’ve two files, a
mp4
and amp3
file. I want to add a3
seconds intro screen with titleWelcome
andblack
background to the head of the video with themp3
as background. So here’s what I wrote.ffmpeg \
-i input.mp4 \
-i bgm.mp3 \
-f lavfi -i color=c=black:s="1280"x"544":d=3.0 \
-filter_complex \
"[2:v]
drawtext=
fontsize=30
:fontcolor=white
:x=(w-text_w)/2
:y=(h-text_h)/2
:text='WELCOME',
geq=0:128:128
[introVideo];
[1:a]
atrim=0.0:3.0
[introAudio];
[introVideo][introAudio][0:v][0:a]concat=n=2:v=1:a=1" -preset superfast output.mp4but am getting below error when I try to execute the command
[Parsed_concat_3 @ 0x55c02756fa00] Input link in1:v0 parameters (size 1280x544, SAR 1299:1280) do not match the corresponding output link in0:v0 parameters (1280x544, SAR 1:1)
[Parsed_concat_3 @ 0x55c02756fa00] Failed to configure output pad on Parsed_concat_3
Error reinitializing filters!
Failed to inject frame into filter network: Invalid argument
Error while processing the decoded data for stream #0:1
Conversion failed!Any help will be highly appreciated.
PS : I am a beginner in video processing and
ffmpeg
. -
How to match precompiled static library's debugging symbols to source code with Xcode 5 ?
21 septembre 2013, par Chris BallingerI have to compile FFmpeg for iOS using an external build script, but when I am debugging I see assembler if I delve too deep into libavformat library functions :
0x109a73: cmpl $0, 1192(%ebp)
0x109a7a: jns 0x109a86 ; mov_write_header + 198 at movenc.c:3539
0x109a7c: movl $1, 1192(%ebp)
0x109a86: movl 16(%ebp), %eax
0x109a89: cmpl $0, 84(%eax)
0x109a8d: movl %edx, %ecx
0x109a8f: jne 0x109ad9 ; mov_write_header + 281 at movenc.c:3548
0x109a91: testb $2, 48(%ecx)
0x109a95: jne 0x109ac1 ; mov_write_header + 257 at movenc.c:3541There are clear debugging symbols left behind which would lead me to believe that there should be some way to tell Xcode the location of this source code to allow easier debugging.
Is this even possible ?
edit : I found a related question here No symbols/source for external library in Xcode 4
So when I run
xcrun dwarfdump libavformat.a | grep "\.c"
I get a bunch of results like this :AT_decl_file( "libavformat/movenc.c" )
So I tried putting the relevant source files in folders relative to both the .a file and my .xcodeproj file, but neither of those methods worked. Full source code is available here : https://github.com/openwatch/livestreamer-ios
edit2 : I found another question about how to set the source mapping for lldb but I'm not quite sure what to do... LLDB equivalent of gdb "directory" command for specifying source search path ?
It seems like I might need to do
(lldb) settings set target.source-map libavformat/movenc.c /path/to/libavformat/movenc.c
for every file I need ?