
Recherche avancée
Autres articles (102)
-
MediaSPIP 0.1 Beta version
25 avril 2011, parMediaSPIP 0.1 beta is the first version of MediaSPIP proclaimed as "usable".
The zip file provided here only contains the sources of MediaSPIP in its standalone version.
To get a working installation, you must manually install all-software dependencies on the server.
If you want to use this archive for an installation in "farm mode", you will also need to proceed to other manual (...) -
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 ;
Sur d’autres sites (11741)
-
FFMPEG segment records a minute worth of data but metadata shows 0.1s length video
1er février 2018, par Soft StrategyI’m recording a stream from a Live555 restream of a rtsp camera. I record in chunks of one minute videos. This is the setup :
RTSP Camera -> Live555 Server -> Recorder
Without the Live555 restreamer server I always record the rtsp camera stream with ffmpeg with no issues. This is the command :
ffmpeg -rtsp_transport tcp -y -i rtsp://IPcamera/url/to/video -c copy -f segment -segment_time 60 -reset_timestamps 1 -segment_atclocktime 1 -strftime 1 /video/%Y-%m-%d_%H-%M-%Stest.ts
I record in a ts container to mitigate framerate inaccuracies.
If I capture the proxy stream after few ours with no errors, something happens the stream starts to record files with the usual space on disk (around 5-10MB each) but when I check the metadata, the duration is 0.16 seconds. If you watch the video, it’s of course too fast but shows the clock hard coded in the image that runs through the whole minute, so the data is there.
The command I use with the restream, just an input change.
ffmpeg -rtsp_transport tcp -y -i rtsp://IPstreamServer/proxyStream-1 -c copy -f segment -segment_time 60 -reset_timestamps 1 -segment_atclocktime 1 -strftime 1 /video/%Y-%m-%d_%H-%M-%Stest.ts
It’s like ffmpeg is messing up the metadata. With the tcp setting there are no packets lost.
What could be the problem ?
Recording on Debian 8.8, ffmpeg version 3.2.5-1 bpo8+1.
EDIT : I’ve found that some guy had problem receiving metadata from the server, could it be the problem ? http://lists.live555.com/pipermail/live-devel/2013-May/017033.html
-
avformat/Makefile : use individual dependencies for librtmp protocols
12 février 2018, par James Almer -
FFMPEG zoompan only applies and shows 3 images out of the many
26 mai 2018, par Sanjyot ShahI am trying to generate a video from images using FFMPEG 4.0 windows built on AWS windows instance using PHP.
$command2="ffmpeg -r 1/5 -i https://<path>/$images%d.jpg -c:v libx264 -r 5 -t $total_video_time -y ".trim($video_name)." -i http://<path>/$audio ";
</path></path>The above generates the correct video output with all the input images (50 in this case) but without the zoompan effect on the images.
Now I try to add the zoompan effect for the images using -
$command2="ffmpeg -r 1/5 -i https://<path>/$images%d.jpg -filter_complex zoompan=z='zoom+0.002':d=25*4:s=1280x800 -pix_fmt yuv420p -c:v libx264 -r 5 -t $total_video_time -y ".trim($video_name)." -i http://<path>/$audio ";
</path></path>This will only pick up the first 3 images and apply the zoompan to the first two images or so.
Can you please help me with this issue ? Any inputs, pointers are welcome too.