
Recherche avancée
Autres articles (92)
-
Pas question de marché, de cloud etc...
10 avril 2011Le vocabulaire utilisé sur ce site essaie d’éviter toute référence à la mode qui fleurit allègrement
sur le web 2.0 et dans les entreprises qui en vivent.
Vous êtes donc invité à bannir l’utilisation des termes "Brand", "Cloud", "Marché" etc...
Notre motivation est avant tout de créer un outil simple, accessible à pour tout le monde, favorisant
le partage de créations sur Internet et permettant aux auteurs de garder une autonomie optimale.
Aucun "contrat Gold ou Premium" n’est donc prévu, aucun (...) -
Automated installation script of MediaSPIP
25 avril 2011, parTo overcome the difficulties mainly due to the installation of server side software dependencies, an "all-in-one" installation script written in bash was created to facilitate this step on a server with a compatible Linux distribution.
You must have access to your server via SSH and a root account to use it, which will install the dependencies. Contact your provider if you do not have that.
The documentation of the use of this installation script is available here.
The code of this (...) -
Support audio et vidéo HTML5
10 avril 2011MediaSPIP utilise les balises HTML5 video et audio pour la lecture de documents multimedia en profitant des dernières innovations du W3C supportées par les navigateurs modernes.
Pour les navigateurs plus anciens, le lecteur flash Flowplayer est utilisé.
Le lecteur HTML5 utilisé a été spécifiquement créé pour MediaSPIP : il est complètement modifiable graphiquement pour correspondre à un thème choisi.
Ces technologies permettent de distribuer vidéo et son à la fois sur des ordinateurs conventionnels (...)
Sur d’autres sites (12099)
-
ffmpeg av_read_frame() need very long time to stop
24 juillet 2017, par yuyingsuifengI use ffmpeg to decode RTSP video.It likes that :
When it’s on the end of file,it block in the av_read_frame() for a long time,why ? -
ffmpeg av_read_frame() need very long time to stop
2 juin 2014, par yuyingsuifengI use ffmpeg to decode RTSP video.It likes that :
When it’s on the end of file,it block in the av_read_frame() for a long time,why ? -
Accurate FFmpeg capture start time
28 juillet 2016, par AdamI’m using ffmpeg from the command line to capture from a webcam to a file using the following :
ffmpeg -y -rtbufsize 702000k -f dshow -s 320x240 -r 25 -i video="<device>" -t 10 -vcodec mjpeg -q:v 2 out.mp4
</device>There is a slight delay between executing the command and the start of the capture ( 0.5 sec).
I’m trying to find a way to accurately determine the start time (UTC/GMT) of the capture.My initial thought was to use the file-creation time as this might accurately reflect when the first frame was encoded (as opposed to when the command was executed). Unfortunately the file creation time is only accurate to the second which is not precise enough (and I’m not sure this would have given an accurate result anyway).
My next thought was to use ffmpegs timestamp option. According to the documentation (http://www.ffmpeg.org/ffmpeg.html) :
‘-timestamp time (output)’
Set the recording timestamp in the container. The syntax for time is:
now|([(YYYY-MM-DD|YYYYMMDD)[T|t| ]]((HH:MM:SS[.m...])|(HHMMSS[.m...]))[Z|z])If the value is "now" it takes the current time. Time is local time unless ’Z’ or
’z’ is appended, in which case it is interpreted as UTC. If the year-month-day part
is not specified it takes the current year-month-day.So I added the option :
ffmpeg -y -rtbufsize 702000k -f dshow -s 320x240 -r 25 -i video="<device>" -t 10 -vcodec mjpeg -q:v 2 -timestamp now out.mp4
</device>Unfortunately ffmpeg doesn’t seem to like this :
Option timestamp (set the recording timestamp (’now’ to set the
current time)) cannot be applied to output file out.mp4 — you are
trying to apply an input option to an output file or vice versa. Move
this option before the file it belongs to.Error parsing options for output file out.mp4.
Error opening output files : Error number -22 occurred
The documentation says -timestamp is an output option and it appears to be applied to the output file so I’m confused by this error.
Can anyone suggest a way to accurately determine the capture start time ?
Does anyone know why the -timestamp option gives an error ?