Recherche avancée

Médias (1)

Mot : - Tags -/blender

Autres articles (40)

  • Les autorisations surchargées par les plugins

    27 avril 2010, par

    Mediaspip core
    autoriser_auteur_modifier() afin que les visiteurs soient capables de modifier leurs informations sur la page d’auteurs

  • HTML5 audio and video support

    13 avril 2011, par

    MediaSPIP uses HTML5 video and audio tags to play multimedia files, taking advantage of the latest W3C innovations supported by modern browsers.
    The MediaSPIP player used has been created specifically for MediaSPIP and can be easily adapted to fit in with a specific theme.
    For older browsers the Flowplayer flash fallback is used.
    MediaSPIP allows for media playback on major mobile platforms with the above (...)

  • Support audio et vidéo HTML5

    10 avril 2011

    MediaSPIP utilise les balises HTML5 video et audio pour la lecture de documents multimedia en profitant des dernières innovations du W3C supportées par les navigateurs modernes.
    Pour les navigateurs plus anciens, le lecteur flash Flowplayer est utilisé.
    Le lecteur HTML5 utilisé a été spécifiquement créé pour MediaSPIP : il est complètement modifiable graphiquement pour correspondre à un thème choisi.
    Ces technologies permettent de distribuer vidéo et son à la fois sur des ordinateurs conventionnels (...)

Sur d’autres sites (7504)

  • Save and re-stream RSTP video as straight UDP

    30 septembre 2013, par user1701362

    I am trying to write a program that will connect to a RTSP video source and redirect the video data to another location using UDP. I am also saving the RTSP packets to be able to replay the video stream at a latter moment in time as well. Right now my program can connect to the RTSP video stream and redirect and save, but when I try to look at the redirected video I get nothing using VLC.

    Currently the program just strips out the datagram from the RTSP video packets it receives in its open UDP socket and re-sends them using this code using the boost asio library.

    newVideoSocket->send_to(&dg.data[0], dg.data.size() ,Endpoint);

    When I look at the traffic using Wireshark I see that it is actually sending the data to the new address and it is recognized as a UDP packet, but when I try and view the video using VLC nothing happens. The video stream is Mpeg4 with the video encoded as H.264 and VLC can play it.

    I have tried to connect to the redirected stream as UDP and as RTP at both multicast and unicast addresses but have had no success. Do I need to add or take something out of the datagram before I resend it ? Or is it something wrong with how I am tring to view it in VLC ? Thanks for the help.

  • iFrameExtractor EXC_BAD_ACCESS

    3 novembre 2013, par Destiny Dawn

    When using the iFrameExtractor for iOS I have been getting the "EXC_BAD_ACCESS(code=1,address=0x8) error on this line :

    - (AVPacket*)readPacket {

       if (_currentPacket.size > 0 || _inBuffer) return &_currentPacket;

       NSMutableData *packetData = [audioPacketQueue objectAtIndex:0];
       _packet = [packetData mutableBytes];

       // NSLog(@"got audio stream");
       **if (_packet->dts != AV_NOPTS_VALUE) {**
           _packet->dts += av_rescale_q(0, AV_TIME_BASE_Q, _audioStream->time_base);
       }
       if (_packet->pts != AV_NOPTS_VALUE) {
           _packet->pts += av_rescale_q(0, AV_TIME_BASE_Q, _audioStream->time_base);
       }
       // NSLog(@"ready with audio");


       [audioPacketQueueLock lock];
       audioPacketQueueSize -= _packet->size;
       [audioPacketQueue removeObjectAtIndex:0];
       [audioPacketQueueLock unlock];



       _currentPacket = *(_packet);

       return &_currentPacket;  
    }
  • Realtime video conversion using nodejs and ffmpeg

    2 février 2015, par LadislavM

    I’m trying to create very simple server-side video conversion using ffmpeg and nodejs.
    So far, I have 2 UDP servers, one for converting video input and second one for listening for converted video and passing it to websocket.

    I’ve created one UDP server, where stream comes, converts the video input by calling ffmpeg. Then the second UDP server get the converted video and pass it to the websocket server to stream video to browser.

    The problem is probably with input into the ffmpeg. The error I get is

    _stream_readable.js:476
     dest.on('unpipe', onunpipe);
          ^
    TypeError: Object

    The code looks like this :

    // Websocket Server
    var socketServer = new (require('ws').Server)({port: 8081});
    socketServer.on('connection', function(socket) {
       socket.on('close', function(code, message){
           console.log( 'Disconnected WebSocket ('+socketServer.clients.length+' total)' );
       });
    });

    socketServer.broadcast = function(data, opts) {
       for( var i in this.clients ) {
           this.clients[i].send(data, opts);
       }
    };

    // UDP Server
    var udpServer = require("dgram").createSocket("udp4");

    udpServer.on("message", function(msg, rinfo) {
       socketServer.broadcast(msg, {binary:true});
       console.log("server got: " + msg + " from " + rinfo.address + ":" + rinfo.port);
    });

    udpServer.on("listening", function() {
       var address = udpServer.address();
       console.log("server listening " + address.address + ":" + address.port);
    });
    udpServer.bind(8082);

    // UDP Server for stream conversion
    var udpServer2 = require("dgram").createSocket("udp4");

    udpServer2.on("message", function(msg, rinfo) {
       // **********  THIS IS WHERE ERROR OCCURS **************
       var ffmpeg = require('child_process')
               .spawn('ffmpeg',['-f','video4linux2','-i','-','-f','mpeg1video','udp://127.0.0.1:8082']);
       ffmpeg.stdin.pipe(msg);
    });

    udpServer2.on("listening", function() {
       var address = udpServer2.address();
       console.log("server listening " + address.address + ":" + address.port);
    });
    udpServer2.bind(8083);