Recherche avancée
Médias (1)
-
Rennes Emotion Map 2010-11
19 octobre 2011, par
Mis à jour : Juillet 2013
Langue : français
Type : Texte
Autres articles (71)
-
Websites made with MediaSPIP
2 mai 2011, parThis page lists some websites based on MediaSPIP.
-
Creating farms of unique websites
13 avril 2011, parMediaSPIP platforms can be installed as a farm, with a single "core" hosted on a dedicated server and used by multiple websites.
This allows (among other things) : implementation costs to be shared between several different projects / individuals rapid deployment of multiple unique sites creation of groups of like-minded sites, making it possible to browse media in a more controlled and selective environment than the major "open" (...) -
Ecrire une actualité
21 juin 2013, parPrésentez les changements dans votre MédiaSPIP ou les actualités de vos projets sur votre MédiaSPIP grâce à la rubrique actualités.
Dans le thème par défaut spipeo de MédiaSPIP, les actualités sont affichées en bas de la page principale sous les éditoriaux.
Vous pouvez personnaliser le formulaire de création d’une actualité.
Formulaire de création d’une actualité Dans le cas d’un document de type actualité, les champs proposés par défaut sont : Date de publication ( personnaliser la date de publication ) (...)
Sur d’autres sites (15026)
-
Decoding RIMM streaming file format
10 septembre 2011, par ThomasI want to decode the video (visual) frames within a Blackberry RIMM file. So far I have a parser, and some corresponding container documentation from RIM.
The video codec is H264 and is explicitly set on the device using one of the video.encodings properties. However, FFMPEG is not able to decode the frames and this is driving me nuts.
Edit 1 : The issues seems to be lack of SPS and PPS in the frames, and artificially inserting them have proven unsuccessful so far (all grey image). Blackberry 9700 sends
0x00 0x00 0x ?? 0x ?? 0xType
where Type is according to table 7-1 in the H264 spec (I and P frames). We believe the 0x ?? 0x ?? represent the size of the frame, however the size does not always correspond to the size found by the parser (the parser seems to be working correctly).
I have a windows decoder codec from blackberry, called mc_demux_mp2_ds.ax, and can play some MPEG-4 files captured the same way, but it is a binary for windows. And the H264 files will not play either way. I am aware of previous attempts. The capture url for javax.microedition.media.Manager is
encoding=video-3gpp_width=176_height=144_video_codec=H264_audio_codec=AACand I am writing to an output stream. Some example files here.
Edit 2 :Turns out that about 3-4 of the 12-15 available video capture modes are flat out failing and refusing to output data, even in the simplest of test applications. So any working solution should implement MPEG-4, H264 and H263 in both AMR and AAC, in so getting fallback alternatives when one sound codec and/or resolution fails. Reboots, hangs and what not litters the Blackberry video implementation and vary from firmware to firmware ; total suckage.
-
Nothing happens when I am clicking on the create video button nothing happens and it displays the error failed to load ffmpeg
3 août 2024, par shashwat bajpaiSo here is my code in react and ffmpeg and wasm which I used to create a simple video editor to just apply audio on top of the image and convert it into mp3


This is my code :


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

function App() {
 const [videosrc, setvideosrc] = useState('');
 const [imgfile, setimgfile] = useState(null);
 const [audiofile, setaudiofile] = useState(null);
 const [ffmpeg, setFfmpeg] = useState(null);
 const [loading, setLoading] = useState(false);
 const [error, setError] = useState(null);

 useEffect(() => {
 const load = async () => {
 try {
 const ffmpegInstance = new FFmpeg();
 ffmpegInstance.on('log', ({ message }) => console.log(message));
 await ffmpegInstance.load({
 coreURL: await toBlobURL(`http://localhost:5173/node_modules/@ffmpeg/core/dist/ffmpeg-core.js`, 'text/javascript'),
 wasmURL: await toBlobURL(`http://localhost:5173/node_modules/@ffmpeg/core/dist/ffmpeg-core.wasm`, 'application/wasm'),
 });
 setFfmpeg(ffmpegInstance);
 console.log('FFmpeg loaded successfully');
 } catch (err) {
 console.error('Failed to load FFmpeg:', err);
 setError('Failed to load FFmpeg');
 }
 };
 load();
 }, []);

 const createVideo = async () => {
 console.log('Create Video button clicked');
 setLoading(true);
 setError(null);

 if (!ffmpeg) {
 console.error('FFmpeg not loaded');
 setError('FFmpeg not loaded');
 setLoading(false);
 return;
 }

 if (!imgfile || !audiofile) {
 console.error('Image or audio file not selected');
 setError('Please select both image and audio files');
 setLoading(false);
 return;
 }

 try {
 console.log('Writing files to MEMFS');
 await ffmpeg.writeFile('image.png', await fetchFile(imgfile));
 await ffmpeg.writeFile('sound.mp3', await fetchFile(audiofile));

 console.log('Running FFmpeg command');
 await ffmpeg.exec([
 "-framerate", "1/10",
 "-i", "image.png",
 "-i", "sound.mp3",
 "-c:v", "libx264",
 "-t", "10",
 "-pix_fmt", "yuv420p",
 "-vf", "scale=1920:1080",
 "test.mp4"
 ]);

 console.log('Reading output file');
 const data = await ffmpeg.readFile('test.mp4');

 console.log('Creating URL for video');
 const url = URL.createObjectURL(new Blob([data.buffer], { type: 'video/mp4' }));
 setvideosrc(url);
 console.log('Video created successfully');
 } catch (err) {
 console.error('Error creating video:', err);
 setError(`Error creating video: ${err.message}`);
 } finally {
 setLoading(false);
 }
 };

 const handlechangeimage = (e) => {
 setimgfile(e.target.files[0]);
 };

 const handlechangesound = (e) => {
 setaudiofile(e.target.files[0]);
 };

 return (
 <div>
 <h1>Image</h1>
 <input type="file" accept="'image/*'" />
 <h1>Audio</h1>
 <input type="file" accept="'audio/*'" />
 <button disabled="{loading}">
 {loading ? 'Creating Video...' : 'Create Video'}
 </button>
 {error && <p style="{{color:">{error}</p>}
 {videosrc && (
 <div>
 <h2>Generated Video:</h2>
 <video controls="controls" src="{videosrc}"></video>
 </div>
 )}
 </div>
 );
}

export default App;


Version which I am using is : "@ffmpeg/ffmpeg" : "^0.12.7",
"@ffmpeg/util" : "^0.12.1",
"@ffmpeg/core" : "^0.12.3",


Is it issue with the version / Blob URL ? How can I run ffmpeg in my system ?


-
arm : Load mb_y properly in mbtree_propagate_list_internal_neon
26 décembre 2016, par Martin Storsjö
Syndiquer tout le site
