
Recherche avancée
Médias (91)
-
MediaSPIP Simple : futur thème graphique par défaut ?
26 septembre 2013, par
Mis à jour : Octobre 2013
Langue : français
Type : Video
-
avec chosen
13 septembre 2013, par
Mis à jour : Septembre 2013
Langue : français
Type : Image
-
sans chosen
13 septembre 2013, par
Mis à jour : Septembre 2013
Langue : français
Type : Image
-
config chosen
13 septembre 2013, par
Mis à jour : Septembre 2013
Langue : français
Type : Image
-
SPIP - plugins - embed code - Exemple
2 septembre 2013, par
Mis à jour : Septembre 2013
Langue : français
Type : Image
-
GetID3 - Bloc informations de fichiers
9 avril 2013, par
Mis à jour : Mai 2013
Langue : français
Type : Image
Autres articles (72)
-
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 (...) -
Gestion de la ferme
2 mars 2010, parLa ferme est gérée dans son ensemble par des "super admins".
Certains réglages peuvent être fais afin de réguler les besoins des différents canaux.
Dans un premier temps il utilise le plugin "Gestion de mutualisation" -
La gestion des forums
3 novembre 2011, parSi les forums sont activés sur le site, les administrateurs ont la possibilité de les gérer depuis l’interface d’administration ou depuis l’article même dans le bloc de modification de l’article qui se trouve dans la navigation de la page.
Accès à l’interface de modération des messages
Lorsqu’il est identifié sur le site, l’administrateur peut procéder de deux manières pour gérer les forums.
S’il souhaite modifier (modérer, déclarer comme SPAM un message) les forums d’un article particulier, il a à sa (...)
Sur d’autres sites (6103)
-
Tools for investigating video corruption — ffmpeg / libavcodec
11 juillet 2013, par GopherkhanIn my current work I'm trying to encode some images to h264 video using the FFMPEG's C library. The resulting video plays fine in VLC, but has no preview image. The video can play in VLC and Mplayer on ubuntu, but won't play on Mac or PC (in fact, it causes a "VTDecoderXPCService quit unexpectedly" error on Mac).
If I run the resulting file through FFMPEG using the command line, the resulting file has a preview image, and plays correctly everywhere.
Apparently the file that I get out of the program is corrupt in some weird place, but I don't have any output during my compilation or run to indicate where. I can't share my code at the moment (work code isn't open source yet :-( ), but I have tried a number of things :
- Writing only header and trailer data (av_write_trailer) and no frames
- writing frames only minus the trailer (using avcodec_encode_video2 and av_write_frame)
- Adjusting our time_base and frame pts values to encode only one frame per second
- Removing all variable frame rate code
- Numerous other variants that I won't bother you with here
In creating my project, I've also followed the following tutorials :
And consulted the deprecated ffmpeg functions list
And compiled FFMPEG on ubuntu according to the official doc
But every run of the program runs into the exact same problem.
My question is, is there anything obvious that causes a programmatic run of FFMpeg to differ from a console run (e.g., an incomplete finalization, some threading issues, etc.) ? Like some obvious reason that a console run could repair a corrupted file ? Or is there a decent tool/method for inspecting a video file and finding the point of corruption ?
-
Why does the video lose few seconds after FFMPEG xfade ?
25 août 2023, par promaxdevI am having a use case where I need to add a few xfade transitions to an existing video at uniform intervals. I followed an approach almost similar to the one explained in the official document here and the SO reply here


Here is the command that I use.


ffmpeg 
-i clean_0.mp4 
-filter_complex "[0] split = 8[i1][i2][i3][i4][i5][i6][i7][i8]; 
 [i1]select='between(t\,0.0\,3.75)',setpts='PTS-STARTPTS'[i11]; 
 [i2]select='between(t\,3.75\,7.5)',setpts='PTS-STARTPTS'[i22]; 
 [i3]select='between(t\,7.5\,11.25)',setpts='PTS-STARTPTS'[i33]; 
 [i4]select='between(t\,11.25\,15.0)',setpts='PTS-STARTPTS'[i44]; 
 [i5]select='between(t\,15.0\,18.75)',setpts='PTS-STARTPTS'[i55]; 
 [i6]select='between(t\,18.75\,22.5)',setpts='PTS-STARTPTS'[i66]; 
 [i7]select='between(t\,22.5\,26.25)',setpts='PTS-STARTPTS'[i77]; 
 [i8]select='between(t\,26.25\,30.0)',setpts='PTS-STARTPTS'[i88]; 
 [i11][i22]xfade=duration=1:offset=2.75:transition=dissolve [c1]; 
 [i33][i44]xfade=duration=1:offset=2.75:transition=distance [c2]; 
 [i55][i66]xfade=duration=1:offset=2.75:transition=fadegrays [c3]; 
 [i77][i88]xfade=duration=1:offset=2.75:transition=pixelize [c4]; 
 [c1][c2][c3][c4]concat=n=4:v=1:a=0 " 
-pix_fmt yuv420p -y clean_out.mp4 



(The above code is executed in a single line broken down for ease of understanding.)


What this does is splits the input video in to parts of equal length in duration and and inserts xfade effects in between and the concats them. So the net effect would be the original video with xfade effects added.


The input video is 30 seconds in length and has 25 fps. But the output video is 26 seconds.


Here are my analysis so far.


- 

- the no. of seconds reduced with each added transition. i.e. when 5 transitions are provided, the output video reduces to 25 seconds
- ffprobe at different stages below

- 

- i1, i2,... being copies of input video had 750 frames @ 25fps ie 30 seconds
- i11, i22,... -> had 94 frames @ 25fps resulting in 3.76 seconds (3.76 X 8 = 30.08s)
- c1, c2,.. -> had 163 frames @ 25fps resulting in 6.52 seconds (6.52 X 4 = 26.08s)








- Enabling trace on ffmpeg showed different filters like 'Parsed_select_', 'Parsed_setpts_' and 'Parsed_xfade_', 'Parsed_concat_' corresponding to the 'select', 'setpts', 'xfade' and concat filters and there was another 'auto_scale_' auto inserted by ffmpeg. But details were found only for Parsed_select_ and Parsed_setpts_* filters in rest of the logs. There was no other trace of Parsed_xfade_* filters. So not much info from there








End result is concat of all c* videos resulting in reduced duration


So we can infer that xfade is causing some frames to be lost. (or I am doing it wrong) I need help to find the reason for the reduction in the duration of the final video and fix it.Also, Is there a way to log Xfade trace ?


-
C program cannot find function which included in header file
17 juin 2013, par Juneyoung OhI made program like this.
1 #include
2 #include
3 #include
4 #include "libavformat/avformat.h"
5
6 int main (int argc, char* argv[]){
7 av_register_all();
8 return 0;
9 }My header file located in
root@ubuntu:/home/juneyoungoh/getDuration# find / -name "avformat.h"
/root/ffmpeg/libavformat/avformat.h
/usr/local/include/libavformat/avformat.hthen I run with
gcc getDuration.c
, but I show message like below.root@ubuntu:/home/juneyoungoh/getDuration# gcc getDuration.c
/tmp/ccwjonqH.o: In function `main':
getDuration.c:(.text+0x10): undefined reference to `av_register_all'
collect2: ld returned 1 exit statusFrankly, I do not have any idea what makes this.
Thanks for your answers.
========================== edited #1 ===========================
when I "ls /usr/local/lib", I get this.
root@ubuntu:/home/juneyoungoh/getDuration# ls /usr/local/lib/
libavcodec.a libavutil.a libopus.la libvpx.a python2.7
libavdevice.a libfdk-aac.a libpostproc.a libx264.a
libavfilter.a libfdk-aac.la libswresample.a libyasm.a
libavformat.a libopus.a libswscale.a pkgconfigyou can see libavformat.a in the very first of the last line.
so if I command like what you suggest, I get below.
/root/ffmpeg/libavformat/vqf.c:244: undefined reference to `av_free_packet'
/usr/local/lib//libavformat.a(vqf.o): In function `add_metadata':
/root/ffmpeg/libavformat/vqf.c:58: undefined reference to `av_malloc'
/root/ffmpeg/libavformat/vqf.c:64: undefined reference to `av_dict_set'
/usr/local/lib//libavformat.a(vqf.o): In function `vqf_read_header':
/root/ffmpeg/libavformat/vqf.c:148: undefined reference to `av_dict_set'
/root/ffmpeg/libavformat/vqf.c:208: undefined reference to `av_log'
/root/ffmpeg/libavformat/vqf.c:216: undefined reference to `av_malloc'
/root/ffmpeg/libavformat/vqf.c:170: undefined reference to `av_log'
/root/ffmpeg/libavformat/vqf.c:121: undefined reference to `av_log'
/root/ffmpeg/libavformat/vqf.c:184: undefined reference to `av_log'
/root/ffmpeg/libavformat/vqf.c:136: undefined reference to `av_log'
/usr/local/lib//libavformat.a(wavenc.o): In function `wav_write_trailer':
/root/ffmpeg/libavformat/wavenc.c:210: undefined reference to `av_rescale'
/usr/local/lib//libavformat.a(wavenc.o): In function `wav_write_packet':
/root/ffmpeg/libavformat/wavenc.c:181: undefined reference to `av_log'It is too long, so I just post little part of that.
I think all link of libavformat has been broken, But I do not know
what can I do to fix that link.
I have installed that their official link said.
https://ffmpeg.org/trac/ffmpeg/wiki/UbuntuCompilationGuideQuantal