Recherche avancée
Médias (91)
-
MediaSPIP Simple : futur thème graphique par défaut ?
26 septembre 2013, par
Mis à jour : Octobre 2013
Langue : français
Type : Video
-
avec chosen
13 septembre 2013, par
Mis à jour : Septembre 2013
Langue : français
Type : Image
-
sans chosen
13 septembre 2013, par
Mis à jour : Septembre 2013
Langue : français
Type : Image
-
config chosen
13 septembre 2013, par
Mis à jour : Septembre 2013
Langue : français
Type : Image
-
SPIP - plugins - embed code - Exemple
2 septembre 2013, par
Mis à jour : Septembre 2013
Langue : français
Type : Image
-
GetID3 - Bloc informations de fichiers
9 avril 2013, par
Mis à jour : Mai 2013
Langue : français
Type : Image
Autres articles (43)
-
Déploiements possibles
31 janvier 2010, parDeux types de déploiements sont envisageable dépendant de deux aspects : La méthode d’installation envisagée (en standalone ou en ferme) ; Le nombre d’encodages journaliers et la fréquentation envisagés ;
L’encodage de vidéos est un processus lourd consommant énormément de ressources système (CPU et RAM), il est nécessaire de prendre tout cela en considération. Ce système n’est donc possible que sur un ou plusieurs serveurs dédiés.
Version mono serveur
La version mono serveur consiste à n’utiliser qu’une (...) -
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 (...) -
Dépôt de média et thèmes par FTP
31 mai 2013, parL’outil MédiaSPIP traite aussi les média transférés par la voie FTP. Si vous préférez déposer par cette voie, récupérez les identifiants d’accès vers votre site MédiaSPIP et utilisez votre client FTP favori.
Vous trouverez dès le départ les dossiers suivants dans votre espace FTP : config/ : dossier de configuration du site IMG/ : dossier des média déjà traités et en ligne sur le site local/ : répertoire cache du site web themes/ : les thèmes ou les feuilles de style personnalisées tmp/ : dossier de travail (...)
Sur d’autres sites (6521)
-
Is there a way to improve video fetching speed when using FFmpeg for trimming ?
14 janvier 2024, par OtisI have a React component that uses the @ffmpeg/ffmpeg library to trim videos. The trimming process involves fetching a video file from a URL and then using FFmpeg to perform the actual trim. I've noticed that when I execute the trimVideo function on a new URL for the first time, it takes a considerable amount of time to fetch the file. However, on subsequent executions with the same URL, it executes in less than 5 seconds.


import { useEffect, useRef, useState } from 'react';
import { FFmpeg } from '@ffmpeg/ffmpeg';
import { fetchFile, toBlobURL } from '@ffmpeg/util';


export default function TrimVideo() {
 const [loaded, setLoaded] = useState(false);
 const [isLoading, setIsLoading] = useState(false);
 const [trimmedBlobUrl, setTrimmedBlobUrl] = useState('');
 const [progress, setProgress] = useState<any>(0);
 const ffmpegRef = useRef<any>(new FFmpeg());
 const videoRef = useRef<any>(null);
 const messageRef = useRef<any>(null);

 const [exporting, setExporting] = useState(false);

 const onlineVideoUrl =
 'http://commondatastorage.googleapis.com/gtv-videos-bucket/sample/BigBuckBunny.mp4';

 const loadFFmpeg = async () => {
 setIsLoading(true);

 const baseURL = 'https://unpkg.com/@ffmpeg/core@0.12.2/dist/umd';
 const ffmpeg = ffmpegRef.current;

 ffmpeg.on('log', ({ message }: any) => {
 if (messageRef.current) messageRef.current.innerHTML = message;
 });

 // Load FFmpeg core and wasm files
 await ffmpeg.load({
 coreURL: await toBlobURL(
 `${baseURL}/ffmpeg-core.js`,
 'text/javascript',
 ),
 wasmURL: await toBlobURL(
 `${baseURL}/ffmpeg-core.wasm`,
 'application/wasm',
 ),
 });

 setLoaded(true);
 setIsLoading(false);
 };

 useEffect(() => {
 loadFFmpeg();
 }, []);

 const trimVideo = async () => {
 const ffmpeg = ffmpegRef.current;
 setExporting(true);
 setProgress(0);

 const trimStart = 1;
 const trimEnd = 40;
 const trimmedVideo = trimEnd - trimStart;


 try {
 console.log('Fetching Video...');
 await ffmpeg.writeFile(
 'myFile.mp4',
 await fetchFile(onlineVideoUrl),
 );
 console.log('Executing FFMPEG...');
 await ffmpeg.exec([
 '-ss',
 `${trimStart}`,
 '-accurate_seek',
 '-i',
 'myFile.mp4',
 '-to',
 `${trimmedVideo}`,
 '-codec',
 'copy',
 'output.mp4',
 ]);

 const data: any = await ffmpeg?.readFile('output.mp4');
 const url = URL.createObjectURL(
 new Blob([data.buffer], { type: 'video/mp4' }),
 );
 setTrimmedBlobUrl(url);
 } catch (error) {
 console.log(error);
 } finally {
 setProgress(0);
 setExporting(false);
 }
 };


 return loaded ? (
 <div>
 {trimmedBlobUrl && (
 <video ref="{videoRef}" controls="controls" src="{trimmedBlobUrl}"></video>
 )}
 <br />

 <button>> trimVideo()}>Trim Video</button>
 <h3>Progress: {progress}</h3>
 <p ref="{messageRef}"></p>
 </div>
 ) : (
 <p>Loading FFmpeg...</p>
 );
}
</any></any></any></any>

Is there a way to improve the fetching of the video to be consistently fast across all executions ?


-
ffmpeg.exe not found inside project directory
8 février 2019, par BayLifeI´m currently working on my first electron / react app, which makes use of ffmpeg. I do have a problem to link the .exe file correctly.
The prolem I´m facing is that I
ffmpeg.exeis not found when trying to link it with a relative path inside my project directory. When using an absolute path it does work.The exe files are in the sub-folder of the current directroy.
It does work when I´m using such path :
'C:\\Users\\xxx\\Documents\\development\\ytDownloader\\app\\utils\\ffmpeg\\ffprobe.exe'But when trying it like this
.setFfmpegPath('.\\ffmpeg\\ffmpeg.exe')or
'./ffmpeg/ffmpeg.exe'it does not working.
Additionally I would really like to avoid using
\\in my project.Does someone have an Idea what I´m doing wrong here ?
I get this error message :
Error: spawn .\ffmpeg\ffmpeg.exe ENOENT
at Process.ChildProcess._handle.onexit (internal/child_process.js:229)
at onErrorNT (internal/child_process.js:406)
at process._tickCallback (internal/process/next_tick.js:63) -
Fluent-FFMPEG redirects to home page when recording is finished
25 mai 2022, par Myles JeffersonI am using fluent-FFmpeg with my node.js and express server to record videos from an RTSP stream. The issue I am encountering is that once the command to record the video is finished, my React client-side always redirects to the home page of my application, even though this is not the behavior I want. I want the user to remain on the page with the RTSP stream and just receive a toast notification indicating that the recording is finished. With this issue, the page redirects before the notification has a chance to display. Is this an issue with my server-side or client-side code ?


Node.js


export const startRecording = async (req, res) => {
 const camera = req.params;
 if (camera.id in runningCommands) { return res.json({ "status": "failure", "error": "Recording already in progress" }) }
 const { recordTime, uid } = req.body;
 let conn = createConnection(config);
 conn.connect();
 let query = 'SELECT * FROM cameras WHERE id = ?';
 conn.query(query, [camera.id], (error, rows) => {
 if (error) { return res.json({ "status": "failure", "error": error }) }
 const camera = rows[0];
 const { ip, fname } = camera;
 const currentDate = new Date().toLocaleString().replace(/[:/\s]/g, '-').replace(',', '');
 const filename = `${fname}-${currentDate}`;

 try {
 // FFmpeg command to start recording
 const command = ffmpeg(`rtsp://${ip}/axis-media/media.amp`)
 .videoCodec('libx264')
 .size('1280x720')
 .duration(recordTime)
 .on('start', commandLine => {
 runningCommands[camera.id] = command
 console.log(`Spawned Ffmpeg with command: ${commandLine}`)
 })
 .on('error', err => console.error(err))
 .on('end', () => {
 delete runningCommands[camera.id]
 console.log('Recording Complete')
 takeScreenshot(filename, `./public/recordings/mp4/${filename}.mp4`)
 conn.query('INSERT INTO recordings (uid, cid, filename) VALUES (?, ?, ?)', [uid, camera.id, filename], () => conn.end())
 res.json({ "status": "success", "message": "Recording ended" })
 })
 .save(`./public/recordings/mp4/${filename}.mp4`);
 } catch (error) { console.error(error)}
 })
}


React :


const handleRecording = async () => {
 try {
 setIsRecording(true)
 const futureTime = new Date().getTime() + recordTime * 1000
 const finishedTime = new Date(futureTime).toLocaleTimeString()
 setTimeRemaining(finishedTime)
 const { data } = await publicRequest.post(`record/startRecording/${id}`, { recordTime, uid: user.id })
 window.location.reload(false)
 if (data.status === 'success') {
 setIsRecording(false)
 toast('Recording finished!', { type: 'success' })
 } else {
 setIsRecording(true)
 toast('Recording already in progress!', { type: 'error' })
 }
 } catch (error) {
 console.error(error)
 }
 }


Syndiquer tout le site
