
Recherche avancée
Médias (1)
-
The Great Big Beautiful Tomorrow
28 octobre 2011, par
Mis à jour : Octobre 2011
Langue : English
Type : Texte
Autres articles (36)
-
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 -
Ajouter notes et légendes aux images
7 février 2011, parPour pouvoir ajouter notes et légendes aux images, la première étape est d’installer le plugin "Légendes".
Une fois le plugin activé, vous pouvez le configurer dans l’espace de configuration afin de modifier les droits de création / modification et de suppression des notes. Par défaut seuls les administrateurs du site peuvent ajouter des notes aux images.
Modification lors de l’ajout d’un média
Lors de l’ajout d’un média de type "image" un nouveau bouton apparait au dessus de la prévisualisation (...) -
Contribute to translation
13 avril 2011You can help us to improve the language used in the software interface to make MediaSPIP more accessible and user-friendly. You can also translate the interface into any language that allows it to spread to new linguistic communities.
To do this, we use the translation interface of SPIP where the all the language modules of MediaSPIP are available. Just subscribe to the mailing list and request further informantion on translation.
MediaSPIP is currently available in French and English (...)
Sur d’autres sites (4603)
-
Thumbnails from S3 Videos using FFMPEG - "No such file or directory : '/bin/ffmpeg'"
28 juin 2022, par NicoI am trying to generate thumbnails from videos in an S3 bucket every x frames by following this documentation : https://aws.amazon.com/blogs/media/processing-user-generated-content-using-aws-lambda-and-ffmpeg/


I am at the point where I'm testing the Lambda code provided in the documentation, but receive this error in CloudWatch Logs :




Here is the portion of the Lambda code associated with this error :




Any help is appreciated. Thanks !


-
FFMPEG streams from Docker container application are not playing on other computers
25 janvier, par tipitoeI'm building a docker container app using dotnet core that captures and plays audio streams using ffmpeg.


Since some of the URLs cannot be played directly in a web browser, audio needs to be processed by ffmpeg first. The ffmpeg output is a local url http://127.0.0.1:8080 that is sent back to a browser in an Ajax call.


The audio plays perfectly in Visual Studio during development. I understand, since URL refers to localhost, there is no issue playing the audio. Unfortunately, with application being installed as docker container, the audio is being blocked. Initially, my guess was it was CORS that was blocking the stream. Also I considered the possibility that I have to use LAN IP address of the machine hosting docker container. This did not solve the problem
either.


Here is my code so far in Startup.cs


services.AddCors(options => options.AddPolicy("AllowAll",
 builder => builder.AllowAnyOrigin().AllowAnyHeader().AllowAnyMethod()));

 app.UseCors("AllowAll");
 app.UseRouting();



Here is an Ajax call


$.ajax({
 type: 'POST',
 url: '/live?handler=PlayStream',
 beforeSend: function (xhr) {
 xhr.setRequestHeader('XSRF-TOKEN',
 $('input:hidden[name="__RequestVerificationToken"]').val());
 },
 dataType: 'json',
 data: { 'streamId': streamId },
 success: function (data) {

 var json = JSON.parse(data);

 source = new Audio(json.InputUri);
 source.play();
 


 },
 failure: function (response) {

 alert(response.responseText);
 },
 error: function (response) {

 alert(response.responseText);
 }



}) ;


I would appreciate any suggestions how to solve this problem. Thanks


-
How to stream video from Node.js
7 mai 2014, par Sunrisingi am trying to request a video stored on server and receive a stream of data to show in a html tag
From the client i request the streaming of a particular file i know exists in my server
Then in node i use this :
function streamvideo(response, request) {
// here i simply read from the response the path and the name of the file i want
var queryparts = url.parse(request.url, true).query;
var path = queryparts.query;
var path = 'tmp/' + path
, stat = fs.statSync(path)
, total = stat.size;
var origin = (request.headers.origin || "*");
// still not sure it is correct to manage range this way but it works
// if i request a range....
if (request.headers['range']) {
var range = request.headers.range
, parts = range.replace(/bytes=/, "").split("-")
, partialstart = parts[0]
, partialend = parts[1]
, start = parseInt(partialstart, 10)
, end = partialend ? parseInt(partialend, 10) : total - 1
, chunksize = (end - start) + 1;
console.log('RANGE: ' + start + ' - ' + end + ' = ' + chunksize + "\n")
response.writeHead(
206
, {
'Access-Control-Allow-Credentials': true,
'Access-Control-Allow-Origin': origin,
'Content-Range': 'bytes ' + start + '-' + end + '/' + total,
'Accept-Ranges': 'bytes',
'Content-Length': chunksize,
'Content-Type': 'video/mp4'
});
} else {
// if i request all the video
console.log('ALL: ' + total);
response.writeHead(
200,
{
'Access-Control-Allow-Credentials': true,
'Access-Control-Allow-Origin': origin,
'Content-Length': total,
'Content-Type': 'video/mp4'
}
);
}
// on-the-fly encoding
var ffmpeg = child_process.spawn("ffmpeg",[
"-i", path, // path
"-b:v" , "64k", // bitrate to 64k
"-bufsize", "64k",
"pipe:1" // Output to STDOUT
]);
//pack-up everything and send back the response with the stream
var file = fs.createReadStream(path);
file.pipe(response);it may be not the best code ever but it works because i receive on the client a stream of something !
BUT how can i verify this ? how can i actually ’see’ the video in the page ?now in the client page i have a tag like this :
<div>
<video class="mejs-wmp" width="320" height="240" src="test.mp4" type="video/mp4" controls="controls" preload="none"></video>
</div>but i can only see a black screen in my player...
Why ?
Thanks !
(feel free to correct any imprecision you see)