
Recherche avancée
Autres articles (51)
-
Les statuts des instances de mutualisation
13 mars 2010, parPour des raisons de compatibilité générale du plugin de gestion de mutualisations avec les fonctions originales de SPIP, les statuts des instances sont les mêmes que pour tout autre objets (articles...), seuls leurs noms dans l’interface change quelque peu.
Les différents statuts possibles sont : prepa (demandé) qui correspond à une instance demandée par un utilisateur. Si le site a déjà été créé par le passé, il est passé en mode désactivé. publie (validé) qui correspond à une instance validée par un (...) -
List of compatible distributions
26 avril 2011, parThe table below is the list of Linux distributions compatible with the automated installation script of MediaSPIP. Distribution nameVersion nameVersion number Debian Squeeze 6.x.x Debian Weezy 7.x.x Debian Jessie 8.x.x Ubuntu The Precise Pangolin 12.04 LTS Ubuntu The Trusty Tahr 14.04
If you want to help us improve this list, you can provide us access to a machine whose distribution is not mentioned above or send the necessary fixes to add (...) -
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 (7228)
-
avformat/mlvdec : demux LJ92 huffman comressed frames
13 décembre 2024, par Peter Rossavformat/mlvdec : demux LJ92 huffman comressed frames
A minimal DNG header is added to each LJ92 compressed frame, allowing
thme to be decoded by the TIFF decoder. The TIFF decoder is responsible
for setting up the MJPEG decoder, signalling the correct s->bayer flag,
and setting pix_fmt.The LJ92 compressed frames can be muxed out to DNG files, and manipulated
in DNG software. Tested with darktable and rawtherapee.Contributor : South East <8billion.people@gmail.com>
-
FFmpeg : Is it better to make a application then using ffmepg directly
14 juillet 2020, par MirabeauFor all my IP camera streams, I use, under Linux, ffmpeg by a bash script which allows me at the same time to manage :


1/ Convert the RTSP streams to HTTP (HLS) for the "Live" and therefore which generates "m3u8" file and *.ts segments


2/ Backup the stream for archiving (in increments of 5 minutes), a cron remove older files (xx days)


ffmpeg -i "rtsp://[IP_CAM01]" -rtsp_transport tcp -c copy -map 0 -f segment -segment_time 300 -segment_atclocktime 1 -segment_format mkv "cam01-% 03d.mkv" -c copy -f segment -segment_list cam01.m3u8 -segment_list_flags + live -segment_time 2 -segment_list_size 20 -segment_wrap 20 cam01-% 03d.ts



The question I ask myself, and the reason for this message is as follows :


- 

- would there be an interest (memory / cpu / speed) to develop a program (C/C++/other ?) to do the same thing by using the libraries of ffmpeg ?
- or the "gain" and the interest would be so minimal that it is not worth the expenditure of energy and time ?






I appeal to your feedback, your opinions, your tips !, and if you had leads (sample) to attack this kind of development, I am interested.


Thank you very much in advance for your feedback.
(this is my fist question on stackoverflow, Champagne ! ;))


-
subprocess.run output is empty (python 3.8)
26 juillet 2022, par Marino LinajeI'm trying to capture the output of a command with the following code :


lines = subprocess.run(['ffmpeg', '-hide_banner', '-nostats', '-i', in_filename, '-vn', '-af', 'silencedetect=n={}:d={}'.format(silence_threshold, silence_duration), '-f', 'null', '-'], capture_output=True, text=True, shell=True, check=True, encoding='utf-8').stdout 
print (lines)



But lines is an empty string and nothing is printed.
When
capture_output=True
is removed, the correct output is showed (without printing it).

I tested many combinations, including removing all the
subprocess.run
parameters and only includecapture_output=True
with the same result.

I also tested with few argument for a minimal example :
subprocess.run(['ffmpeg', '-version'], capture_output=True, text=True, shell=True, check=True, encoding='utf-8').stdout


Also tested
stdout=subprocess.PIPE
andstderr=subprocess.PIPE
assubprocess.run
arguments instead ofcapture_output=True


I can't figure out what is happening. Thanks in advance !