
Recherche avancée
Médias (1)
-
Collections - Formulaire de création rapide
19 février 2013, par
Mis à jour : Février 2013
Langue : français
Type : Image
Autres articles (22)
-
Supporting all media types
13 avril 2011, parUnlike most software and media-sharing platforms, MediaSPIP aims to manage as many different media types as possible. The following are just a few examples from an ever-expanding list of supported formats : images : png, gif, jpg, bmp and more audio : MP3, Ogg, Wav and more video : AVI, MP4, OGV, mpg, mov, wmv and more text, code and other data : OpenOffice, Microsoft Office (Word, PowerPoint, Excel), web (html, CSS), LaTeX, Google Earth and (...)
-
Submit bugs and patches
13 avril 2011Unfortunately a software is never perfect.
If you think you have found a bug, report it using our ticket system. Please to help us to fix it by providing the following information : the browser you are using, including the exact version as precise an explanation as possible of the problem if possible, the steps taken resulting in the problem a link to the site / page in question
If you think you have solved the bug, fill in a ticket and attach to it a corrective patch.
You may also (...) -
La sauvegarde automatique de canaux SPIP
1er avril 2010, parDans le cadre de la mise en place d’une plateforme ouverte, il est important pour les hébergeurs de pouvoir disposer de sauvegardes assez régulières pour parer à tout problème éventuel.
Pour réaliser cette tâche on se base sur deux plugins SPIP : Saveauto qui permet une sauvegarde régulière de la base de donnée sous la forme d’un dump mysql (utilisable dans phpmyadmin) mes_fichiers_2 qui permet de réaliser une archive au format zip des données importantes du site (les documents, les éléments (...)
Sur d’autres sites (3929)
-
lavu/timer.h : add Linux Perf API support
2 septembre 2017, par Clément Bœschlavu/timer.h : add Linux Perf API support
Refer to "checkasm : use perf API on Linux ARM*" commit for the
rationale.The implementation is somehow duplicated with checkasm, but so is the
current usage of AV_READ_TIME(). Until these implementations and
heuristics are made consistent, I don't see a way of sharing that code.Note : when using libavutil/timer.h, it is now important to include
before any other include due to the _GNU_SOURCE requirement. -
How to restream an RTSP stream without processing anything on linux computer ?
16 août 2016, par user2365252I am working with Embedded Linux machine which can get the RTSP stream from other source. Now if I configure my FFMPEG and try to restream it, the CPU usage reaches very high. This probably is due to Embedded Hardware capability.
Is there any possible way we can simply restream the incoming stream with out processing it at all using any type of library ?
-
FFmpeg : Windows vs Linux issues
16 octobre 2022, par ChrisI have run into an issue that I am pretty sure I have narrowed down to FFmpeg.


I have a Flask app that restreams live streams using FFmpeg.


...

@app.route("/play/", methods=["GET"])
def play():
 def streamData():
 try:
 with subprocess.Popen(
 ffmpegcmd,
 stdin=subprocess.DEVNULL,
 stdout=subprocess.PIPE,
 stderr=subprocess.PIPE,
 ) as ffmpeg_sb:
 while True:
 chunk = ffmpeg_sb.stdout.read(1024)
 if len(chunk) == 0:
 break
 yield chunk
 except:
 pass
 finally:
 ffmpeg_sb.kill()

 return Response(streamData())

...




I am using the following command.


ffmpeg -loglevel panic -hide_banner -i <url> -vcodec copy -acodec copy -f mpegts pipe:</url>


When I run my Flask app on Windows, both VLC and TVHeadend play the piped output perfectly.
However under Linux only VLC will play the piped output. I can get TVHeadend to play the stream from Linux, but it requires me to enable the AV Library option in TVHeadend, which I want to avoid. I have tested this using WSL (Ubuntu) and Docker (alpine + Ubuntu) on my Ubuntu server where the app will live.


I can only assume its because FFmpeg behaves differently between Windows and Linux ? I have tried several different version of FFmpeg... So I don't think its a version issue.


The version of FFmpeg I am currently using on Windows is this one https://www.gyan.dev/ffmpeg/builds/ but I experienced the same success on older versions, so again, I don't think its a version number issue.


Can anyone suggest how I can go about finding out what the cause is ?
Is it possible that some default values differ between Windows and Linux ?


Any advice is appreciated !