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 (111)
-
Script d’installation automatique de MediaSPIP
25 avril 2011, parAfin de palier aux difficultés d’installation dues principalement aux dépendances logicielles coté serveur, un script d’installation "tout en un" en bash a été créé afin de faciliter cette étape sur un serveur doté d’une distribution Linux compatible.
Vous devez bénéficier d’un accès SSH à votre serveur et d’un compte "root" afin de l’utiliser, ce qui permettra d’installer les dépendances. Contactez votre hébergeur si vous ne disposez pas de cela.
La documentation de l’utilisation du script d’installation (...) -
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 (...)
-
Les notifications de la ferme
1er décembre 2010, parAfin d’assurer une gestion correcte de la ferme, il est nécessaire de notifier plusieurs choses lors d’actions spécifiques à la fois à l’utilisateur mais également à l’ensemble des administrateurs de la ferme.
Les notifications de changement de statut
Lors d’un changement de statut d’une instance, l’ensemble des administrateurs de la ferme doivent être notifiés de cette modification ainsi que l’utilisateur administrateur de l’instance.
À la demande d’un canal
Passage au statut "publie"
Passage au (...)
Sur d’autres sites (7717)
-
Problem importing whatsapp-web.js nodejs module in electron react app
26 mai 2021, par Sunil ShahI am trying to build an electron react app. I need to integrate this node modules https://www.npmjs.com/package/whatsapp-web.js in my electron react app. My main.js of electron looks like this :




// Modules to control application life and create native browser window
const { app, BrowserWindow } = require("electron");
const path = require("path");

function createWindow() {
 // Create the browser window.
 const mainWindow = new BrowserWindow({
 width: 800,
 height: 600,
 webPreferences: {
 webSecurity: false,
 },
 });

 // and load the index.html of the app.
 mainWindow.loadURL("your ip address:3000");

 // Open the DevTools.
 // mainWindow.webContents.openDevTools()
}

app.whenReady().then(() => {
 createWindow();

 app.on("activate", function () {
 // On macOS it's common to re-create a window in the app when the
 // dock icon is clicked and there are no other windows open.
 if (BrowserWindow.getAllWindows().length === 0) createWindow();
 });
});

// Quit when all windows are closed, except on macOS. There, it's common
// for applications and their menu bar to stay active until the user quits
// explicitly with Cmd + Q.
app.on("window-all-closed", function () {
 if (process.platform !== "darwin") app.quit();
});

// In this file you can include the rest of your app's specific main process
// code. You can also put them in separate files and require them here.






And the React code where i want to import whatsapp-web.js module looks like




import React from "react";
import styled from "styled-components";
const qrcode = require('qrcode-terminal');
const Client = require('whatsapp-web.js');
function Error() {
 var client = new Client();
 client.initialize();
 console.log(client);
 console.log(qrcode);
 return (
 <container>
 <errorimage src="https://cdn4.iconfinder.com/data/icons/smiley-vol-3-2/48/134-512.png"></errorimage>
 <errormessage>Oops, you are not connected to any number.</errormessage>
 </container>
 );
}

export default Error;

const Container = styled.div`
 display: flex;
 height: 100vh;
 width: 100%;
 padding-top: 20vh;
 position: center;
 /* align-items: center; */
 justify-content: center;
`;

const ErrorImage = styled.img`
 background-color: transparent;
 background-repeat: no-repeat;
 background-size: cover;
 object-fit: contain;

 width: 25%;
 height: 25%;

 /* border: 2px solid black; */
`;

const ErrorMessage = styled.div`
 margin: 10px;
 width: 50%;
 height: 25%;
 /* top: 20px; */
 font-size: 30px;
 align-items: center;
 font-family: "Lucida Console", "Courier New", monospace;
 /* font-weight: bold; */
`;






Now everytime I try to import const Client = require('whatsapp-web.js') It throws error like this :
**
[0] ./node_modules/fluent-ffmpeg/index.js
[0] Module not found : Can't resolve './lib-cov/fluent-ffmpeg' in 'D :\Sunil\Zarir_app-main\Zarir_app-main\node_modules\fluent-ffmpeg'
[0] Compiling...
[0] Failed to compile.


and I tried the solution
https://github.com/fluent-ffmpeg/node-fluent-ffmpeg/issues/573#issuecomment-305408048
and other resources but still nothing works and just loops in errors and errors.
Please help if you have any information related to it.
Thank you.


-
ffmpeg timeout with rtsp
17 janvier 2024, par eSlavkoI have script that capture image from wifi camera with ffmpeg.
It works fine until camera is not reachable due to network troubles.
The script stuck in ffmpeg capture and never exit. Is it possible to have some kind of timeout ? -stimeout (in miliseconds) seems not working.


There is part of script that capture images. (there are some manipulation after that)


#!/bin/bash
week="$(date '+%Y_%U')"
ts="$(date '+%Y-%m-%d_%H:%M:%S')"
ffmpeg -rtsp_transport tcp -y -i "rtsp://192.168.64.101" -frames:v 1 $week/$ts.jpg -stimeout 3000 -y


I did test on other camera and results are :


ffmpeg -y -i "rtsp://192.168.64.112:8554/profile0" -frames:v 1 Ilatest.jpg


Does work OK, but with timeout of 5 seconds as


ffmpeg -timeout 5000000 -y -i "rtsp://192.168.64.112:8554/profile0" -frames:v 1 Ilatest.jpg


doesn't and I got error report as :


ffmpeg version 4.2.4-1ubuntu0.1 Copyright (c) 2000-2020 the FFmpeg developers built with gcc 9 (Ubuntu 9.3.0-10ubuntu2)
...
...
[rtsp @ 0x55d250488740] Unable to open RTSP for listening
rtsp://192.168.64.112:8554/profile0: Cannot assign requested address


-
ffmpeg scale doesn't work if destination res is larger than source
21 décembre 2017, par VibokI just tried ffmpeg filter
scale=320x180:force_original_aspect_ratio=disableto resize a 270x480 video into a 320x180 video, and it still keeps aspect ratio.force_original_aspect_ratio=disablegot ignored.I guess the problem is that the destination width is bigger than the source width, while the destination height is smaller. Because it worked for other videos, even without
force_original_aspect_ratio=disable.The resulted file is also weird. It says it’s 320x180, while its weight is obliviously smaller than that.
Here are the video files, original and resized. https://drive.google.com/file/d/1UNXlfwpzoizhx7WOjqn44mlcbQgacOHS/view?usp=sharing
Here is my command :
ffmpeg -i 480P_600K_107047752.mp4 -force_key_frames 00:00:03.000 -filter_complex [0:v]scale=320x180:force_original_aspect_ratio=disable,fps=30[vid];[vid]
Syndiquer tout le site
