
Recherche avancée
Autres articles (97)
-
Emballe médias : à quoi cela sert ?
4 février 2011, parCe plugin vise à gérer des sites de mise en ligne de documents de tous types.
Il crée des "médias", à savoir : un "média" est un article au sens SPIP créé automatiquement lors du téléversement d’un document qu’il soit audio, vidéo, image ou textuel ; un seul document ne peut être lié à un article dit "média" ; -
Librairies et logiciels spécifiques aux médias
10 décembre 2010, parPour un fonctionnement correct et optimal, plusieurs choses sont à prendre en considération.
Il est important, après avoir installé apache2, mysql et php5, d’installer d’autres logiciels nécessaires dont les installations sont décrites dans les liens afférants. Un ensemble de librairies multimedias (x264, libtheora, libvpx) utilisées pour l’encodage et le décodage des vidéos et sons afin de supporter le plus grand nombre de fichiers possibles. Cf. : ce tutoriel ; FFMpeg avec le maximum de décodeurs et (...) -
HTML5 audio and video support
13 avril 2011, parMediaSPIP uses HTML5 video and audio tags to play multimedia files, taking advantage of the latest W3C innovations supported by modern browsers.
The MediaSPIP player used has been created specifically for MediaSPIP and can be easily adapted to fit in with a specific theme.
For older browsers the Flowplayer flash fallback is used.
MediaSPIP allows for media playback on major mobile platforms with the above (...)
Sur d’autres sites (7736)
-
FFmpeg help, how should I use FFmpeg ? [closed]
11 septembre 2023, par Señor TontoI'm trying to use FFmpeg in my code, which is a C++ win32 application that I'm coding from Visual Studio Code 2022. I've downloaded FFmpeg from the BtnB Github that they link in their offical site as a pre-built binary. Now, I got the shared version, as I believed this would both have the command-line .exe app & the normal code headers & libraries. I tried using some code inside of my main.cpp to decode frames from .mp4 files as a test. For some reason though, on launch I got these errors : avcodec-60.dll cannot be found, avformat-60.dll cannot be found, avutil-58.dll cannot be found, swscale-7.dll cannot be found. So now I'm wondering why aren't these provided in the shared code ? there are only dll.a files but no actual .dll files, I also found .def files with the names of the .dll files I am apparently missing, now I want to know why these .dll files aren't provided. Do I need to build from source for that ? Or should I just forget using the .h & .lib files of FFmpeg & use the command-line app ? Any help appreciated.


I want to use FFmpeg, but I can't find any guidance as to whether to use the command-line tool or the code function that aren't working due to the absent .dll filess


-
FFMPEG : Reconnect not working for HTTP source with UDP output [closed]
5 octobre 2023, par QuinnellI am streaming an audio input with a static video slate. Audio comes from an HTTP source. I output to a multicast IP via UDP.


The stream periodically fails. The process needs to be killed and manually restarted. Would like to have the stream automatically reconnect itself upon failure.


Server runs CentOS 7.
FFMPEG version : ffmpeg version N-107408-g882aac99d2 Copyright (c) 2000-2022 the FFmpeg developers
built with gcc 4.8.5 (GCC) 20150623 (Red Hat 4.8.5-44)


The server will eventually be replaced with AlmaLinux 8.8 running the latest version of ffmpeg.


Currently experimenting with the RECONNECT option but so far it has failed to restore the stream automatically.


note : IPs and identifying variables have been sanitized.


#! /bin/bash

filename="test1.yuv"
streamTitle="Reconnect_TEST1" # friendly name for stream. Helps when running pgrep
streamInput="100.100.100.100:8002" # Input IP:Port we're receiving on.
multicastOut="232.100.100.100:5500" # Multicast IP:Port we're sending to
logFile=/home/username/logs/${streamTitle}.log # Log file we output the nohup data to.

nohup ffmpeg \
 -re \
 -video_size 854x480 \
 -i $filename \
 -i http://${streamInput} \
 -reconnect 1 \
 -reconnect_at_eof 1 \
 -reconnect_streamed 1 \
 -reconnect_on_network_error 1 \
 -reconnect_on_http_error 1 \
 -reconnect_delay_max 10 \
 -c:a ac3 \
 -ac 1 \
 -af loudnorm \
 -vf loop=loop=-1:size=1:start=0 \
 -c:v libx264 \
 -profile:v main \
 -s:v 854x480 \
 -aspect 16:9 \
 -r 15 -g 30 -bf 0 -crf 30 \
 -fflags +genpts -flags +cgop+ilme \
 -metadata title=$streamTitle \
 -metadata:s:a:0 language=eng \
 -mpegts_flags +pat_pmt_at_frames \
 -flush_packets 0 -threads 1 \
 -v verbose \
 -f mpegts udp://${multicastOut}?pkt_size=1316 \
 -loglevel verbose >$logFile &



-
doc/html : support texinfo 7.0
8 novembre 2023, par Frank Plowmandoc/html : support texinfo 7.0
Resolves trac ticket #10636 (http://trac.ffmpeg.org/ticket/10636).
Texinfo 7.0, released in November 2022, changed the names of various
functions. Compiling docs with Texinfo 7.0 resulted in warnings and
improperly formatted documentation. More old names appear to have
been removed in Texinfo 7.1, released October 2023, which causes docs
compilation to fail.This commit addresses the issue by adding logic to switch between the old
and new function names depending on the Texinfo version. Texinfo 6.8
produces identical documentation before and after the patch.CC
https://www.mail-archive.com/debian-bugs-dist@lists.debian.org/msg1938238.html
https://bugs.gentoo.org/916104Signed-off-by : Frank Plowman <post@frankplowman.com>