
Recherche avancée
Autres articles (84)
-
Mise à jour de la version 0.1 vers 0.2
24 juin 2013, parExplications des différents changements notables lors du passage de la version 0.1 de MediaSPIP à la version 0.3. Quelles sont les nouveautés
Au niveau des dépendances logicielles Utilisation des dernières versions de FFMpeg (>= v1.2.1) ; Installation des dépendances pour Smush ; Installation de MediaInfo et FFprobe pour la récupération des métadonnées ; On n’utilise plus ffmpeg2theora ; On n’installe plus flvtool2 au profit de flvtool++ ; On n’installe plus ffmpeg-php qui n’est plus maintenu au (...) -
Personnaliser en ajoutant son logo, sa bannière ou son image de fond
5 septembre 2013, parCertains thèmes prennent en compte trois éléments de personnalisation : l’ajout d’un logo ; l’ajout d’une bannière l’ajout d’une image de fond ;
-
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 (12424)
-
How to fix scrambled output
26 janvier 2020, par KrishnakumarI am seeing the following scrambled output for a live stream when processing an udp input stream. I am using the recently downloaded ffmpeg from GIT. Stop and Start of ffmpeg command resolves the issues temporarily.
Sample Logs :
Sun Jan 26 03:52:00 2020 ffmpeg version N-94528-gfaa9cd3 Copyright (c) 2000-2019 the FFmpeg developers
Sun Jan 26 03:52:00 2020 built with gcc 4.8.5 (GCC) 20150623 (Red Hat 4.8.5-36)
Sun Jan 26 03:52:00 2020 configuration: --prefix=/root/ffmpeg_build --pkg-config-flags=--static --extra-cflags=-I/root/ffmpeg_build/include --extra-ldflags=-L/root/ffmpeg_build/lib --extra-libs=-lpthread --extra-libs=-lm --bindir=/root/bin --enable-gpl --enable-libfdk_aac --enable-libfreetype --enable-libmp3lame --enable-libopus --enable-libvpx --enable-libx264 --enable-libx265 --enable-nonfree --enable-openssl
Sun Jan 26 03:52:00 2020 libavutil 56. 33.100 / 56. 33.100
Sun Jan 26 03:52:00 2020 libavcodec 58. 55.100 / 58. 55.100
Sun Jan 26 03:52:00 2020 libavformat 58. 30.100 / 58. 30.100
Sun Jan 26 03:52:00 2020 libavdevice 58. 9.100 / 58. 9.100
Sun Jan 26 03:52:00 2020 libavfilter 7. 58.100 / 7. 58.100
Sun Jan 26 03:52:00 2020 libswscale 5. 6.100 / 5. 6.100
Sun Jan 26 03:52:00 2020 libswresample 3. 6.100 / 3. 6.100
Sun Jan 26 03:52:00 2020 libpostproc 55. 6.100 / 55. 6.100
Sun Jan 26 04:02:46 2020 [h264 @ 0x4d988c0] illegal short term buffer state detected
Sun Jan 26 04:02:46 2020 [h264 @ 0x4e54f80] reference picture missing during reorder
Sun Jan 26 04:02:46 2020 Last message repeated 1 times
Sun Jan 26 04:02:46 2020 [h264 @ 0x4e54f80] Missing reference picture, default is 56257016
Sun Jan 26 04:02:46 2020 Last message repeated 1 times
Sun Jan 26 04:02:46 2020 [h264 @ 0x4cc2e00] mmco: unref short failure
Sun Jan 26 04:02:46 2020 [h264 @ 0x594f4c0] illegal short term buffer state detected
Sun Jan 26 04:02:46 2020 [h264 @ 0x4f66800] reference picture missing during reorder
Sun Jan 26 04:02:46 2020 [h264 @ 0x4f66800] Missing reference picture, default is 56257692
Sun Jan 26 04:02:46 2020 [h264 @ 0x4c75a00] mmco: unref short failure
Sun Jan 26 04:02:46 2020 [h264 @ 0x4d988c0] illegal short term buffer state detected
Sun Jan 26 04:02:47 2020 [h264 @ 0x4e54f80] reference picture missing during reorder
Sun Jan 26 04:02:47 2020 Last message repeated 1 times
Sun Jan 26 04:02:47 2020 [h264 @ 0x4e54f80] Missing reference picture, default is 56257032
Sun Jan 26 04:02:47 2020 Last message repeated 1 times
Sun Jan 26 04:02:47 2020 [h264 @ 0x4cc16c0] reference picture missing during reorder
Sun Jan 26 04:02:47 2020 [h264 @ 0x4cc16c0] Missing reference picture, default is 56257700
Sun Jan 26 04:02:47 2020 [h264 @ 0x4cc2e00] mmco: unref short failure
Sun Jan 26 04:02:47 2020 [h264 @ 0x594f4c0] illegal short term buffer state detected
Sun Jan 26 04:02:47 2020 udp://230.1.1.2:12000?fifo_size=5000000&overrun_nonfatal=1: corrupt decoded frame in stream 3
Sun Jan 26 04:02:47 2020 [h264 @ 0x4f66800] reference picture missing during reorder
Sun Jan 26 04:02:47 2020 [h264 @ 0x4f66800] Missing reference picture, default is 56257708
Sun Jan 26 04:02:47 2020 [h264 @ 0x4c75a00] mmco: unref short failure
Sun Jan 26 04:02:47 2020 [h264 @ 0x4d988c0] illegal short term buffer state detected
Sun Jan 26 04:02:47 2020 [h264 @ 0x4e54f80] reference picture missing during reorder
Sun Jan 26 04:02:47 2020 Last message repeated 1 times
Sun Jan 26 04:02:47 2020 [h264 @ 0x4e54f80] Missing reference picture, default is 56257048
Sun Jan 26 04:02:47 2020 Last message repeated 1 times
Sun Jan 26 04:02:47 2020 [h264 @ 0x4cc16c0] reference picture missing during reorder
Sun Jan 26 04:02:47 2020 [h264 @ 0x4cc16c0] Missing reference picture, default is 56257716
Sun Jan 26 04:02:47 2020 [h264 @ 0x4cc2e00] mmco: unref short failure
Sun Jan 26 04:02:47 2020 [h264 @ 0x594f4c0] illegal short term buffer state detected -
FFMPEG command runs forever even on using timelimit
21 décembre 2017, par t6nandMostly I use a java code to run FFMPEG bash commands for watermarking a logo on video. I am using the following FFmpeg command to overlay an image on video. I have observed that at times for some random videos, the process keeps on running even after the timelimit assigned to it expires. At times it’s more than a day or couple of days until not directly killed using
kill -9 pid
:ffmpeg -timelimit 900 -y -i
input_video
-i logoImage -filter_complex "[0:v]scale=trunc(iw/2)*2:trunc(ih/2)*2[even] ;[1:v][even]scale2ref=iw*0.25 :(iw*0.25)*(0.46446702)[2nd][ref] ;[ref][2nd]overlay=(main_w-overlay_w) :(main_h-overlay_h)"
-c:v libx264 -b:v 300K -crf 28 -preset slow outputVideoBut this command never completes even on using
-timelimit
flag at times for some videos.I have observed that for such processes output from
ps aux|grep ffmpeg
yeilds in something like :ubuntu 16620 0.6 6.7 1595044 515392 ? Sl Dec20 12:05
ffmpeg -timelimit 900 -y -i
input_video
-i logoImage -filter_complex "[0:v]scale=trunc(iw/2)*2:trunc(ih/2)*2[even] ;[1:v][even]scale2ref=iw*0.25 :(iw*0.25)*(0.46446702)[2nd][ref] ;[ref][2nd]overlay=(main_w-overlay_w) :(main_h-overlay_h)"
-c:v libx264 -b:v 300K -crf 28 -preset slow outputVideoIt indicates that this process is in interruptible sleep state i.e. waiting for an event to complete. On using
sudo strace -p 16620
to trace which system call is this process hung up on it results in something like :Process 16620 attached write(2, "frame= 4121 fps= 10 q=33.0 size="...,
99i.e. it’s stuck writing to a file.
What could be the reason for this problem ?
And is there any other way to kill FFMPEG process which overshoots desired time limit ? -
How do I connect two GIFs to play one after another in Python ?
9 novembre 2022, par AndrewIf I have two GIFs, GIF 1 being 10 seconds long and GIF 2 being 5 seconds long, is there a way to connect them so the final GIF is a total of 15 seconds long ?


Would I have to loop through each frame of both the GIFs with
imageio.mimread()
and output, once all the frames are read in memory ?

Or is there another way by knowing the start and end times and shifting it ?


Edit :
The solution presented by FirefoxMetzger is extremely Pythonic, ideal if you do not wish to install other software / packages like gifsicle.


import imageio.v3 as iio
import numpy as np

frames = np.vstack([
 iio.imread("imageio1.gif"),
 iio.imread("imageio2.gif"),
])

# get duration each frame is displayed
iio.imwrite("imageio_combined.gif", frames)



This completes in 15.6 seconds for two GIFs, each containing 100 frames.


However, if runtime is important, I recommend gifsicle :


gifsicle(
 sources=["imageio1.gif", "imageio2.gif"], # or just omit it and will use the first source provided.
 destination="imageio3.gif",
 options=["--optimize=2", "--threads=2", "--no-conserve-memory"]
)



This completes in 4.8 seconds, which is three times as fast.