
Recherche avancée
Autres articles (97)
-
MediaSPIP 0.1 Beta version
25 avril 2011, parMediaSPIP 0.1 beta is the first version of MediaSPIP proclaimed as "usable".
The zip file provided here only contains the sources of MediaSPIP in its standalone version.
To get a working installation, you must manually install all-software dependencies on the server.
If you want to use this archive for an installation in "farm mode", you will also need to proceed to other manual (...) -
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. -
ANNEXE : Les plugins utilisés spécifiquement pour la ferme
5 mars 2010, parLe site central/maître de la ferme a besoin d’utiliser plusieurs plugins supplémentaires vis à vis des canaux pour son bon fonctionnement. le plugin Gestion de la mutualisation ; le plugin inscription3 pour gérer les inscriptions et les demandes de création d’instance de mutualisation dès l’inscription des utilisateurs ; le plugin verifier qui fournit une API de vérification des champs (utilisé par inscription3) ; le plugin champs extras v2 nécessité par inscription3 (...)
Sur d’autres sites (6681)
-
Live streaming using FFMPEG to web audio api
19 janvier 2014, par NayanI am trying to stream audio using node.js + ffmpeg to browsers connected in LAN only using web audio api.
Not using element because it's adding it's own buffer of 8 to 10 secs and I want to get maximum high latency possible (around 1 to 2 sec max).
Audio plays successfully but audio is very choppy and noisy.
Here is my node.js (server side) file :
var ws = require('websocket.io'),
server = ws.listen(3000);
var child_process = require("child_process");
var i = 0;
server.on('connection', function (socket)
{
console.log('New client connected');
var ffmpeg = child_process.spawn("ffmpeg",[
"-re","-i",
"A.mp3","-f",
"f32le",
"pipe:1" // Output to STDOUT
]);
ffmpeg.stdout.on('data', function(data)
{
var buff = new Buffer(data);
socket.send(buff.toString('base64'));
});
});And here is my HTML :
var audioBuffer = null;
var context = null;
window.addEventListener('load', init, false);
function init() {
try {
context = new webkitAudioContext();
} catch(e) {
alert('Web Audio API is not supported in this browser');
}
}
var ws = new WebSocket("ws://localhost:3000/");
ws.onmessage = function(message)
{
var d1 = base64DecToArr(message.data).buffer;
var d2 = new DataView(d1);
var data = new Float32Array(d2.byteLength / Float32Array.BYTES_PER_ELEMENT);
for (var jj = 0; jj < data.length; ++jj)
{
data[jj] = d2.getFloat32(jj * Float32Array.BYTES_PER_ELEMENT, true);
}
var audioBuffer = context.createBuffer(2, data.length, 44100);
audioBuffer.getChannelData(0).set(data);
var source = context.createBufferSource(); // creates a sound source
source.buffer = audioBuffer;
source.connect(context.destination); // connect the source to the context's destination (the speakers)
source.start(0);
};Can any one advise what is wrong ?
Regards,
Nayan -
JW Player can't play mp4 video downloaded from youtube
20 janvier 2015, par kheyaI have doenloaded am mp4 video using IE Realplayer plugin from youtube.
https://www.youtube.com/watch?v=e3a80c5Ar3YI have a test site on my local machine where I have HTML5 JW Player.
I download the video and then play locally using realplay to see if it plays.
I notice that not all mp4 downloads from youtube plays in Realplayer.
The ones that play in Realplayer also play in JW Player on local website.
But the mp4 files that don’t play in Realplayer also don’t play in JW player.This is the error I get in the player :
the video playback was aborted due to a corruption problem or because the video used features your browser didnot support mylocalsite/xyz.mp4 undefinedI tested IE, FF, Chrome. It works nowhere.
Here is my jw player setup and html :
<video src="mylocalsite/test.mp4" type="video/mp4" poster="mylocalsite/test.jpg" width="640" height="360"></video>
player setup :
var modes = '';
var swfPath = '/content/jw/player.swf';
if (navigator.userAgent.toLowerCase().match(/(android)/) || navigator.userAgent.toLowerCase().match(/(chrom)/)) {
modes = [{ type: 'flash', src: swfPath }, { type: "html5"}];
} else {
modes = [{ type: 'html5' }, { type: 'flash', src: swfPath }, { type: "download"}];
}
jwplayer('container').setup({
'flashplayer': swfPath,
'width': '640',
'height': '360',
'provider': 'video',
'modes': modes,
});Here is the details info about the file returned by ffmpeg :
ffmpeg version 1.1.4 Copyright (c) 2000-2013 the FFmpeg developers
built on Jul 31 2013 02:49:36 with gcc 4.6.2 (GCC)
configuration: --prefix=/c/Users/Administrator/ffmpeg --extra-cflags=-I/c/User
s/Administrator/ffmpeg/include --extra-ldflags=-L/c/Users/Administrator/ffmpeg/l
ib --cpu=i686 --enable-gpl --enable-libfdk-aac --enable-libx264 --enable-nonfree
libavutil 52. 13.100 / 52. 13.100
libavcodec 54. 86.100 / 54. 86.100
libavformat 54. 59.106 / 54. 59.106
libavdevice 54. 3.102 / 54. 3.102
libavfilter 3. 32.100 / 3. 32.100
libswscale 2. 1.103 / 2. 1.103
libswresample 0. 17.102 / 0. 17.102
libpostproc 52. 2.100 / 52. 2.100
Input #0, mov,mp4,m4a,3gp,3g2,mj2, from 'C:\videos\woh.mp4':
Metadata:
major_brand : dash
minor_version : 0
compatible_brands: iso6avc1mp41
creation_time : 2013-09-08 23:34:28
Duration: 00:03:50.96, start: 0.000000, bitrate: 189 kb/s
Stream #0:0(und): Video: h264 (Main) (avc1 / 0x31637661), yuv420p, 480x360,
187 kb/s, 25 tbr, 90k tbn, 50 tbc
Metadata:
creation_time : 2013-09-08 23:34:28
handler_name : VideoHandlerWhat can be causing this issue ?
-
Video created via ffmpeg will not play on iPhone 10 or Huawei Android using Chrome
17 février 2020, par MHattonI have created a video from a image and adding an MP3 file. It plays fine on my Moto G Android phone and on my desktop, but a collegue has said it will not play on his iPhone 10 or Huawei Android phone running Chrome.
Does the following ffmpeg need an extra command adding to make the created MP4 more compatible across devices ?
ffmpeg -loop 1 -i 6f4aa5dfefc4dd32186f41315ad9d1e2-0.png -i "download.mp3" -c:v libx264 -tune stillimage -c:a aac -b:a 192k -pix_fmt yuv420p -shortest aw-slide0.mp4