
Recherche avancée
Médias (1)
-
Bug de détection d’ogg
22 mars 2013, par
Mis à jour : Avril 2013
Langue : français
Type : Video
Autres articles (99)
-
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 (...) -
ANNEXE : Les plugins utilisés spécifiquement pour la ferme
5 mars 2010, parLe site central/maître de la ferme a besoin d’utiliser plusieurs plugins supplémentaires vis à vis des canaux pour son bon fonctionnement. le plugin Gestion de la mutualisation ; le plugin inscription3 pour gérer les inscriptions et les demandes de création d’instance de mutualisation dès l’inscription des utilisateurs ; le plugin verifier qui fournit une API de vérification des champs (utilisé par inscription3) ; le plugin champs extras v2 nécessité par inscription3 (...)
-
Publier sur MédiaSpip
13 juin 2013Puis-je poster des contenus à partir d’une tablette Ipad ?
Oui, si votre Médiaspip installé est à la version 0.2 ou supérieure. Contacter au besoin l’administrateur de votre MédiaSpip pour le savoir
Sur d’autres sites (8998)
-
Softwares for adding real time text to a video [on hold]
30 juillet 2013, par user763410I am trying to add real time text (like weather information, stock quotes) to a video and broadcast it. My videos are going to be 2 hours long. I have been searching for decent softwares which can do the work for me. FFmpeg can do overlays only if text to be added is available fully before running ffmpeg code, so its not real time. I have not been able to able to get gstreamer to work on my hardware.
So, My question is :
Please suggest some softwares which can add (text)data to a video in real time.
Please don't post comparisons as that will trigger moderator's anger ! I don't want to start a flame war. Purpose of the question is to make a list. Btw, this should work from command line rather than a GUI.(Ps : If the question is closed because of being "not cnonstructive, please answer it on my google docs page here.
http://goo.gl/14dR2H)Thanks very much in advance.
-
Libav (ffmpeg) What is the most robust way to set the output stream time base ?
29 octobre 2016, par Jason CThis is a follow up to the solution to this question. My question is : When creating a new output stream, what is the most robust way to ensure that the output stream time base is set to a valid value for arbitrary formats ?
Another way to phrase this question is : If I leave the output stream time base set to 0/0, will
avformat_write_header
always initialize it to something appropriate ?Consider the following snippet (assume, unlike the above linked question, that I’m just encoding video and I do not have any input video timing info to refer to or copy from) :
AVFormatContext *formatx;
AVCodec *codec;
AVStream *stream;
...
stream = avformat_new_stream(formatx, codec);
stream->time_base = { 1, 10000 };
...
avformat_write_header(formatx, NULL);Here, my rationale is as follows :
- I observed, for MOV output formats, that if the stream time base is 0/0 when
avformat_write_header
is called, it is changed to 1/90000. Conclusion : At least one format (MOV) has a preferred time base that is set here, so others may be the same. - I do not know if
avformat_write_header
can be relied on to do this first, so I figure I’ll give it an initial reasonable value (1/10000) just in case.
So this covers cases where
avformat_write_header
doesn’t set the time base. However, now I’ve observed two worrisome things :- If I do initialize the time base (to 1/10000 in this case),
avformat_write_header
does not modify it. No worries yet, except... - As an experiment I set it to 1/1000000. The MOV muxer issued a warning that the time base was too high. This means
avformat_write_header
seems to obey the time base that was set even if it’s not necessarily appropriate for the muxer.
So my conflict is as follows :
- If I don’t set the time base before writing the header, then I know that in at least some cases
avformat_write_header
will initialize it to something appropriate. However, I don’t know if this is true in all cases, so I run the risk of this failing (or do I ? that’s the question here). - If I do set the time base before writing the header, then I’m safe in situations where
avformat_write_header
doesn’t, but I run the risk of breaking the muxer, since I can’t know what time bases are valid for arbitrary muxers (or can I ?) - The time base can’t be changed after writing the header, of course. So I can’t initialize it to 0/0 then check it for validity and set it to something afterwards. That is, if I set it to 0/0, and
avformat_write_header
does not fill it in, then I’ve missed an opportunity to set it myself and the program unnecessarily fails.
So what do I do ? How do I ensure that an output stream time base is both a) always set, and b) always set to something appropriate for the muxer ?
- I observed, for MOV output formats, that if the stream time base is 0/0 when
-
Can ffmpeg burn in time code ?
12 août 2017, par spinonI have a need to burn in a time code to a video and am wondering if this is something that ffmpeg is capable of ?