Recherche avancée

Médias (91)

Autres articles (67)

  • Installation en mode ferme

    4 février 2011, par

    Le mode ferme permet d’héberger plusieurs sites de type MediaSPIP en n’installant qu’une seule fois son noyau fonctionnel.
    C’est la méthode que nous utilisons sur cette même plateforme.
    L’utilisation en mode ferme nécessite de connaïtre un peu le mécanisme de SPIP contrairement à la version standalone qui ne nécessite pas réellement de connaissances spécifique puisque l’espace privé habituel de SPIP n’est plus utilisé.
    Dans un premier temps, vous devez avoir installé les mêmes fichiers que l’installation (...)

  • Multilang : améliorer l’interface pour les blocs multilingues

    18 février 2011, par

    Multilang 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.

  • Publier sur MédiaSpip

    13 juin 2013

    Puis-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

Sur d’autres sites (10610)

  • ffmepg always get broken video streaming from rtsp protocol [on hold]

    6 janvier 2014, par poc

    I'm trying to capture rtsp streaming from Ip Camera by the command

    ffmpeg -t 10 -i  rtsp://172.19.1.42/live.sdp  -ss 00:00:02.500  -c:v copy download.mp4

    However I always get the broken streaming, but if I used the VLC or Qucicktime to watch the RTSP streaming, it worked fine , there was no broken streaming.

    Is there any setting or options for ffmpeg can improve the streaming quality ? Thanks

    [rtsp @ 0x7f9a84017c00] Estimating duration from bitrate, this may be inaccurate
    Input #0, rtsp, from 'rtsp://172.19.1.42/live.sdp':
     Metadata:
       title           : RTSP server
     Duration: N/A, start: 0.000000, bitrate: N/A
       Stream #0:0: Video: h264 (Main), yuv420p, 2048x1536, 13.33 tbr, 90k tbn, 180k tbc
    -t is not an input option, keeping it for the next output; consider fixing your command line.
    Output #0, mp4, to 'c0_s1_h264_1920x1536_10_cbr_500_6000000_imagequality.mp4':
     Metadata:
       title           : RTSP server
       encoder         : Lavf54.63.104
       Stream #0:0: Video: h264 ([33][0][0][0] / 0x0021), yuv420p, 2048x1536, q=2-31, 90k tbn, 90k tbc
    Stream mapping:
     Stream #0:0 -> #0:0 (copy)
    Press [q] to stop, [?] for help
    [NULL @ 0x7f9a83805200] RTP: missed 3 packets
       Last message repeated 1 times
    RTP: missed 3 packets=-1.0 size=     521kB time=00:00:00.80 bitrate=5303.8kbits/s
    [NULL @ 0x7f9a83805200] RTP: missed 3 packets
    RTP: missed 3 packets=-1.0 size=     895kB time=00:00:01.40 bitrate=5224.0kbits/s
    [NULL @ 0x7f9a83805200] RTP: missed 3 packets
    RTP: missed 3 packets=-1.0 size=    1271kB time=00:00:02.00 bitrate=5192.3kbits/s
    [NULL @ 0x7f9a83805200] RTP: missed 3 packets
    RTP: missed 3 packets=-1.0 size=    1646kB time=00:00:02.60 bitrate=5175.1kbits/s
    RTP: missed 2 packets=-1.0 size=    2029kB time=00:00:03.20 bitrate=5183.5kbits/s
    RTP: missed 3 packets=-1.0 size=    2420kB time=00:00:03.80 bitrate=5207.3kbits/s
    RTP: missed 2 packets=-1.0 size=    2801kB time=00:00:04.40 bitrate=5206.0kbits/s
    [NULL @ 0x7f9a83805200] RTP: missed 3 packets
    RTP: missed 2 packets=-1.0 size=    3180kB time=00:00:05.00 bitrate=5201.6kbits/s
    [NULL @ 0x7f9a83805200] RTP: missed 3 packets
    RTP: missed 3 packets=-1.0 size=    4708kB time=00:00:07.41 bitrate=5204.6kbits/s
    RTP: missed 2 packets=-1.0 size=    5088kB time=00:00:08.01 bitrate=5202.7kbits/s
    RTP: missed 2 packets=-1.0 size=    5857kB time=00:00:09.21 bitrate=5207.3kbits/s
    [NULL @ 0x7f9a83805200] RTP: missed 2 packets
    frame=  100 fps= 10 q=-1.0 Lsize=    6382kB time=00:00:09.96 bitrate=5246.4kbits/s
  • I need to create a streaming app Where videos store in aws S3

    27 juillet 2023, par abuzar zaidi

    I need to create a video streaming app. where my videos will store in S3 and the video will stream from the backend. Right now I am trying to use ffmpeg in the backend but it does not work properly.

    


    what am I doing wrong in this code ? And if ffmpeg not support streaming video that store in aws s3 please suggest other options.

    


    Backend

    


    const express = require('express');
const aws = require('aws-sdk');
const ffmpeg = require('fluent-ffmpeg');
const cors = require('cors'); 
const app = express();

//   Set up AWS credentials
aws.config.update({
accessKeyId: '#######################',
secretAccessKey: '###############',
region: '###############3',
});

const s3 = new aws.S3();
app.use(cors());

app.get('/stream', (req, res) => {
const bucketName = '#######';
const key = '##############'; // Replace with the key/path of the video file in the S3 bucket
const params = { Bucket: bucketName, Key: key };
const videoStream = s3.getObject(params).createReadStream();

// Transcode to HLS format
 const hlsStream = ffmpeg(videoStream)
.format('hls')
.outputOptions([
  '-hls_time 10',
  '-hls_list_size 0',
  '-hls_segment_filename segments/segment%d.ts',
 ])
.pipe(res);

// Transcode to DASH format and pipe the output to the response
ffmpeg(videoStream)
.format('dash')
.outputOptions([
  '-init_seg_name init-stream$RepresentationID$.mp4',
  '-media_seg_name chunk-stream$RepresentationID$-$Number%05d$.mp4',
 ])
.output(res)
.run();
});

const port = 5000;
app.listen(port, () => {
console.log(`Server running on http://localhost:${port}`);
});


    


    Frontend

    


        import React from &#x27;react&#x27;;&#xA;&#xA;    const App = () => {&#xA;     const videoUrl = &#x27;http://localhost:3000/api/playlist/runPlaylist/6c3e7af45a3b8a5caf2fef17a42ef9a0&#x27;; //          Replace with your backend URL&#xA;Please list down solution or option i can use here&#xA;    const videoUrl = &#x27;http://localhost:5000/stream&#x27;;&#xA;         return (&#xA;      <div>&#xA;      <h1>Video Streaming Example</h1>&#xA;      <video controls="controls">&#xA;        <source src="{videoUrl}" type="video/mp4"></source>&#xA;        Your browser does not support the video tag.&#xA;      </video>&#xA;    </div>&#xA;     );&#xA;     };&#xA;&#xA;    export default App;&#xA;

    &#xA;

  • nginx video mp4 streaming - jwplayer seeking

    18 juin 2012, par abrahab

    As you can see nginx streaming solution works and return different content-length when flv requested with start parameter :
    http://www.hotgirlscompany.com/1.flv?start=0
    http://www.hotgirlscompany.com/1.flv?start=300000

    But the problem that jwplayer v5 can not seek this video to any position. Seems (from http sniffer) player request ?start=0 and then ignore any mouse clicks at loading line, and can not go to position I want).

    Of course, I added provider=http to flashVars.
    You can download the video and see that its converted as H.264/AAC. Then maked mp4box -inter 500 1.flv. But still can not steam it :(

    Any suggestions ?
    Maybe example how to property reconvert this video with ffmpeg to make it playable ?