Recherche avancée
Médias (1)
-
Revolution of Open-source and film making towards open film making
6 octobre 2011, par
Mis à jour : Juillet 2013
Langue : English
Type : Texte
Autres articles (31)
-
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 -
Encoding and processing into web-friendly formats
13 avril 2011, parMediaSPIP automatically converts uploaded files to internet-compatible formats.
Video files are encoded in MP4, Ogv and WebM (supported by HTML5) and MP4 (supported by Flash).
Audio files are encoded in MP3 and Ogg (supported by HTML5) and MP3 (supported by Flash).
Where possible, text is analyzed in order to retrieve the data needed for search engine detection, and then exported as a series of image files.
All uploaded files are stored online in their original format, so you can (...) -
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 (...)
Sur d’autres sites (6035)
-
smoothstreamingenc : Write to a temp file while updating the manifest
17 août 2013, par Martin Storsjösmoothstreamingenc : Write to a temp file while updating the manifest
If a client tries to read the file while it’s being updated, the client
would get an incomplete manifest. Instead write to a separate temp file
and atomically rename it to replace the previous one.Signed-off-by : Martin Storsjö <martin@martin.st>
-
avformat/gif : Do not write GIF89a header if loop is set to -1.
6 juillet 2013, par Eugene Dzhurinsky -
NodeJS - FFmpeg : Extract Frame from Video stdin stream (EPIPE write Error)
3 avril 2022, par ManiBI want to pipe an input steam (video) (should later be an http stream) to ffmpeg child process to extract an thumbnail :


require("stream").pipeline(
 require("fs").createReadStream("files/myVideo.mp4"),
 require("child_process").spawn("ffmpeg", ["-i", "-", "-ss", "00:00:01", "-frames:v", "1", "-y", "files/myImage.jpeg"]).stdin,
 (err) => console.log("Done", err)
);


So far so good, I get an extracted Image, but also an Error :


Error: write EPIPE
 at WriteWrap.onWriteComplete [as oncomplete] (node:internal/stream_base_commons:94:16) {
 errno: -32,
 code: 'EPIPE',
 syscall: 'write'
}


Converting full videos (e.g. mp4 -> mkv) works without errors.


My suggestion is, FFmpeg will close stdin too early (because image is already found on first second) and readable-stream is not able to write to stdin anymore.


How can I manage, to fix the error and gracefully close all streams ?


System :


- 

- Linux Centos 7 (also tried Windows Server 1809)
- NodeJS v16.14.1 (Windows v16.13.0)
- FFmpeg v4.4.1-static (Windows v4.4-full_build-www.gyan.dev)








Syndiquer tout le site
