Recherche avancée

Médias (1)

Mot : - Tags -/musée

Autres articles (28)

  • 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

  • Contribute to a better visual interface

    13 avril 2011

    MediaSPIP is based on a system of themes and templates. Templates define the placement of information on the page, and can be adapted to a wide range of uses. Themes define the overall graphic appearance of the site.
    Anyone can submit a new graphic theme or template and make it available to the MediaSPIP community.

  • Des sites réalisés avec MediaSPIP

    2 mai 2011, par

    Cette page présente quelques-uns des sites fonctionnant sous MediaSPIP.
    Vous pouvez bien entendu ajouter le votre grâce au formulaire en bas de page.

Sur d’autres sites (4917)

  • Video stream played too fast if HTTP Live Stream starts at the beginning

    22 avril 2013, par monkeymad2

    Bit of an odd problem this, I'm building a server that Transcodes video and streams it to the WiiU.

    The WiiU seems to have quite good support of HTTP Live Streams, but I'm running into a problem where the video stream will play about x3 faster than intended (the audio plays at normal rate).

    I'd figure something was up with my ffmpeg command, but if I let the stream run (so the first segment grabbed by the WiiU isn't actually the first segment) before I actually connect to it the WiiU will play the video at the normal rate !

    Here's the ffmpeg command I've been using (post-shlex breakup) :

    ['./ffmpeg', '-threads', '4', '-i', '../../Torrents/Breaking.Bad.S05E02.720p.HDTV.x264-ORENJI.mkv', '-map', '0', '-codec:v', 'libx264', '-preset', 'superfast', '-codec:a', 'aac', '-ac', '2', '-crf', '23', '-flags', '-global_header', '-strict', 'experimental', '-f', 'segment', '-segment_list', 'playlist.m3u8', '-segment_list_flags', '+live', '-segment_time', '10', 'tmp/out%03d.ts']

    And the first few lines of the .m3u8 :

    #EXTM3U
    #EXT-X-VERSION:3
    #EXT-X-MEDIA-SEQUENCE:0
    #EXT-X-ALLOWCACHE:1
    #EXT-X-TARGETDURATION:10
    #EXTINF:11.761756,
    tmp/out000.ts
    #EXTINF:8.591911,
    tmp/out001.ts
    #EXTINF:18.810467,
    tmp/out002.ts
    #EXTINF:7.841178,
    ...

    (PS, VLC + Safari can play the stream file.)

    Any ideas what's happening ?

    If it's a bug I have to work around rather than solve, any recommendations ?

    Just tested starting the stream with a dummy.ts file (knowing it wont be read as the wiiu only reads the last 3 files in live mode) it still had the speedup, implying that it's something ffmpeg is putting in the first file (and only the first file...)

  • ffmpeg for x264 core 136 lib in iOS [on hold]

    23 août 2013, par 官承翰

    I want to develop a service (written in php) to provide mobile platforms(iOS/android/..etc) or desktop PCs to stream videos.

    I have tried a lot and found.

    My iPhone4 didn't support core 136 lib based on x264...it would crash or freeze when I tried playing it.

    Here is my question :

    Can ffmpeg decode video so that iOS can play ?
    Or is there another way to solve it ?
    I am new to these things...

    Thanks in advance

  • How do I close a Node.js FFMPEG child process that is actively streaming from a live capture source ?

    1er juin 2013, par RickZ

    I'm new to Node.js and have figured out how to utilize child.spawn to launch an instance of FFMPEG that is being used to capture live video and send it over to Adobe Media Server via rtmp.

    Every example I've seen of FFMPEG being used in conjunction with Node.js has been with a time limited sample, so the child process closes once FFMPEG reaches the end of the file it is converting.

    In this case, there is no "end of file".

    If I instantiate :

       var ffmpeg = child.spawn('ffmpeg.exe', [args]);

    it creates the live feed.

    I have tried immediately shutting the child process down with a :

       setTimeout(function() {
           ffmpeg.stdin.resume();
           ffmpeg.stdin.write('insert command to echo q to close FFMPEG');
           ffmpeg.stdin.end();
       });

    However, that does not seem to work. I continue to see my rtmp feed on my test box.

    Is there any way to pass FFMPEG a shut down command via stdin in Node.js ?

    Thanks in advance !

    Rick