
Recherche avancée
Autres articles (108)
-
Multilang : améliorer l’interface pour les blocs multilingues
18 février 2011, parMultilang est un plugin supplémentaire qui n’est pas activé par défaut lors de l’initialisation de MediaSPIP.
Après son activation, une préconfiguration est mise en place automatiquement par MediaSPIP init permettant à la nouvelle fonctionnalité d’être automatiquement opérationnelle. Il n’est donc pas obligatoire de passer par une étape de configuration pour cela. -
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. -
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 (15214)
-
Fail to get the statistics of https video using ffprobe
23 janvier 2017, par amithI want to collect the statistics of a video stream backed by https url.
on executing
ffprobe https://www.youtube.com/watch?v=YbYjtSFa5FsI get the following output
vagrant@kaybus:/vagrant/kaybus$ ffprobe https://www.youtube.com/watch?v=YbYjtSFa5Fs
ffprobe version N-80901-gfebc862 Copyright (c) 2007-2016 the FFmpeg developers
built with gcc 4.8 (Ubuntu 4.8.4-2ubuntu1~14.04.3)
configuration: --extra-libs=-ldl --prefix=/opt/ffmpeg --mandir=/usr/share/man --enable-avresample --disable-debug --enable-nonfree --enable-gpl --enable-version3 --enable-libopencore-amrnb --enable-libopencore-amrwb --disable-decoder=amrnb --disable-decoder=amrwb --enable-libpulse --enable-libfreetype --enable-gnutls --enable-libx264 --enable-libx265 --enable-libfdk-aac --enable-libvorbis --enable-libmp3lame --enable-libopus --enable-libvpx --enable-libspeex --enable-libass --enable-avisynth --enable-libsoxr --enable-libxvid --enable-libvidstab
libavutil 55. 28.100 / 55. 28.100
libavcodec 57. 48.101 / 57. 48.101
libavformat 57. 41.100 / 57. 41.100
libavdevice 57. 0.102 / 57. 0.102
libavfilter 6. 47.100 / 6. 47.100
libavresample 3. 0. 0 / 3. 0. 0
libswscale 4. 1.100 / 4. 1.100
libswresample 2. 1.100 / 2. 1.100
libpostproc 54. 0.100 / 54. 0.100
[tls @ 0x3547140] A TLS packet with unexpected length was received.
https://www.youtube.com/watch?v=YbYjtSFa5Fs: Input/output error[tls @ 0x3547140] A TLS packet with unexpected length was received.
How to fix the above error ?https is listed in ffprobe’s supported input and output protocols.
ffprobe -version
vagrant@kaybus:/vagrant/kaybus$ ffprobe -version
ffprobe version N-80901-gfebc862 Copyright (c) 2007-2016 the FFmpeg developers
built with gcc 4.8 (Ubuntu 4.8.4-2ubuntu1~14.04.3)Thanks
-
How to reduce the size of video file as a buffer or blob before writing it on Nodejs ?
7 novembre 2022, par HypothesisI send live feed from client to the server using websocket from the client side like this :


recorder = new MediaRecorder(canvasStream, {
 mimeType: 'video/webm;codecs=vp9',
 videoBitsPerSecond: 3 * 1024 * 1024
 });
 recorder.ondataavailable = async (e) => {
 const arbuf = await e.data.arrayBuffer()
 ws.send(pack({ type: 'REC', data: arbuf })) //sends to server
 }



and on the server side I get them like this :


let blob = new Blob(chunks, { type: 'video/mp4' })
 const buffer = Buffer.from(await blob.arrayBuffer());
 fs.writeFile("foo.mp4", buffer, () => console.log('video saved!'));



However
foo.mp4
is really large. Please help me find a way to reduce the size offoo.mp4
as it is being written down to the disc. ( I can reduce it after it is written, however that won't do the trick for me. It has to be encoded and compressed before it is written )

-
avformat/matroskaenc : Write level 1 elements in one go
30 décembre 2019, par Andreas Rheinhardtavformat/matroskaenc : Write level 1 elements in one go
Up until now, writing level 1 elements proceeded as follows : First, the
element id was written to the ordinary output AVIOContext and a dynamic
buffer was opened for the content of the level 1 element in
start_ebml_master_crc32(). Then this buffer was actually used and after it
was closed (in end_ebml_master_crc32()), the size field corresponding to
the buffer's size was written, after which the actual data was written.This commit changes this : Nothing is written to the main AVIOContext any
more in start_ebml_master_crc32(). end_ebml_master_crc32() now writes
both the id, the length field as well as the data. This implies that
one can start a level 1 element in memory without outputting anything.
This is done to enable to test whether enough space has been reserved
for the Cues (if space has been reserved for them) before writing them.
A large duration between outputting the header and outputting the rest
could also break certain streaming usecases like the one from #8578
(which this commit fixes).Signed-off-by : Andreas Rheinhardt <andreas.rheinhardt@gmail.com>