
Recherche avancée
Autres articles (97)
-
Des sites réalisés avec MediaSPIP
2 mai 2011, parCette page présente quelques-uns des sites fonctionnant sous MediaSPIP.
Vous pouvez bien entendu ajouter le votre grâce au formulaire en bas de page. -
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 (...) -
De l’upload à la vidéo finale [version standalone]
31 janvier 2010, parLe chemin d’un document audio ou vidéo dans SPIPMotion est divisé en trois étapes distinctes.
Upload et récupération d’informations de la vidéo source
Dans un premier temps, il est nécessaire de créer un article SPIP et de lui joindre le document vidéo "source".
Au moment où ce document est joint à l’article, deux actions supplémentaires au comportement normal sont exécutées : La récupération des informations techniques des flux audio et video du fichier ; La génération d’une vignette : extraction d’une (...)
Sur d’autres sites (11820)
-
For converting video to frames, should I do client or server side processing ?
23 mars 2024, par Tomas MarsonHere is the thing, I have a Nodejs API that serves one video at a time when client request it.


The client (made in react) receives the video, which has no more than 15 seconds, watch it and decide if he wants to approve or deny it.
If he approves the video, it must be displayed in a sort of frames carousel, with one frame per second, so there is no more than 15 images/frames.


So the question is, should I do the conversion video-to-frames on client once he approves the video or should I do it on server-side and then request each frame (or streaming all frames with one request if possible) ?


Now, I'm doing the conversion on server with ffmpeg, but it seems tricky to send all the frames when the client already have them inside the video.


-
avformat/matroskaenc : Don't use stream side-data size
21 mai 2020, par Andreas Rheinhardtavformat/matroskaenc : Don't use stream side-data size
av_stream_get_side_data() tells the caller whether a stream has side
data of a specific type ; if present it can also tell the caller the size
of the side data via an optional argument. The Matroska muxer always
used this optional argument, although it doesn't really need the size,
as the relevant side-data are not buffers, but structures. So change
this.Furthermore, relying on the size also made the code susceptible to
a quirk of av_stream_get_side_data() : It only sets the size argument if
it found side data of the desired type. mkv_write_video_color() checks
for side-data twice with the same variable for the size without resetting
the size in between ; if the second type of side-data isn't present, the
size will still be what it was after the first call. This was not
dangerous in practice, as the check for the existence of the second
side-data compared the size with the expected size, so it would only be
problematic if lots of elements were to be added to AVContentLightMetadata.Reviewed-by : James Almer <jamrial@gmail.com>
Signed-off-by : Andreas Rheinhardt <andreas.rheinhardt@gmail.com> -
avfilter/showinfo : support Content Light Level information
9 août 2019, par Limin Wang